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.
|
 |
07-23-2019, 11:12 PM
|
#1
|
|
Member
Registered: Sep 2004
Distribution: Slackware 15, Devuan, Void
Posts: 273
Rep: 
|
SATA Hard Disk read error
i received a WD 1TB SATA hard disk last week and was told that it contains errors.
anyway, i messed with it for a while and found that i couldn't boot this disk (i was told it has windows Os installed) so i check it with 'smartctl' in linux.
here are the results - disk is /dev/sda:
Code:
[erdos@quantum ~]$ sudo fdisk -l
Password:
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10SPZX-24Z
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: B38D5E9C-2F0B-4BE1-B387-2881A97E58B9
Device Start End Sectors Size Type
/dev/sda1 2048 534527 532480 260M EFI System
/dev/sda2 534528 567295 32768 16M Microsoft reserved
/dev/sda3 567296 1899046911 1898479616 905.3G Microsoft basic data
/dev/sda4 1899046912 1951475711 52428800 25G Microsoft basic data
/dev/sda5 1951475712 1953523711 2048000 1000M Windows recovery environment
Disk /dev/sdb: 9.5 GiB, 10202050560 bytes, 19925880 sectors
Disk model: QUANTUM FIREBALL
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: 0x00510051
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 19925879 19923832 9.5G 83 Linux
[erdos@quantum ~]$ su
Password:
sh-5.0# smartctl -i /dev/sda
smartctl 7.0 2018-12-30 r4883 [i686-linux-4.19.42_1] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: WDC WD10SPZX-24Z10
Serial Number: WD-WX11A78H3ZNA
LU WWN Device Id: 5 0014ee 6b37f2892
Firmware Version: 04.01A04
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-3 T13/2161-D revision 5
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is: Wed Jan 1 22:51:10 2003 EST
SMART support is: Available - device has SMART capability.
SMART support is: Disabled
sh-5.0# smartctl -s on -d ata /dev/sda
smartctl 7.0 2018-12-30 r4883 [i686-linux-4.19.42_1] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.
sh-5.0# smartctl -d ata -H /dev/sda
smartctl 7.0 2018-12-30 r4883 [i686-linux-4.19.42_1] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: FAILED!
Drive failure expected in less than 24 hours. SAVE ALL DATA.
Failed Attributes:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 001 001 051 Pre-fail Always FAILING_NOW 24915
sh-5.0# smartctl --attributes --log=selftest /dev/sda
smartctl 7.0 2018-12-30 r4883 [i686-linux-4.19.42_1] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 001 001 051 Pre-fail Always FAILING_NOW 24915
3 Spin_Up_Time 0x0027 195 192 021 Pre-fail Always - 1225
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 440
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 129
10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 149
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 1840
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 40
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 455
194 Temperature_Celsius 0x0022 105 091 000 Old_age Always - 38 (Min/Max 3/52)
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 145
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0
206 Flying_Height 0x0022 100 000 000 Old_age Always - 4
240 Head_Flying_Hours 0x0032 100 100 000 Old_age Always - 126
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
sh-5.0# smartctl -d ata -a /dev/sda
smartctl 7.0 2018-12-30 r4883 [i686-linux-4.19.42_1] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: WDC WD10SPZX-24Z10
Serial Number: WD-WX11A78H3ZNA
LU WWN Device Id: 5 0014ee 6b37f2892
Firmware Version: 04.01A04
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-3 T13/2161-D revision 5
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is: Tue Jul 23 23:56:11 2019 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: FAILED!
Drive failure expected in less than 24 hours. SAVE ALL DATA.
See vendor-specific Attribute list for failed Attributes.
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 480) seconds.
Offline data collection
capabilities: (0x71) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 104) minutes.
Conveyance self-test routine
recommended polling time: ( 4) minutes.
SCT capabilities: (0x303d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
is this HDD salvageable or going to trash bin? |
|
|
|
|
07-24-2019, 02:01 AM
|
#2
|
|
Senior Member
Registered: Mar 2009
Location: Earth, unfortunately...
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,881
|
If it's failed the SMART test, that's not a good sign.
You can see if libata is reporting problems with it;
Code:
dmesg | grep -i ata
If that's also reporting problems with the same drive, then I'd say that would all but confirm it's toast. Try to read files on it, then run the command above.
In any case, I would do what smartctl is telling you: BACKUP anything on that drive you want to keep.
You can also read this to get a better understanding for smartctl reports. |
|
|
|
|
08-03-2019, 07:21 AM
|
#3
|
|
Member
Registered: Sep 2004
Distribution: Slackware 15, Devuan, Void
Posts: 273
Original Poster
Rep:
|
here's the output of
Code:
dmesg | grep -i ata
Code:
[erdos@quantum ~]$ sudo dmesg | grep -i ata
[ 0.000000] BIOS-e820: [mem 0x000000007fff3000-0x000000007fffffff] ACPI data
[ 2.174275] Memory: 1941672K/2096696K available (7076K kernel code, 381K rwda ta, 1836K rodata, 600K init, 792K bss, 155024K reserved, 0K cma-reserved, 118983 2K highmem)
.data : 0xcd6e910c - 0xcd915740 (2225 kB)
[ 4.157930] Write protecting the kernel read-only data: 1840k
[ 4.157931] NX-protecting the kernel data: 3160k
[ 4.158076] mark_rodata_ro+0xfd/0x105
[ 4.889721] libata version 3.00 loaded.
[ 4.898253] pata_amd 0000:00:08.0: version 0.4.1
[ 4.899358] sata_nv 0000:00:09.0: version 3.5
[ 4.909152] scsi host0: sata_nv
[ 4.913656] scsi host1: sata_nv
[ 4.913847] ata3: SATA max UDMA/133 cmd 0x9e0 ctl 0xbe0 bmdma 0xc800 irq 20
[ 4.913849] ata4: SATA max UDMA/133 cmd 0x960 ctl 0xb60 bmdma 0xc808 irq 20
[ 4.919060] scsi host2: pata_amd
[ 4.923664] scsi host3: sata_nv
[ 4.923955] scsi host4: pata_amd
[ 4.924079] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xdc00 irq 14
[ 4.924081] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xdc08 irq 15
[ 4.927674] scsi host5: sata_nv
[ 4.927832] ata5: SATA max UDMA/133 cmd 0x9f0 ctl 0xbf0 bmdma 0xb000 irq 23
[ 4.927834] ata6: SATA max UDMA/133 cmd 0x970 ctl 0xb70 bmdma 0xb008 irq 23
[ 5.098149] ata1.00: ATA-5: QUANTUM FIREBALLP LM10.2, A35.0700, max UDMA/66
[ 5.098152] ata1.00: 19925880 sectors, multi 16: LBA
[ 5.098162] ata1: nv_mode_filter: 0x1f39f&0x1f39f->0x1f39f, BIOS=0x1f000 (0xc 500c0c5) ACPI=0x1f01f (30:120:0x1b)
[ 5.243800] ata5: SATA link down (SStatus 0 SControl 300)
[ 5.374638] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 5.412405] ata3.00: ATA-10: WDC WD10SPZX-24Z10, 04.01A04, max UDMA/133
[ 5.412407] ata3.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
[ 5.414812] ata3.00: configured for UDMA/133
[ 5.415102] scsi 0:0:0:0: Direct-Access ATA WDC WD10SPZX-24Z 1A04 PQ : 0 ANSI: 5
[ 5.723985] ata4: SATA link down (SStatus 0 SControl 300)
[ 5.724322] scsi 2:0:0:0: Direct-Access ATA QUANTUM FIREBALL 0700 PQ: 0 ANSI: 5
[ 6.072863] ata2.00: ATAPI: HL-DT-ST CD-RW/DVD-ROM GCC-4482B, E107, max UDMA/33
[ 6.072871] ata2.01: ATAPI: DVDRW DRW-5S163, YSG5, max UDMA/66
[ 6.072880] ata2: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc500c0c5) ACPI=0x701f (60:30:0x1f)
[ 6.072884] ata2: nv_mode_filter: 0x1f39f&0x1f39f->0x1f39f, BIOS=0x1f000 (0xc500c0c5) ACPI=0x1f01f (60:30:0x1f)
[ 6.451984] ata6: SATA link down (SStatus 0 SControl 300)
[ 9.837277] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[ 10.215272] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[ 32.438714] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 619.894680] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 619.894688] ata3.00: BMDMA stat 0x25
[ 619.894692] ata3.00: failed command: READ DMA
[ 619.894699] ata3.00: cmd c8/00:00:a0:c0:67/00:00:00:00:00/e0 tag 0 dma 131072 in
[ 619.894703] ata3.00: status: { DRDY ERR }
[ 619.894705] ata3.00: error: { UNC }
[ 620.034068] ata3.00: configured for UDMA/133
[ 620.034167] ata3: EH complete
[ 623.871653] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 623.871661] ata3.00: BMDMA stat 0x25
[ 623.871666] ata3.00: failed command: READ DMA
[ 623.871673] ata3.00: cmd c8/00:00:a0:c3:67/00:00:00:00:00/e0 tag 0 dma 131072 in
[ 623.871677] ata3.00: status: { DRDY ERR }
[ 623.871679] ata3.00: error: { UNC }
[ 624.007174] ata3.00: configured for UDMA/133
[ 624.007268] ata3: EH complete
[ 626.848673] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 626.848681] ata3.00: BMDMA stat 0x25
[ 626.848685] ata3.00: failed command: READ DMA
[ 626.848692] ata3.00: cmd c8/00:01:18:c4:67/00:00:00:00:00/e0 tag 0 dma 512 in
[ 626.848696] ata3.00: status: { DRDY ERR }
[ 626.848698] ata3.00: error: { UNC }
[ 626.984169] ata3.00: configured for UDMA/133
[ 626.984262] ata3: EH complete
[ 629.838655] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 629.838663] ata3.00: BMDMA stat 0x25
[ 629.838667] ata3.00: failed command: READ DMA
[ 629.838674] ata3.00: cmd c8/00:01:19:c4:67/00:00:00:00:00/e0 tag 0 dma 512 in
[ 629.838678] ata3.00: status: { DRDY ERR }
[ 629.838680] ata3.00: error: { UNC }
[ 629.974159] ata3.00: configured for UDMA/133
[ 629.974248] ata3: EH complete
[ 632.814701] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 632.814709] ata3.00: BMDMA stat 0x25
[ 632.814713] ata3.00: failed command: READ DMA
[ 632.814721] ata3.00: cmd c8/00:06:1a:c4:67/00:00:00:00:00/e0 tag 0 dma 3072 in
[ 632.814724] ata3.00: status: { DRDY ERR }
[ 632.814726] ata3.00: error: { UNC }
[ 632.950204] ata3.00: configured for UDMA/133
[ 632.950406] ata3: EH complete
[ 635.792647] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 635.792655] ata3.00: BMDMA stat 0x25
[ 635.792659] ata3.00: failed command: READ DMA
[ 635.792666] ata3.00: cmd c8/00:08:18:c4:67/00:00:00:00:00/e0 tag 0 dma 4096 in
[ 635.792670] ata3.00: status: { DRDY ERR }
[ 635.792672] ata3.00: error: { UNC }
[ 635.928202] ata3.00: configured for UDMA/133
[ 635.928520] ata3: EH complete
[ 638.838645] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 638.838653] ata3.00: BMDMA stat 0x25
[ 638.838657] ata3.00: failed command: READ DMA
[ 638.838664] ata3.00: cmd c8/00:08:18:c4:67/00:00:00:00:00/e0 tag 0 dma 4096 in
[ 638.838668] ata3.00: status: { DRDY ERR }
[ 638.838670] ata3.00: error: { UNC }
[ 638.974172] ata3.00: configured for UDMA/133
[ 638.974280] ata3: EH complete
[erdos@quantum ~]$ sudo dmesg | grep -i ata
[ 0.000000] BIOS-e820: [mem 0x000000007fff3000-0x000000007fffffff] ACPI data
[ 2.174275] Memory: 1941672K/2096696K available (7076K kernel code, 381K rwdata, 1836K rodata, 600K init, 792K bss, 155024K reserved, 0K cma-reserved, 1189832K highmem)
.data : 0xcd6e910c - 0xcd915740 (2225 kB)
[ 4.157930] Write protecting the kernel read-only data: 1840k
[ 4.157931] NX-protecting the kernel data: 3160k
[ 4.158076] mark_rodata_ro+0xfd/0x105
[ 4.889721] libata version 3.00 loaded.
[ 4.898253] pata_amd 0000:00:08.0: version 0.4.1
[ 4.899358] sata_nv 0000:00:09.0: version 3.5
[ 4.909152] scsi host0: sata_nv
[ 4.913656] scsi host1: sata_nv
[ 4.913847] ata3: SATA max UDMA/133 cmd 0x9e0 ctl 0xbe0 bmdma 0xc800 irq 20
[ 4.913849] ata4: SATA max UDMA/133 cmd 0x960 ctl 0xb60 bmdma 0xc808 irq 20
[ 4.919060] scsi host2: pata_amd
[ 4.923664] scsi host3: sata_nv
[ 4.923955] scsi host4: pata_amd
[ 4.924079] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xdc00 irq 14
[ 4.924081] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xdc08 irq 15
[ 4.927674] scsi host5: sata_nv
[ 4.927832] ata5: SATA max UDMA/133 cmd 0x9f0 ctl 0xbf0 bmdma 0xb000 irq 23
[ 4.927834] ata6: SATA max UDMA/133 cmd 0x970 ctl 0xb70 bmdma 0xb008 irq 23
[ 5.098149] ata1.00: ATA-5: QUANTUM FIREBALLP LM10.2, A35.0700, max UDMA/66
[ 5.098152] ata1.00: 19925880 sectors, multi 16: LBA
[ 5.098162] ata1: nv_mode_filter: 0x1f39f&0x1f39f->0x1f39f, BIOS=0x1f000 (0xc500c0c5) ACPI=0x1f01f (30:120:0x1b)
[ 5.243800] ata5: SATA link down (SStatus 0 SControl 300)
[ 5.374638] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 5.412405] ata3.00: ATA-10: WDC WD10SPZX-24Z10, 04.01A04, max UDMA/133
[ 5.412407] ata3.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
[ 5.414812] ata3.00: configured for UDMA/133
[ 5.415102] scsi 0:0:0:0: Direct-Access ATA WDC WD10SPZX-24Z 1A04 PQ: 0 ANSI: 5
[ 5.723985] ata4: SATA link down (SStatus 0 SControl 300)
[ 5.724322] scsi 2:0:0:0: Direct-Access ATA QUANTUM FIREBALL 0700 PQ: 0 ANSI: 5
[ 6.072863] ata2.00: ATAPI: HL-DT-ST CD-RW/DVD-ROM GCC-4482B, E107, max UDMA/33
[ 6.072871] ata2.01: ATAPI: DVDRW DRW-5S163, YSG5, max UDMA/66
[ 6.072880] ata2: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc500c0c5) ACPI=0x701f (60:30:0x1f)
[ 6.072884] ata2: nv_mode_filter: 0x1f39f&0x1f39f->0x1f39f, BIOS=0x1f000 (0xc500c0c5) ACPI=0x1f01f (60:30:0x1f)
[ 6.451984] ata6: SATA link down (SStatus 0 SControl 300)
9.837277] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[ 10.215272] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[ 32.438714] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 619.894680] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 619.894688] ata3.00: BMDMA stat 0x25
[ 619.894692] ata3.00: failed command: READ DMA
[ 619.894699] ata3.00: cmd c8/00:00:a0:c0:67/00:00:00:00:00/e0 tag 0 dma 131072 in
[ 619.894703] ata3.00: status: { DRDY ERR }
[ 619.894705] ata3.00: error: { UNC }
[ 620.034068] ata3.00: configured for UDMA/133
[ 620.034167] ata3: EH complete
[ 623.871653] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 623.871661] ata3.00: BMDMA stat 0x25
[ 623.871666] ata3.00: failed command: READ DMA
[ 623.871673] ata3.00: cmd c8/00:00:a0:c3:67/00:00:00:00:00/e0 tag 0 dma 131072 in
[ 623.871677] ata3.00: status: { DRDY ERR }
[ 623.871679] ata3.00: error: { UNC }
[ 624.007174] ata3.00: configured for UDMA/133
[ 624.007268] ata3: EH complete
[ 626.848673] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 626.848681] ata3.00: BMDMA stat 0x25
[ 626.848685] ata3.00: failed command: READ DMA
[ 626.848692] ata3.00: cmd c8/00:01:18:c4:67/00:00:00:00:00/e0 tag 0 dma 512 in
[ 626.848696] ata3.00: status: { DRDY ERR }
[ 626.848698] ata3.00: error: { UNC }
[ 626.984169] ata3.00: configured for UDMA/133
[ 626.984262] ata3: EH complete
[ 629.838655] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 629.838663] ata3.00: BMDMA stat 0x25
[ 629.838667] ata3.00: failed command: READ DMA
[ 629.838674] ata3.00: cmd c8/00:01:19:c4:67/00:00:00:00:00/e0 tag 0 dma 512 in
[ 629.838678] ata3.00: status: { DRDY ERR }
[ 629.838680] ata3.00: error: { UNC }
[ 629.974159] ata3.00: configured for UDMA/133
[ 629.974248] ata3: EH complete
[ 632.814701] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 632.814709] ata3.00: BMDMA stat 0x25
[ 632.814713] ata3.00: failed command: READ DMA
[ 632.814721] ata3.00: cmd c8/00:06:1a:c4:67/00:00:00:00:00/e0 tag 0 dma 3072 in
[ 632.814724] ata3.00: status: { DRDY ERR }
[ 632.814726] ata3.00: error: { UNC }
[ 632.950204] ata3.00: configured for UDMA/133
[ 632.950406] ata3: EH complete
[ 635.792647] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 635.792655] ata3.00: BMDMA stat 0x25
[ 635.792659] ata3.00: failed command: READ DMA
[ 635.792666] ata3.00: cmd c8/00:08:18:c4:67/00:00:00:00:00/e0 tag 0 dma 4096 in
[ 635.792670] ata3.00: status: { DRDY ERR }
[ 635.792672] ata3.00: error: { UNC }
[ 635.928202] ata3.00: configured for UDMA/133
[ 635.928520] ata3: EH complete
[ 638.838645] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 638.838653] ata3.00: BMDMA stat 0x25
[ 638.838657] ata3.00: failed command: READ DMA
[ 638.838664] ata3.00: cmd c8/00:08:18:c4:67/00:00:00:00:00/e0 tag 0 dma 4096 in
[ 638.838668] ata3.00: status: { DRDY ERR }
[ 638.838670] ata3.00: error: { UNC }
[ 638.974172] ata3.00: configured for UDMA/133
[ 638.974280] ata3: EH complete
ata3 is the problematic drive, looks like a complete toast :| |
|
|
|
|
08-05-2019, 10:38 AM
|
#4
|
|
Senior Member
Registered: Mar 2009
Location: Earth, unfortunately...
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,881
|
Yeah, it doesn't look good. While it could just be bad sectors, given the smartctl report, I'd say it's very likely failing. It's worth noting that even if the smartctl report wasn't reporting any failed attributes, that doesn't mean the drive itself isn't failing.
The last drive I had that failed didn't report any failed attributes in it's SMART status. At first I noticed that all the files had suddenly disappeared, with just a bunch of empty folders left (that most certainly had files in them beforehand), and then the device node disappeared altogether (libata was reporting errors with the same drive while all of this was happening). The drive also made clicking sounds right before the device node disappeared altogether as well. From start to finish, it was probably no more than maybe an hour or two - if even that.
In any case, you can have a look at this for more info about libata's error messages in your kernel log. |
|
|
|
|
06-06-2020, 05:34 AM
|
#5
|
|
LQ Newbie
Registered: Jun 2020
Posts: 2
Rep: 
|
Quote:
Originally Posted by jsbjsb001
Yeah, it doesn't look good. While it could just be bad sectors, given the smartctl report, I'd say it's very likely failing. It's worth noting that even if the smartctl report wasn't reporting any failed attributes, that doesn't mean the drive itself isn't failing.
The last drive I had that failed didn't report any failed attributes in it's SMART status. At first I noticed that all the files had suddenly disappeared, with just a bunch of empty folders left (that most certainly had files in them beforehand), and then the device node disappeared altogether (libata was reporting errors with the same drive while all of this was happening). The drive also made clicking sounds right before the device node disappeared altogether as well. From start to finish, it was probably no more than maybe an hour or two - if even that. PrepaidCardStatus
In any case, you can have a look at for more info about libata's error messages in your kernel log. |
Thank you so much for your great information, It is too useful for me.
Last edited by evocategh; 06-08-2020 at 02:11 AM.
|
|
|
|
|
06-06-2020, 08:01 AM
|
#6
|
|
Senior Member
Registered: Jan 2007
Location: Wild West Wales, UK
Distribution: Linux Mint 22 MATE, Peppermint OS-Devuan, EndeavourOS, antiX
Posts: 4,359
|
xiongnu,
The report from #197 Current Pending Sector Count shows a figure of 145 which indicates imminent drive failure. Bin the drive.
|
|
|
|
All times are GMT -5. The time now is 04:30 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
|
|
