USB drive won't mount, but still works( I think! ).

also for reference, heres what dmesg says: (not the whole thing just the last bit thats red and talks about usb etc)

3401.915611] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 3401.917333] sd 0:0:0:0: [sda] 15240576 512-byte logical blocks: (7.80 GB/7.27 GiB)
[ 3401.917870] sd 0:0:0:0: [sda] Write Protect is off
[ 3401.917880] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
[ 3401.918088] sd 0:0:0:0: [sda] No Caching mode page found
[ 3401.918089] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 3401.921594] sda: sda1 sda2
[ 3401.921902] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 3402.753442] usb 3-1: USB disconnect, device number 9
[ 3403.129161] usb 3-1: new high-speed USB device number 10 using xhci_hcd
[ 3403.257256] usb 3-1: Device not responding to setup address.
[ 3403.465286] usb 3-1: Device not responding to setup address.
[ 3403.673200] usb 3-1: device not accepting address 10, error -71
[ 3427.673288] usb 4-1: new SuperSpeed USB device number 3 using xhci_hcd
[ 3427.696919] usb 4-1: New USB device found, idVendor=0951, idProduct=1666, bcdDevice= 1.10
[ 3427.696931] usb 4-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 3427.696936] usb 4-1: Product: DataTraveler 3.0
[ 3427.696940] usb 4-1: Manufacturer: Kingston
[ 3427.696943] usb 4-1: SerialNumber: 4CEDFB74A33317316979059E
[ 3427.698705] usb-storage 4-1:1.0: USB Mass Storage device detected
[ 3427.699614] scsi host0: usb-storage 4-1:1.0
[ 3428.732506] scsi 0:0:0:0: Direct-Access Kingston DataTraveler 3.0 0000 PQ: 0 ANSI: 6
[ 3428.733015] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 3428.733531] sd 0:0:0:0: [sda] Media removed, stopped polling
[ 3428.734299] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 3428.740004] sd 0:0:0:0: [sda] 242155521 512-byte logical blocks: (124 GB/115 GiB)
[ 3428.740370] sd 0:0:0:0: [sda] Write Protect is on
[ 3428.740373] sd 0:0:0:0: [sda] Mode Sense: 23 00 80 00
[ 3428.740512] sda: detected capacity change from 0 to 242155521
[ 3428.741708] sda: sda1
[ 3431.126915] /dev/sda1: Can't open blockdev
[ 3431.130219] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[ 3431.130227] EXT4-fs (sda1): write access unavailable, cannot proceed (try mounting with n
oload)
[ 3569.001745] ACPI Error: No handler for Region [CMS0] (000000000739d4d7) [SystemCMOS] (202
20331/evregion-130)
[ 3569.001763] ACPI Error: Region SystemCMOS (ID=5) has no handler (20220331/exfldio-261)
[ 3569.001772] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0._Q33 due to previous error (AE
_NOT_EXIST) (20220331/psparse-529)
[ 4310.208979] /dev/sda1: Can't open blockdev
[ 4310.211916] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[ 4310.211921] EXT4-fs (sda1): write access unavailable, cannot proceed (try mounting with n
oload)
[ 4323.626165] /dev/sda1: Can't open blockdev
[ 4323.629057] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[ 4323.629063] EXT4-fs (sda1): write access unavailable, cannot proceed (try mounting with n
oload)
 


Plug in your flash drive and use journalctl -xe to see what device name the drive is using. Then use e2fsck -fv /dev/sdb1 if it registers as /dev/sdb and you want to check partition 1. Adjust as needed. Then use tune2fs -O ^read-only /dev/sdb1 to turn off the read-only file system feature for /dev/sdb1. Once again, adjust the name and number as needed.

Signed,

Matthew Campbell
the journalctl command gives some weird errors and i dont know where it says the device name

Jan 27 14:43:28 debian12 rtkit-daemon[945]: Supervising 10 threads of 7 processes of 1 users.
Jan 27 14:44:53 debian12 kwin_x11[1427]: kwin_core: XCB error: 152 (BadDamage), sequence: 4593, resource id: 18950402, major code: 143 (
Jan 27 14:44:58 debian12 rtkit-daemon[945]: Supervising 10 threads of 7 processes of 1 users.
Jan 27 14:44:58 debian12 rtkit-daemon[945]: Supervising 10 threads of 7 processes of 1 users.
Jan 27 14:45:12 debian12 plasmashell[7279]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x563500804110) QQmlContext(0x5634fc47f
Jan 27 14:45:12 debian12 plasmashell[7279]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x563500804110) QQmlContext(0x5634fc47f
Jan 27 14:43:28 debian12 rtkit-daemon[945]: Supervising 10 threads of 7 processes of 1 users.
Jan 27 14:44:53 debian12 kwin_x11[1427]: kwin_core: XCB error: 152 (BadDamage), sequence: 4593, resource id: 18950402, major code: 143 >
Jan 27 14:44:58 debian12 rtkit-daemon[945]: Supervising 10 threads of 7 processes of 1 users.
Jan 27 14:44:58 debian12 rtkit-daemon[945]: Supervising 10 threads of 7 processes of 1 users.
Jan 27 14:45:12 debian12 plasmashell[7279]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x563500804110) QQmlContext(0x5634fc47>
Jan 27 14:45:12 debian12 plasmashell[7279]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x563500804110) QQmlContext(0x5634fc47>
Jan 27 14:45:13 debian12 rtkit-daemon[945]: Supervising 10 threads of 7 processes of 1 users.
Jan 27 14:45:13 debian12 rtkit-daemon[945]: Supervising 10 threads of 7 processes of 1 users.
Jan 27 14:45:16 debian12 kwin_x11[1427]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 13963, resource id: 146801525,>
Jan 27 14:45:26 debian12 plasmashell[5823]: 14:45:26.834 › [GatewaySocket] [RECONNECT] gateway requested I reconnect.
Jan 27 14:45:26 debian12 plasmashell[5823]: 14:45:26.835 › [GatewaySocket] Setting connection state to WILL_RECONNECT
Jan 27 14:45:26 debian12 plasmashell[5823]: 14:45:26.835 › [GatewaySocket] Setting connection state to CONNECTING
Jan 27 14:45:26 debian12 plasmashell[5823]: 14:45:26.835 › [GatewaySocket] [CONNECT] wss://gateway-us-east1-b.discord.gg, encoding: etf>
Jan 27 14:45:26 debian12 plasmashell[5823]: 14:45:26.966 › [GatewaySocket] [CONNECTED] wss://gateway-us-east1-b.discord.gg/?encoding=et>
Jan 27 14:45:26 debian12 plasmashell[5823]: 14:45:26.967 › [GatewaySocket] Setting connection state to RESUMING
Jan 27 14:45:26 debian12 plasmashell[5823]: 14:45:26.967 › [GatewaySocket] [RESUME] resuming session 1013aab2d0d97af39f66bfa54ea37957, >
Jan 27 14:45:26 debian12 plasmashell[5823]: 14:45:26.968 › [GatewaySocket] [HELLO] via
Jan 27 14:45:26 debian12 plasmashell[5823]: gateway-prd-us-east1-b-0qnf: 0, heartbeat interval: 41250, took 132 ms
Jan 27 14:45:27 debian12 plasmashell[5823]: 14:45:27.023 › [GatewaySocket]
Jan 27 14:45:27 debian12 plasmashell[5823]: gateway-prd-us-east1-b-0qnf: 5.032
Jan 27 14:45:27 debian12 plasmashell[5823]: | id_created: 0
Jan 27 14:45:27 debian12 plasmashell[5823]: | session_lookup_time: 4.805
Jan 27 14:45:27 debian12 plasmashell[5823]: | session_lookup_finished: 0.014
Jan 27 14:45:27 debian12 plasmashell[5823]: | discord-sessions-prd-1-127: 0.021
Jan 27 14:45:27 debian12 plasmashell[5823]: 14:45:27.023 › [GatewaySocket] Setting connection state to SESSION_ESTABLISHED
Jan 27 14:45:27 debian12 plasmashell[5823]: 14:45:27.108 › [Flux] Dispatching CONNECTION_RESUMED
Jan 27 14:45:27 debian12 plasmashell[5823]: 14:45:27.112 › [GatewaySocket] [RESUMED] took 277ms, replayed 0 events, new seq: 1124
Jan 27 14:45:35 debian12 plasmashell[5823]: 14:45:35.154 › [discord_protos.discord_users.v1.FrecencyUserSettings] Scheduling save from >
Jan 27 14:45:35 debian12 plasmashell[5823]: 14:45:35.155 › [discord_protos.discord_users.v1.FrecencyUserSettings] Persisting proto
Jan 27 14:46:33 debian12 rtkit-daemon[945]: Supervising 10 threads of 7 processes of 1 users.
Jan 27 14:46:33 debian12 rtkit-daemon[945]: Supervising 10 threads of 7 processes of 1 users.
 
All those command won't help you. You don't have a /dev/sdb

But too many chefs here. I'm out.
 
An error occurred while accessing 'usbthumbdrive', the system responded: The requested operation has failed: Error mounting /dev/sda1 at /media/username/usbthumbdrive: cannot mount /dev/sda1 read-only
The drive is read-only: I do not mean that there is a read-only file system, but that the drive is readable but not writable (like a CDROM or DVD). This might be caused by some help system or competing system, so it is worthwhile to try according to this list,


  • On some pendrives and on many memory cards there is a small mechanical switch for write protection, that can toggle between read/write and read-only. You might have set it read-only without intention.
  • Reboot the computer and try again to restore or wipe the first megabyte with mkusb.
  • Disconnect other USB devices. Sometimes USB devices can disturb the function for each other.
  • Try other USB ports, and/or other card adapters.
  • Try another computer.
  • Try another operating system (Windows, MacOS) in another computer.
  • If you still cannot wipe the first megabyte of the drive, and the drive is read-only, it is probably 'gridlocked', and the next stage is that it will be completely 'bricked'. There is a limit, when you have to accept that the pendrive is damaged.
 
The drive is read-only: I do not mean that there is a read-only file system, but that the drive is readable but not writable (like a CDROM or DVD). This might be caused by some help system or competing system, so it is worthwhile to try according to this list,


  • On some pendrives and on many memory cards there is a small mechanical switch for write protection, that can toggle between read/write and read-only. You might have set it read-only without intention.
  • Reboot the computer and try again to restore or wipe the first megabyte with mkusb.
  • Disconnect other USB devices. Sometimes USB devices can disturb the function for each other.
  • Try other USB ports, and/or other card adapters.
  • Try another computer.
  • Try another operating system (Windows, MacOS) in another computer.
  • If you still cannot wipe the first megabyte of the drive, and the drive is read-only, it is probably 'gridlocked', and the next stage is that it will be completely 'bricked'. There is a limit, when you have to accept that the pendrive is damaged.
the only thing i have not tried is wiping the first megabyte. ill give that a try.
 
It looks to me like your usb flash drive may be going bad. I've never seen anything like a flash drive not responding to "setup address" before.

You can use dumpe2fs /dev/sda1 | less to see the file system features. Adjust using 1 or 2 as needed.

Signed,

Matthew Campbell
 
It looks to me like your usb flash drive may be going bad. I've never seen anything like a flash drive not responding to "setup address" before.

You can use dumpe2fs /dev/sda1 | less to see the file system features. Adjust using 1 or 2 as needed.

Signed,

Matthew Campbell
thanks!
 
im just bummed i think the drive is dead, i only bought it like 6 months ago. and its a kingston. honestly dont know if theres anything that can be done for it.
 
mount: /mnt: cannot mount /dev/sda1 read-only.
dmesg(1) may have more information after failed mount system call.

did this as sudo root superuser etc
Thanks for that output from the mount command, it looks like exact output from mount.

It may be possible to overcome that issue but running some other options of mount such as the following:
Code:
 mount -o ro,noload /dev/sda1 /mnt
Your post #11 output shows that /dev/sda does exist, and post #22 shows the partition /dev/sda1 exists.
 
Thanks for that output from the mount command, it looks like exact output from mount.

It may be possible to overcome that issue but running some other options of mount such as the following:
Code:
 mount -o ro,noload /dev/sda1 /mnt
Your post #11 output shows that /dev/sda does exist, so presumably it has a partition which would make the mountable partition: /dev/sda1.
that worked, its mounted, now what should i do!? :O!!
 
that worked, its mounted, now what should i do!? :O!!
Now what you can do is save what you need to save from the usb :)
That is, copy any files from it that you wish to save.

Other than that, you could reformat it by deleting all partitions on it with fdisk, and, create a new partition, write it, and then add a new filesystem with mkfs, either ext4 or fat32 is common.
 
Use a new USB!!
yes agreed, I need better long term storage methods. I was looking up and supposedly blueray disks by Verbatim are very good, but they are single write, which is fine i guess. also SUPER expensive.
 
Thanks for that output from the mount command, it looks like exact output from mount.

It may be possible to overcome that issue but running some other options of mount such as the following:
Code:
 mount -o ro,noload /dev/sda1 /mnt
Your post #11 output shows that /dev/sda does exist, and post #22 shows the partition /dev/sda1 exists.
this worked, I was able to copy everything off just fine, however i cannot reformat it or delete anything off it. so its just useless now, but at least I got the data I needed off. thanks everyone for the help!
 
You might try using 'chown' to change ownership.
 
this worked, I was able to copy everything off just fine, however i cannot reformat it or delete anything off it. so its just useless now, but at least I got the data I needed off. thanks everyone for the help!
One possible approach is to clear the disk totally. There are a few programs to do this, but the one I've had success with is dd. For example:
Code:
dd if=/dev/zero of=/dev/sda bs=4M  status=progress
This will fill the disk with zeros. I haven't done it on a usb with 128G, so can't vouch for that. I expect this command would take a very long time to run over that size.

The advantage of this approach is that it clears any software that is on the usb that may be impeding it's operation. Once done, then one can reformat and add a filesystem as mentioned in post #33. If there's no hardware impairment to the usb, this approach may save it.
 
You might try using 'chown' to change ownership.
the files on the usb drive are under my ownership, however for whatever reason I still cannot delete them.
 
One possible approach is to clear the disk totally. There are a few programs to do this, but the one I've had success with is dd. For example:
Code:
dd if=/dev/zero of=/dev/sda bs=4M  status=progress
This will fill the disk with zeros. I haven't done it on a usb with 128G, so can't vouch for that. I expect this command would take a very long time to run over that size.

The advantage of this approach is that it clears any software that is on the usb that may be impeding it's operation. Once done, then one can reformat and add a filesystem as mentioned in post #33. If there's no hardware impairment to the usb, this approach may save it.
when I plug it back in and run sudo fdisk -l it shows the USB thumbdrive as "
Disk /dev/sdb: 115.47 GiB, 123983626752 bytes, 242155521 sectors
Disk model: DataTraveler 3.0
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: 0x2a283129

Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 242155519 242153472 115.5G 83 Linux"

so I presume id do


dd if=/dev/zero of=/dev/sbd1 bs=4M status=progress

(instead of sda?) I dont wanna wipe the wrong device! lol!
 
when I plug it back in and run sudo fdisk -l it shows the USB thumbdrive as "
Disk /dev/sdb: 115.47 GiB, 123983626752 bytes, 242155521 sectors
Disk model: DataTraveler 3.0
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: 0x2a283129

Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 242155519 242153472 115.5G 83 Linux"

so I presume id do


dd if=/dev/zero of=/dev/sbd1 bs=4M status=progress

(instead of sda?) I dont wanna wipe the wrong device! lol!
Yes of course, you must target the correct device, which from your fdisk output is
/dev/sdb. My example was just an example from my notes, not meant as an instruction.
 

Staff online

Members online


Top