On Wed, Nov 6, 2024 at 1:10 PM Ranjan Maitra via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > On Wed Nov06'24 11:59:42AM, Jeffrey Walton wrote: > > From: Jeffrey Walton <noloader@xxxxxxxxx> > > Date: Wed, 6 Nov 2024 11:59:42 -0500 > > To: Community support for Fedora users <users@xxxxxxxxxxxxxxxxxxxxxxx> > > CC: Ranjan Maitra <mlmaitra@xxxxxxx> > > Reply-To: noloader@xxxxxxxxx, Community support for Fedora users > > <users@xxxxxxxxxxxxxxxxxxxxxxx> > > Subject: Re: mounting a 16TB USB on Fedora 40 > > > > On Wed, Nov 6, 2024 at 11:54 AM Ranjan Maitra via users > > <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > > > > > I recently got a 16TB USB disk and was trying to mount it on Fedora 40 using spacefm. I get the following: > > > > > > Mount /dev/sdb: > > > > > > Status: Finished with error (Exit status 1). > > > > > > Object /org/freedesktop/UDisks2/block_devices/sdb is not a mountable file system. > > > > What does the tail of dmeg say? I believe that's where you will see > > the initial kernel and udev activity. > > I think that here is the relevant output from dmesg. Let me know if you need more information. > > .[122815.654311] usb 2-1: USB disconnect, device number 96 > .[122817.986491] usb 2-1: new high-speed USB device number 97 using xhci_hcd > .[122818.113185] usb 2-1: New USB device found, idVendor=048d, idProduct=1234, bcdDevice= 1.00 > .[122818.113209] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > .[122818.113217] usb 2-1: Product: USB 3.1 > .[122818.113222] usb 2-1: Manufacturer: PSSD > .[122818.113226] usb 2-1: SerialNumber: > .[122818.115101] usb-storage 2-1:1.0: USB Mass Storage device detected > .[122818.115817] scsi host6: usb-storage 2-1:1.0 > .[122819.145247] scsi 6:0:0:0: Direct-Access AL SSD 5.00 PQ: 0 ANSI: 2 > .[122819.146573] sd 6:0:0:0: Attached scsi generic sg1 type 0 > .[122819.147125] sd 6:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16). > .[122819.148810] sd 6:0:0:0: [sdb] 4096000000 4096-byte logical blocks: (16.8 TB/15.3 TiB) > .[122819.148933] sd 6:0:0:0: [sdb] Write Protect is off > .[122819.148935] sd 6:0:0:0: [sdb] Mode Sense: 0b 00 00 08 > .[122819.149051] sd 6:0:0:0: [sdb] No Caching mode page found > .[122819.149053] sd 6:0:0:0: [sdb] Assuming drive cache: write through > .[122819.150014] sd 6:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16). > .[122819.155413] sd 6:0:0:0: [sdb] Attached SCSI removable disk > .[122819.181249] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s > .[122819.181262] sd 6:0:0:0: [sdb] tag#0 Sense Key : Illegal Request [current] > .[122819.181266] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Logical block address out of range > .[122819.181272] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 f4 23 ff f0 00 00 01 00 > .[122819.181275] critical target error, dev sdb, sector 32767999872 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 > .[122819.181735] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s > .[122819.181738] sd 6:0:0:0: [sdb] tag#0 Sense Key : Illegal Request [current] > .[122819.181740] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Logical block address out of range > .[122819.181741] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 f4 23 ff f0 00 00 01 00 > .[122819.181742] critical target error, dev sdb, sector 32767999872 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 > .[122819.181745] Buffer I/O error on dev sdb, logical block 4095999984, async page read Based on the Buffer I/O error, this could indicate a failing drive; see <https://www.reddit.com/r/debian/comments/omic2r/buffer_io_on_dev_sdb_logical_block_0_async_page/>. `smartctl -x /dev/sdb` may give you more information. If the sectors were reallocated, like in <https://forums.debian.net/viewtopic.php?t=149547>, then it would be less of a concern. But yours seems to be a hard problem. I better defer to some of the folks more experienced with disk problems. > > > My first instinct was that I got taken for a ride so I hopped over to a colleague's Windoze machine, but there the USB drive is visible (with the capacitty of 15.2 GiB, as expected). > > > > One comment here... I understand the counterfits have an additional > > chip or logic that misreports the size. The real problems do not > > surface until you actually try to use the space. So plugging the usb > > drive in may not be enough to validate the drive. Instead, you want to > > write a 12 TB or 14 TB of data to ensure it's not a 256 GB or 1 TB > > drive. > > I see, thanks for this information. I was not aware. Jeff -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
