From: Deepak <dee...@gm...> - 2006-02-28 18:45:40
|
Hello, I am getting the following error when starting smartd. ----------- smartd[25998]: Device /dev/sda, SATA disks accessed via libata are not currently supported by smartmontools. When libata is given an ATA pass-thru ioctl() then an additional '-d libata' device type will be added to smartmontools. ----------- I have got harddrives under 3ware controller on the same server and they work just fine. This one is not connected to 3ware card. Could anyone tell me how can I fix the issue. |
From: Bruce A. <ba...@gr...> - 2006-02-28 22:44:33
|
Use a 2..6.15 or later Linux kernel. Add '-d ata' onto the /dev/sdaX line in smartd.conf Cheers, Bruce On Wed, 1 Mar 2006, Deepak wrote: > Hello, > > I am getting the following error when starting smartd. > > ----------- > smartd[25998]: Device /dev/sda, SATA disks accessed via libata are not > currently supported by smartmontools. When libata is given an ATA > pass-thru ioctl() then an additional '-d libata' device type will be > added to smartmontools. > ----------- > > I have got harddrives under 3ware controller on the same server and > they work just fine. This one is not connected to 3ware card. Could > anyone tell me how can I fix the issue. > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd_______________________________________________ > Smartmontools-support mailing list > Sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support > |
From: Jeremy J. <jb...@fo...> - 2006-02-28 22:45:22
|
Deepak wrote: > I am getting the following error when starting smartd. > > ----------- > smartd[25998]: Device /dev/sda, SATA disks accessed via libata are not > currently supported by smartmontools. When libata is given an ATA > pass-thru ioctl() then an additional '-d libata' device type will be > added to smartmontools. > ----------- > > I have got harddrives under 3ware controller on the same server and > they work just fine. This one is not connected to 3ware card. Could > anyone tell me how can I fix the issue. I think the standard procedure is (correct me if I'm wrong): 1) Use a 2.6.15 kernel (libata only just started supporting pass-through for SMART and other commands) 2) Make sure you're using a recent version of smartmontools (although actually 5.32 works fine for me here through an Intel SATA controller) 3) Run 'smartctl -a -d ata /dev/sda' (or similar - note ata *not* libata) 4) If you've done all the above and still having problems, let us know. Best wishes, Jeremy |
From: Deepak <dee...@gm...> - 2006-03-01 20:26:18
|
I had already given it a try using -d option earlier. I have tried "-d ata" as well as "-d sata" option, but no luck. I got the following error --------------- smartctl -d ata -a /dev/sda smartctl version 5.33 [i686-pc-linux-gnu] Copyright (C) 2002-4 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. ---------- Can anyone shed some light on this? On 3/1/06, Jeremy James <jb...@fo...> wrote: > Deepak wrote: > > I am getting the following error when starting smartd. > > > > ----------- > > smartd[25998]: Device /dev/sda, SATA disks accessed via libata are not > > currently supported by smartmontools. When libata is given an ATA > > pass-thru ioctl() then an additional '-d libata' device type will be > > added to smartmontools. > > ----------- > > > > I have got harddrives under 3ware controller on the same server and > > they work just fine. This one is not connected to 3ware card. Could > > anyone tell me how can I fix the issue. > > > I think the standard procedure is (correct me if I'm wrong): > > 1) Use a 2.6.15 kernel (libata only just started supporting pass-through > for SMART and other commands) > > 2) Make sure you're using a recent version of smartmontools (although > actually 5.32 works fine for me here through an Intel SATA controller) > > 3) Run 'smartctl -a -d ata /dev/sda' (or similar - note ata *not* libata) > > 4) If you've done all the above and still having problems, let us know. > > Best wishes, > Jeremy > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting langua= ge > that extends applications into web and mobile media. Attend the live webc= ast > and join the prime developer group breaking into this new coding territor= y! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat= =3D121642 > _______________________________________________ > Smartmontools-support mailing list > Sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support > |
From: Bruce A. <ba...@gr...> - 2006-03-01 20:45:15
|
What is your linux kernel version? If 2.6.15 or greater, try rebuilding smartmontools from CVS. If less than 2.6.15 it won't work. Bruce On Thu, 2 Mar 2006, Deepak wrote: > I had already given it a try using -d option earlier. I have tried > "-d ata" as well as "-d sata" option, but no luck. I got the following > error > > --------------- > smartctl -d ata -a /dev/sda > smartctl version 5.33 [i686-pc-linux-gnu] Copyright (C) 2002-4 Bruce Allen > Home page is http://smartmontools.sourceforge.net/ > > Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) > > A mandatory SMART command failed: exiting. To continue, add one or > more '-T permissive' options. > ---------- > > Can anyone shed some light on this? > > On 3/1/06, Jeremy James <jb...@fo...> wrote: >> Deepak wrote: >>> I am getting the following error when starting smartd. >>> >>> ----------- >>> smartd[25998]: Device /dev/sda, SATA disks accessed via libata are not >>> currently supported by smartmontools. When libata is given an ATA >>> pass-thru ioctl() then an additional '-d libata' device type will be >>> added to smartmontools. >>> ----------- >>> >>> I have got harddrives under 3ware controller on the same server and >>> they work just fine. This one is not connected to 3ware card. Could >>> anyone tell me how can I fix the issue. >> >> >> I think the standard procedure is (correct me if I'm wrong): >> >> 1) Use a 2.6.15 kernel (libata only just started supporting pass-through >> for SMART and other commands) >> >> 2) Make sure you're using a recent version of smartmontools (although >> actually 5.32 works fine for me here through an Intel SATA controller) >> >> 3) Run 'smartctl -a -d ata /dev/sda' (or similar - note ata *not* libata) >> >> 4) If you've done all the above and still having problems, let us know. >> >> Best wishes, >> Jeremy >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by xPML, a groundbreaking scripting language >> that extends applications into web and mobile media. Attend the live webcast >> and join the prime developer group breaking into this new coding territory! >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 >> _______________________________________________ >> Smartmontools-support mailing list >> Sma...@li... >> https://lists.sourceforge.net/lists/listinfo/smartmontools-support >> > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd_______________________________________________ > Smartmontools-support mailing list > Sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support > |
From: Leon W. <le...@ma...> - 2006-03-01 23:27:36
|
Hello all, you *might* be bitten by a kernel SCSI midlayer change somewhere in 2.6.13/14/15, that is if you are compiling your own kernels and/or collecting driver sources externally. The Linux SCSI subsystem has been altered so that all SCSI internal I/O goes via the block layer. This change results in the simpler commands also having the scatter/gather flag set. See the 2.6.14 changeset and search for "Fix READ CAPACITY". I had to convert the Marvell driver over to the new model and from using printk I could see INQUIRY (0x12), READ_CAPACITY (0x25) and MODE_SENSE (0x1a) all with use_sg being set, and failing on my newer kernels (because the driver was taken from outside the mainstream kernel sources). I think most of the included drivers have been converted to cope with the new SCSI model, although I have seen late changes in the Changelist of earlier forgotten drivers. If your drive is regconized OK and reports its size correctly this issue does not apply. Just a heads up, regards, Leon. Bruce Allen wrote: > What is your linux kernel version? If 2.6.15 or greater, try > rebuilding smartmontools from CVS. If less than 2.6.15 it won't work. > On Thu, 2 Mar 2006, Deepak wrote: > >> Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) |