Re: [gentoo-user] SATA raptor failure - why?
On 5/25/06, Raymond Lewis Rebbeck <[EMAIL PROTECTED]> wrote: smartmontools does in fact support SATA disks starting with kernel 2.6.15. Use the '-d ata' argument with SATA disks and it will work fine. For example: # smartmontools -d ata -a /dev/sda -- Raymond Lewis Rebbeck -- gentoo-user@gentoo.org mailing list Thank you very much :D -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] SATA raptor failure - why?
These are supported by libata as of kernel 2.6.15 On Thursday, 25 May 2006 19:09, Jarry wrote: > CapSel wrote: > > Unfortunately smartmontools does not support SATA disks. > > More exactly: > > "Smartmontools should work correctly with SATA drives under both > Linux 2.4 and 2.6 kernels, if you use the standard IDE drivers > in drivers/ide. If you use the new libata drivers, it won't work > correctly because libata doesn't yet support the needed > ATA-passthrough ioctl() calls." (smartmontools.sourceforge.net) > > Jarry -- Raymond Lewis Rebbeck -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] SATA raptor failure - why?
On 5/25/06, Jarry <[EMAIL PROTECTED]> wrote: > Unfortunately smartmontools does not support SATA disks. More exactly: "Smartmontools should work correctly with SATA drives under both Linux 2.4 and 2.6 kernels, if you use the standard IDE drivers in drivers/ide. If you use the new libata drivers, it won't work correctly because libata doesn't yet support the needed ATA-passthrough ioctl() calls." (smartmontools.sourceforge.net) Jarry -- gentoo-user@gentoo.org mailing list How to set up a SATA disk to be seen as IDE disk to the kernel? Can this be done by adding something to kernel command line in grub? I used genkernel to compile kernel. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] SATA raptor failure - why?
smartmontools does in fact support SATA disks starting with kernel 2.6.15. Use the '-d ata' argument with SATA disks and it will work fine. For example: # smartmontools -d ata -a /dev/sda On Thursday, 25 May 2006 19:03, CapSel wrote: > Unfortunately smartmontools does not support SATA disks. Is there any > other tool to check S.M.A.R.T. on this kind of disks? -- Raymond Lewis Rebbeck -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] SATA raptor failure - why?
CapSel wrote: Unfortunately smartmontools does not support SATA disks. More exactly: "Smartmontools should work correctly with SATA drives under both Linux 2.4 and 2.6 kernels, if you use the standard IDE drivers in drivers/ide. If you use the new libata drivers, it won't work correctly because libata doesn't yet support the needed ATA-passthrough ioctl() calls." (smartmontools.sourceforge.net) Jarry -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] SATA raptor failure - why?
On 5/25/06, Ryan Tandy <[EMAIL PROTECTED]> wrote: Make a backup. Now. When you start seeing 'end_request: I/O error', it's always (in my experience) been a sign of a disk getting ready to pack it in. Double check physical connections, make sure no wires are loose; if S.M.A.R.T. is available, check its status - but I highly doubt a software issue here. -- gentoo-user@gentoo.org mailing list Unfortunately smartmontools does not support SATA disks. Is there any other tool to check S.M.A.R.T. on this kind of disks? -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] SATA raptor failure - why?
CapSel wrote:
May 24 23:31:43 foo ata1: command 0x35 timeout, stat 0xd1 host_stat 0x21
May 24 23:31:43 foo ata1: translated ATA stat/err 0xd1/00 to SCSI
SK/ASC/ASCQ 0xb/47/00
May 24 23:31:43 foo ata1: status=0xd1 { Busy }
May 24 23:31:43 foo sd 0:0:0:0: SCSI error: return code = 0x802
May 24 23:31:43 foo sda: Current: sense key=0xb
May 24 23:31:43 foo ASC=0x47 ASCQ=0x0
May 24 23:31:43 foo end_request: I/O error, dev sda, sector 17059167
Make a backup. Now.
When you start seeing 'end_request: I/O error', it's always (in my
experience) been a sign of a disk getting ready to pack it in.
Double check physical connections, make sure no wires are loose; if
S.M.A.R.T. is available, check its status - but I highly doubt a
software issue here.
--
gentoo-user@gentoo.org mailing list
