Fred Moyer wrote:
Sounds like SMART is likely disabled on that drive. You can try doing
"smartctl -s on /dev/sda" and see if that will turn it on.
Sorry - that last post of mine was brain dead. Here's the one with
(hopefully) useful data.
app2 ~ # smartctl -d ata -a /dev/sda
smartctl
Fred Moyer wrote:
Sounds like SMART is likely disabled on that drive. You can try doing
smartctl -s on /dev/sda and see if that will turn it on.
Sorry - that last post of mine was brain dead. Here's the one with
(hopefully) useful data.
app2 ~ # smartctl -d ata -a /dev/sda
smartctl
> > This appears to be a different problem. Something is issuing SMART-related
> > commands (smartd or smartctl perhaps) which the drive seems to be reacting
> > strangely to.
..
> Specifically, I could trigger it by running 'smartctl -d ata -S on
> /dev/sda' OR (s-S/o/).
This sounds like a
This appears to be a different problem. Something is issuing SMART-related
commands (smartd or smartctl perhaps) which the drive seems to be reacting
strangely to.
..
Specifically, I could trigger it by running 'smartctl -d ata -S on
/dev/sda' OR (s-S/o/).
This sounds like a known
Robert Hancock wrote:
Fred Moyer wrote:
This appears to be a different problem. Something is issuing
SMART-related commands (smartd or smartctl perhaps) which the drive
seems to be reacting strangely to. It apparently completed the
command but never raised DRQ to request any data being
On Sat, May 12, 2007 at 12:48:59PM -0600, Robert Hancock wrote:
> Fred Moyer wrote:
> > I just joined the list today so apologies if this email breaks any email
> > client post threading.
> > I have been seeing similar errors on two different systems. I applied
> > Robert's sata_nv patch
Fred Moyer wrote:
This appears to be a different problem. Something is issuing
SMART-related commands (smartd or smartctl perhaps) which the drive
seems to be reacting strangely to. It apparently completed the command
but never raised DRQ to request any data being transferred even though
we
Robert Hancock wrote:
Fred Moyer wrote:
I just joined the list today so apologies if this email breaks any
email client post threading.
I have been seeing similar errors on two different systems. I applied
Robert's sata_nv patch posted to the list on May 5th, and approved
today by Jeff
Fred Moyer wrote:
I just joined the list today so apologies if this email breaks any email
client post threading.
I have been seeing similar errors on two different systems. I applied
Robert's sata_nv patch posted to the list on May 5th, and approved today
by Jeff Garzik. I've taken
Gerhard Mack wrote:
On Wed, 9 May 2007, Robert Hancock wrote:
Gerhard Mack wrote:
On Wed, 9 May 2007, Jeff Garzik wrote:
Gerhard Mack wrote:
May 9 14:51:35 mgerhard kernel: ata1.00: exception Emask 0x0 SAct 0x0
SErr
0x180 action 0x2 frozen
May 9 14:51:35 mgerhard kernel: ata1.00: cmd
Gerhard Mack wrote:
On Wed, 9 May 2007, Robert Hancock wrote:
Gerhard Mack wrote:
On Wed, 9 May 2007, Jeff Garzik wrote:
Gerhard Mack wrote:
May 9 14:51:35 mgerhard kernel: ata1.00: exception Emask 0x0 SAct 0x0
SErr
0x180 action 0x2 frozen
May 9 14:51:35 mgerhard kernel: ata1.00: cmd
Fred Moyer wrote:
I just joined the list today so apologies if this email breaks any email
client post threading.
I have been seeing similar errors on two different systems. I applied
Robert's sata_nv patch posted to the list on May 5th, and approved today
by Jeff Garzik. I've taken
Robert Hancock wrote:
Fred Moyer wrote:
I just joined the list today so apologies if this email breaks any
email client post threading.
I have been seeing similar errors on two different systems. I applied
Robert's sata_nv patch posted to the list on May 5th, and approved
today by Jeff
Fred Moyer wrote:
This appears to be a different problem. Something is issuing
SMART-related commands (smartd or smartctl perhaps) which the drive
seems to be reacting strangely to. It apparently completed the command
but never raised DRQ to request any data being transferred even though
we
Robert Hancock wrote:
Fred Moyer wrote:
This appears to be a different problem. Something is issuing
SMART-related commands (smartd or smartctl perhaps) which the drive
seems to be reacting strangely to. It apparently completed the
command but never raised DRQ to request any data being
Robert Hancock wrote:
>Gerhard Mack wrote:
>> On Wed, 9 May 2007, Jeff Garzik wrote:
>>> Gerhard Mack wrote:
May 9 14:51:35 mgerhard kernel: ata1.00: exception Emask 0x0 SAct
0x0 SErr
0x180 action 0x2 frozen
May 9 14:51:35 mgerhard kernel: ata1.00: cmd
On Wed, 9 May 2007, Robert Hancock wrote:
> Gerhard Mack wrote:
> > On Wed, 9 May 2007, Jeff Garzik wrote:
> > > Gerhard Mack wrote:
> > > > May 9 14:51:35 mgerhard kernel: ata1.00: exception Emask 0x0 SAct 0x0
> > > > SErr
> > > > 0x180 action 0x2 frozen
> > > > May 9 14:51:35 mgerhard
On Thu, 10 May 2007, Mikael Pettersson wrote:
> Date: Thu, 10 May 2007 10:51:57 +0200
> From: Mikael Pettersson <[EMAIL PROTECTED]>
> To: Gerhard Mack <[EMAIL PROTECTED]>
> Cc: Jeff Garzik <[EMAIL PROTECTED]>, linux-kernel@vger.kernel.org
> Subject: Re: [2.6.21
Gerhard Mack writes:
> On Wed, 9 May 2007, Jeff Garzik wrote:
> > Gerhard Mack wrote:
> > > May 9 14:51:35 mgerhard kernel: ata1.00: exception Emask 0x0 SAct 0x0
> > > SErr
> > > 0x180 action 0x2 frozen
> > > May 9 14:51:35 mgerhard kernel: ata1.00: cmd
> > >
Gerhard Mack writes:
On Wed, 9 May 2007, Jeff Garzik wrote:
Gerhard Mack wrote:
May 9 14:51:35 mgerhard kernel: ata1.00: exception Emask 0x0 SAct 0x0
SErr
0x180 action 0x2 frozen
May 9 14:51:35 mgerhard kernel: ata1.00: cmd
35/00:00:80:6d:c8/00:04:09:00:00/e0 tag 0
On Thu, 10 May 2007, Mikael Pettersson wrote:
Date: Thu, 10 May 2007 10:51:57 +0200
From: Mikael Pettersson [EMAIL PROTECTED]
To: Gerhard Mack [EMAIL PROTECTED]
Cc: Jeff Garzik [EMAIL PROTECTED], linux-kernel@vger.kernel.org
Subject: Re: [2.6.21.1] SATA freeze
Gerhard Mack writes
On Wed, 9 May 2007, Robert Hancock wrote:
Gerhard Mack wrote:
On Wed, 9 May 2007, Jeff Garzik wrote:
Gerhard Mack wrote:
May 9 14:51:35 mgerhard kernel: ata1.00: exception Emask 0x0 SAct 0x0
SErr
0x180 action 0x2 frozen
May 9 14:51:35 mgerhard kernel: ata1.00: cmd
Robert Hancock wrote:
Gerhard Mack wrote:
On Wed, 9 May 2007, Jeff Garzik wrote:
Gerhard Mack wrote:
May 9 14:51:35 mgerhard kernel: ata1.00: exception Emask 0x0 SAct
0x0 SErr
0x180 action 0x2 frozen
May 9 14:51:35 mgerhard kernel: ata1.00: cmd
35/00:00:80:6d:c8/00:04:09:00:00/e0
Gerhard Mack wrote:
On Wed, 9 May 2007, Jeff Garzik wrote:
Gerhard Mack wrote:
May 9 14:51:35 mgerhard kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr
0x180 action 0x2 frozen
May 9 14:51:35 mgerhard kernel: ata1.00: cmd
35/00:00:80:6d:c8/00:04:09:00:00/e0 tag 0 cdb 0x0 data 524288 out
Gerhard Mack wrote:
> On Wed, 9 May 2007, Jeff Garzik wrote:
>> Gerhard Mack wrote:
>>> May 9 14:51:35 mgerhard kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr
>>> 0x180 action 0x2 frozen
>>> May 9 14:51:35 mgerhard kernel: ata1.00: cmd
>>> 35/00:00:80:6d:c8/00:04:09:00:00/e0 tag 0 cdb
Gerhard Mack wrote:
May 9 14:51:35 mgerhard kernel: ata1.00: exception Emask 0x0 SAct 0x0
SErr 0x180 action 0x2 frozen
May 9 14:51:35 mgerhard kernel: ata1.00: cmd
35/00:00:80:6d:c8/00:04:09:00:00/e0 tag 0 cdb 0x0 data 524288 out
May 9 14:51:35 mgerhard kernel: res
Gerhard Mack wrote:
May 9 14:51:35 mgerhard kernel: ata1.00: exception Emask 0x0 SAct 0x0
SErr 0x180 action 0x2 frozen
May 9 14:51:35 mgerhard kernel: ata1.00: cmd
35/00:00:80:6d:c8/00:04:09:00:00/e0 tag 0 cdb 0x0 data 524288 out
May 9 14:51:35 mgerhard kernel: res
Gerhard Mack wrote:
On Wed, 9 May 2007, Jeff Garzik wrote:
Gerhard Mack wrote:
May 9 14:51:35 mgerhard kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr
0x180 action 0x2 frozen
May 9 14:51:35 mgerhard kernel: ata1.00: cmd
35/00:00:80:6d:c8/00:04:09:00:00/e0 tag 0 cdb 0x0 data 524288
Gerhard Mack wrote:
On Wed, 9 May 2007, Jeff Garzik wrote:
Gerhard Mack wrote:
May 9 14:51:35 mgerhard kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr
0x180 action 0x2 frozen
May 9 14:51:35 mgerhard kernel: ata1.00: cmd
35/00:00:80:6d:c8/00:04:09:00:00/e0 tag 0 cdb 0x0 data 524288 out
29 matches
Mail list logo