Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
Today, 10:52 AM
|
#1
|
|
LQ Newbie
Registered: Oct 2025
Posts: 1
Rep: 
|
SSD stopped working
[ Log in to get rid of this advertisement]
After a reboot Grub couldn't find SSD. I installed ubuntu on a second drive and I can see it in the list of devices (sda):
Code:
$ lsblk
sda 8:0 0 931,5G 0 disk
├─sda1 8:1 0 512M 0 part
├─sda2 8:2 0 46,6G 0 part
├─sda3 8:3 0 651,9G 0 part
├─sda4 8:4 0 39,1G 0 part
└─sda5 8:5 0 32G 0 part
nvme0n1 259:0 0 476,9G 0 disk
├─nvme0n1p1 259:1 0 1G 0 part /boot/efi
├─nvme0n1p2 259:2 0 119,2G 0 part /
└─nvme0n1p3 259:3 0 356,7G 0 part /home
Code:
$ fdisk -x /dev/sda
Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 870
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: gpt
Disk identifier: FD704DFA-6FA0-4142-B344-C73FE8EDD72B
First usable LBA: 34
Last usable LBA: 1953525134
Alternative LBA: 1953525167
Partition entries starting LBA: 2
Allocated partition entries: 128
Partition entries ending LBA: 33
Device Start End Sectors Type-UUID UUID Name Attrs
/dev/sda1 2048 1050623 1048576 EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 E03748DE-F071-4A20-83B7-24D9597E3DAB
/dev/sda2 1050624 98707455 97656832 0FC63DAF-8483-4772-8E79-3D69D8477DE4 1385C4BA-C407-47D1-8268-961897F1336B
/dev/sda3 98707456 1465894911 1367187456 0FC63DAF-8483-4772-8E79-3D69D8477DE4 A9A562A8-3284-498E-B20E-44B003EBCA4E
/dev/sda4 1465894912 1547816959 81922048 0FC63DAF-8483-4772-8E79-3D69D8477DE4 D9BD59AE-8866-4BD8-8278-CF8C054398A5 var
/dev/sda5 1547816960 1614925823 67108864 0657FD6D-A4AB-43C4-84E5-0933C84B4F4F 4BDB390B-B446-4E0F-A188-07EADE1C58FA swap
Code:
$ smartctl -x /dev/sda
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.14.0-33-generic] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Samsung based SSDs
Device Model: Samsung SSD 870 EVO 1TB
Serial Number: S6P5NX0RB06197P
LU WWN Device Id: 5 002538 f41b43edf
Firmware Version: SVT01B6Q
User Capacity: 1,000,204,886,016 bytes [1.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: In smartctl database 7.3/5528
ATA Version is: ACS-4 T13/BSR INCITS 529 revision 5
SATA Version is: SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Thu Oct 9 18:33:58 2025 MSK
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM feature is: Unavailable
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Unavailable
ATA Security is: Disabled, frozen [SEC2]
Read SCT Status failed: scsi error badly formed scsi parameters
Wt Cache Reorder: Unknown (SCT Feature Control command failed)
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
General Purpose Log Directory Version 1
Address Access R/W Size Description
0x00 GPL R/O 1 Log Directory
0x03 GPL R/O 1 Ext. Comprehensive SMART error log
0x04 GPL R/O 8 Device Statistics log
0x07 GPL R/O 1 Extended self-test log
0x10 GPL R/O 1 NCQ Command Error log
0x11 GPL R/O 1 SATA Phy Event Counters log
0x13 GPL R/O 1 SATA NCQ Send and Receive log
0x30 GPL R/O 9 IDENTIFY DEVICE data log
0x80-0x9f GPL R/W 16 Host vendor specific log
0xe0 GPL R/W 1 SCT Command/Status
0xe1 GPL R/W 1 SCT Data Transfer
SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
Device Error Count: 633 (device log contains only the most recent 4 errors)
CR = Command Register
FEATR = Features Register
COUNT = Count (was: Sector Count) Register
LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
LH = LBA High (was: Cylinder High) Register ] LBA
LM = LBA Mid (was: Cylinder Low) Register ] Register
LL = LBA Low (was: Sector Number) Register ]
DV = Device (was: Device/Head) Register
DC = Device Control Register
ER = Error register
ST = Status register
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 633 [0] occurred at disk power-on lifetime: 18195 hours (758 days + 3 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 b0 00 00 51 bf c4 e0 40 00 Error: UNC at LBA = 0x51bfc4e0 = 1371522272
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 08 00 b0 00 00 51 bf c4 e0 40 16 10:33:59.419 READ FPDMA QUEUED
ef 00 10 00 03 00 00 00 00 00 00 40 14 10:33:59.419 SET FEATURES [Enable SATA feature]
47 00 00 00 01 00 00 00 00 03 30 40 14 10:33:59.419 READ LOG DMA EXT
47 00 00 00 01 00 00 00 00 00 30 40 14 10:33:59.419 READ LOG DMA EXT
47 00 00 00 01 00 00 00 00 00 00 40 14 10:33:59.419 READ LOG DMA EXT
Error 632 [3] occurred at disk power-on lifetime: 18195 hours (758 days + 3 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 a0 00 00 51 bf c4 e0 40 00 Error: UNC at LBA = 0x51bfc4e0 = 1371522272
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 08 00 a0 00 00 51 bf c4 e0 40 14 10:33:59.213 READ FPDMA QUEUED
61 00 08 00 b8 00 00 5a 80 2b b8 40 17 10:33:59.213 WRITE FPDMA QUEUED
61 00 10 00 b0 00 00 5a 80 2b a0 40 16 10:33:59.213 WRITE FPDMA QUEUED
ef 00 10 00 03 00 00 00 00 00 00 40 1b 10:33:59.213 SET FEATURES [Enable SATA feature]
47 00 00 00 01 00 00 00 00 03 30 40 1b 10:33:59.213 READ LOG DMA EXT
Error 631 [2] occurred at disk power-on lifetime: 18195 hours (758 days + 3 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 d8 00 00 5a 80 2b a0 40 00 Error: WP at LBA = 0x5a802ba0 = 1518349216
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
61 00 10 00 d8 00 00 5a 80 2b a0 40 1b 10:33:59.012 WRITE FPDMA QUEUED
60 00 08 00 98 00 00 51 bf c4 e0 40 13 10:33:59.012 READ FPDMA QUEUED
ea 00 00 00 00 00 00 00 00 00 00 40 0c 10:33:59.012 FLUSH CACHE EXT
61 00 08 00 60 00 00 59 a8 10 a8 40 0c 10:33:59.012 WRITE FPDMA QUEUED
ea 00 00 00 00 00 00 00 00 00 00 40 0a 10:33:59.012 FLUSH CACHE EXT
Error 630 [1] occurred at disk power-on lifetime: 18195 hours (758 days + 3 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 90 00 00 51 bf c4 e0 40 00 Error: UNC at LBA = 0x51bfc4e0 = 1371522272
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 08 00 90 00 00 51 bf c4 e0 40 12 10:33:57.082 READ FPDMA QUEUED
ef 00 10 00 03 00 00 00 00 00 00 40 06 10:33:57.082 SET FEATURES [Enable SATA feature]
47 00 00 00 01 00 00 00 00 03 30 40 06 10:33:57.082 READ LOG DMA EXT
47 00 00 00 01 00 00 00 00 00 30 40 06 10:33:57.082 READ LOG DMA EXT
47 00 00 00 01 00 00 00 00 00 00 40 06 10:33:57.082 READ LOG DMA EXT
SMART Extended Self-test Log Version: 1 (1 sectors)
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 10745 -
Selective Self-tests/Logging not supported
Read SCT Status failed: scsi error badly formed scsi parameters
Read SCT Status failed: scsi error badly formed scsi parameters
SCT (Get) Error Recovery Control command failed
Device Statistics (GP Log 0x04)
Page Offset Size Value Flags Description
0x01 ===== = = === == General Statistics (rev 1) ==
0x01 0x008 4 2098 --- Lifetime Power-On Resets
0x01 0x010 4 19073 --- Power-on Hours
0x01 0x018 6 74727473761 --- Logical Sectors Written
0x01 0x020 6 1224665415 --- Number of Write Commands
0x01 0x028 6 27930246372 --- Logical Sectors Read
0x01 0x030 6 415660788 --- Number of Read Commands
0x01 0x038 6 3274000 --- Date and Time TimeStamp
0x04 ===== = = === == General Errors Statistics (rev 1) ==
0x04 0x008 4 633 --- Number of Reported Uncorrectable Errors
0x04 0x010 4 263 --- Resets Between Cmd Acceptance and Completion
0x05 ===== = = === == Temperature Statistics (rev 1) ==
0x05 0x008 1 43 --- Current Temperature
0x05 0x020 1 53 --- Highest Temperature
0x05 0x028 1 20 --- Lowest Temperature
0x05 0x058 1 70 --- Specified Maximum Operating Temperature
0x06 ===== = = === == Transport Statistics (rev 1) ==
0x06 0x008 4 8266 --- Number of Hardware Resets
0x06 0x010 4 0 --- Number of ASR Events
0x06 0x018 4 0 --- Number of Interface CRC Errors
0x07 ===== = = === == Solid State Device Statistics (rev 1) ==
0x07 0x008 1 1 N-- Percentage Used Endurance Indicator
|||_ C monitored condition met
||__ D supports DSN
|___ N normalized value
Pending Defects log (GP Log 0x0c) not supported
SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x0001 2 0 Command failed due to ICRC error
0x0002 2 0 R_ERR response for data FIS
0x0003 2 0 R_ERR response for device-to-host data FIS
0x0004 2 0 R_ERR response for host-to-device data FIS
0x0005 2 0 R_ERR response for non-data FIS
0x0006 2 0 R_ERR response for device-to-host non-data FIS
0x0007 2 0 R_ERR response for host-to-device non-data FIS
0x0008 2 0 Device-to-host non-data FIS retries
0x0009 2 103 Transition from drive PhyRdy to drive PhyNRdy
0x000a 2 103 Device-to-host register FISes sent due to a COMRESET
0x000b 2 0 CRC errors within host-to-device FIS
0x000d 2 0 Non-CRC errors within host-to-device FIS
0x000f 2 0 R_ERR response for host-to-device data FIS, CRC
0x0010 2 0 R_ERR response for host-to-device data FIS, non-CRC
0x0012 2 0 R_ERR response for host-to-device non-data FIS, CRC
0x0013 2 0 R_ERR response for host-to-device non-data FIS, non-CRC
Code:
$ dmesg
[ 1.433586] ata1: SATA max UDMA/133 abar m2048@0xfc601000 port 0xfc601100 irq 54 lpm-pol 3
[ 1.434218] ahci 0000:06:00.1: AHCI vers 0001.0301, 32 command slots, 6 Gbps, SATA mode
[ 1.434229] ahci 0000:06:00.1: 1/1 ports implemented (port mask 0x1)
[ 1.434234] ahci 0000:06:00.1: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part
[ 1.434955] scsi host1: ahci
[ 1.895516] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1.895832] ata1.00: Model 'Samsung SSD 870 EVO 1TB', rev 'SVT01B6Q', applying quirks: noncqtrim zeroaftertrim noncqonati nolpmonati
[ 1.895954] ata1.00: failed to read native max address (err_mask=0x1)
[ 1.895964] ata1.00: HPA support seems broken, skipping HPA handling
[ 1.895972] ata1.00: supports DRM functions and may not be fully accessible
[ 1.895978] ata1.00: ATA-11: Samsung SSD 870 EVO 1TB, SVT01B6Q, max UDMA/133
[ 1.896095] ata1.00: failed to enable AA (error_mask=0x1)
[ 1.896525] ata1.00: 1953525168 sectors, multi 1: LBA48 NCQ (depth 32)
[ 1.900721] ata1.00: Features: Trust Dev-Sleep NCQ-sndrcv
[ 1.901030] ata1.00: supports DRM functions and may not be fully accessible
[ 1.901108] ata1.00: failed to enable AA (error_mask=0x1)
[ 1.906218] ata1.00: configured for UDMA/133 (device error ignored)
[ 1.916721] scsi 0:0:0:0: Direct-Access ATA Samsung SSD 870 1B6Q PQ: 0 ANSI: 5
[ 1.917568] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 1.917585] ata1.00: Enabling discard_zeroes_data
[ 1.917621] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[ 1.917650] sd 0:0:0:0: [sda] Write Protect is off
[ 1.917659] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1.917698] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.917800] sd 0:0:0:0: [sda] Preferred minimum I/O size 512 bytes
[ 1.918758] ata1.00: Enabling discard_zeroes_data
[ 1.938543] sda: sda1 sda2 sda3 sda4 sda5
[ 1.940157] sd 0:0:0:0: [sda] supports TCG Opal
[ 1.940161] sd 0:0:0:0: [sda] Attached SCSI disk
But when I run a parted I get the following error:
Code:
$ parted /dev/sda
Warning: Error fsyncing/closing /dev/sda1: Input/output error
Retry/Ignore?
Also there are a lot of errors in the log:
Code:
$ dmesg
[ 229.660412] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 229.660430] ata1.00: irq_stat 0x40000001
[ 229.660440] ata1.00: failed command: FLUSH CACHE EXT
[ 229.660447] ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 13
res 51/04:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
[ 229.660468] ata1.00: status: { DRDY ERR }
[ 229.660476] ata1.00: error: { ABRT }
[ 229.671157] ata1.00: supports DRM functions and may not be fully accessible
[ 229.671228] ata1.00: failed to enable AA (error_mask=0x1)
[ 229.677344] ata1.00: supports DRM functions and may not be fully accessible
[ 229.677420] ata1.00: failed to enable AA (error_mask=0x1)
[ 229.682302] ata1.00: configured for UDMA/133 (device error ignored)
[ 229.692906] ata1.00: device reported invalid CHS sector 0
[ 229.692943] ata1: EH complete
[ 229.947143] sd 0:0:0:0: [sda] tag#25 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[ 229.947155] sd 0:0:0:0: [sda] tag#25 Sense Key : Illegal Request [current]
[ 229.947165] sd 0:0:0:0: [sda] tag#25 Add. Sense: Unaligned write command
[ 229.947175] sd 0:0:0:0: [sda] tag#25 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00
[ 229.947186] I/O error, dev sda, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
Could you please help to fix it? |
|
|
|
|
Today, 04:04 PM
|
#2
|
|
LQ Guru
Registered: Apr 2010
Location: Continental USA
Distribution: Debian, Ubuntu, RedHat, DSL, Puppy, CentOS, Knoppix, Mint-DE, Sparky, VSIDO, tinycore, Q4OS, Manjaro
Posts: 6,534
|
It might be time to get a new SSD and restore it from your backup.
You do have a backup, yes?
|
|
|
|
|
Today, 04:44 PM
|
#3
|
|
Member
Registered: Oct 2022
Posts: 158
Rep: 
|
Have you tried a different USB cable on a different computer?
|
|
|
|
All times are GMT -5. The time now is 04:45 PM.
|
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
|
 Latest Threads
LQ News
|
|
