I've just bought a 4TB SSD portable drive (USB). When I plug it in it puts errors into the log as follows:-
I am using a Pi 4 running either "Debian GNU/Linux 11 (bullseye)"or "Raspbian GNU/Linux 12
Drive info:-
Device: /dev/sda
Model: AL SSD
Serial:
Sector size: 4096
Total sectors: 1024000000
Heads: 255
Sectors/track: 9
Cylinders: 446187
The drive works ok on both a Windows and Mac systems using either exFat and NTFS as the file systems, I also copied 2TB+ of data and all is good.
On the raspberry Pi 4 it also works using a exFat file system, also copied 2TB+ of data to this file system without any errors or performance issues.
I then re partition the drive with one partition of size around 95GB and format an ext4 file system with mkfs.ext4, this works without any problems too but you still get the error in the log on boot and plugging in the drive as above.
But now if you add more partitions and make an ext4 file system using mkfs.ext4, the mkfs.ext4 command runs as expected, but when you check these new file systems with fsck they are all corrupted with many errors.
One side effect of adding more file systems is the first one which was working ok gets corrupted and stops working. then if you check it with fsck many errors are found and can not be fixed. so somehow making the new file systems writes over the first filesystem.
Also if you make a 1st partition of more than 95GB or the whole drive with a ext4 file system this also is corrupted when you check with fsck.
Well, I have no idea whats going on here is it the Drive or the OS and or USB drivers ?
Code:
81963.221535] usb 1-1.4: new high-speed USB device number 5 using dwc_otg[81963.352504] usb 1-1.4: New USB device found, idVendor=048d, idProduct=1234, bcdDevice= 1.00[81963.352555] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3[81963.352578] usb 1-1.4: Product: USB 3.1[81963.352597] usb 1-1.4: Manufacturer: PSSD[81963.352614] usb 1-1.4: SerialNumber: [81963.353843] usb-storage 1-1.4:1.0: USB Mass Storage device detected[81963.355604] scsi host1: usb-storage 1-1.4:1.0[81964.412414] scsi 1:0:0:0: Direct-Access AL SSD 5.00 PQ: 0 ANSI: 2[81964.413503] sd 1:0:0:0: Attached scsi generic sg1 type 0[81964.414324] sd 1:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).[81964.414794] sd 1:0:0:0: [sdb] 1024000000 4096-byte logical blocks: (4.19 TB/3.81 TiB)[81964.415336] sd 1:0:0:0: [sdb] Write Protect is off[81964.415370] sd 1:0:0:0: [sdb] Mode Sense: 0b 00 00 08[81964.415779] sd 1:0:0:0: [sdb] No Caching mode page found[81964.415808] sd 1:0:0:0: [sdb] Assuming drive cache: write through[81964.418364] sd 1:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).[81964.420557] sdb:[81964.420828] sd 1:0:0:0: [sdb] Attached SCSI disk[81964.500337] sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s[81964.500391] sd 1:0:0:0: [sdb] tag#0 Sense Key : 0x5 [current] [81964.500415] sd 1:0:0:0: [sdb] tag#0 ASC=0x21 ASCQ=0x0 [81964.500443] sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 3d 08 ff f0 00 00 01 00[81964.500462] critical target error, dev sdb, sector 8191999872 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2[81964.501207] sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s[81964.501238] sd 1:0:0:0: [sdb] tag#0 Sense Key : 0x5 [current] [81964.501261] sd 1:0:0:0: [sdb] tag#0 ASC=0x21 ASCQ=0x0 [81964.501284] sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 3d 08 ff f0 00 00 01 00[81964.501301] critical target error, dev sdb, sector 8191999872 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2[81964.501329] Buffer I/O error on dev sdb, logical block 1023999984, async page readpi@piserver3:~ $ Drive info:-
Device: /dev/sda
Model: AL SSD
Serial:
Sector size: 4096
Total sectors: 1024000000
Heads: 255
Sectors/track: 9
Cylinders: 446187
The drive works ok on both a Windows and Mac systems using either exFat and NTFS as the file systems, I also copied 2TB+ of data and all is good.
On the raspberry Pi 4 it also works using a exFat file system, also copied 2TB+ of data to this file system without any errors or performance issues.
I then re partition the drive with one partition of size around 95GB and format an ext4 file system with mkfs.ext4, this works without any problems too but you still get the error in the log on boot and plugging in the drive as above.
But now if you add more partitions and make an ext4 file system using mkfs.ext4, the mkfs.ext4 command runs as expected, but when you check these new file systems with fsck they are all corrupted with many errors.
One side effect of adding more file systems is the first one which was working ok gets corrupted and stops working. then if you check it with fsck many errors are found and can not be fixed. so somehow making the new file systems writes over the first filesystem.
Also if you make a 1st partition of more than 95GB or the whole drive with a ext4 file system this also is corrupted when you check with fsck.
Well, I have no idea whats going on here is it the Drive or the OS and or USB drivers ?
Statistics: Posted by Geralds — Fri Jan 26, 2024 12:09 pm
