new 4TB SSD gives read errors

[bill_p]

I've just bought a 4TB SSD portable drive (USB). When I plug it in it puts errors into the log but nothing on screen. Start gparted to see what partitions are present: and it pops up an error report:
'Input/output error during read on /dev/sda, Retry/Cancel/Ignore' retry simply repeats, Ignore then reports: 'The backup GPT is corrupt, but the primary appears OK, so that will be used'.

Gparted then shows a 16MB reserved microsoft partion and the rest of the disk allocated, but not formatted? Tried the format to ext4 option and got the same errors reported.
Tried deleting the unformatted partion, which seemed to be accepted, then create a new partition in that space with ext4 format. That was accepted, but both changes were
simply queued. When I tried to apply the pending requests it then comes up with the same errors again.

gparted offered to save details, but that produces a .htm file, which doesn't seem to be supported on this forum as an attachment, but I opened it in Firefox and copy and pasted it here:
-------------------------------------------------------------------------------------------------------
GParted 1.3.1

configuration --enable-libparted-dmraid --enable-online-resize

libparted 3.5

========================================
Device: /dev/nvme0n1
Model: WDC PC SN530 SDBPNPZ-1T00-1114
Serial:
Sector size: 512
Total sectors: 2000409264

Heads: 255
Sectors/track: 2
Cylinders: 3922371

Partition table: gpt

Partition Type Start End Flags Partition Name File System Label Mount Point
/dev/nvme0n1p1 Primary 2048 206847 boot, esp EFI system partition fat32 /boot/efi
/dev/nvme0n1p2 Primary 206848 239615 msftres Microsoft reserved partition unknown
/dev/nvme0n1p3 Primary 239616 203532287 Basic data partition bitlocker
/dev/nvme0n1p4 Primary 203532288 205037567 hidden, diag ntfs
/dev/nvme0n1p5 Primary 205039616 322226175 root ext4 /
/dev/nvme0n1p6 Primary 322226176 400351231 swap linux-swap
/dev/nvme0n1p7 Primary 400351232 1999155199 ext4 /home

========================================
Device: /dev/sda
Model: AL SSD
Serial:
Sector size: 4096
Total sectors: 1024000000

Heads: 255
Sectors/track: 9
Cylinders: 446187

Partition table: gpt

Partition Type Start End Flags Partition Name File System Label Mount Point
/dev/sda1 Primary 6 4095 msftres Microsoft reserved partition unknown
/dev/sda2 Primary 4096 1023999993 msftdata Basic data partition unknown

========================================
Delete /dev/sda2 (unknown, 3.81 TiB) from /dev/sda 00:00:34 ( SUCCESS )

calibrate /dev/sda2 00:00:14 ( SUCCESS )

path: /dev/sda2 (partition)
start: 4096
end: 1023999993
size: 1023995898 (3.81 TiB)
libparted messages ( INFO )

Input/output error during read on /dev/sda
The backup GPT table is corrupt, but the primary appears OK, so that will be used.
delete partition 00:00:20 ( SUCCESS )

libparted messages ( INFO )

Input/output error during read on /dev/sda
The backup GPT table is corrupt, but the primary appears OK, so that will be used.
Input/output error during write on /dev/sda

========================================
Create Primary Partition #1 (ext4, 3.81 TiB) on /dev/sda 00:00:12 ( ERROR )

create empty partition 00:00:12 ( ERROR )

libparted messages ( ERROR )

Input/output error during read on /dev/sda
-------------------------------------------------------------------------------------------------------

I then tried running gsmart_control which produced:
--------------------------------------------------------------------------------------------------------
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-11-amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor: AL
Product: SSD
Revision: 5.00
User Capacity: 4,194,304,000,000 bytes [4.19 TB]
Logical block size: 4096 bytes
scsiModePageOffset: response length too short, resp_len=12 offset=12 bd_len=8
scsiModePageOffset: response length too short, resp_len=12 offset=12 bd_len=8
>> Terminate command early due to bad response to IEC mode page
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
------------------------------------------------------------------------------------------------------------

I passed the drive on to a friend who runs Windows, and he mounted the drive and ran various diagnostics which report the drive has no problems!
Is this a bug in the kernel? Have I wasted my money?

[arzgi]

Usually when I install a new hdd/sdd I wipe I all partitions (if any), then make new partitions then format.

I use fdisk to handle partitions, and mkfs.ext* to format.

[lindi]

Check dmesg

[bill_p]

Plugged in the disk and copied from dmesg:

[941877.381008] usb 1-3: new high-speed USB device number 12 using xhci_hcd
[941877.530033] usb 1-3: New USB device found, idVendor=048d, idProduct=1234, bcdDevice= 1.00
[941877.530042] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[941877.530045] usb 1-3: Product: USB 3.1
[941877.530048] usb 1-3: Manufacturer: PSSD
[941877.530050] usb 1-3: SerialNumber:
[941877.531420] usb-storage 1-3:1.0: USB Mass Storage device detected
[941877.531614] scsi host2: usb-storage 1-3:1.0
[941878.553399] scsi 2:0:0:0: Direct-Access AL SSD 5.00 PQ: 0 ANSI: 2
[941878.553679] sd 2:0:0:0: Attached scsi generic sg0 type 0
[941878.554078] sd 2:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
[941878.554206] sd 2:0:0:0: [sda] 1024000000 4096-byte logical blocks: (4.19 TB/3.81 TiB)
[941878.554331] sd 2:0:0:0: [sda] Write Protect is off
[941878.554334] sd 2:0:0:0: [sda] Mode Sense: 0b 00 00 08
[941878.554456] sd 2:0:0:0: [sda] No Caching mode page found
[941878.554459] sd 2:0:0:0: [sda] Assuming drive cache: write through
[941878.555026] sd 2:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
[941878.562458] sd 2:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[941878.562471] sd 2:0:0:0: [sda] tag#0 Sense Key : Illegal Request [current]
[941878.562477] sd 2:0:0:0: [sda] tag#0 Add. Sense: Logical block address out of range
[941878.562484] sd 2:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 3d 08 ff ff 00 00 01 00
[941878.562487] critical target error, dev sda, sector 8191999992 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[941878.562501] Buffer I/O error on dev sda, logical block 1023999999, async page read
[941878.562519] Alternate GPT is invalid, using primary GPT.
[941878.562532] sda: sda1 sda2
[941878.562854] sd 2:0:0:0: [sda] Attached SCSI disk
[941878.571540] sd 2:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[941878.571544] sd 2:0:0:0: [sda] tag#0 Sense Key : Illegal Request [current]
[941878.571546] sd 2:0:0:0: [sda] tag#0 Add. Sense: Logical block address out of range
[941878.571548] sd 2:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 3d 08 ff f0 00 00 01 00
[941878.571549] critical target error, dev sda, sector 8191999872 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
[941878.572033] sd 2:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[941878.572041] sd 2:0:0:0: [sda] tag#0 Sense Key : Illegal Request [current]
[941878.572044] sd 2:0:0:0: [sda] tag#0 Add. Sense: Logical block address out of range
[941878.572046] sd 2:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 3d 08 ff f0 00 00 01 00
[941878.572048] critical target error, dev sda, sector 8191999872 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[941878.572054] Buffer I/O error on dev sda, logical block 1023999984, async page read
[941878.581662] sd 2:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[941878.581665] sd 2:0:0:0: [sda] tag#0 Sense Key : Illegal Request [current]
[941878.581666] sd 2:0:0:0: [sda] tag#0 Add. Sense: Logical block address out of range
[941878.581668] sd 2:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 3d 08 fe f0 00 00 01 00
[941878.581668] critical target error, dev sda, sector 8191997824 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
[941878.582783] sd 2:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[941878.582784] sd 2:0:0:0: [sda] tag#0 Sense Key : Illegal Request [current]
[941878.582784] sd 2:0:0:0: [sda] tag#0 Add. Sense: Logical block address out of range
[941878.582785] sd 2:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 3d 08 fe f0 00 00 01 00
[941878.582786] critical target error, dev sda, sector 8191997824 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[941878.582788] Buffer I/O error on dev sda2, logical block 1023995632, async page read

[bill_p]

arzgi: I had tried fdisk:

# fdisk /dev/sda

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

fdisk: cannot open /dev/sda: Input/output error
#

[bill_p]

tried running gsmartcontrol:
-----------------------------------------------------------------------------------
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-11-amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor: AL
Product: SSD
Revision: 5.00
User Capacity: 4,194,304,000,000 bytes [4.19 TB]
Logical block size: 4096 bytes
scsiModePageOffset: response length too short, resp_len=12 offset=12 bd_len=8
scsiModePageOffset: response length too short, resp_len=12 offset=12 bd_len=8
>> Terminate command early due to bad response to IEC mode page
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
-------------------------------------------------------------------
added '-T permissive' to the options, but that just made it omit the last line!

[sunrat]

Please use code tags for terminal text.

[arzgi]

Try lsblk:

Code: Select all

~$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda      8:0    0 223,6G  0 disk 
├─sda1   8:1    0   524M  0 part /boot/efi
├─sda2   8:2    0     1K  0 part 
├─sda5   8:5    0 178,9G  0 part /home
├─sda6   8:6    0   7,4G  0 part [SWAP]
└─sda7   8:7    0  36,7G  0 part /

[bill_p]

I tried running parted and it has deleted the partitions and created two 2TB partitions, ran mkfs (ext4) on both of them) but again got read errors.
Tried again, this time rewriting the lbell as msdos format, but again read errors.

Code: Select all

$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    0   3.8T  0 disk 
|-sda1        8:1    0   1.9T  0 part 
`-sda2        8:2    0   1.9T  0 part 
nvme0n1     259:0    0 953.9G  0 disk 
|-nvme0n1p1 259:1    0   100M  0 part /boot/efi
|-nvme0n1p2 259:2    0    16M  0 part 
|-nvme0n1p3 259:3    0  96.9G  0 part 
|-nvme0n1p4 259:4    0   735M  0 part 
|-nvme0n1p5 259:5    0  55.9G  0 part /
|-nvme0n1p6 259:6    0  37.3G  0 part [SWAP]
`-nvme0n1p7 259:7    0 762.4G  0 part /home

[arzgi]

Code: Select all

$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    0   3.8T  0 disk 
|-sda1        8:1    0   1.9T  0 part 
`-sda2        8:2    0   1.9T  0 part 
nvme0n1     259:0    0 953.9G  0 disk 
|-nvme0n1p1 259:1    0   100M  0 part /boot/efi
|-nvme0n1p2 259:2    0    16M  0 part 
|-nvme0n1p3 259:3    0  96.9G  0 part 
|-nvme0n1p4 259:4    0   735M  0 part 
|-nvme0n1p5 259:5    0  55.9G  0 part /
|-nvme0n1p6 259:6    0  37.3G  0 part [SWAP]
`-nvme0n1p7 259:7    0 762.4G  0 part /home

Some progress, you have now nearly 1 G nvme0n1 partition. Does

Code: Select all

$ sudo fdisk -l
[sudo] arto-käyttäjän salasana: 
Disk /dev/sda: 223,57 GiB, 240057409536 bytes, 468862128 sectors
Disk model: KINGSTON SA400S3
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: 0x7d845d39

Device     Boot    Start       End   Sectors   Size Id Type
/dev/sda1  *        2048   1075199   1073152   524M ef EFI (FAT-12/16/32)
/dev/sda2        1077246 468860927 467783682 223,1G  5 Extended
/dev/sda5       93749248 468860927 375111680 178,9G 83 Linux
/dev/sda6        1077248  16699391  15622144   7,4G 82 Linux swap / Solaris
/dev/sda7       16701440  93749247  77047808  36,7G 83 Linux

Partition table entries are not in disk order.

show the same? Have you tried different usb-port?

And one more

Code: Select all

sudo fsck /dev/sda1
sudo fsck /dev/sda2

[bill_p]

Can't get fdisk to do anything:

Code: Select all

# fdisk /dev/sda

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

fdisk: cannot open /dev/sda: Input/output error

fsck on /dev/sda1:

Code: Select all

# fsck /dev/sda1
fsck from util-linux 2.38.1
e2fsck 1.47.0 (5-Feb-2023)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
Superblock has an invalid journal (inode 8).
Clear<y>? yes
*** journal has been deleted ***

Pass 1: Checking inodes, blocks, and sizes
Journal inode is not in use, but contains data.  Clear<y>? yes
Deleted inode 56993 has zero dtime.  Fix<y>? yes
Deleted inode 73377 has zero dtime.  Fix<y>? yes
Inode 89761 seems to contain garbage.  Clear<y>? yes
Inode 89762 seems to contain garbage.  Clear<y>? yes
Inode 89763 seems to contain garbage.  Clear<y>? yes
Inode 89764 seems to contain garbage.  Clear<y>? yes
Inode 89765 seems to contain garbage.  Clear<y>? yes
Inode 89766 seems to contain garbage.  Clear<y>? yes
Inode 89767 seems to contain garbage.  Clear<y>? yes
Inode 89768 seems to contain garbage.  Clear<y>? yes
Inode 89769 seems to contain garbage.  Clear<y>? yes
Inode 89770 seems to contain garbage.  Clear<y>? yes
Inode 89771 seems to contain garbage.  Clear<y>? yes
Inode 89772 seems to contain garbage.  Clear<y>? yes
Inode 89773 seems to contain garbage.  Clear<y>? yes
Inode 89774 seems to contain garbage.  Clear<y>? yes
Inode 89775 seems to contain garbage.  Clear<y>? yes
Inode 89776 seems to contain garbage.  Clear<y>? yes
Inode 89777 is in use, but has dtime set.  Fix<y>? yes
Inode 89777 has imagic flag set.  Clear<y>? yes
Inode 89777 has a extra size (8244) which is invalid
Fix<y>? yes
Special (device/socket/fifo) inode 89777 has non-zero size.  Fix<y>? yes
Inode 89778 is in use, but has dtime set.  Fix<y>? yes
Inode 89778 has imagic flag set.  Clear<y>? yes
Inode 89778 has a extra size (8372) which is invalid
Fix<y>? yes
Special (device/socket/fifo) inode 89778 has non-zero size.  Fix<y>? yes
Inode 89779 is in use, but has dtime set.  Fix<y>? yes
Inode 89779 has imagic flag set.  Clear<y>? yes
Inode 89779 has a extra size (8500) which is invalid
Fix<y>? yes
Special (device/socket/fifo) inode 89779 has non-zero size.  Fix<y>? yes
Inode 89780 has the casefold flag set but is not a directory.  Clear flag<y>? yes
Special (device/socket/fifo) file (inode 89780) has extents
or inline-data flag set.  Clear<y>? yes
Inode 89780 is in use, but has dtime set.  Fix<y>? yes
Inode 89780 has imagic flag set.  Clear<y>? yes
Inode 89780 has a extra size (11281) which is invalid
Fix<y>? yes
Special (device/socket/fifo) inode 89780 has non-zero size.  Fix<y>? yes
Inode 89781 is in use, but has dtime set.  Fix<y>? yes
Inode 89781 has imagic flag set.  Clear<y>? yes
Inode 89781 has a extra size (11456) which is invalid
Fix<y>? yes
Inode 89781 has encrypt flag but no encryption extended attribute.
Clear flag<y>? yes
Inode 89782 has INLINE_DATA_FL flag on filesystem without inline data support.
Clear<y>? yes
Inode 89783 has the casefold flag set but is not a directory.  Clear flag<y>? yes
Inode 89783 seems to have inline data but extent flag is set.
Fix<y>? yes
Inode 89783 has INLINE_DATA_FL flag on filesystem without inline data support.
Clear<y>? yes
Inode 89780, i_blocks is 48426318504322, should be 0.  Fix<y>? yes
Inode 89777, i_blocks is 35382477660162, should be 0.  Fix<y>? yes
Inode 89778, i_blocks is 35932241862786, should be 0.  Fix<y>? yes
Inode 89779, i_blocks is 36482006065410, should be 0.  Fix<y>? yes
Inode 89781, i_size is 3222374694326119554, should be 0.  Fix<y>? yes
Inode 89781, i_blocks is 49178123185294, should be 0.  Fix<y>? yes
Inode 97953 seems to contain garbage.  Clear<y>? yes
Inode 97954 seems to contain garbage.  Clear<y>? yes
Inode 97955 seems to contain garbage.  Clear<y>? yes
Inode 97956 seems to contain garbage.  Clear<y>? yes
Inode 97957 seems to contain garbage.  Clear<y>? yes
Inode 97958 seems to contain garbage.  Clear<y>? yes
Inode 97959 seems to contain garbage.  Clear<y>? yes
Inode 97960 seems to contain garbage.  Clear<y>? yes
Inode 97961 seems to contain garbage.  Clear<y>? yes
Inode 97962 seems to contain garbage.  Clear<y>? yes
Inode 97963 seems to contain garbage.  Clear<y>? yes
Inode 97964 seems to contain garbage.  Clear<y>? yes
Inode 97965 seems to contain garbage.  Clear<y>? yes
Inode 97966 seems to contain garbage.  Clear<y>? yes
Inode 97967 seems to contain garbage.  Clear<y>? yes
Inode 97968 seems to contain garbage.  Clear<y>? yes
Inode 97969 is in use, but has dtime set.  Fix<y>? yes
Inode 97969 has imagic flag set.  Clear<y>? yes
Inode 97969 has a extra size (8244) which is invalid
Fix<y>?
.....ad infinitum....

hadn't run mkfs on sda2, until now. Output from this:

Code: Select all

# mkfs -t ext4 /dev/sda2
mke2fs 1.47.0 (5-Feb-2023)
Warning: could not erase sector 2: Input/output error
Creating filesystem with 512000000 4k blocks and 128000000 inodes
Filesystem UUID: 69b469ba-1b4f-49f5-82ea-3c48dea9b2a9
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
	4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 
	102400000, 214990848

Allocating group tables: done                            
Warning: could not read block 0: Input/output error
Warning: could not erase sector 0: Input/output error
Writing inode tables: done                            
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: mkfs.ext4: Input/output error while writing out and closing file system

[arzgi]

It was

Code: Select all

fdisk -l

short hand for llist, Did you try fsck?

[bill_p]

"Did you try fsck?"
Yes, see above...

[happyfeet8827]

It could also be that instead of a brand new drive the OP was misled by the seller which does happen when sellers are just wanting to rid themself or their suppliers of refurbished/remanufactured items. That's why if I see either of the two aforementioned words next or underneath an item description I keep looking elsewhere. Another place that I recommend that people try and steer clear of when purchasing SSDs or HDDS is eBay and that is again due to the aforementioned issue of the occasional remanufactured or reclaimed hardware issues if you are not careful you could potentially even get a complete dud all together.

[bill_p]

Well this one does look brand new, and seems to work on Windows but not on Debian 12. I've tried all sorts, reformatting on Windows goes OK, but it still produces supposed data errors
on Debian. The error messages imply that the numbers in the disk label are incorrect, even after I wiped the disk (Used PV to write 100MB of zeros over the front of the disk
without any problem, then used Parted to write a new GPT label, and immediately get these 'data read' errors.

[CwF]

Well this one does look brand new,

Has it occurred to you smart tells you exactly?

[bill_p]

CwF said "Has it occurred to you smart tells you exactly?"

Well, I have no idea what it is saying in terms that I can relate to.

[CwF]

A line like this reporting zero hours, aka 'new'

Code: Select all

  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       0

I think some have come with 1 hour or so, maybe tested...

[bill_p]

It doesn't get that far! Here's all that I got (repeated):
----------------------------------------------------------------------------------

Code: Select all

smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-11-amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor: AL
Product: SSD
Revision: 5.00
User Capacity: 4,194,304,000,000 bytes [4.19 TB]
Logical block size: 4096 bytes
scsiModePageOffset: response length too short, resp_len=12 offset=12 bd_len=8
scsiModePageOffset: response length too short, resp_len=12 offset=12 bd_len=8
>> Terminate command early due to bad response to IEC mode page
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

------------------------------------------------------------------------------

[CwF]

Since the claim is windows works fine, I assume after working there you have then used Debian and see it enumerate in /dev/disk, then still unmounted run smartctl and then receive the error, suggesting some Debian incompatibility.

I would write a random working disk image, ISO, whatever, to the device. Use dd or my preferred qemu-img. If that failed, I'd personally throw it away - life is short... Or you could try packages f3 or diskscan to see their results. I'd assume the device is not legit, but if it works under windows, use it under windows.