SSD failure after power outage

froep · 2022-10-18 01:22:30

I have a problem with a ~1y old Samsung 870 EVO SATA SSD.
After a power outage during operation, it is not detected in BIOS anymore.
From a live system I checked dmesg and smartctl output; see below.
I checked with multiple SATA cables and ports on multiple machines, so I'm pretty sure the SSD itself is the problem.

Any clue if this is a hardware failure or something that can be fixed? How should I proceed?

dmesg output when plugging in the SSD:

[27743.045682] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[27743.045977] ata4.00: failed to read native max address (err_mask=0x1)
[27743.045985] ata4.00: HPA support seems broken, skipping HPA handling
[27743.045993] ata4.00: supports DRM functions and may not be fully accessible
[27743.046000] ata4.00: ATA-11: Samsung SSD 870 EVO 4TB, SVT01B6Q, max UDMA/133
[27743.046007] ata4.00: 7814037168 sectors, multi 1: LBA48 NCQ (not used)
[27743.048086] ata4.00: supports DRM functions and may not be fully accessible
[27743.049906] ata4.00: configured for UDMA/133 (device error ignored)
[27743.050201] scsi 5:0:0:0: Direct-Access     ATA      Samsung SSD 870  1B6Q PQ: 0 ANSI: 5
[27743.051468] scsi 5:0:0:0: Attached scsi generic sg2 type 0
[27743.052610] ata4.00: Enabling discard_zeroes_data
[27743.052740] sd 5:0:0:0: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
[27743.052779] sd 5:0:0:0: [sdb] Write Protect is off
[27743.052783] sd 5:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[27743.052805] sd 5:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[27743.081985] ata4.00: Enabling discard_zeroes_data
[27743.083197]  sdb: sdb1 sdb2 sdb3 sdb4
[27743.084497] ata4.00: Enabling discard_zeroes_data
[27743.106981] sd 5:0:0:0: [sdb] supports TCG Opal
[27743.106986] sd 5:0:0:0: [sdb] Attached SCSI disk
[27743.337744] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[27743.337755] ata4.00: irq_stat 0x40000001
[27743.337758] ata4.00: failed command: FLUSH CACHE EXT
[27743.337761] ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 24
                        res 51/04:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
[27743.337769] ata4.00: status: { DRDY ERR }
[27743.337771] ata4.00: error: { ABRT }
[27743.337994] ata4.00: supports DRM functions and may not be fully accessible
[27743.339927] ata4.00: supports DRM functions and may not be fully accessible
[27743.342242] ata4.00: configured for UDMA/133 (device error ignored)
[27743.342251] ata4.00: device reported invalid CHS sector 0
[27743.342271] ata4: EH complete
[27743.365645] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[27743.365656] ata4.00: irq_stat 0x40000001
[27743.365659] ata4.00: failed command: FLUSH CACHE EXT
[27743.365662] ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 26
                        res 51/04:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
[27743.365671] ata4.00: status: { DRDY ERR }
[27743.365675] ata4.00: error: { ABRT }
[27743.365901] ata4.00: supports DRM functions and may not be fully accessible
[27743.368166] ata4.00: supports DRM functions and may not be fully accessible
[27743.369860] ata4.00: configured for UDMA/133 (device error ignored)
[27743.369866] ata4.00: device reported invalid CHS sector 0
[27743.369885] ata4: EH complete
[27743.393698] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[27743.393707] ata4.00: irq_stat 0x40000001
[27743.393710] ata4.00: failed command: FLUSH CACHE EXT
[27743.393712] ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 23
                        res 51/04:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
[27743.393718] ata4.00: status: { DRDY ERR }
[27743.393720] ata4.00: error: { ABRT }
[27743.393941] ata4.00: supports DRM functions and may not be fully accessible
[27743.395916] ata4.00: supports DRM functions and may not be fully accessible
[27743.398103] ata4.00: configured for UDMA/133 (device error ignored)
[27743.398112] ata4.00: device reported invalid CHS sector 0
[27743.398138] ata4: EH complete
[27743.421689] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[27743.421699] ata4.00: irq_stat 0x40000001
[27743.421701] ata4.00: failed command: FLUSH CACHE EXT
[27743.421703] ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 17
                        res 51/04:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
[27743.421708] ata4.00: status: { DRDY ERR }
[27743.421710] ata4.00: error: { ABRT }
[27743.421963] ata4.00: supports DRM functions and may not be fully accessible
[27743.424264] ata4.00: supports DRM functions and may not be fully accessible
[27743.425987] ata4.00: configured for UDMA/133 (device error ignored)
[27743.426006] ata4.00: device reported invalid CHS sector 0
[27743.426044] ata4: EH complete
[27743.445658] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[27743.445668] ata4.00: irq_stat 0x40000001
[27743.445672] ata4.00: failed command: FLUSH CACHE EXT
[27743.445675] ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 30
                        res 51/04:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
[27743.445684] ata4.00: status: { DRDY ERR }
[27743.445687] ata4.00: error: { ABRT }
[27743.445917] ata4.00: supports DRM functions and may not be fully accessible
[27743.448092] ata4.00: supports DRM functions and may not be fully accessible
[27743.449870] ata4.00: configured for UDMA/133 (device error ignored)
[27743.449879] ata4.00: device reported invalid CHS sector 0
[27743.449899] ata4: EH complete
[27743.473647] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[27743.473659] ata4.00: irq_stat 0x40000001
[27743.473662] ata4.00: failed command: FLUSH CACHE EXT
[27743.473665] ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 3
                        res 51/04:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
[27743.473674] ata4.00: status: { DRDY ERR }
[27743.473678] ata4.00: error: { ABRT }
[27743.473914] ata4.00: supports DRM functions and may not be fully accessible
[27743.475844] ata4.00: supports DRM functions and may not be fully accessible
[27743.477528] ata4.00: configured for UDMA/133 (device error ignored)
[27743.477536] ata4.00: device reported invalid CHS sector 0
[27743.477556] sd 5:0:0:0: [sdb] tag#3 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[27743.477559] sd 5:0:0:0: [sdb] tag#3 Sense Key : Illegal Request [current] 
[27743.477561] sd 5:0:0:0: [sdb] tag#3 Add. Sense: Unaligned write command
[27743.477564] sd 5:0:0:0: [sdb] tag#3 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00
[27743.477569] blk_update_request: I/O error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
[27743.477588] ata4: EH complete
[27743.477597] ata4.00: Enabling discard_zeroes_data
[27743.550086] ata4.00: Enabling discard_zeroes_data
[27743.609736] ata4: limiting SATA link speed to 1.5 Gbps
[27743.609752] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[27743.609767] ata4.00: irq_stat 0x40000001
[27743.609775] ata4.00: failed command: FLUSH CACHE EXT
[27743.609782] ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 14
                        res 51/04:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
[27743.609807] ata4.00: status: { DRDY ERR }
[27743.609815] ata4.00: error: { ABRT }
[27743.609826] ata4: hard resetting link
[27744.085706] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[27744.085978] ata4.00: supports DRM functions and may not be fully accessible
[27744.088122] ata4.00: supports DRM functions and may not be fully accessible
[27744.089898] ata4.00: configured for UDMA/133 (device error ignored)
[27744.089918] ata4.00: device reported invalid CHS sector 0
[27744.089971] ata4: EH complete
[27744.105716] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[27744.105737] ata4.00: irq_stat 0x40000001
[27744.105744] ata4.00: failed command: FLUSH CACHE EXT
[27744.105751] ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 17
                        res 51/04:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
[27744.105776] ata4.00: status: { DRDY ERR }
[27744.105785] ata4.00: error: { ABRT }
[27744.106023] ata4.00: supports DRM functions and may not be fully accessible
[27744.108100] ata4.00: supports DRM functions and may not be fully accessible
[27744.109872] ata4.00: configured for UDMA/133 (device error ignored)
[27744.109887] ata4.00: device reported invalid CHS sector 0
[27744.109920] ata4: EH complete
[27744.141714] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[27744.141732] ata4.00: irq_stat 0x40000001
[27744.141739] ata4.00: failed command: FLUSH CACHE EXT
[27744.141745] ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 19
                        res 51/04:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
[27744.141767] ata4.00: status: { DRDY ERR }
[27744.141774] ata4.00: error: { ABRT }
[27744.142011] ata4.00: supports DRM functions and may not be fully accessible
[27744.144067] ata4.00: supports DRM functions and may not be fully accessible
[27744.145836] ata4.00: configured for UDMA/133 (device error ignored)
[27744.145851] ata4.00: device reported invalid CHS sector 0
[27744.145881] ata4: EH complete
[27744.173711] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[27744.173729] ata4.00: irq_stat 0x40000001
[27744.173735] ata4.00: failed command: FLUSH CACHE EXT
[27744.173741] ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 21
                        res 51/04:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
[27744.173761] ata4.00: status: { DRDY ERR }
[27744.173768] ata4.00: error: { ABRT }
[27744.174005] ata4.00: supports DRM functions and may not be fully accessible
[27744.176072] ata4.00: supports DRM functions and may not be fully accessible
[27744.177848] ata4.00: configured for UDMA/133 (device error ignored)
[27744.177863] ata4.00: device reported invalid CHS sector 0
[27744.177903] ata4: EH complete
[27744.201713] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[27744.201730] ata4.00: irq_stat 0x40000001
[27744.201736] ata4.00: failed command: FLUSH CACHE EXT
[27744.201742] ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 23
                        res 51/04:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
[27744.201763] ata4.00: status: { DRDY ERR }
[27744.201769] ata4.00: error: { ABRT }
[27744.202003] ata4.00: supports DRM functions and may not be fully accessible
[27744.204067] ata4.00: supports DRM functions and may not be fully accessible
[27744.205833] ata4.00: configured for UDMA/133 (device error ignored)
[27744.205847] ata4.00: device reported invalid CHS sector 0
[27744.205876] ata4: EH complete
[27744.225722] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[27744.225739] ata4.00: irq_stat 0x40000001
[27744.225745] ata4.00: failed command: FLUSH CACHE EXT
[27744.225751] ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
                        res 51/04:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
[27744.225772] ata4.00: status: { DRDY ERR }
[27744.225778] ata4.00: error: { ABRT }
[27744.226017] ata4.00: supports DRM functions and may not be fully accessible
[27744.228078] ata4.00: supports DRM functions and may not be fully accessible
[27744.229845] ata4.00: configured for UDMA/133 (device error ignored)
[27744.229859] ata4.00: device reported invalid CHS sector 0
[27744.229893] sd 5:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[27744.229903] sd 5:0:0:0: [sdb] tag#0 Sense Key : Illegal Request [current] 
[27744.229911] sd 5:0:0:0: [sdb] tag#0 Add. Sense: Unaligned write command
[27744.229919] sd 5:0:0:0: [sdb] tag#0 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00
[27744.229929] blk_update_request: I/O error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
[27744.229966] ata4: EH complete
[27744.230356] ata4.00: Enabling discard_zeroes_data
[27744.254319] ata4.00: Enabling discard_zeroes_data

Running

smartctl -a /dev/sdb

gives

=== START OF INFORMATION SECTION ===
Device Model:     Samsung SSD 870 EVO 4TB
Serial Number:    [...]
LU WWN Device Id: 5 002538 f7150044f
Firmware Version: SVT01B6Q
User Capacity:    4,000,787,030,016 bytes [4.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
TRIM Command:     Available, deterministic, zeroed
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-4 T13/BSR INCITS 529 revision 5
SATA Version is:  SATA 3.3, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is:    Mon Oct 17 16:49:14 2022 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Read SMART Data failed: scsi error badly formed scsi parameters

=== START OF READ SMART DATA SECTION ===
SMART Status command failed: scsi error badly formed scsi parameters
SMART overall-health self-assessment test result: UNKNOWN!
SMART Status, Attributes and Thresholds cannot be read.

Read SMART Log Directory failed: scsi error badly formed scsi parameters

Read SMART Error Log failed: scsi error badly formed scsi parameters

Read SMART Self-test Log failed: scsi error badly formed scsi parameters

Selective Self-tests/Logging not supported

Last edited by froep (2022-10-18 17:05:51)

d_fajardo · 2022-10-18 08:00:30

After a power outage during operation, it is not detected in BIOS anymore.

Have you tried attaching it to another SATA port? If the BIOS can't detect it then I assume the softwares won't be able to access it properly neither.

froep · 2022-10-18 09:37:28

d_fajardo wrote:

After a power outage during operation, it is not detected in BIOS anymore.
Have you tried attaching it to another SATA port? If the BIOS can't detect it then I assume the softwares won't be able to access it properly neither.

Yes, I did. Same result.

sabroad · 2022-10-19 08:23:48

If the power failed whilst the SSD was updating internal block translation tables, then it could be that they're corrupted. If that's the case then: the data is (mostly) lost; and the SSD might (only) be recoverable with an OPAL (secure) erase (through BIOS) to re-initialise.

froep · 2022-10-20 10:38:40

sabroad wrote:

If the power failed whilst the SSD was updating internal block translation tables, then it could be that they're corrupted. If that's the case then: the data is (mostly) lost; and the SSD might (only) be recoverable with an OPAL (secure) erase (through BIOS) to re-initialise.

Thanks for the assessment. How would the OPAL erase work? I don't see such option in my BIOS (Intel NUC NUC7CJYH2), and as said, the SSD doesn't even show up as connected there.

Is there a way to determine that the block translation tables are actually corrupted and that this is causing the problems?

Last edited by froep (2022-10-20 11:10:37)

frostschutz · 2022-10-20 10:59:23

Is this your model? https://www.techpowerup.com/forums/thre … re.291504/

It also seems there was a firmware update available. Not sure if it would help at all.

If you don't mind erasing all data, and if your SSD has a PSID printed on the label, and if it's still detected at all in Linux when hotplugging it - you can try your luck with sedutil-cli PSIDrevert. But it may be you have to go through RMA all the same.

froep · 2022-10-21 14:53:05

frostschutz wrote:

Is this your model? https://www.techpowerup.com/forums/thre … re.291504/
It also seems there was a firmware update available. Not sure if it would help at all.
If you don't mind erasing all data, and if your SSD has a PSID printed on the label, and if it's still detected at all in Linux when hotplugging it - you can try your luck with sedutil-cli PSIDrevert. But it may be you have to go through RMA all the same.

Yes, it is. With the exception that my SSD was produced in May 2021, while the posts states that the failure "primarily affect drives produced in January/February 2021". And I am not even able to read SMART values to check.

Thanks for the pointing to the FW Update and for the the tool suggestion. I'll give both a try. It does have a PSID printed. Rescuing the data would be nice, but getting the SSD usable again is better than nothing :)

froep · 2024-01-03 00:07:57

frostschutz wrote:

If you don't mind erasing all data, and if your SSD has a PSID printed on the label, and if it's still detected at all in Linux when hotplugging it - you can try your luck with sedutil-cli PSIDrevert. But it may be you have to go through RMA all the same.

I tried to reset the SSD using

sedutil-cli --yesIreallywanttoERASEALLmydatausingthePSID $PSID $DEVICE

which failed with the following output:

Command failed on recv255
Command failed on exec 255
Properties exchange failed
Command failed on send 255
Command failed on exec 255
Session start failed rc = 255
Command failed on send 255
Command failed on exec 255
EndSession Failed

After that, I had to un-/re-plug it to make

sedutil-cli --query $DEVICE

work on it again.
Guess I'm out of options then..?

Arch Linux

#1 2022-10-18 01:22:30

SSD failure after power outage

#2 2022-10-18 08:00:30

Re: SSD failure after power outage

#3 2022-10-18 09:37:28

Re: SSD failure after power outage

#4 2022-10-19 08:23:48

Re: SSD failure after power outage

#5 2022-10-20 10:38:40

Re: SSD failure after power outage

#6 2022-10-20 10:59:23

Re: SSD failure after power outage

#7 2022-10-21 14:53:05

Re: SSD failure after power outage

#8 2024-01-03 00:07:57

Re: SSD failure after power outage

Board footer