Usb is read-only, Write Protect is on/off - I can't write again on pendrive

English Install/Boot/Login
1

Hello,

I have something similar to this post., but my pendrive doesn’t have any button or special plastic in order to protect the content.

When I plug the usb, the /var/log/messages shows:

2024-09-16T14:35:05.557862-03:00 localhost kernel: [ 95.358891][ T422] usb 8-2: new high-speed USB device number 2 using ehci-pci
2024-09-16T14:35:05.733836-03:00 localhost kernel: [ 95.534892][ T422] usb 8-2: New USB device found, idVendor=058f, idProduct=6387, bcdDevice= 1.04
2024-09-16T14:35:05.733855-03:00 localhost kernel: [ 95.534902][ T422] usb 8-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2024-09-16T14:35:05.733858-03:00 localhost kernel: [ 95.534905][ T422] usb 8-2: Product: Mass Storage
2024-09-16T14:35:05.733860-03:00 localhost kernel: [ 95.534908][ T422] usb 8-2: Manufacturer: Generic
2024-09-16T14:35:05.733861-03:00 localhost kernel: [ 95.534910][ T422] usb 8-2: SerialNumber: C927AB09
2024-09-16T14:35:05.740575-03:00 localhost mtp-probe: checking bus 8, device 2: “/sys/devices/pci0000:00/0000:00:1d.7/usb8/8-2”
2024-09-16T14:35:05.740688-03:00 localhost mtp-probe: bus: 8, device: 2 was not an MTP device
2024-09-16T14:35:05.753741-03:00 localhost kernel: [ 95.557981][ T3087] usb-storage 8-2:1.0: USB Mass Storage device detected
2024-09-16T14:35:05.753756-03:00 localhost kernel: [ 95.558108][ T3087] scsi host6: usb-storage 8-2:1.0
2024-09-16T14:35:05.753758-03:00 localhost kernel: [ 95.558180][ T3087] usbcore: registered new interface driver usb-storage
2024-09-16T14:35:05.757737-03:00 localhost kernel: [ 95.561634][ T3087] usbcore: registered new interface driver uas
2024-09-16T14:35:05.762910-03:00 localhost mtp-probe: checking bus 8, device 2: “/sys/devices/pci0000:00/0000:00:1d.7/usb8/8-2”
2024-09-16T14:35:05.763008-03:00 localhost mtp-probe: bus: 8, device: 2 was not an MTP device
2024-09-16T14:35:06.785746-03:00 localhost kernel: [ 96.589201][ T64] scsi 6:0:0:0: Direct-Access Generic Flash Disk 8.07 PQ: 0 ANSI: 4
2024-09-16T14:35:06.785764-03:00 localhost kernel: [ 96.589595][ T64] sd 6:0:0:0: Attached scsi generic sg2 type 0
2024-09-16T14:35:06.789742-03:00 localhost kernel: [ 96.590970][ T67] sd 6:0:0:0: [sdc] 15974400 512-byte logical blocks: (8.18 GB/7.62 GiB)
2024-09-16T14:35:06.789759-03:00 localhost kernel: [ 96.592077][ T67] sd 6:0:0:0: [sdc] Write Protect is off
2024-09-16T14:35:06.789761-03:00 localhost kernel: [ 96.592082][ T67] sd 6:0:0:0: [sdc] Mode Sense: 23 00 00 00
2024-09-16T14:35:06.789762-03:00 localhost kernel: [ 96.593196][ T67] sd 6:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn’t support DPO or FUA
2024-09-16T14:35:06.801743-03:00 localhost kernel: [ 96.605030][ T67] sdc:
2024-09-16T14:35:06.801758-03:00 localhost kernel: [ 96.605217][ T67] sd 6:0:0:0: [sdc] Attached SCSI removable disk

The usb pendrive doesn’t have restriction readonly, because in the log appear:
“sd 6:0:0:0: [sdc] Write Protect is off”

But, when I try “fdisk /dev/sdc”, I get:

2024-09-16T14:38:17.205835-03:00 localhost kernel: [ 287.010542][ T3091] sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
2024-09-16T14:38:17.205858-03:00 localhost kernel: [ 287.010552][ T3091] sd 6:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current]
2024-09-16T14:38:17.205860-03:00 localhost kernel: [ 287.010558][ T3091] sd 6:0:0:0: [sdc] tag#0 <>ASC=0xff <>ASCQ=0xff
2024-09-16T14:38:17.205861-03:00 localhost kernel: [ 287.010562][ T3091] sd 6:0:0:0: [sdc] tag#0 CDB: Write(10) 2a 00 00 00 00 00 00 00 08 00
2024-09-16T14:38:17.205867-03:00 localhost kernel: [ 287.010565][ T3091] I/O error, dev sdc, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
2024-09-16T14:38:17.205870-03:00 localhost kernel: [ 287.010580][ T3091] Buffer I/O error on dev sdc, logical block 0, lost async page write
2024-09-16T14:38:17.209808-03:00 localhost kernel: [ 287.011849][ T3091] sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
2024-09-16T14:38:17.209816-03:00 localhost kernel: [ 287.011856][ T3091] sd 6:0:0:0: [sdc] tag#0 Sense Key : Data Protect [current]
2024-09-16T14:38:17.209820-03:00 localhost kernel: [ 287.011860][ T3091] sd 6:0:0:0: [sdc] tag#0 Add. Sense: Write protected
2024-09-16T14:38:17.209821-03:00 localhost kernel: [ 287.011863][ T3091] sd 6:0:0:0: [sdc] tag#0 CDB: Write(10) 2a 00 00 00 00 00 00 00 08 00
2024-09-16T14:38:17.209823-03:00 localhost kernel: [ 287.011865][ T3091] critical target error, dev sdc, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
2024-09-16T14:38:17.209824-03:00 localhost kernel: [ 287.011878][ T3091] Buffer I/O error on dev sdc, logical block 0, lost async page write
2024-09-16T14:38:17.209826-03:00 localhost kernel: [ 287.012842][ T3091] sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
2024-09-16T14:38:17.209831-03:00 localhost kernel: [ 287.012847][ T3091] sd 6:0:0:0: [sdc] tag#0 Sense Key : Data Protect [current]
2024-09-16T14:38:17.209833-03:00 localhost kernel: [ 287.012850][ T3091] sd 6:0:0:0: [sdc] tag#0 Add. Sense: Write protected
2024-09-16T14:38:17.209834-03:00 localhost kernel: [ 287.012853][ T3091] sd 6:0:0:0: [sdc] tag#0 CDB: Write(10) 2a 00 00 00 00 00 00 00 08 00
2024-09-16T14:38:17.209835-03:00 localhost kernel: [ 287.012855][ T3091] critical target error, dev sdc, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
2024-09-16T14:38:17.209836-03:00 localhost kernel: [ 287.012865][ T3091] Buffer I/O error on dev sdc, logical block 0, lost async page write
2024-09-16T14:38:17.297751-03:00 localhost kernel: [ 287.101623][ T550] sd 6:0:0:0: [sdc] Write Protect is on
2024-09-16T14:38:17.297769-03:00 localhost kernel: [ 287.101632][ T550] sd 6:0:0:0: [sdc] Mode Sense: 23 00 80 00
2024-09-16T14:38:17.301752-03:00 localhost kernel: [ 287.103733][ T550] sdc: sdc1 sdc2 sdc3

And I get “[sdc] Write Protect is on”. Then, I can’t format or write to pendrive.

This pendrive shows files and directories relatives to EFI partition:

localhost:/home/user # fdisk -l /dev/sdc
Disk /dev/sdc: 7.62 GiB, 8178892800 bytes, 15974400 sectors
Disk model: Flash Disk
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x7c782b0b

Device Boot Start End Sectors Size Id Type
/dev/sdc1 276 8087 7812 3.8M ef EFI (FAT-12/16/32)
/dev/sdc2 * 8088 255999 247912 121.1M 17 Hidden HPFS/NTFS
/dev/sdc3 256000 15974399 15718400 7.5G c W95 FAT32 (LBA)

How can I recover my pendrive, in order to install new data on it?

Others pendrives works fine.

In Windows 11 I have the same message: It is a read only.

I read this post, and it works until when I write on pendrive, the system auto protect and denied I write on it.

sudo modprobe -r $(lsmod | sed -n 's:,: :g ; s,^usb_storage[ 0-9]*,,p') usb_storage

I can specify my hardware: 058f:6387, but I can’t continue and the pendrive is readonly again.

modprobe usb_storage quirks=058f:6387:w

Regards!

2

@sucrmmc I’m assuming there is nothing on the device your need?

If so, make sure none of the partitions are mounted?

Assuming it’s as your output, /dev/sdc? If so as root user, check and unmount the partitions and wipe…

lsblk
umount /dev/sdc3
umount /dev/sdc2
umount /dev/sdc1

wipefs -a /dev/sdc3
wipefs -a /dev/sdc2
wipefs -a /dev/sdc1
wipefs -a /dev/sdc

Then use gdisk /dev/sdc to create a new partition.

3

Hi Malcolmlewis!

I try this:

localhost:/home/ # grep sdc /var/log/messages
2024-09-16T22:19:45.748152-03:00 localhost kernel: [ 143.515771][ T66] sd 6:0:0:0: [sdc] 15974400 512-byte logical blocks: (8.18 GB/7.62 GiB)
2024-09-16T22:19:45.748163-03:00 localhost kernel: [ 143.516886][ T66] sd 6:0:0:0: [sdc] Write Protect is off
2024-09-16T22:19:45.748165-03:00 localhost kernel: [ 143.516890][ T66] sd 6:0:0:0: [sdc] Mode Sense: 23 00 00 00
2024-09-16T22:19:45.748166-03:00 localhost kernel: [ 143.517883][ T66] sd 6:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn’t support DPO or FUA
2024-09-16T22:19:45.760025-03:00 localhost kernel: [ 143.529695][ T66] sdc:
2024-09-16T22:19:45.760036-03:00 localhost kernel: [ 143.529910][ T66] sd 6:0:0:0: [sdc] Attached SCSI removable disk
localhost:/home/ # lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 953.9G 0 disk
├─sda1 8:1 0 353.9G 0 part
…
└─sda7 8:7 0 157G 0 part
sdb 8:16 0 223.6G 0 disk
├─sdb1 8:17 0 8M 0 part
…
└─sdb10 8:26 0 504M 0 part /[deleted]
sdc 8:32 1 7.6G 0 disk
localhost:/home/ # wipefs -a /dev/sdc
/dev/sdc: 8 bytes were erased at offset 0x00000052 (vfat): 46 41 54 33 32 20 20 20
/dev/sdc: 1 byte was erased at offset 0x00000000 (vfat): eb
/dev/sdc: 2 bytes were erased at offset 0x000001fe (vfat): 55 aa
localhost:/home/ # date
lun 16 sep 2024 22:22:09 -03
localhost:/home/# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 953.9G 0 disk
├─sda1 8:1 0 353.9G 0 part
…
└─sda7 8:7 0 157G 0 part
sdb 8:16 0 223.6G 0 disk
├─sdb1 8:17 0 8M 0 part
…
└─sdb10 8:26 0 504M 0 part /copywinlinux
sdc 8:32 1 7.6G 1 disk
├─sdc1 8:33 1 3.8M 1 part
├─sdc2 8:34 1 121.1M 1 part
└─sdc3 8:35 1 7.5G 1 part
localhost:/home/ # umount /dev/sdc3
umount: /dev/sdc3: not mounted.
localhost:/home/ # umount /dev/sdc2
umount: /dev/sdc2: not mounted.
localhost:/home/ # umount /dev/sdc1
umount: /dev/sdc1: not mounted.
localhost:/home/ # wipefs -a /dev/sdc3
wipefs: error: /dev/sdc3: probing initialization failed: Read-only file system
localhost:/home/ # wipefs -a /dev/sdc2
wipefs: error: /dev/sdc2: probing initialization failed: Read-only file system
localhost:/home/ # wipefs -a /dev/sdc1
wipefs: error: /dev/sdc1: probing initialization failed: Read-only file system
localhost:/home/ # wipefs -a /dev/sdc
wipefs: error: /dev/sdc: probing initialization failed: Read-only file system
localhost:/home/ # grep sdc /var/log/messages |tail -30
2024-09-16T19:44:25.960080-03:00 localhost kernel: [ 1256.882170][ T4272] sd 6:0:0:0: [sdc] Write Protect is on
2024-09-16T19:44:25.960094-03:00 localhost kernel: [ 1256.882176][ T4272] sd 6:0:0:0: [sdc] Mode Sense: 23 00 80 00
2024-09-16T19:44:25.964074-03:00 localhost kernel: [ 1256.887713][ T4275] sdc: sdc1 sdc2 sdc3
2024-09-16T22:19:45.748152-03:00 localhost kernel: [ 143.515771][ T66] sd 6:0:0:0: [sdc] 15974400 512-byte logical blocks: (8.18 GB/7.62 GiB)
2024-09-16T22:19:45.748163-03:00 localhost kernel: [ 143.516886][ T66] sd 6:0:0:0: [sdc] Write Protect is off
2024-09-16T22:19:45.748165-03:00 localhost kernel: [ 143.516890][ T66] sd 6:0:0:0: [sdc] Mode Sense: 23 00 00 00
2024-09-16T22:19:45.748166-03:00 localhost kernel: [ 143.517883][ T66] sd 6:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn’t support DPO or FUA
2024-09-16T22:19:45.760025-03:00 localhost kernel: [ 143.529695][ T66] sdc:
2024-09-16T22:19:45.760036-03:00 localhost kernel: [ 143.529910][ T66] sd 6:0:0:0: [sdc] Attached SCSI removable disk
2024-09-16T22:21:51.220027-03:00 localhost kernel: [ 268.988971][ T2858] sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
2024-09-16T22:21:51.220042-03:00 localhost kernel: [ 268.988977][ T2858] sd 6:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current]
2024-09-16T22:21:51.220043-03:00 localhost kernel: [ 268.988981][ T2858] sd 6:0:0:0: [sdc] tag#0 <>ASC=0xff <>ASCQ=0xff
2024-09-16T22:21:51.220044-03:00 localhost kernel: [ 268.988984][ T2858] sd 6:0:0:0: [sdc] tag#0 CDB: Write(10) 2a 00 00 00 00 00 00 00 08 00
2024-09-16T22:21:51.220049-03:00 localhost kernel: [ 268.988986][ T2858] I/O error, dev sdc, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
2024-09-16T22:21:51.220050-03:00 localhost kernel: [ 268.988996][ T2858] Buffer I/O error on dev sdc, logical block 0, lost async page write
2024-09-16T22:21:51.220051-03:00 localhost kernel: [ 268.990461][ T2858] sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
2024-09-16T22:21:51.220052-03:00 localhost kernel: [ 268.990466][ T2858] sd 6:0:0:0: [sdc] tag#0 Sense Key : Data Protect [current]
2024-09-16T22:21:51.220052-03:00 localhost kernel: [ 268.990468][ T2858] sd 6:0:0:0: [sdc] tag#0 Add. Sense: Write protected
2024-09-16T22:21:51.220053-03:00 localhost kernel: [ 268.990471][ T2858] sd 6:0:0:0: [sdc] tag#0 CDB: Write(10) 2a 00 00 00 00 00 00 00 08 00
2024-09-16T22:21:51.220054-03:00 localhost kernel: [ 268.990472][ T2858] critical target error, dev sdc, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
2024-09-16T22:21:51.220054-03:00 localhost kernel: [ 268.990480][ T2858] Buffer I/O error on dev sdc, logical block 0, lost async page write
2024-09-16T22:21:51.224239-03:00 localhost kernel: [ 268.991464][ T2858] sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
2024-09-16T22:21:51.224251-03:00 localhost kernel: [ 268.991468][ T2858] sd 6:0:0:0: [sdc] tag#0 Sense Key : Data Protect [current]
2024-09-16T22:21:51.224254-03:00 localhost kernel: [ 268.991470][ T2858] sd 6:0:0:0: [sdc] tag#0 Add. Sense: Write protected
2024-09-16T22:21:51.224255-03:00 localhost kernel: [ 268.991473][ T2858] sd 6:0:0:0: [sdc] tag#0 CDB: Write(10) 2a 00 00 00 00 00 00 00 08 00
2024-09-16T22:21:51.224256-03:00 localhost kernel: [ 268.991474][ T2858] critical target error, dev sdc, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
2024-09-16T22:21:51.224257-03:00 localhost kernel: [ 268.991482][ T2858] Buffer I/O error on dev sdc, logical block 0, lost async page write
2024-09-16T22:21:51.312169-03:00 localhost kernel: [ 269.079546][ T558] sd 6:0:0:0: [sdc] Write Protect is on
2024-09-16T22:21:51.312186-03:00 localhost kernel: [ 269.079553][ T558] sd 6:0:0:0: [sdc] Mode Sense: 23 00 80 00
2024-09-16T22:21:51.312188-03:00 localhost kernel: [ 269.081530][ T558] sdc: sdc1 sdc2 sdc3

May be the EFI system, because the size of usb first partition is 3.8MB, and the content is this (EFI option on bios is enabled):

localhost:/home/ # mount /dev/sdc1 /mnt
mount: /mnt: WARNING: source write-protected, mounted read-only.
localhost:/home/ # ls -l /mnt
total 2
drwxr-xr-x 3 root root 512 may 15 2019 EFI
-rwxr-xr-x 1 root root 118 may 15 2019 .packages.grub2-efi
drwxr-xr-x 2 root root 512 abr 8 2020 System Volume Information
localhost:/home/ # ls -l /mnt/EFI/
total 1
drwxr-xr-x 3 root root 512 may 15 2019 BOOT
localhost:/home/ # ls -l /mnt/EFI/BOOT/
total 3355
-rwxr-xr-x 1 root root 1208968 may 15 2019 bootx64.efi
-rwxr-xr-x 1 root root 2651 may 15 2019 grub.cfg
-rwxr-xr-x 1 root root 1062752 may 15 2019 grub.efi
drwxr-xr-x 2 root root 512 may 15 2019 locale
-rwxr-xr-x 1 root root 1158688 may 15 2019 MokManager.efi

And fdisk shows these:

localhost:/home/ # fdisk -l /dev/sdc
Disk /dev/sdc: 7.62 GiB, 8178892800 bytes, 15974400 sectors
Disk model: Flash Disk
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x7c782b0b

Device Boot Start End Sectors Size Id Type
/dev/sdc1 276 8087 7812 3.8M ef EFI (FAT-12/16/32)
/dev/sdc2 * 8088 255999 247912 121.1M 17 Hidden HPFS/NTFS
/dev/sdc3 256000 15974399 15718400 7.5G c W95 FAT32 (LBA)

Additional info is this:

/dev/sdc3 on /run/media/user/openSUSE-Leap-15.1-NET-x86_64470 type vfat (ro,nosuid,nodev,relatime,uid=1000,gid=100,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks2)
/dev/sdc2 on /run/media/user/openSUSE-Leap-15.1-NET-x86_644701 type iso9660 (ro,nosuid,nodev,relatime,nojoliet,check=s,map=n,blocksize=2048,uid=1000,gid=100,dmode=500,fmode=400,iocharset=utf8,uhelper=udisks2)
/dev/sdc1 on /mnt type vfat (ro,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
localhost:/home/ # ls -l /run/media/user/openSUSE-Leap-15.1-NET-x86_644701/
total 209
dr-xr-xr-x 3 user users 2048 may 14 2019 boot
-r–r–r-- 1 user users 15267 may 14 2019 CHECKSUMS
-r–r–r-- 1 user users 2048 may 14 2019 CHECKSUMS.asc
dr-xr-xr-x 2 user users 6144 may 14 2019 docu
dr-xr-xr-x 3 user users 2048 may 14 2019 EFI
-r–r–r-- 1 user users 37 may 14 2019 glump
-r–r–r-- 1 user users 615 may 14 2019 gpg-pubkey-307e3d54-5aaa90a5.asc
-r–r–r-- 1 user users 972 may 14 2019 gpg-pubkey-39db7c82-5847eb1f.asc
-r–r–r-- 1 user users 1059 may 14 2019 gpg-pubkey-3dbdc284-53674dd4.asc
-r–r–r-- 1 user users 18092 may 14 2019 GPLv2.txt
-r–r–r-- 1 user users 35147 may 14 2019 GPLv3.txt
dr-xr-xr-x 2 user users 2048 may 14 2019 media.1
-r–r–r-- 1 user users 1250 may 14 2019 README
-r–r–r-- 1 user users 99678 may 14 2019 SUSEgo.ico
-r–r–r-- 1 user users 10247 may 14 2019 SUSEgo.png
-r–r–r-- 1 user users 11612 may 14 2019 SUSEgo.svg
-r–r–r-- 1 user users 351 may 14 2019 .treeinfo
dr-xr-xr-x 2 user users 2048 may 14 2019 x86_64
localhost:/home/ # ls -l /run/media/user/openSUSE-Leap-15.1-NET-x86_64470
total 8
drwxr-xr-x 2 user users 4096 abr 28 2020 System Volume Information
drwxr-xr-x 2 user users 4096 jun 9 2020 VIDEO_TS

4

@sucrmmc Well it could have died…? Try (as root user) make sure it’s actually sdc!! hdparm -r0 /dev/sdc

5

Hi @malcolmlewis ,

If the pendrive is died, I don’t think so, because I can boot from it, and it shows the grub menu, opensuse Leap 15.1, with the options installation, boot from hard disks, and others options. Only can do the first phase: select the option, because, these code is in the first and second partition.

I try with hdparam -r0 /dev/sdc and sdc*, but in all partitions, the system shows: readonly partition.

localhost:/home/ # hdparm -v -r /dev/sdc

/dev/sdc:
multcount = 0 (off)
readonly = 0 (off)
readahead = 1024 (on)
geometry = 1022/252/62, sectors = 15974400, start = 0
localhost:/home/ # hdparm -v -r0 /dev/sdc*

/dev/sdc:
setting readonly to 0 (off)
multcount = 0 (off)
readonly = 0 (off)
readahead = 1024 (on)
geometry = 1022/252/62, sectors = 15974400, start = 0
localhost:/home/ # fdisk /dev/sdc

Welcome to fdisk (util-linux 2.37.4).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

The device contains ‘vfat’ signature and it will be removed by a write command. See fdisk(8) man page and --wipe option for more details.

Command (m for help): p

Disk /dev/sdc: 7.62 GiB, 8178892800 bytes, 15974400 sectors
Disk model: Flash Disk
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Command (m for help): o
Created a new DOS disklabel with disk identifier 0x6be67180.
The device contains ‘vfat’ signature and it will be removed by a write command. See fdisk(8) man page and --wipe option for more details.

Command (m for help): n
Partition type
p primary (0 primary, 0 extended, 4 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1):
First sector (2048-15974399, default 2048):
Last sector, +/-sectors or +/-size{K,M,G,T,P} (2048-15974399, default 15974399):

Created a new partition 1 of type ‘Linux’ and of size 7.6 GiB.

Command (m for help): t
Selected partition 1
Hex code or alias (type L to list all): 16
Changed type of partition ‘Linux’ to ‘Hidden FAT16’.

Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Re-reading the partition table failed.: Read-only file system

The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or partx(8).

localhost:/home/ # hdparm -v -r0 /dev/sdc*

/dev/sdc:
setting readonly to 0 (off)
multcount = 0 (off)
readonly = 1 (on)
readahead = 1024 (on)
geometry = 7800/64/32, sectors = 15974400, start = 0

/dev/sdc1:
setting readonly to 0 (off)
multcount = 0 (off)
readonly = 1 (on)
readahead = 1024 (on)
geometry = 7800/64/32, sectors = 7812, start = 276

/dev/sdc2:
setting readonly to 0 (off)
multcount = 0 (off)
readonly = 1 (on)
readahead = 1024 (on)
geometry = 7800/64/32, sectors = 247912, start = 8088

/dev/sdc3:
setting readonly to 0 (off)
multcount = 0 (off)
readonly = 1 (on)
readahead = 1024 (on)
geometry = 7800/64/32, sectors = 15718400, start = 256000

I like convert my efi pendrive (isohybrid with iso9660 fs) to normal usb fat32, and write on it again.

[SDB:Live USB stick - openSUSE Wiki](how to Recover the usb stick for normal use again)

6

You can read from it; it does not mean you can write to it. You are aware that SSD cannot be rewritten indefinitely, are not you?

7

Win diskpart did it for me
How to Remove Write Protection from a USB

8

This seems to be an openSUSE installation OSI file copied to a medium to become there an ISO 9660 file system. Aren’t those made read-only by design (to be on a DVD)?

9

PLease, to make your posts better consumable by technical oriented people:

(In fact I do have problems interpreting all what you did, specially the part about the writing of a new DOS partitions table).

10

Yes, I can read but not write on usb. I reply it because @malcolmlewis ask me “Well it could have died…?”. The pendrive is running and I can boot (read) from it, and select options from grub menu.

Disks and pendrive with SSD technology cannot be rewritten indefinitely?. I don’t know it. I have some disks SSD working some years without difficulties.

The pendrive was grabbed with Opensuse Leap 15.1 NET iso in order to install it on a new partition. It works, but now, I like recover the pendrive and write a new version of opensuse.

The partition DOS is just an example in order to recover the pendrive. I follow the instrucciones from https://en.opensuse.org/SDB:Live_USB_stick . I read optional steps in >>How to Recover the USB Stick for “Normal” Use Again<<

11

I try another tool, but it doesn’t format the pendrive.

localhost:/home/ # gdisk /dev/sdc
GPT fdisk (gdisk) version 1.0.8

Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present

Found invalid GPT and valid MBR; converting MBR to GPT format
in memory. THIS OPERATION IS POTENTIALLY DESTRUCTIVE! Exit by
typing ‘q’ if you don’t want to convert your MBR partitions
to GPT format!

Command (? for help): x

Expert command (? for help): ?
a set attributes
b byte-swap a partition’s name
c change partition GUID
d display the sector alignment value
e relocate backup data structures to the end of the disk
f randomize disk and partition unique GUIDs
g change disk GUID
h recompute CHS values in protective/hybrid MBR
i show detailed information on a partition
j move the main partition table
l set the sector alignment value
m return to main menu
n create a new protective MBR
o print protective MBR data
p print the partition table
q quit without saving changes
r recovery and transformation options (experts only)
s resize partition table
t transpose two partition table entries
u replicate partition table on new device
v verify disk
w write table to disk and exit
z zap (destroy) GPT data structures and exit
? print this menu

Expert command (? for help): z
About to wipe out GPT on /dev/sdc. Proceed? (Y/N): Y
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
GPT data structures destroyed! You may now partition the disk using fdisk or
other utilities.
Blank out MBR? (Y/N): Y
Warning! MBR not overwritten! Error is 30!
localhost:/home/photo # partprobe
Warning: Unable to open /dev/sdc read-write (Read-only file system). /dev/sdc has been opened read-only.
…
Warning: Unable to open /dev/sdc read-write (Read-only file system). /dev/sdc has been opened read-only.

12

Please use the Preformatted text feature! Not the " button, but the </> button.
As explained in the link I provided.

When those tools keep complaining about what they see, then first zero out the begin of the device:

dd if=/dev/zero of=/def/sdc count=10

And then try again with fdisk to write a new partition table.

13

Yup, there’s that thing called “write cycles” that flash memory, including pendrives and SSDs, have that if you run off of it the drive will no longer be writable and will be read-only. Think of them as a stamina in a survival game - if you run out of it, it will no longer run.

It used to be really bad, but these days SSDs have ridiculous amount of write cycles available so that may explain why you never ran into any issues with SSDs.

Pendrives though, unless they use the SSD technology or are just external SSD drives, are a different story. Especially brandless/chinese pendrives have really miniscule amount of write cycles available. I’d suggest getting a new pendrive and copying all the data over from the old, read only one.

14

Hi @hcvv ,

I connect (plug) the pendrive on the box. Please, note “Write Protect is off” in /var/log/messages

2024-09-18T13:11:50.040105-03:00 localhost kernel: [  182.148868][  T147] usb 8-1: new high-speed USB device number 2 using ehci-pci
2024-09-18T13:11:50.208171-03:00 localhost kernel: [  182.316862][  T147] usb 8-1: New USB device found, idVendor=058f, idProduct=6387, bcdDevice= 1.04
2024-09-18T13:11:50.208194-03:00 localhost kernel: [  182.316877][  T147] usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2024-09-18T13:11:50.208196-03:00 localhost kernel: [  182.316880][  T147] usb 8-1: Product: Mass Storage
2024-09-18T13:11:50.208197-03:00 localhost kernel: [  182.316882][  T147] usb 8-1: Manufacturer: Generic
2024-09-18T13:11:50.208198-03:00 localhost kernel: [  182.316884][  T147] usb 8-1: SerialNumber: C927AB09
2024-09-18T13:11:50.214136-03:00 localhost mtp-probe: checking bus 8, device 2: "/sys/devices/pci0000:00/0000:00:1d.7/usb8/8-1"
2024-09-18T13:11:50.214284-03:00 localhost mtp-probe: bus: 8, device: 2 was not an MTP device
2024-09-18T13:11:50.228033-03:00 localhost kernel: [  182.338871][ T2650] usb-storage 8-1:1.0: USB Mass Storage device detected
2024-09-18T13:11:50.228050-03:00 localhost kernel: [  182.339033][ T2650] scsi host6: usb-storage 8-1:1.0
2024-09-18T13:11:50.228052-03:00 localhost kernel: [  182.339114][ T2650] usbcore: registered new interface driver usb-storage
2024-09-18T13:11:50.232033-03:00 localhost kernel: [  182.342547][ T2650] usbcore: registered new interface driver uas
2024-09-18T13:11:50.234089-03:00 localhost mtp-probe: checking bus 8, device 2: "/sys/devices/pci0000:00/0000:00:1d.7/usb8/8-1"
2024-09-18T13:11:50.234159-03:00 localhost mtp-probe: bus: 8, device: 2 was not an MTP device
2024-09-18T13:11:51.256032-03:00 localhost kernel: [  183.367193][   T63] scsi 6:0:0:0: Direct-Access     Generic  Flash Disk       8.07 PQ: 0 ANSI: 4
2024-09-18T13:11:51.256054-03:00 localhost kernel: [  183.367606][   T63] sd 6:0:0:0: Attached scsi generic sg2 type 0
2024-09-18T13:11:51.260038-03:00 localhost kernel: [  183.369442][   T65] sd 6:0:0:0: [sdc] 15974400 512-byte logical blocks: (8.18 GB/7.62 GiB)
2024-09-18T13:11:51.260052-03:00 localhost kernel: [  183.370615][   T65] sd 6:0:0:0: [sdc] Write Protect is off
2024-09-18T13:11:51.260054-03:00 localhost kernel: [  183.370619][   T65] sd 6:0:0:0: [sdc] Mode Sense: 23 00 00 00
2024-09-18T13:11:51.260055-03:00 localhost kernel: [  183.371726][   T65] sd 6:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
2024-09-18T13:11:51.272083-03:00 localhost kernel: [  183.383807][   T65]  sdc:
2024-09-18T13:11:51.272093-03:00 localhost kernel: [  183.383967][   T65] sd 6:0:0:0: [sdc] Attached SCSI removable disk

Then I try this command:

dd if=/dev/zero of=/dev/sdc count=10
10+0 records in
10+0 records out
5120 bytes (5.1 kB, 5.0 KiB) copied, 0.536356 s, 9.5 kB/s

And the output in /var/log/messages was this:

2024-09-18T13:18:05.248065-03:00 localhost kernel: [  557.359852][ T2654] sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
2024-09-18T13:18:05.248080-03:00 localhost kernel: [  557.359858][ T2654] sd 6:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current] 
2024-09-18T13:18:05.248082-03:00 localhost kernel: [  557.359861][ T2654] sd 6:0:0:0: [sdc] tag#0 <<vendor>>ASC=0xff <<vendor>>ASCQ=0xff 
2024-09-18T13:18:05.248083-03:00 localhost kernel: [  557.359864][ T2654] sd 6:0:0:0: [sdc] tag#0 CDB: Write(10) 2a 00 00 00 00 00 00 00 10 00
2024-09-18T13:18:05.248093-03:00 localhost kernel: [  557.359865][ T2654] I/O error, dev sdc, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
2024-09-18T13:18:05.248096-03:00 localhost kernel: [  557.359874][ T2654] Buffer I/O error on dev sdc, logical block 0, lost async page write
2024-09-18T13:18:05.248097-03:00 localhost kernel: [  557.359884][ T2654] Buffer I/O error on dev sdc, logical block 1, lost async page write
2024-09-18T13:18:05.252019-03:00 localhost kernel: [  557.362129][  T538] sd 6:0:0:0: [sdc] Write Protect is on
2024-09-18T13:18:05.252026-03:00 localhost kernel: [  557.362135][  T538] sd 6:0:0:0: [sdc] Mode Sense: 23 00 80 00
2024-09-18T13:18:05.260025-03:00 localhost kernel: [  557.371382][  T538]  sdc: sdc1 sdc2 sdc3

The system auto protect (EFI? isohybrid? iso9660?) and shows “Write Protect is on”.

I try change with hdparm:

localhost:/home/ # hdparm -v -r /dev/sdc*

/dev/sdc:
 multcount     =  0 (off)
 readonly      =  1 (on)
 readahead     = 1024 (on)
 geometry      = 7800/64/32, sectors = 15974400, start = 0

/dev/sdc1:
 multcount     =  0 (off)
 readonly      =  1 (on)
 readahead     = 1024 (on)
 geometry      = 7800/64/32, sectors = 7812, start = 276

/dev/sdc2:
 multcount     =  0 (off)
 readonly      =  1 (on)
 readahead     = 1024 (on)
 geometry      = 7800/64/32, sectors = 247912, start = 8088

/dev/sdc3:
 multcount     =  0 (off)
 readonly      =  1 (on)
 readahead     = 1024 (on)
 geometry      = 7800/64/32, sectors = 15718400, start = 256000
localhost:/home/ # hdparm -v -r0 /dev/sdc*

/dev/sdc:
 setting readonly to 0 (off)
 multcount     =  0 (off)
 readonly      =  1 (on)
 readahead     = 1024 (on)
 geometry      = 7800/64/32, sectors = 15974400, start = 0

/dev/sdc1:
 setting readonly to 0 (off)
 multcount     =  0 (off)
 readonly      =  1 (on)
 readahead     = 1024 (on)
 geometry      = 7800/64/32, sectors = 7812, start = 276

/dev/sdc2:
 setting readonly to 0 (off)
 multcount     =  0 (off)
 readonly      =  1 (on)
 readahead     = 1024 (on)
 geometry      = 7800/64/32, sectors = 247912, start = 8088

/dev/sdc3:
 setting readonly to 0 (off)
 multcount     =  0 (off)
 readonly      =  1 (on)
 readahead     = 1024 (on)
 geometry      = 7800/64/32, sectors = 15718400, start = 256000

None changes. The devices keeps in readonly.

Now, I umount the usb pendrive device:

2024-09-18T13:22:50.795735-03:00 localhost udisksd[1481]: Mounted /dev/sdc2 at /run/media/user/openSUSE-Leap-15.1-NET-x86_64470 on behalf of uid 1000
2024-09-18T13:22:50.796074-03:00 localhost kernel: [  842.904892][ T3212] ISO 9660 Extensions: Microsoft Joliet Level 3
2024-09-18T13:22:50.796085-03:00 localhost kernel: [  842.906643][ T3212] ISO 9660 Extensions: RRIP_1991A
2024-09-18T13:22:51.965851-03:00 localhost udisksd[1481]: Cleaning up mount point /run/media/user/openSUSE-Leap-15.1-NET-x86_64470 (device 8:34 is not mounted)
2024-09-18T13:22:51.965982-03:00 localhost udisksd[1481]: Unmounted /dev/sdc2 on behalf of uid 1000
2024-09-18T13:22:51.966547-03:00 localhost systemd[1]: run-media-user-openSUSE\x2dLeap\x2d15.1\x2dNET\x2dx86_64470.mount: Deactivated successfully.
2024-09-18T13:22:52.120027-03:00 localhost kernel: [  844.228400][ T3233] sdc: detected capacity change from 15974400 to 0
2024-09-18T13:22:52.122271-03:00 localhost plasmashell[1661]: file:///usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier/contents/ui/DeviceItem.qml:174:5: Unable to assign [undefined] to QString
2024-09-18T13:22:52.136064-03:00 localhost (udev-worker)[3215]: sdc1: Failed to remove '/dev/disk/by-label/openSUSE-Leap-15.1-NET-x86_64470', ignoring: No such file or directory
2024-09-18T13:22:52.136181-03:00 localhost (udev-worker)[3215]: sdc1: Failed to remove/update device symlink '/dev/disk/by-label/openSUSE-Leap-15.1-NET-x86_64470', ignoring: No such file or directory
2024-09-18T13:22:52.137025-03:00 localhost (udev-worker)[3241]: sdc3: Failed to remove '/dev/disk/by-label/openSUSE-Leap-15.1-NET-x86_64470', ignoring: No such file or directory
2024-09-18T13:22:52.137113-03:00 localhost (udev-worker)[3241]: sdc3: Failed to remove/update device symlink '/dev/disk/by-label/openSUSE-Leap-15.1-NET-x86_64470', ignoring: No such file or directory
2024-09-18T13:22:52.137443-03:00 localhost (udev-worker)[3240]: sdc2: Failed to remove '/dev/disk/by-label/openSUSE-Leap-15.1-NET-x86_64470', ignoring: No such file or directory
2024-09-18T13:22:52.137530-03:00 localhost (udev-worker)[3240]: sdc2: Failed to remove/update device symlink '/dev/disk/by-label/openSUSE-Leap-15.1-NET-x86_64470', ignoring: No such file or directory
2024-09-18T13:22:52.199522-03:00 localhost plasmashell[1661]: file:///usr/lib64/qt5/qml/org/kde/plasma/extras/ExpandableListItem.qml:291: TypeError: Cannot read property 'enabled' of null
2024-09-18T13:22:52.199974-03:00 localhost plasmashell[1661]: file:///usr/lib64/qt5/qml/org/kde/plasma/extras/ExpandableListItem.qml:291: TypeError: Cannot read property 'enabled' of null
2024-09-18T13:22:53.777780-03:00 localhost plasmashell[1661]: file:///usr/lib64/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
2024-09-18T13:24:37.633546-03:00 localhost systemd[1]: Starting Cleanup of Temporary Directories...
2024-09-18T13:24:37.725576-03:00 localhost systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
2024-09-18T13:24:37.726047-03:00 localhost systemd[1]: Finished Cleanup of Temporary Directories.
2024-09-18T13:25:10.504106-03:00 localhost kernel: [  982.615301][ T3249] usb 8-1: USB disconnect, device number 2

Then I with modprobe, unload the usb_storage module and specify the vendor:product of pendrive. Then I plug the pendrive on the box:

2024-09-18T13:26:06.938697-03:00 localhost sudo:     root : TTY=pts/2 ; PWD=/home/user ; USER=root ; COMMAND=/usr/sbin/modprobe -r uas usb_storage
2024-09-18T13:26:06.944026-03:00 localhost kernel: [ 1039.054232][ T3271] usbcore: deregistering interface driver uas
2024-09-18T13:26:07.000152-03:00 localhost kernel: [ 1039.107704][ T3271] usbcore: deregistering interface driver usb-storage
[...]
2024-09-18T13:26:15.736030-03:00 localhost kernel: [ 1047.845476][ T3277] usbcore: registered new interface driver usb-storage
2024-09-18T13:26:15.740023-03:00 localhost kernel: [ 1047.849278][ T3277] usbcore: registered new interface driver uas

2024-09-18T13:26:33.560149-03:00 localhost kernel: [ 1065.667563][ T3249] usb 8-1: new high-speed USB device number 3 using ehci-pci
2024-09-18T13:26:33.724039-03:00 localhost kernel: [ 1065.834945][ T3249] usb 8-1: New USB device found, idVendor=058f, idProduct=6387, bcdDevice= 1.04
2024-09-18T13:26:33.724057-03:00 localhost kernel: [ 1065.834956][ T3249] usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2024-09-18T13:26:33.724060-03:00 localhost kernel: [ 1065.834959][ T3249] usb 8-1: Product: Mass Storage
2024-09-18T13:26:33.724061-03:00 localhost kernel: [ 1065.834962][ T3249] usb 8-1: Manufacturer: Generic
2024-09-18T13:26:33.724067-03:00 localhost kernel: [ 1065.834964][ T3249] usb 8-1: SerialNumber: C927AB09
2024-09-18T13:26:33.724068-03:00 localhost kernel: [ 1065.835313][ T3249] usb-storage 8-1:1.0: USB Mass Storage device detected
2024-09-18T13:26:33.728037-03:00 localhost kernel: [ 1065.835933][ T3249] scsi host6: usb-storage 8-1:1.0
2024-09-18T13:26:33.733842-03:00 localhost mtp-probe: checking bus 8, device 3: "/sys/devices/pci0000:00/0000:00:1d.7/usb8/8-1"
2024-09-18T13:26:33.733946-03:00 localhost mtp-probe: bus: 8, device: 3 was not an MTP device
2024-09-18T13:26:33.746775-03:00 localhost mtp-probe: checking bus 8, device 3: "/sys/devices/pci0000:00/0000:00:1d.7/usb8/8-1"
2024-09-18T13:26:33.746906-03:00 localhost mtp-probe: bus: 8, device: 3 was not an MTP device
2024-09-18T13:26:34.744042-03:00 localhost kernel: [ 1066.853475][   T63] scsi 6:0:0:0: Direct-Access     Generic  Flash Disk       8.07 PQ: 0 ANSI: 4
2024-09-18T13:26:34.744062-03:00 localhost kernel: [ 1066.853931][   T63] sd 6:0:0:0: Attached scsi generic sg2 type 0
2024-09-18T13:26:34.744064-03:00 localhost kernel: [ 1066.855147][ T3263] sd 6:0:0:0: [sdc] 15974400 512-byte logical blocks: (8.18 GB/7.62 GiB)
2024-09-18T13:26:34.748095-03:00 localhost kernel: [ 1066.856226][ T3263] sd 6:0:0:0: [sdc] Write Protect is off
2024-09-18T13:26:34.748106-03:00 localhost kernel: [ 1066.856231][ T3263] sd 6:0:0:0: [sdc] Mode Sense: 23 00 00 00
2024-09-18T13:26:34.748111-03:00 localhost kernel: [ 1066.857343][ T3263] sd 6:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
2024-09-18T13:26:34.760031-03:00 localhost kernel: [ 1066.869148][ T3263]  sdc:
2024-09-18T13:26:34.760053-03:00 localhost kernel: [ 1066.869297][ T3263] sd 6:0:0:0: [sdc] Attached SCSI removable disk
2024-09-18T13:26:34.970154-03:00 localhost plasmashell[1661]: file:///usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier/contents/ui/DeviceItem.qml:36:5: Unable to assign [undefined] to bool
2024-09-18T13:26:34.970248-03:00 localhost plasmashell[1661]: file:///usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier/contents/ui/DeviceItem.qml:35:5: Unable to assign [undefined] to bool

I try change with hdparm the readonly status on each partition and this disk (pendrive).

localhost:/home/ # hdparm -v -r /dev/sdc 

/dev/sdc:
 multcount     =  0 (off)
 readonly      =  1 (on)
 readahead     = 1024 (on)
 geometry      = 7800/64/32, sectors = 15974400, start = 0
localhost:/home/ # hdparm -v -r /dev/sdc*

/dev/sdc:
 multcount     =  0 (off)
 readonly      =  1 (on)
 readahead     = 1024 (on)
 geometry      = 7800/64/32, sectors = 15974400, start = 0

/dev/sdc1:
 multcount     =  0 (off)
 readonly      =  1 (on)
 readahead     = 1024 (on)
 geometry      = 7800/64/32, sectors = 7812, start = 276

/dev/sdc2:
 multcount     =  0 (off)
 readonly      =  1 (on)
 readahead     = 1024 (on)
 geometry      = 7800/64/32, sectors = 247912, start = 8088

/dev/sdc3:
 multcount     =  0 (off)
 readonly      =  1 (on)
 readahead     = 1024 (on)
 geometry      = 7800/64/32, sectors = 15718400, start = 256000
localhost:/home/ # hdparm -v -r0 /dev/sdc*

/dev/sdc:
 setting readonly to 0 (off)
 multcount     =  0 (off)
 readonly      =  1 (on)
 readahead     = 1024 (on)
 geometry      = 7800/64/32, sectors = 15974400, start = 0

/dev/sdc1:
 setting readonly to 0 (off)
 multcount     =  0 (off)
 readonly      =  1 (on)
 readahead     = 1024 (on)
 geometry      = 7800/64/32, sectors = 7812, start = 276

/dev/sdc2:
 setting readonly to 0 (off)
 multcount     =  0 (off)
 readonly      =  1 (on)
 readahead     = 1024 (on)
 geometry      = 7800/64/32, sectors = 247912, start = 8088

/dev/sdc3:
 setting readonly to 0 (off)
 multcount     =  0 (off)
 readonly      =  1 (on)
 readahead     = 1024 (on)
 geometry      = 7800/64/32, sectors = 15718400, start = 256000

Nothing yet. Now, I try fdisk but with the new “Write Protect is off”:

localhost:/home/ # date; fdisk /dev/sdc
wed 18 sep 2024 13:33:44 -03

Welcome to fdisk (util-linux 2.37.4).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

The device contains 'vfat' signature and it will be removed by a write command. See fdisk(8) man page and --wipe option for more details.

Command (m for help): w

The partition table has been altered.
Calling ioctl() to re-read partition table.
Re-reading the partition table failed.: Read-only file system

The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or partx(8).

localhost:/home/ # sync
localhost:/home/ # partprobe 
Warning: Unable to open /dev/sdc read-write (Read-only file system).  /dev/sdc has been opened read-only.
Warning: Unable to open /dev/sdc read-write (Read-only file system).  /dev/sdc has been opened read-only.
Warning: Unable to open /dev/sdc read-write (Read-only file system).  /dev/sdc has been opened read-only.
Warning: Unable to open /dev/sdc read-write (Read-only file system).  /dev/sdc has been opened read-only.
Warning: Unable to open /dev/sdc read-write (Read-only file system).  /dev/sdc has been opened read-only.
Warning: Unable to open /dev/sdc read-write (Read-only file system).  /dev/sdc has been opened read-only.