2.6.26-rc1 ata2 problems????

2.6.26-rc1 ata2 problems????

[Peter Teoh]

Just found this error in the dmesg:


ata2.00: qc timeout (cmd 0xa0)
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata2.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 0 pio 16392 in
         cdb 4a 01 00 00 10 00 00 00  08 00 00 00 00 00 00 00
         res 51/04:01:01:14:eb/00:00:00:00:00/a0 Emask 0x5 (timeout)
ata2.00: status: { DRDY ERR }
ata2: link is slow to respond, please be patient (ready=0)
ata2: device not ready (errno=-16), forcing hardreset
ata2: soft resetting link
ata2.00: configured for UDMA/33
ata2: EH complete
ADDRCONF(NETDEV_UP): eth1: link is not ready
ADDRCONF(NETDEV_UP): eth1: link is not ready
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
eth1: no IPv6 routers present
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
         cdb 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
         res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: status: { DRDY ERR }
ata2.00: qc timeout (cmd 0xa0)
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata2.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
         cdb 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
         res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5 (timeout)
ata2.00: status: { DRDY ERR }
ata2: link is slow to respond, please be patient (ready=0)
ata2: device not ready (errno=-16), forcing hardreset
ata2: soft resetting link
ata2.00: configured for UDMA/33
ata2: EH complete
sr 1:0:0:0: ioctl_internal_command return code = 8000002
   : Sense Key : No Sense [current]
   : Add. Sense: No additional sense information


Any clues to these messages?


-- 
Regards,
Peter Teoh
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.26-rc1 ata2 problems????

[Roman Mindalev]

Peter Teoh wrote:
> Just found this error in the dmesg:
> 
> 
> ata2.00: qc timeout (cmd 0xa0)
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
> ata2.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 0 pio 16392 in
>          cdb 4a 01 00 00 10 00 00 00  08 00 00 00 00 00 00 00
>          res 51/04:01:01:14:eb/00:00:00:00:00/a0 Emask 0x5 (timeout)
> ata2.00: status: { DRDY ERR }
> ata2: link is slow to respond, please be patient (ready=0)
> ata2: device not ready (errno=-16), forcing hardreset
> ata2: soft resetting link
> ata2.00: configured for UDMA/33
> ata2: EH complete
> ADDRCONF(NETDEV_UP): eth1: link is not ready
> ADDRCONF(NETDEV_UP): eth1: link is not ready
> ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
> eth1: no IPv6 routers present
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> ata2.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
>          cdb 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>          res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
> ata2.00: status: { DRDY ERR }
> ata2.00: qc timeout (cmd 0xa0)
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
> ata2.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
>          cdb 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>          res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5 (timeout)
> ata2.00: status: { DRDY ERR }
> ata2: link is slow to respond, please be patient (ready=0)
> ata2: device not ready (errno=-16), forcing hardreset
> ata2: soft resetting link
> ata2.00: configured for UDMA/33
> ata2: EH complete
> sr 1:0:0:0: ioctl_internal_command return code = 8000002
>    : Sense Key : No Sense [current]
>    : Add. Sense: No additional sense information
> 
> 
> Any clues to these messages?
> 
> 
Yes, I got messages "device not ready (errno=-16)" with 2.6.26-rcX
(seems and with 2.6.25-rcX) on system startup.
When has been disconnected old DVD/CD-RW drive (it can write on speed
14x max, may be optics crashed), booting process normal.
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.26-rc1 ata2 problems????

[Rik van Riel]

On Sat, 24 May 2008 14:24:47 +0800
"Peter Teoh" <htmldeveloper@gmail.com> wrote:

> Just found this error in the dmesg:
> 
> 
> ata2.00: qc timeout (cmd 0xa0)
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
> ata2.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 0 pio 16392 in
>          cdb 4a 01 00 00 10 00 00 00  08 00 00 00 00 00 00 00
>          res 51/04:01:01:14:eb/00:00:00:00:00/a0 Emask 0x5 (timeout)
> ata2.00: status: { DRDY ERR }

> Any clues to these messages?
 
Try smartctl -d ata -a /dev/sdc and look for errors on the disk.

Chances are the disk is going bad in one way or another.  In the
most benign way you are getting timeouts because the drive cannot
read a sector easily and keeps retrying over and over again. 

In that case, you may be able to force the disk to rewrite the
sectors properly (and/or relocate them) with a badblocks -n run
over the whole drive - when booted from a rescue disk!

If your luck is not as good, the drive may have some uncorrectable
errors, which means it is going bad and you'll want to buy a new
disk to copy all your data onto.

While you're looking at the smart data anyway, check the drive
temperature - is it simply running too hot because of sitting
near other equipment in your case?

-- 
All rights reversed.

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@nl.linux.org
Please read the FAQ at http://kernelnewbies.org/FAQ

Re: 2.6.26-rc1 ata2 problems????

[Peter Teoh]

Thank you Rik for the answer......just want to confirm some questions...

On Sat, May 24, 2008 at 9:40 PM, Rik van Riel <riel-ebMLmSuQjDVBDgjK7y7TUQ@public.gmane.org> wrote:
> On Sat, 24 May 2008 14:24:47 +0800
> "Peter Teoh" <htmldeveloper-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
>> Just found this error in the dmesg:
>>
>>
>> ata2.00: qc timeout (cmd 0xa0)
>> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
>> ata2.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 0 pio 16392 in
>>          cdb 4a 01 00 00 10 00 00 00  08 00 00 00 00 00 00 00
>>          res 51/04:01:01:14:eb/00:00:00:00:00/a0 Emask 0x5 (timeout)
>> ata2.00: status: { DRDY ERR }
>
>> Any clues to these messages?
>
> Try smartctl -d ata -a /dev/sdc and look for errors on the disk.
>
> Chances are the disk is going bad in one way or another.  In the
> most benign way you are getting timeouts because the drive cannot
> read a sector easily and keeps retrying over and over again.
>
> In that case, you may be able to force the disk to rewrite the
> sectors properly (and/or relocate them) with a badblocks -n run
> over the whole drive - when booted from a rescue disk!
>
> If your luck is not as good, the drive may have some uncorrectable
> errors, which means it is going bad and you'll want to buy a new
> disk to copy all your data onto.
>
> While you're looking at the smart data anyway, check the drive
> temperature - is it simply running too hot because of sitting
> near other equipment in your case?


Just out of curiosity.....when OS build the list of inodes....it scan
and identify all the corrupted blocks, and so the outcome of mkfs will
be all the uncorrupted blocks on the harddisk - right?   so possibly
there are many other corrupted blocks on the harddisk that failed the
criteria of mkfs on the harddisk - any linux harddisk....is that
correct?

Is there any tools that can allow me to see / identify all these
corrupted blocks?

And given that there are many corrupted blocks, when I do a mkfs to
create a new filesystem, all the corrupted blocks will be marked away,
and therefore the new filesystem should have less total space, but
guaranteed NOT TO HAVE any corrupted blocks, right?

Thank you Rik.


-- 
Regards,
Peter Teoh
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.26-rc1 ata2 problems????

[Rik van Riel]

On Sat, 24 May 2008 23:45:24 +0800
"Peter Teoh" <htmldeveloper-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

> Just out of curiosity.....when OS build the list of inodes....it scan
> and identify all the corrupted blocks, and so the outcome of mkfs will
> be all the uncorrupted blocks on the harddisk - right?  

No, mkfs just writes and hopes that the blocks it wrote
can be read in again later. I do not believe it does any
testing by default.

> so possibly there are many other corrupted blocks on the harddisk

Yes.

> Is there any tools that can allow me to see / identify all these
> corrupted blocks?

badblocks

Read the man page carefully, you probably want the "-n" option.
 
> And given that there are many corrupted blocks, when I do a mkfs to
> create a new filesystem, all the corrupted blocks will be marked away,
> and therefore the new filesystem should have less total space, but
> guaranteed NOT TO HAVE any corrupted blocks, right?

No, mkfs does not scan the disk for bad blocks by default.

-- 
All rights reversed.
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.26-rc1 ata2 problems????

[Peter Teoh]

Thank you Rik...

On Sun, May 25, 2008 at 12:15 AM, Rik van Riel <riel-ebMLmSuQjDVBDgjK7y7TUQ@public.gmane.org> wrote:
> On Sat, 24 May 2008 23:45:24 +0800
> "Peter Teoh" <htmldeveloper-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
>> Just out of curiosity.....when OS build the list of inodes....it scan
>> and identify all the corrupted blocks, and so the outcome of mkfs will
>> be all the uncorrupted blocks on the harddisk - right?
>
> No, mkfs just writes and hopes that the blocks it wrote
> can be read in again later. I do not believe it does any
> testing by default.
>

thank you for the summary....i am looking for codes that does
that.....but got no time to read/understand everything of mkfs......

>> so possibly there are many other corrupted blocks on the harddisk
>
> Yes.
>
>> Is there any tools that can allow me to see / identify all these
>> corrupted blocks?
>
> badblocks
>

wow...this is amazing.....part of e2fs....found my answer...and really
got to start understanding the e2fs package....

> Read the man page carefully, you probably want the "-n" option.
>
>> And given that there are many corrupted blocks, when I do a mkfs to
>> create a new filesystem, all the corrupted blocks will be marked away,
>> and therefore the new filesystem should have less total space, but
>> guaranteed NOT TO HAVE any corrupted blocks, right?
>
> No, mkfs does not scan the disk for bad blocks by default.
>
> --
> All rights reversed.
>

i always find this amusing....it means that I will be paid if I copied
your ideas....or I have to pay you in order that u can copy my
ideas....


-- 
Regards,
Peter Teoh
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html