You are not logged in.

Pages: 1

#1 2016-02-11 13:08:02

flecha
Member
Registered: 2009-01-16
Posts: 26

HD breaking (READ FPDMA QUEUED / DRDY ERR)

Hello,

Short history:
Lost an HD with these errors and now they started to appear in the new HD after a few days of use. sad

Long history:
Some days ago I decided do expand my encrypted partition (ext4 luks dm-crypt). I started wiping the unused space in my HD following this method.
My HD had 1TB and I was wiping about 500GB. After about 5h the system freezed. Had to hold power button to shut it down. That's when the problems started. Some times, when booting, it failed to find Grub, and the times when it did, it failed to boot Arch, giving many errors about "READ FPDMA QUEUED", "DRDY ERR", ...
After booting other distros from Live DVDs/Pendrive and all giving the same errors when trying to read/write the HD, I decided to buy a new HD.
Now, after a few days reinstalling/configuring Arch in the new HD, I got that terrifying error once when booting. It didn't stopped the boot, but I fear it will get worst. sad

When wiping the old HD I used 4096 for dd blocksize, and now formated the EXT4 partition of the new HD with 4096 blocksize too (trying to make better use of Advanced Format). Not sure if this is related...

Tested the old HD in another notebook and it seems unusable there too, so it seems to be really broken and not (only) a problem with my notebook.

My notebook is an Asus K45VM (2-3 years old).

Some info using the new HD:

$ dmesg
(below only parts that seem related, errors start with "ata1")
(full log)

...
[   51.877063] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 1
[   51.948418] systemd[1]: Created slice system-systemd\x2dbacklight.slice.
[   51.964041] systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:intel_backlight...
[   52.004400] systemd[1]: Started Load/Save RF Kill Switch Status.
[   52.157731] systemd[1]: Found device ST9750420AS EFI\x20System.
[   52.233904] systemd[1]: Mounting /boot...
[   52.414997] systemd[1]: Started Load/Save Screen Backlight Brightness of backlight:intel_backlight.
[   57.450370] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   57.450840] ACPI: \_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM
[   57.450860] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   57.451165] nouveau 0000:01:00.0: DRM: suspending console...
[   57.451172] nouveau 0000:01:00.0: DRM: suspending display...
[   57.451192] nouveau 0000:01:00.0: DRM: evicting buffers...
[   57.451195] nouveau 0000:01:00.0: DRM: waiting for kernel channels to go idle...
[   57.451254] nouveau 0000:01:00.0: DRM: suspending client object trees...
[   57.451418] nouveau 0000:01:00.0: DRM: suspending kernel object tree...
[   63.526872] ata1.00: READ LOG DMA EXT failed, trying unqueued
[   68.526780] ata1.00: qc timeout (cmd 0x2f)
[   68.540110] ata1: failed to read log page 10h (errno=-5)
[   68.540169] ata1.00: exception Emask 0x1 SAct 0x38000 SErr 0x0 action 0x6 frozen
[   68.540223] ata1.00: irq_stat 0x40000008
[   68.540258] ata1.00: failed command: READ FPDMA QUEUED
[   68.540301] ata1.00: cmd 60/00:78:10:9c:11/01:00:00:00:00/40 tag 15 ncq 131072 in
                        res 40/00:80:00:1b:10/00:00:00:00:00/40 Emask 0x1 (device error)
[   68.540402] ata1.00: status: { DRDY }
[   68.540432] ata1.00: failed command: READ FPDMA QUEUED
[   68.540474] ata1.00: cmd 60/00:80:00:1b:10/01:00:00:00:00/40 tag 16 ncq 131072 in
                        res 40/00:80:00:1b:10/00:00:00:00:00/40 Emask 0x1 (device error)
[   68.540575] ata1.00: status: { DRDY }
[   68.540604] ata1.00: failed command: READ FPDMA QUEUED
[   68.540645] ata1.00: cmd 60/28:88:c0:05:19/00:00:0a:00:00/40 tag 17 ncq 20480 in
                        res 40/00:80:00:1b:10/00:00:00:00:00/40 Emask 0x1 (device error)
[   68.540746] ata1.00: status: { DRDY }
[   68.540778] ata1: hard resetting link
[   68.866776] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   68.868284] ata1.00: ACPI cmd ef/90:06:00:00:00:00 (SET FEATURES) succeeded
[   68.868293] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[   68.868297] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[   68.870744] ata1.00: ACPI cmd ef/90:06:00:00:00:00 (SET FEATURES) succeeded
[   68.870754] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[   68.870758] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[   68.871694] ata1.00: configured for UDMA/133
[   68.871747] ata1: EH complete
[   75.423690] ata1.00: exception Emask 0x0 SAct 0x400000 SErr 0x0 action 0x0
[   75.423758] ata1.00: irq_stat 0x40000008
[   75.423795] ata1.00: failed command: READ FPDMA QUEUED
[   75.423843] ata1.00: cmd 60/00:b0:10:9c:11/01:00:00:00:00/40 tag 22 ncq 131072 in
                        res 41/40:00:f8:9c:11/00:01:00:00:00/00 Emask 0x409 (media error) <F>
[   75.423957] ata1.00: status: { DRDY ERR }
[   75.423990] ata1.00: error: { UNC }
[   75.492032] ata1.00: configured for UDMA/133
[   75.492062] sd 0:0:0:0: [sda] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[   75.492067] sd 0:0:0:0: [sda] tag#22 Sense Key : 0x3 [current] [descriptor] 
[   75.492071] sd 0:0:0:0: [sda] tag#22 ASC=0x11 ASCQ=0x4 
[   75.492076] sd 0:0:0:0: [sda] tag#22 CDB: opcode=0x28 28 00 00 11 9c 10 00 01 00 00
[   75.492080] blk_update_request: I/O error, dev sda, sector 1154296
[   75.492194] ata1: EH complete
[   75.816428] systemd[1]: Mounted /boot.
[   75.818789] systemd[1]: Reached target Local File Systems.
[   93.636609] ata1.00: exception Emask 0x0 SAct 0x40000000 SErr 0x0 action 0x0
[   93.636678] ata1.00: irq_stat 0x40000008
[   93.636715] ata1.00: failed command: READ FPDMA QUEUED
[   93.636763] ata1.00: cmd 60/08:f0:f8:9c:11/00:00:00:00:00/40 tag 30 ncq 4096 in
                        res 41/40:08:f8:9c:11/00:00:00:00:00/00 Emask 0x409 (media error) <F>
[   93.641288] ata1.00: status: { DRDY ERR }
[   93.643547] ata1.00: error: { UNC }
[   93.706572] ata1.00: configured for UDMA/133
[   93.706601] sd 0:0:0:0: [sda] tag#30 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[   93.706606] sd 0:0:0:0: [sda] tag#30 Sense Key : 0x3 [current] [descriptor] 
[   93.706610] sd 0:0:0:0: [sda] tag#30 ASC=0x11 ASCQ=0x4 
[   93.706614] sd 0:0:0:0: [sda] tag#30 CDB: opcode=0x28 28 00 00 11 9c f8 00 00 08 00
[   93.706618] blk_update_request: I/O error, dev sda, sector 1154296
[   93.708792] ata1: EH complete
[   93.709296] systemd-journald[301]: /var/log/journal/9086d847d07845de8db1dd025c1a46fc/system.journal: IO error, rotating.
[  100.078769] systemd[1]: Started Journal Service.
[  100.131128] systemd-journald[301]: Received request to flush runtime journal from PID 1
[  112.332537] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
[  112.791234] r8169 0000:02:00.0 enp2s0: link down
[  112.791239] r8169 0000:02:00.0 enp2s0: link down
[  112.791301] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
...

# smartctl --all /dev/sda

smartctl 6.4 2015-06-04 r4109 [x86_64-linux-4.4.1-2-ARCH] (local build)
Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Momentus 7200.5
Device Model:     ST9750420AS
Serial Number:    6WS1HB40
LU WWN Device Id: 5 000c50 046fec17d
Firmware Version: 0002DEM1
User Capacity:    750.156.374.016 bytes [750 GB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Thu Feb 11 10:31:14 2016 BRST
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: PASSED
See vendor-specific Attribute list for marginal 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:      ( 121)	The previous self-test completed having
					the read element of the test failed.
Total time to complete Offline 
data collection: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x73) SMART execute Offline immediate.
					Auto Offline data collection on/off 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: 	 ( 148) minutes.
Conveyance self-test routine
recommended polling time: 	 (   3) minutes.
SCT capabilities: 	       (0x303f)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   098   086   006    Pre-fail  Always       -       207615422
  3 Spin_Up_Time            0x0003   098   097   085    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   084   084   020    Old_age   Always       -       17110
  5 Reallocated_Sector_Ct   0x0033   092   092   036    Pre-fail  Always       -       1397
  7 Seek_Error_Rate         0x000f   081   060   030    Pre-fail  Always       -       157986738
  9 Power_On_Hours          0x0032   093   093   000    Old_age   Always       -       6842
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   092   092   020    Old_age   Always       -       8549
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       6241
188 Command_Timeout         0x0032   100   099   000    Old_age   Always       -       8590065680
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   060   040   045    Old_age   Always   In_the_past 40 (Min/Max 26/40 #98)
191 G-Sense_Error_Rate      0x0032   097   097   000    Old_age   Always       -       7278
192 Power-Off_Retract_Count 0x0032   087   087   000    Old_age   Always       -       26413
193 Load_Cycle_Count        0x0032   068   068   000    Old_age   Always       -       64902
194 Temperature_Celsius     0x0022   040   060   000    Old_age   Always       -       40
195 Hardware_ECC_Recovered  0x001a   119   099   000    Old_age   Always       -       207615422
197 Current_Pending_Sector  0x0012   100   098   000    Old_age   Always       -       16
198 Offline_Uncorrectable   0x0010   100   098   000    Old_age   Offline      -       16
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       6715 (12 199 0)
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       547170488
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       3425180500
254 Free_Fall_Sensor        0x0032   001   001   000    Old_age   Always       -       26274

SMART Error Log Version: 1
ATA Error Count: 428 (device log contains only the most recent five errors)
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
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 428 occurred at disk power-on lifetime: 6839 hours (284 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 f8 9c 11 00  Error: UNC at LBA = 0x00119cf8 = 1154296

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 f8 9c 11 40 00      00:01:43.785  READ FPDMA QUEUED
  60 00 08 c8 9c 11 40 00      00:01:43.782  READ FPDMA QUEUED
  60 00 10 c8 7a 11 40 00      00:01:43.777  READ FPDMA QUEUED
  60 00 00 88 1d da 40 00      00:01:43.756  READ FPDMA QUEUED
  61 00 10 28 19 d0 4a 00      00:01:43.756  WRITE FPDMA QUEUED

Error 427 occurred at disk power-on lifetime: 6839 hours (284 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 f8 9c 11 00  Error: WP at LBA = 0x00119cf8 = 1154296

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 90 ff ff ff 4f 00      00:01:21.644  WRITE FPDMA QUEUED
  60 00 18 28 04 19 4a 00      00:01:21.639  READ FPDMA QUEUED
  60 00 00 10 9c 11 40 00      00:01:21.614  READ FPDMA QUEUED
  60 00 00 00 1b 10 40 00      00:01:21.614  READ FPDMA QUEUED
  60 00 28 c0 05 19 4a 00      00:01:21.613  READ FPDMA QUEUED

Error 426 occurred at disk power-on lifetime: 6839 hours (284 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 f8 9c 11 00  Error: UNC at LBA = 0x00119cf8 = 1154296

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 00 00 1b 10 40 00      00:01:05.346  READ FPDMA QUEUED
  60 00 00 10 9c 11 40 00      00:01:05.342  READ FPDMA QUEUED
  60 00 00 00 1a 10 40 00      00:01:05.337  READ FPDMA QUEUED
  60 00 88 78 97 11 40 00      00:01:05.331  READ FPDMA QUEUED
  60 00 c8 38 19 10 40 00      00:01:05.295  READ FPDMA QUEUED

Error 425 occurred at disk power-on lifetime: 6827 hours (284 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 80 74 1b 00  Error: UNC at LBA = 0x001b7480 = 1799296

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 00 00 1b 10 40 00      01:04:25.008  READ FPDMA QUEUED
  60 00 08 80 74 1b 40 00      01:04:25.001  READ FPDMA QUEUED
  60 00 00 00 1a 10 40 00      01:04:24.990  READ FPDMA QUEUED
  60 00 c8 38 19 10 40 00      01:04:24.980  READ FPDMA QUEUED
  60 00 d0 60 50 11 40 00      01:04:24.978  READ FPDMA QUEUED

Error 424 occurred at disk power-on lifetime: 6827 hours (284 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 80 74 1b 00  Error: UNC at LBA = 0x001b7480 = 1799296

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 ff ff ff 4f 00      01:04:19.774  READ FPDMA QUEUED
  60 00 a8 ff ff ff 4f 00      01:04:19.774  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      01:04:19.773  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      01:04:19.769  READ FPDMA QUEUED
  60 00 18 00 1f 94 4a 00      01:04:19.768  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%      6841         1154296
# 2  Short offline       Completed: read failure       90%      6733         13130496
# 3  Short offline       Completed: read failure       90%      6461         119999656
# 4  Short offline       Completed without error       00%      2050         -
# 5  Short offline       Completed without error       00%      1935         -
# 6  Short offline       Completed without error       00%      1786         -
# 7  Short offline       Completed without error       00%      1608         -
# 8  Short offline       Completed without error       00%      1434         -
# 9  Short offline       Completed without error       00%      1194         -
#10  Short offline       Completed without error       00%       873         -
#11  Short offline       Completed without error       00%       486         -
#12  Short offline       Completed without error       00%       333         -
#13  Short offline       Completed without error       00%       263         -
#14  Short offline       Completed without error       00%         0         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

# fdisk -l

Disk /dev/sda: 698.7 GiB, 750156374016 bytes, 1465149168 sectors
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: 6BDF8FA1-4150-443D-A742-D763E75F9CF3

Device       Start        End    Sectors   Size Type
/dev/sda1     2048    1048576    1046529   511M EFI System
/dev/sda2  1050624 1258291200 1257240577 599.5G Linux filesystem

Disk /dev/mapper/nevoeiro: 599.5 GiB, 643705078272 bytes, 1257236481 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

I fear my notebook or an installed software is breaking the HDs... sad

Another worry: the SMART test says "Power_On_Hours: 6842", isn't that strange for a new HD? Can it be they sold me an used one?

Thanks for the attention.

Offline

#2 2016-02-11 13:19:14

x33a
Forum Fellow
Registered: 2009-08-15
Posts: 4,587

Re: HD breaking (READ FPDMA QUEUED / DRDY ERR)

Not just the power on hours, even the start/stop count says 17110. So unless the SMART values are horribly broken, I believe that you have received a used hard drive. You should talk to the vendor.

Offline

#3 2016-02-11 13:25:12

frostschutz
Member
Registered: 2013-11-15
Posts: 1,647

Re: HD breaking (READ FPDMA QUEUED / DRDY ERR)

The drive is toast in any case.

Offline

#4 2016-02-11 16:03:39

mich41
Member
Registered: 2012-06-22
Posts: 796

Re: HD breaking (READ FPDMA QUEUED / DRDY ERR)

And 1397 reallocated sectors and 3 failed self-tests? Definitely a scam.

Offline

#5 2016-02-11 17:08:22

flecha
Member
Registered: 2009-01-16
Posts: 26

Re: HD breaking (READ FPDMA QUEUED / DRDY ERR)

Thanks!
I went back to the store and the guy told me he'll change the HD for a new one...

I did a long test, but it seems to give no new info:

smartctl 6.4 2015-06-04 r4109 [x86_64-linux-4.4.1-2-ARCH] (local build)
Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Momentus 7200.5
Device Model:     ST9750420AS
Serial Number:    6WS1HB40
LU WWN Device Id: 5 000c50 046fec17d
Firmware Version: 0002DEM1
User Capacity:    750.156.374.016 bytes [750 GB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Thu Feb 11 14:59:56 2016 BRST
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: PASSED
See vendor-specific Attribute list for marginal 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: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x73) SMART execute Offline immediate.
					Auto Offline data collection on/off 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: 	 ( 148) minutes.
Conveyance self-test routine
recommended polling time: 	 (   3) minutes.
SCT capabilities: 	       (0x303f)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   098   086   006    Pre-fail  Always       -       223832750
  3 Spin_Up_Time            0x0003   098   097   085    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   084   084   020    Old_age   Always       -       17112
  5 Reallocated_Sector_Ct   0x0033   092   092   036    Pre-fail  Always       -       1397
  7 Seek_Error_Rate         0x000f   081   060   030    Pre-fail  Always       -       158007238
  9 Power_On_Hours          0x0032   093   093   000    Old_age   Always       -       6846
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   092   092   020    Old_age   Always       -       8550
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       6241
188 Command_Timeout         0x0032   100   099   000    Old_age   Always       -       8590065680
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   063   040   045    Old_age   Always   In_the_past 37 (0 98 37 33 0)
191 G-Sense_Error_Rate      0x0032   097   097   000    Old_age   Always       -       7278
192 Power-Off_Retract_Count 0x0032   087   087   000    Old_age   Always       -       26413
193 Load_Cycle_Count        0x0032   068   068   000    Old_age   Always       -       65096
194 Temperature_Celsius     0x0022   037   060   000    Old_age   Always       -       37
195 Hardware_ECC_Recovered  0x001a   119   099   000    Old_age   Always       -       223832750
197 Current_Pending_Sector  0x0012   100   098   000    Old_age   Always       -       16
198 Offline_Uncorrectable   0x0010   100   098   000    Old_age   Offline      -       16
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       6718 (23 122 0)
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       3290289592
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       2230062021
254 Free_Fall_Sensor        0x0032   001   001   000    Old_age   Always       -       26274

SMART Error Log Version: 1
ATA Error Count: 428 (device log contains only the most recent five errors)
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
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 428 occurred at disk power-on lifetime: 6839 hours (284 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 f8 9c 11 00  Error: UNC at LBA = 0x00119cf8 = 1154296

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 f8 9c 11 40 00      00:01:43.785  READ FPDMA QUEUED
  60 00 08 c8 9c 11 40 00      00:01:43.782  READ FPDMA QUEUED
  60 00 10 c8 7a 11 40 00      00:01:43.777  READ FPDMA QUEUED
  60 00 00 88 1d da 40 00      00:01:43.756  READ FPDMA QUEUED
  61 00 10 28 19 d0 4a 00      00:01:43.756  WRITE FPDMA QUEUED

Error 427 occurred at disk power-on lifetime: 6839 hours (284 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 f8 9c 11 00  Error: WP at LBA = 0x00119cf8 = 1154296

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 90 ff ff ff 4f 00      00:01:21.644  WRITE FPDMA QUEUED
  60 00 18 28 04 19 4a 00      00:01:21.639  READ FPDMA QUEUED
  60 00 00 10 9c 11 40 00      00:01:21.614  READ FPDMA QUEUED
  60 00 00 00 1b 10 40 00      00:01:21.614  READ FPDMA QUEUED
  60 00 28 c0 05 19 4a 00      00:01:21.613  READ FPDMA QUEUED

Error 426 occurred at disk power-on lifetime: 6839 hours (284 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 f8 9c 11 00  Error: UNC at LBA = 0x00119cf8 = 1154296

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 00 00 1b 10 40 00      00:01:05.346  READ FPDMA QUEUED
  60 00 00 10 9c 11 40 00      00:01:05.342  READ FPDMA QUEUED
  60 00 00 00 1a 10 40 00      00:01:05.337  READ FPDMA QUEUED
  60 00 88 78 97 11 40 00      00:01:05.331  READ FPDMA QUEUED
  60 00 c8 38 19 10 40 00      00:01:05.295  READ FPDMA QUEUED

Error 425 occurred at disk power-on lifetime: 6827 hours (284 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 80 74 1b 00  Error: UNC at LBA = 0x001b7480 = 1799296

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 00 00 1b 10 40 00      01:04:25.008  READ FPDMA QUEUED
  60 00 08 80 74 1b 40 00      01:04:25.001  READ FPDMA QUEUED
  60 00 00 00 1a 10 40 00      01:04:24.990  READ FPDMA QUEUED
  60 00 c8 38 19 10 40 00      01:04:24.980  READ FPDMA QUEUED
  60 00 d0 60 50 11 40 00      01:04:24.978  READ FPDMA QUEUED

Error 424 occurred at disk power-on lifetime: 6827 hours (284 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 80 74 1b 00  Error: UNC at LBA = 0x001b7480 = 1799296

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 ff ff ff 4f 00      01:04:19.774  READ FPDMA QUEUED
  60 00 a8 ff ff ff 4f 00      01:04:19.774  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      01:04:19.773  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      01:04:19.769  READ FPDMA QUEUED
  60 00 18 00 1f 94 4a 00      01:04:19.768  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       90%      6844         1154296
# 2  Short offline       Completed: read failure       90%      6841         1154296
# 3  Short offline       Completed: read failure       90%      6733         13130496
# 4  Short offline       Completed: read failure       90%      6461         119999656
# 5  Short offline       Completed without error       00%      2050         -
# 6  Short offline       Completed without error       00%      1935         -
# 7  Short offline       Completed without error       00%      1786         -
# 8  Short offline       Completed without error       00%      1608         -
# 9  Short offline       Completed without error       00%      1434         -
#10  Short offline       Completed without error       00%      1194         -
#11  Short offline       Completed without error       00%       873         -
#12  Short offline       Completed without error       00%       486         -
#13  Short offline       Completed without error       00%       333         -
#14  Short offline       Completed without error       00%       263         -
#15  Short offline       Completed without error       00%         0         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
frostschutz wrote:

The drive is toast in any case.

You mean about the high temperature? We are in summer here... =P
Can it be related to the HD crashes? I'm used to monitor CPU temperature, but not HD temperature...

Offline

#6 2016-02-11 17:10:56

alphaniner
Member
From: Ancapistan
Registered: 2010-07-12
Posts: 2,810

Re: HD breaking (READ FPDMA QUEUED / DRDY ERR)

flecha wrote:

Thanks!
I went back to the store and the guy told me he'll change the HD for a new one...

I did a long test, but it seems to give no new info

Here's the new info:

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       90%      6844         1154296

Last edited by alphaniner (2016-02-11 17:11:07)

But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner

Offline

#7 2016-02-11 17:26:06

flecha
Member
Registered: 2009-01-16
Posts: 26

Re: HD breaking (READ FPDMA QUEUED / DRDY ERR)

Thanks, alphaniner. I saw that line too, but it doesn't seem to help much, since the short test already gave pretty much the same result:

Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 2  Short offline       Completed: read failure       90%      6841         1154296

And I'm still worried about the causes of the errors. Maybe it's just a coincidence that the old HD crashed and the (fake) new one gave a similar error. But maybe the problem is at another place (a bugged driver, notebook motherboard, too high temperature, ...). So changing the HD will only give me more work to reinstall everything, but crash the HD in a few days again. sad

Offline

#8 2016-02-11 18:26:27

flecha
Member
Registered: 2009-01-16
Posts: 26

Re: HD breaking (READ FPDMA QUEUED / DRDY ERR)

frostschutz, I found what seems to be the current HD specs, and it seems to operate up to 60C (PDF page 19, Document page 13). So the current 40C wouldn't be a problem. Did I understand right?

Offline

#9 2016-02-11 18:28:00

alphaniner
Member
From: Ancapistan
Registered: 2010-07-12
Posts: 2,810

Re: HD breaking (READ FPDMA QUEUED / DRDY ERR)

The drive was demonstrably bad when the short test failed at POH 6461. Have you used it long enough to have added about 15 days worth of POH?

Yes, you should see if you can find a way to prevent the drive overheating. But like the others I suspect you just got a lemon and the similar errors are a coincidence. That or the SATA controller itself has issues, but not such that I'd suspect it of damaging drives.

But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner

Offline

#10 2016-02-12 13:09:42

flecha
Member
Registered: 2009-01-16
Posts: 26

Re: HD breaking (READ FPDMA QUEUED / DRDY ERR)

alphaniner wrote:

The drive was demonstrably bad when the short test failed at POH 6461. Have you used it long enough to have added about 15 days worth of POH?

No, today is my 7th day with it. So that first failed short test was done before I even got the HD.

Offline

Pages: 1

Board footer

Powered by FluxBB