Prev: Hplip
Next: sound devices
From: Alex Samad on 5 May 2008 17:20
Hi

I have been getting alot of these

May 5 23:31:46 hufpuf kernel: ata2: timeout waiting for ADMA IDLE,
stat=0x440
May 5 23:31:46 hufpuf kernel: ata2.00: exception Emask 0x0 SAct
0x7fffffff SErr 0x0 action 0x0
May 5 23:31:46 hufpuf kernel: ata2.00: CPB resp_flags 0x11: , CMD error
May 5 23:31:46 hufpuf kernel: ata2.00: cmd
61/08:00:42:e8:21/00:00:01:00:00/40 tag 0 ncq 4096 out
May 5 23:31:46 hufpuf kernel: res
41/04:00:cd:7d:91/04:00:31:00:00/40 Emask 0x1 (device error)
May 5 23:31:46 hufpuf kernel: ata2.00: status: { DRDY ERR }
May 5 23:31:46 hufpuf kernel: ata2.00: error: { ABRT }
May 5 23:31:46 hufpuf kernel: ata2.00: cmd
61/08:08:1a:e8:25/00:00:01:00:00/40 tag 1 ncq 4096 out
May 5 23:31:46 hufpuf kernel: res
41/04:08:1a:e8:25/24:00:01:00:00/40 Emask 0x401 (device error) <F>
May 5 23:31:46 hufpuf kernel: ata2.00: status: { DRDY ERR }



and finding my machine in a hung state (caps lock and the third led
flashing) I have had to reset the machine (3 times now in the last 3
weeks).

I am guessing it is a hard drive problem, cause I recently bought new
hard drives.

I am trying to figure out is it sda or sdb can you tell from ata2.00
?(if so how)

Ale
--
Objects are lost only because people look where they are not rather than
where they are.
From: Douglas A. Tutty on 5 May 2008 22:10
On Tue, May 06, 2008 at 07:10:34AM +1000, Alex Samad wrote:
>
> May 5 23:31:46 hufpuf kernel: ata2: timeout waiting for ADMA IDLE,
> stat=0x440
> May 5 23:31:46 hufpuf kernel: ata2.00: exception Emask 0x0 SAct
> 0x7fffffff SErr 0x0 action 0x0
> May 5 23:31:46 hufpuf kernel: ata2.00: CPB resp_flags 0x11: , CMD error
> May 5 23:31:46 hufpuf kernel: ata2.00: cmd
> 61/08:00:42:e8:21/00:00:01:00:00/40 tag 0 ncq 4096 out
> May 5 23:31:46 hufpuf kernel: res
> 41/04:00:cd:7d:91/04:00:31:00:00/40 Emask 0x1 (device error)
> May 5 23:31:46 hufpuf kernel: ata2.00: status: { DRDY ERR }
> May 5 23:31:46 hufpuf kernel: ata2.00: error: { ABRT }
> May 5 23:31:46 hufpuf kernel: ata2.00: cmd
> 61/08:08:1a:e8:25/00:00:01:00:00/40 tag 1 ncq 4096 out
> May 5 23:31:46 hufpuf kernel: res
> 41/04:08:1a:e8:25/24:00:01:00:00/40 Emask 0x401 (device error) <F>
> May 5 23:31:46 hufpuf kernel: ata2.00: status: { DRDY ERR }
>
> and finding my machine in a hung state (caps lock and the third led
> flashing) I have had to reset the machine (3 times now in the last 3
> weeks).
>
> I am guessing it is a hard drive problem, cause I recently bought new
> hard drives.
>
> I am trying to figure out is it sda or sdb can you tell from ata2.00
> ?(if so how)

First, ensure you have good recent backups.

Then install smartmontools and run a long S.M.A.R.T. test and check the
results.

Why did you recently buy new drives? If it was because old drives
failed, they may have damaged the controller and you're seeing
controller failure instead of drive failure.

Doug.


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Alex Samad on 6 May 2008 17:30
On Tue, May 06, 2008 at 10:17:23AM -0400, Douglas A. Tutty wrote:
> On Tue, May 06, 2008 at 06:08:47PM +1000, Alex Samad wrote:
> > On Mon, May 05, 2008 at 09:33:19PM -0400, Douglas A. Tutty wrote:
> > > On Tue, May 06, 2008 at 07:10:34AM +1000, Alex Samad wrote:
> > > >
> >
> > [snip]
> >
> > > > ?(if so how)
> > >
> > > First, ensure you have good recent backups.
> > >
> > > Then install smartmontools and run a long S.M.A.R.T. test and check the
> > > results.
> > >
> > > Why did you recently buy new drives? If it was because old drives
> > > failed, they may have damaged the controller and you're seeing
> > > controller failure instead of drive failure.
> >
> > upgraded drives 500G -> 1TB. This is one drive of a raid1 md. and I have
> > onsite and off site backups.
> >
> > I just want to make sure its sdb not sda
>
> You snipped so much, I forget what the problem was. IIRC, you had drive
> errors showing up in syslog on an ata controller and you didn't know
> which drive was the culprit.
sorry and yes

>
> Since its raid, see what the raid status is. Does it show an active
> raid with two copies synced, or does it show degraded status. mdadm
> should email you with a problem, but it doesn't hurt to check.
>
my main question was weather ata2 == sdb and ata1 == sda seems like it
does

My raid set was okay, when the machine hanged and was reboot, the would
be a resync

> If you have a third hard drive as a spare, you could add it to the
> array, let it sync, then remove on of the origional drives and see if
> the error goes away.
got another one replaced it and reseated the sata cable. Came back to
me i had problems in this drive bay before - loose cable! (hopefully not
the control), but this is one of those boxes that I have had problems
with from the beginning

Thanks

>
> Doug.
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
>
>

--
Sauron is alive in Argentina!
From: Alex Samad on 6 May 2008 04:20
On Mon, May 05, 2008 at 09:33:19PM -0400, Douglas A. Tutty wrote:
> On Tue, May 06, 2008 at 07:10:34AM +1000, Alex Samad wrote:
> >

[snip]

> > ?(if so how)
>
> First, ensure you have good recent backups.
>
> Then install smartmontools and run a long S.M.A.R.T. test and check the
> results.
>
> Why did you recently buy new drives? If it was because old drives
> failed, they may have damaged the controller and you're seeing
> controller failure instead of drive failure.

upgraded drives 500G -> 1TB. This is one drive of a raid1 md. and I have
onsite and off site backups.

I just want to make sure its sdb not sda

alex

>
> Doug.
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
>
>

--
Von Neumann was the subject of many dotty professor stories. Von Neumann
supposedly had the habit of simply writing answers to homework assignments on
the board (the method of solution being, of course, obvious) when he was asked
how to solve problems. One time one of his students tried to get more helpful
information by asking if there was another way to solve the problem. Von
Neumann looked blank for a moment, thought, and then answered, "Yes.".
From: Douglas A. Tutty on 6 May 2008 10:30
On Tue, May 06, 2008 at 06:08:47PM +1000, Alex Samad wrote:
> On Mon, May 05, 2008 at 09:33:19PM -0400, Douglas A. Tutty wrote:
> > On Tue, May 06, 2008 at 07:10:34AM +1000, Alex Samad wrote:
> > >
>
> [snip]
>
> > > ?(if so how)
> >
> > First, ensure you have good recent backups.
> >
> > Then install smartmontools and run a long S.M.A.R.T. test and check the
> > results.
> >
> > Why did you recently buy new drives? If it was because old drives
> > failed, they may have damaged the controller and you're seeing
> > controller failure instead of drive failure.
>
> upgraded drives 500G -> 1TB. This is one drive of a raid1 md. and I have
> onsite and off site backups.
>
> I just want to make sure its sdb not sda

You snipped so much, I forget what the problem was. IIRC, you had drive
errors showing up in syslog on an ata controller and you didn't know
which drive was the culprit.

Since its raid, see what the raid status is. Does it show an active
raid with two copies synced, or does it show degraded status. mdadm
should email you with a problem, but it doesn't hurt to check.

If you have a third hard drive as a spare, you could add it to the
array, let it sync, then remove on of the origional drives and see if
the error goes away.

Doug.


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
 | 
Pages: 1
Prev: Hplip
Next: sound devices