Sever Hard disk Problem?

English Hardware
1

Dear all,

during boot time I am getting the following type of messages. The system boot ups though and everything seem to be running ok (in kde right now). Could you please give me feedback how sever this problem is and what should I do for fixing it?

Regards
Alex

   12.724971] ata1.00: exception Emask 0x0 SAct 0xb SErr 0x0 action 0x0
   12.725013] ata1.00: irq_stat 0x40000008
   12.725036] ata1.00: failed command: READ FPDMA QUEUED
   12.725066] ata1.00: cmd 60/a8:00:5a:6f:06/00:00:07:00:00/40 tag 0 ncq 86016 in
   12.725067]          res 41/40:00:60:6f:06/00:00:07:00:00/40 Emask 0x409 (media error) <F>
   12.725140] ata1.00: status: { DRDY ERR }
   12.725165] ata1.00: error: { UNC }
   12.738176] ata1.00: configured for UDMA/133
   12.738189] ata1: EH complete
   13.319097] ata1.00: exception Emask 0x0 SAct 0x4 SErr 0x0 action 0x0
   13.319136] ata1.00: irq_stat 0x40000008
   13.319158] ata1.00: failed command: READ FPDMA QUEUED
   13.319188] ata1.00: cmd 60/a8:10:5a:6f:06/00:00:07:00:00/40 tag 2 ncq 86016 in
   13.319189]          res 41/40:00:60:6f:06/00:00:07:00:00/40 Emask 0x409 (media error) <F>
   13.319263] ata1.00: status: { DRDY ERR }
   13.319289] ata1.00: error: { UNC }
   13.331480] ata1.00: configured for UDMA/133
   13.331488] ata1: EH complete
   13.740562] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
   13.740596] ata1.00: irq_stat 0x40000008
   13.740618] ata1.00: failed command: READ FPDMA QUEUED
   13.740647] ata1.00: cmd 60/a8:00:5a:6f:06/00:00:07:00:00/40 tag 0 ncq 86016 in
   13.740648]          res 41/40:00:60:6f:06/00:00:07:00:00/40 Emask 0x409 (media error) <F>
   13.740722] ata1.00: status: { DRDY ERR }
   13.740743] ata1.00: error: { UNC }
   13.753008] ata1.00: configured for UDMA/133
   13.753030] ata1: EH complete
   14.224296] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
   14.224331] ata1.00: irq_stat 0x40000008
   14.224353] ata1.00: failed command: READ FPDMA QUEUED
   14.224382] ata1.00: cmd 60/a8:00:5a:6f:06/00:00:07:00:00/40 tag 0 ncq 86016 in
   14.224384]          res 41/40:00:60:6f:06/00:00:07:00:00/40 Emask 0x409 (media error) <F>
   14.224457] ata1.00: status: { DRDY ERR }
   14.224478] ata1.00: error: { UNC }
   14.238721] ata1.00: configured for UDMA/133
   14.238727] ata1: EH complete
   14.712193] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
   14.712226] ata1.00: irq_stat 0x40000008
   14.712247] ata1.00: failed command: READ FPDMA QUEUED
   14.712277] ata1.00: cmd 60/a8:00:5a:6f:06/00:00:07:00:00/40 tag 0 ncq 86016 in
   14.712278]          res 41/40:00:60:6f:06/00:00:07:00:00/40 Emask 0x409 (media error) <F>
   14.712350] ata1.00: status: { DRDY ERR }
   14.712371] ata1.00: error: { UNC }
   14.724660] ata1.00: configured for UDMA/133
   14.724666] ata1: EH complete
   15.164590] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
   15.164624] ata1.00: irq_stat 0x40000008
   15.164645] ata1.00: failed command: READ FPDMA QUEUED
   15.164675] ata1.00: cmd 60/a8:00:5a:6f:06/00:00:07:00:00/40 tag 0 ncq 86016 in
   15.164676]          res 41/40:00:60:6f:06/00:00:07:00:00/40 Emask 0x409 (media error) <F>
   15.164749] ata1.00: status: { DRDY ERR }
   15.164770] ata1.00: error: { UNC }
   15.177008] ata1.00: configured for UDMA/133
   15.177041] sd 0:0:0:0: [sda] Unhandled sense code
   15.177044] sd 0:0:0:0: [sda]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
   15.177048] sd 0:0:0:0: [sda]  Sense Key : Medium Error [current] [descriptor]
   15.177052] Descriptor sense data with sense descriptors (in hex):
   15.177054]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
   15.177062]         07 06 6f 60 
   15.177066] sd 0:0:0:0: [sda]  Add. Sense: Unrecovered read error - auto reallocate failed
   15.177071] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 07 06 6f 5a 00 00 a8 00
   15.177079] end_request: I/O error, dev sda, sector 117862240
   15.178444] Buffer I/O error on device sda2, logical block 117444550
   15.179783] Buffer I/O error on device sda2, logical block 117444551
   15.181116] Buffer I/O error on device sda2, logical block 117444552
   15.182448] Buffer I/O error on device sda2, logical block 117444553
   15.183745] Buffer I/O error on device sda2, logical block 117444554
   15.185042] Buffer I/O error on device sda2, logical block 117444555
   15.186293] Buffer I/O error on device sda2, logical block 117444556
   15.187537] Buffer I/O error on device sda2, logical block 117444557
   15.188759] Buffer I/O error on device sda2, logical block 117444558
   15.189948] Buffer I/O error on device sda2, logical block 117444559
   15.191224] ata1: EH complete
   15.604186] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
   15.605429] ata1.00: irq_stat 0x40000008
   15.606584] ata1.00: failed command: READ FPDMA QUEUED
   15.607733] ata1.00: cmd 60/02:00:60:6f:06/00:00:07:00:00/40 tag 0 ncq 1024 in
   15.607734]          res 41/40:00:60:6f:06/00:00:07:00:00/40 Emask 0x409 (media error) <F>
   15.610079] ata1.00: status: { DRDY ERR }
   15.611260] ata1.00: error: { UNC }
   15.626600] ata1.00: configured for UDMA/133
   15.626612] ata1: EH complete
   16.036693] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
   16.037951] ata1.00: irq_stat 0x40000008
   16.039166] ata1.00: failed command: READ FPDMA QUEUED
   16.040395] ata1.00: cmd 60/02:00:60:6f:06/00:00:07:00:00/40 tag 0 ncq 1024 in
   16.040396]          res 41/40:00:60:6f:06/00:00:07:00:00/40 Emask 0x409 (media error) <F>
   16.042847] ata1.00: status: { DRDY ERR }
   16.044082] ata1.00: error: { UNC }
   16.058422] ata1.00: configured for UDMA/133
   16.058431] ata1: EH complete
   16.434098] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
   16.435397] ata1.00: irq_stat 0x40000008
   16.436642] ata1.00: failed command: READ FPDMA QUEUED
   16.437892] ata1.00: cmd 60/02:00:60:6f:06/00:00:07:00:00/40 tag 0 ncq 1024 in
   16.437893]          res 41/40:00:60:6f:06/00:00:07:00:00/40 Emask 0x409 (media error) <F>
   16.440414] ata1.00: status: { DRDY ERR }
   16.441673] ata1.00: error: { UNC }
   16.455753] ata1.00: configured for UDMA/133
   16.455760] ata1: EH complete
   16.864823] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
   16.866147] ata1.00: irq_stat 0x40000008
   16.867392] ata1.00: failed command: READ FPDMA QUEUED
   16.868643] ata1.00: cmd 60/02:00:60:6f:06/00:00:07:00:00/40 tag 0 ncq 1024 in
   16.868644]          res 41/40:00:60:6f:06/00:00:07:00:00/40 Emask 0x409 (media error) <F>
   16.871156] ata1.00: status: { DRDY ERR }
   16.872399] ata1.00: error: { UNC }
   16.886360] ata1.00: configured for UDMA/133
   16.886372] ata1: EH complete
   17.284096] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
   17.285422] ata1.00: irq_stat 0x40000008
   17.286670] ata1.00: failed command: READ FPDMA QUEUED
   17.287922] ata1.00: cmd 60/02:00:60:6f:06/00:00:07:00:00/40 tag 0 ncq 1024 in
   17.287923]          res 41/40:00:60:6f:06/00:00:07:00:00/40 Emask 0x409 (media error) <F>
   17.290438] ata1.00: status: { DRDY ERR }
   17.291686] ata1.00: error: { UNC }
   17.317936] ata1.00: configured for UDMA/133
   17.317946] ata1: EH complete
   17.891266] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
   17.892585] ata1.00: irq_stat 0x40000008
   17.893830] ata1.00: failed command: READ FPDMA QUEUED
   17.895077] ata1.00: cmd 60/02:00:60:6f:06/00:00:07:00:00/40 tag 0 ncq 1024 in
   17.895078]          res 41/40:00:60:6f:06/00:00:07:00:00/40 Emask 0x409 (media error) <F>
   17.897594] ata1.00: status: { DRDY ERR }
   17.898842] ata1.00: error: { UNC }
   17.912996] ata1.00: configured for UDMA/133
   17.913020] sd 0:0:0:0: [sda] Unhandled sense code
   17.913021] sd 0:0:0:0: [sda]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
   17.913024] sd 0:0:0:0: [sda]  Sense Key : Medium Error [current] [descriptor]
2

On 07/23/2012 08:16 AM, alaios wrote:
> Could you please give me feedback how sever this problem is
> and what should I do for fixing it?

i can’t answer you, and i do not think anyone can until you tell us a
little more, like:

-operating system and version

-what log did you post? is it from Xorg.0.log ?? are there
similar/complementary problems being logged to /var/log/messages

-file system on the drive complaining (ext3, ext4, btrfs, reiser, etc)

-is RAID in use? hardware or software? which type 0 - 10

-have you installed SMART and run smartctl on the the disk? does it have
any unrecoverable bad blocks? maybe your disk is dying? how old is this
system? and disk?

-tell us more about the hardware (age, brand, CPU, RAM,
hours/months/years running)

-have you downloaded the drive maker’s diagnostics software and run that
against the disk?

-when you googled the error message, did you find any useful info, like:

https://www.google.com/search?q=site%3Aforums.opensuse.org+“READ+FPDMA+QUEUED”

and/or

https://www.google.com/search?q=linux+“READ+FPDMA+QUEUED”

-is your data backed up to an off machine medium

–
dd http://tinyurl.com/DD-Caveat

3

On 2012-07-23 08:16, alaios wrote:
>
> Dear all,
>
> during boot time I am getting the following type of messages. The
> system boot ups though and everything seem to be running ok (in kde
> right now). Could you please give me feedback how sever this problem is
> and what should I do for fixing it?

It might be quite dangerous.
Test your disk using the test facility provided by the disk manufacturer; f.i., if seagate,
then seatools.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

4

Latest opensuse. Filesystem ext4. Data output to /var/log/messages/
No raid in use. I am not sure about SMART (how to check?)

Data is not fully backep up. I have not run any test on the pc. I have stopped using it after I sent this post.

The system is running one year now. The question then is what if I just try to clone the hard disk (bit by bit copy to a new one?) Would that solve the problem ? Would that be the safest option? Regards

5

So you could issue the following command at the terminal prompt and substitute an a, b, c etc for the actual drive or use hd? if not in the sd format.

sudo /usr/sbin/smartctl --all /dev/sd?

If SMART is not enabled, you will not get any data. Post your response between code # tags in the Advance Message Editor, it will look like the command above, but bigger.

Now also realize that while this does say media error, seeing errors are not all that uncommon and I wonder if you are actually seeing any problem? The fastest way to clone a disk partition is using the dd command. The disks don’t need to be identical, but for the dd command, the partitions need to be the same in every way. For instance, say the source partition was ext4 at 20 GB called /dev/sda2 and the target was then ext4 at 20 GB called /dev/sdc2. I would run the dd command:

sudo /bin/dd if=/dev/sda2 of=/dev/sdc2

Since you are trying to duplicate the original, the two existing partitions must be the same in every way because you are doing a by sector copy. You can use the YaST Partitioner or any other good Linux partitioning software from a bootable external cd or dvd disk. A by File copy can also be made if the source and target are not identical. In every case where the original disk is bootable, you must reload grub and mark the appropriate partition is active for booting when installing a new boot hard drive.

Thank You,

6

On 2012-07-23 21:26, alaios wrote:
>
> Latest opensuse. Filesystem ext4. Data output to /var/log/messages/
> No raid in use. I am not sure about SMART (how to check?)

Forget smart. Go to the website of your hardisk manufacturer, download their test suite and use
it. ASAP!

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

7

Good advice if they have a Linux app or a bootable disk you can make I guess.

Thank You,

8

On 2012-07-24 01:56, jdmcdaniel3 wrote:
>
> robin_listas;2476110 Wrote:

>> Forget smart. Go to the website of your hardisk manufacturer, download
>> their test suite and use
>> it. ASAP!

> Good advice if they have a Linux app or a bootable disk you can make I
> guess.

Seagate publishes a bootable ISO image. You burn it, you boot it, go (it does not matter what
OS it runs in). It is in fact about the same tests that the smart bios does, but run externally
so that errors can be printed. It also tests the cables.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

9

Thanks a lot for the replies…

I would check but what would happen If I just try to clone the hard disk to a new disk (That I already have available?).

Btw It looks like that I am running smart

smartctl -a /dev/sda reports also an error after 1982 hours.

Regards
A.

10

On Mon, 23 Jul 2012 19:26:02 +0000, alaios wrote:

> Latest opensuse.

Please define with a specific version number.

Your idea of “latest” may be 12.1, but those who use factory may be on a
pre-milestone 12.3, or may be running a 12.2 release candidate.

Specific version numbers are always more helpful than “latest version”.

Jim

–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

11

On 2012-07-24 06:16, alaios wrote:
>
> Thanks a lot for the replies…
>
> I would check but what would happen If I just try to clone the hard
> disk to a new disk (That I already have available?)

Who knows? Try.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

12

Tried it and it worked :slight_smile:
Now I am running on a new hard disk.

Cheers to all