You are not logged in.

Pages: 1

#1 2012-08-16 15:56:45

lspci
Member
From: Virginia, USA
Registered: 2012-06-09
Posts: 242

[Solved] READ FPDMA QUEUED (DRDY ERR) -- Toshiba MK2555GSX HDD Error

I'm afraid that my Hard Drive's gonna be failing soon, but I'm not sure.  I don't know what a READ FPDMA QUEUED MEDIA ERROR means, so I'm goggling it right now somewhat apprehensively. 

here's the error(s) as smartctl recorded them 

SMART Error Log Version: 1
ATA Error Count: 2978 (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 2978 occurred at disk power-on lifetime: 17926 hours (746 days + 22 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 41 02 3c f5 4e 60  Error: UNC at LBA = 0x004ef53c = 5174588

  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 08 00 38 f5 4e 40 08      01:44:58.612  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      01:44:58.612  SET FEATURES [Reserved for Serial ATA]
  ec 00 00 00 00 00 a0 00      01:44:58.611  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      01:44:58.611  SET FEATURES [Set transfer mode]
  ef 10 02 00 00 00 a0 00      01:44:58.611  SET FEATURES [Reserved for Serial ATA]

Error 2977 occurred at disk power-on lifetime: 17926 hours (746 days + 22 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 41 02 3c f5 4e 60  Error: UNC at LBA = 0x004ef53c = 5174588

  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 08 00 38 f5 4e 40 08      01:44:54.778  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      01:44:54.778  SET FEATURES [Reserved for Serial ATA]
  ec 00 00 00 00 00 a0 00      01:44:54.778  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      01:44:54.778  SET FEATURES [Set transfer mode]
  ef 10 02 00 00 00 a0 00      01:44:54.778  SET FEATURES [Reserved for Serial ATA]

Error 2976 occurred at disk power-on lifetime: 17926 hours (746 days + 22 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 41 02 3c f5 4e 60  Error: UNC at LBA = 0x004ef53c = 5174588

  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 08 00 38 f5 4e 40 08      01:44:50.945  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      01:44:50.945  SET FEATURES [Reserved for Serial ATA]
  ec 00 00 00 00 00 a0 00      01:44:50.944  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      01:44:50.944  SET FEATURES [Set transfer mode]
  ef 10 02 00 00 00 a0 00      01:44:50.944  SET FEATURES [Reserved for Serial ATA]

Error 2975 occurred at disk power-on lifetime: 17926 hours (746 days + 22 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 41 02 3c f5 4e 60  Error: UNC at LBA = 0x004ef53c = 5174588

  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 08 00 38 f5 4e 40 08      01:44:47.111  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      01:44:47.111  SET FEATURES [Reserved for Serial ATA]
  ec 00 00 00 00 00 a0 00      01:44:47.111  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      01:44:47.111  SET FEATURES [Set transfer mode]
  ef 10 02 00 00 00 a0 00      01:44:47.110  SET FEATURES [Reserved for Serial ATA]

Error 2974 occurred at disk power-on lifetime: 17926 hours (746 days + 22 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 41 02 3c f5 4e 60  Error: UNC at LBA = 0x004ef53c = 5174588

  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 08 00 38 f5 4e 40 08      01:44:43.278  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      01:44:43.278  SET FEATURES [Reserved for Serial ATA]
  ec 00 00 00 00 00 a0 00      01:44:43.277  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      01:44:43.277  SET FEATURES [Set transfer mode]
  ef 10 02 00 00 00 a0 00      01:44:43.277  SET FEATURES [Reserved for Serial ATA]

The full smartctl report that the above came from can be viewed here
SMARTCTL REPORT

So here's the problem as I experienced it.  I can't actually remember whether my drive first began taking a hit on performance or if it started spitting out errors first.  I had to re-install Arch Linux using the new install media, there's a real learning curve to get from Grub legacy to Grub2 (but GRUB2's pretty groovy, so it's all good) so I don't have any of the logs and stuff that would have the actual error messages in them.  I'm currently extracting my last backup that I made just a day or two ago so that I can post a copy of the actual error message(s).  I googled 'READ FPDMA' and here's a post that I found extremely interesting.... and scary. 


http://askubuntu.com/questions/133946/a … 960#133960

This is a comment for the above post. 
http://askubuntu.com/questions/133946/a … 960#133960


HA! Found the little sucker.  Ahem, I remembered that after the new install I still encountered another set of those weird HDD errors, and I managed to find the one that I remembered.  Here it is.  

Aug 15 07:42:13 nLorrie kernel: [ 5444.278976] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
Aug 15 07:42:13 nLorrie kernel: [ 5444.280721] ata1.00: irq_stat 0x40000008
Aug 15 07:42:13 nLorrie kernel: [ 5444.282518] ata1.00: failed command: READ FPDMA QUEUED
Aug 15 07:42:13 nLorrie kernel: [ 5444.284261] ata1.00: cmd 60/08:00:00:d8:a8/00:00:17:00:00/40 tag 0 ncq 4096 in
Aug 15 07:42:13 nLorrie kernel: [ 5444.287739] ata1.00: status: { DRDY ERR }
Aug 15 07:42:13 nLorrie kernel: [ 5444.289444] ata1.00: error: { UNC }
Aug 15 07:42:17 nLorrie kernel: [ 5448.168246] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
Aug 15 07:42:17 nLorrie kernel: [ 5448.170014] ata1.00: irq_stat 0x40000008
Aug 15 07:42:17 nLorrie kernel: [ 5448.171725] ata1.00: failed command: READ FPDMA QUEUED
Aug 15 07:42:17 nLorrie kernel: [ 5448.173432] ata1.00: cmd 60/08:00:00:d8:a8/00:00:17:00:00/40 tag 0 ncq 4096 in
Aug 15 07:42:17 nLorrie kernel: [ 5448.176840] ata1.00: status: { DRDY ERR }
Aug 15 07:42:17 nLorrie kernel: [ 5448.178490] ata1.00: error: { UNC }
Aug 15 07:42:21 nLorrie kernel: [ 5452.079726] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
Aug 15 07:42:21 nLorrie kernel: [ 5452.081380] ata1.00: irq_stat 0x40000008
Aug 15 07:42:21 nLorrie kernel: [ 5452.083035] ata1.00: failed command: READ FPDMA QUEUED
Aug 15 07:42:21 nLorrie kernel: [ 5452.084667] ata1.00: cmd 60/08:00:00:d8:a8/00:00:17:00:00/40 tag 0 ncq 4096 in
Aug 15 07:42:21 nLorrie kernel: [ 5452.087960] ata1.00: status: { DRDY ERR }
Aug 15 07:42:26 nLorrie kernel: [ 5452.089572] ata1.00: error: { UNC }
Aug 15 07:42:26 nLorrie kernel: [ 5455.935649] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
Aug 15 07:42:26 nLorrie kernel: [ 5455.937298] ata1.00: irq_stat 0x40000008
Aug 15 07:42:26 nLorrie kernel: [ 5455.938880] ata1.00: failed command: READ FPDMA QUEUED
Aug 15 07:42:26 nLorrie kernel: [ 5455.940486] ata1.00: cmd 60/08:00:00:d8:a8/00:00:17:00:00/40 tag 0 ncq 4096 in
Aug 15 07:42:26 nLorrie kernel: [ 5455.943692] ata1.00: status: { DRDY ERR }
Aug 15 07:42:26 nLorrie kernel: [ 5455.945267] ata1.00: error: { UNC }

Thanks in advanced, dude(s).

Oh, and this is on a laptop.

Last edited by lspci (2012-09-02 22:46:34)

Please don't be a help vampire. | Bitbucket

Give a little more for a little less today.  smile

Offline

#2 2012-09-02 22:47:06

lspci
Member
From: Virginia, USA
Registered: 2012-06-09
Posts: 242

Re: [Solved] READ FPDMA QUEUED (DRDY ERR) -- Toshiba MK2555GSX HDD Error

My /var partition died.  So I went ahead and got a new laptop.  Problem solved... sort of.

Please don't be a help vampire. | Bitbucket

Give a little more for a little less today.  smile

Offline

Pages: 1

Board footer

Powered by FluxBB