From: Afonso I. <afo...@po...> - 2003-04-28 23:15:12
|
Hi! I have a motherboard with an integrated Highpoint HPT374 ATA Host = Adapter, and I'm using version 2.01 of Highpoint's own drivers for Linux, as a = module for kernel 2.4.19 (hpt374.o). The drivers use /dev/sd[a-h] for the = disks, although they are IDE. I'm not using RAID at all - I have 3 disks on this adapter, = independently. One of them is an IBM 120GXP, which is known to support SMART (the = others are WDs that don't support SMART). However:=20 # smartctl -a /dev/sdb smartctl version 5.1-10 Copyright (C) 2002-3 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Device: IC35L120 AVVA07-0 Version: VA6O Serial number:=20 Local Time is: Tue Apr 29 01:08:00 2003 CEST Device does not support SMART [No such device] Request Sense failed, [No such device] No Error counter log to report Any idea of what might be wrong? Best regards, AI |
From: Bruce A. <ba...@gr...> - 2003-04-29 04:13:05
|
Hi Alfonso, > I have a motherboard with an integrated Highpoint HPT374 ATA Host > Adapter, and I'm using version 2.01 of Highpoint's own drivers for > Linux, as a module for kernel 2.4.19 (hpt374.o). The drivers use > /dev/sd[a-h] for the disks, although they are IDE. > > I'm not using RAID at all - I have 3 disks on this adapter, > independently. One of them is an IBM 120GXP, which is known to support > SMART (the others are WDs that don't support SMART). However: > > # smartctl -a /dev/sdb > smartctl version 5.1-10 Copyright (C) 2002-3 Bruce Allen > Home page is http://smartmontools.sourceforge.net/ > > Device: IC35L120 AVVA07-0 Version: VA6O > Serial number: > Local Time is: Tue Apr 29 01:08:00 2003 CEST > Device does not support SMART [No such device] > Request Sense failed, [No such device] > > No Error counter log to report > > Any idea of what might be wrong? Because the path /dev/sdb looks like a SCSI device, smartmontools is trying to use SCSI ioctl() calls, which can't get the ATA SMART data. Try using: smartctl -a /dev/sdb --device=ata /dev/sdb and see what happens. A lot depends upon the controller, and I don't know how this one will respond. Cheers, Bruce |
From: Afonso I. <afo...@po...> - 2003-04-29 12:25:54
|
Hi! Actually, I had tried that too, but: # smartctl -a /dev/sdb --device=3Data =20 smartctl version 5.1-10 Copyright (C) 2002-3 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Error ATA GET HD Identity Failed: Invalid argument Smartctl: Hard Drive Read Identity Failed A mandatory SMART command has failed: exiting. To continue, use the -T option to set the tolerance level to 'permissive' # smartctl -a /dev/sdb --device=3Data -T permissive smartctl version 5.1-10 Copyright (C) 2002-3 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Error ATA GET HD Identity Failed: Invalid argument Smartctl: Hard Drive Read Identity Failed =3D=3D=3D START OF INFORMATION SECTION =3D=3D=3D Device Model: [No Information Found] Serial Number: [No Information Found] Firmware Version: [No Information Found] Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 1 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Tue Apr 29 14:06:14 2003 CEST SMART is only available in ATA Version 3 Revision 3 or greater. We will try to proceed in spite of this. SMART support is: Unavailable - device lacks SMART capability. Checking to be sure by trying SMART ENABLE command. Error SMART Enable failed: Invalid argument No SMART functionality found. Sorry. SMART support is: Available - device has SMART capability. SMART support is: Disabled SMART Disabled. Use option -s with argument 'on' to enable it. soundform:~ # So, no luck there... Best regards, Afonso Infante. > -----Original Message----- > From: Bruce Allen [mailto:ba...@gr...] > Sent: dinsdag 29 april 2003 6:12 > To: Afonso Infante > Cc: sma...@li... > Subject: Re: [Smartmontools-support]S.M.A.R.T. Monitoring Tools and = HPT374 > from Highpoint >=20 > Hi Alfonso, >=20 > > I have a motherboard with an integrated Highpoint HPT374 ATA Host > > Adapter, and I'm using version 2.01 of Highpoint's own drivers for > > Linux, as a module for kernel 2.4.19 (hpt374.o). The drivers use > > /dev/sd[a-h] for the disks, although they are IDE. > > > > I'm not using RAID at all - I have 3 disks on this adapter, > > independently. One of them is an IBM 120GXP, which is known to = support > > SMART (the others are WDs that don't support SMART). However: > > > > # smartctl -a /dev/sdb > > smartctl version 5.1-10 Copyright (C) 2002-3 Bruce Allen > > Home page is http://smartmontools.sourceforge.net/ > > > > Device: IC35L120 AVVA07-0 Version: VA6O > > Serial number: > > Local Time is: Tue Apr 29 01:08:00 2003 CEST > > Device does not support SMART [No such device] > > Request Sense failed, [No such device] > > > > No Error counter log to report > > > > Any idea of what might be wrong? >=20 > Because the path /dev/sdb looks like a SCSI device, smartmontools is > trying to use SCSI ioctl() calls, which can't get the ATA SMART data. >=20 > Try using: > smartctl -a /dev/sdb --device=3Data /dev/sdb > and see what happens. A lot depends upon the controller, and I don't = know > how this one will respond. >=20 > Cheers, > Bruce |
From: Bruce A. <ba...@gr...> - 2003-04-29 13:45:01
|
Hi Afonso, [I apologize for mis-spelling your name in my previous email reply.] I'm afraid that there is not much that we can do to reach these disks behind the controller. What the output below shows is that the controller can not pass the raw ATA commands to the disk. Without these, it's impossible to give the SMART commands to the disk. And the driver does not implement enough of the SCSI command set to use the SCSI "equivalent" commands. I'm sorry - it looks like if you want to use the SMART features of the disk, it will either have to be impelemented by the controller driver, or you'll have to attach the disks to an IDE-type controller. Cheers, Bruce On Tue, 29 Apr 2003, Afonso Infante wrote: > Hi! > > Actually, I had tried that too, but: > > # smartctl -a /dev/sdb --device=ata > smartctl version 5.1-10 Copyright (C) 2002-3 Bruce Allen > Home page is http://smartmontools.sourceforge.net/ > > Error ATA GET HD Identity Failed: Invalid argument > Smartctl: Hard Drive Read Identity Failed > > A mandatory SMART command has failed: exiting. To continue, use the -T > option to set the tolerance level to 'permissive' > > # smartctl -a /dev/sdb --device=ata -T permissive > smartctl version 5.1-10 Copyright (C) 2002-3 Bruce Allen > Home page is http://smartmontools.sourceforge.net/ > > Error ATA GET HD Identity Failed: Invalid argument > Smartctl: Hard Drive Read Identity Failed > > === START OF INFORMATION SECTION === > Device Model: [No Information Found] > Serial Number: [No Information Found] > Firmware Version: [No Information Found] > Device is: Not in smartctl database [for details use: -P showall] > ATA Version is: 1 > ATA Standard is: Exact ATA specification draft version not indicated > Local Time is: Tue Apr 29 14:06:14 2003 CEST > SMART is only available in ATA Version 3 Revision 3 or greater. > We will try to proceed in spite of this. > SMART support is: Unavailable - device lacks SMART capability. > Checking to be sure by trying SMART ENABLE command. > Error SMART Enable failed: Invalid argument > No SMART functionality found. Sorry. > SMART support is: Available - device has SMART capability. > SMART support is: Disabled > > SMART Disabled. Use option -s with argument 'on' to enable it. > soundform:~ # > > So, no luck there... > > Best regards, > > Afonso Infante. > > > -----Original Message----- > > From: Bruce Allen [mailto:ba...@gr...] > > Sent: dinsdag 29 april 2003 6:12 > > To: Afonso Infante > > Cc: sma...@li... > > Subject: Re: [Smartmontools-support]S.M.A.R.T. Monitoring Tools and HPT374 > > from Highpoint > > > > Hi Alfonso, > > > > > I have a motherboard with an integrated Highpoint HPT374 ATA Host > > > Adapter, and I'm using version 2.01 of Highpoint's own drivers for > > > Linux, as a module for kernel 2.4.19 (hpt374.o). The drivers use > > > /dev/sd[a-h] for the disks, although they are IDE. > > > > > > I'm not using RAID at all - I have 3 disks on this adapter, > > > independently. One of them is an IBM 120GXP, which is known to support > > > SMART (the others are WDs that don't support SMART). However: > > > > > > # smartctl -a /dev/sdb > > > smartctl version 5.1-10 Copyright (C) 2002-3 Bruce Allen > > > Home page is http://smartmontools.sourceforge.net/ > > > > > > Device: IC35L120 AVVA07-0 Version: VA6O > > > Serial number: > > > Local Time is: Tue Apr 29 01:08:00 2003 CEST > > > Device does not support SMART [No such device] > > > Request Sense failed, [No such device] > > > > > > No Error counter log to report > > > > > > Any idea of what might be wrong? > > > > Because the path /dev/sdb looks like a SCSI device, smartmontools is > > trying to use SCSI ioctl() calls, which can't get the ATA SMART data. > > > > Try using: > > smartctl -a /dev/sdb --device=ata /dev/sdb > > and see what happens. A lot depends upon the controller, and I don't know > > how this one will respond. > > > > Cheers, > > Bruce > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Smartmontools-support mailing list > Sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support > |
From: <kn...@mo...> - 2003-04-29 14:26:35
|
On Tue, 29 Apr 2003, Bruce Allen wrote: >I'm sorry - it looks like if you want to use the SMART features of the >disk, it will either have to be impelemented by the controller driver, or >you'll have to attach the disks to an IDE-type controller. Afonso: have you tried a newer 2.4.x kernel and the kernels own highpoint drivers? 2.4.21rc1 or 2.4.21rc1ac2 might be good candidates to try. These would probably expose the disks in the standard ide way. Warning: don't try if you don't know what you're doing. Keep backups handy - it may very well crash and do evil things to your data :/ I have had a few bad experiences with highpoint-provided drivers on $OTHER_OS. -- Erik I. Bolsø | email: <knan at mo.himolde.no> The UNIX philosophy basically involves giving you enough rope to hang yourself. And then a couple of feet more, just to be sure. |
From: Afonso I. <afo...@po...> - 2003-04-29 14:37:25
|
Hi! > On Tue, 29 Apr 2003, Bruce Allen wrote: > >I'm sorry - it looks like if you want to use the SMART features of = the > >disk, it will either have to be impelemented by the controller = driver, or > >you'll have to attach the disks to an IDE-type controller. >=20 > Afonso: have you tried a newer 2.4.x kernel and the kernels own = highpoint > drivers? 2.4.21rc1 or 2.4.21rc1ac2 might be good candidates to try. >=20 > These would probably expose the disks in the standard ide way. Yes, I believe that the kernel's drivers do support it, however, last = time I tried they didn't work with the HPT374 very well. The problem now is = that since the device names would change, trying the kernel drivers will be a = lot of work, especially because I have my root volume hanging off one of the disks (/dev/sda). =20 > Warning: don't try if you don't know what you're doing. Keep backups > handy - it may very well crash and do evil things to your data :/ Ah, yes. But I know what I'm doing *and* I keep backups. :-) =20 > I have had a few bad experiences with highpoint-provided drivers on > $OTHER_OS. That makes two of us! :-) > The UNIX philosophy basically involves giving you enough rope to > hang yourself. And then a couple of feet more, just to be sure. Very true! :-) Best regards, Afonso Infante. |
From: <kn...@mo...> - 2003-04-29 15:00:09
|
On Tue, 29 Apr 2003, Afonso Infante wrote: >> On Tue, 29 Apr 2003, Bruce Allen wrote: >> >I'm sorry - it looks like if you want to use the SMART features of the >> >disk, it will either have to be impelemented by the controller driver, or >> >you'll have to attach the disks to an IDE-type controller. >> >> Afonso: have you tried a newer 2.4.x kernel and the kernels own highpoint >> drivers? 2.4.21rc1 or 2.4.21rc1ac2 might be good candidates to try. >> >> These would probably expose the disks in the standard ide way. > > Yes, I believe that the kernel's drivers do support it, however, last time >I tried they didn't work with the HPT374 very well. The problem now is that >since the device names would change, trying the kernel drivers will be a lot >of work, especially because I have my root volume hanging off one of the >disks (/dev/sda). Tricky, I agree. How about taking a slackware live cd (or other cd-bootable-and-runnable linux distro) and customizing it a little (add newest kernel and smartmontools), boot from it and test smartmontools from there? Then, if it works, mount the root partition and do the necessary changes. That cd saved me recently when my root reiserfs had to be repaired... (of course reiser decides to have a flaky moment just when I'm in the middle of upgrading slackware 8.1 to slackware 9.0, thus half my device files disappeared so I couldn't log in) >> Warning: don't try if you don't know what you're doing. Keep backups >> handy - it may very well crash and do evil things to your data :/ > > Ah, yes. But I know what I'm doing *and* I keep backups. :-) > >> I have had a few bad experiences with highpoint-provided drivers on >> $OTHER_OS. > > That makes two of us! :-) Thus, I don't trust highpoint-provided drivers on Linux :) -- Erik I. Bolsø | email: <knan at mo.himolde.no> The UNIX philosophy basically involves giving you enough rope to hang yourself. And then a couple of feet more, just to be sure. |
From: Afonso I. <afo...@po...> - 2003-05-05 20:41:11
|
Hi! " Tricky, I agree. How about taking a slackware live cd (or other cd-bootable-and-runnable linux distro) and customizing it a little (add newest kernel and smartmontools), boot from it and test smartmontools from there? Then, if it works, mount the root partition = and do the necessary changes. That cd saved me recently when my root reiserfs had to be repaired... (of course reiser decides to have a flaky moment just when I'm in the middle of upgrading slackware 8.1 to slackware 9.0, thus half my device files disappeared so I couldn't log in) " OK, I browsed through the source code and apparently in the 2.4.x = kernels only the -ac series has HPT374 support. For some reason that escapes me = the "official" tree has HPT-series drivers from 2 years ago, which dodn't support the HPT374. Sad, but true. I cannot use the -ac series because I use xfs and the xfs patches = and/or modules were made for the official tree.=20 The latest 2.5.x do have both XFS and HPT374 support but I don't want = to try a 2.5.x kernel because they still have too many issues. So, apparently I'll have to wait for 2.6.x... Or 3.0.x (has Linus = decided yet?). " >> I have had a few bad experiences with highpoint-provided drivers on >> $OTHER_OS. > > That makes two of us! :-) Thus, I don't trust highpoint-provided drivers on Linux :) " I wouldn't blame Highpoint too much. They provide ample info for Open Source developers. Promise, for example, is not as forthcoming and builds horrible = drivers too. I recently had a pretty bad experience with Promise: I had to build = a desktop with a brand new Asus P4C800 motherboard with the new Promise PDC20378 chip on it (besides an Intel ICH5); for reasons I won't discuss = :-) the PC had to have $OTHER_OS installed, but the Promise driver was so = bad it froze the computer for a fraction of a second each time the HD was = accessed. So the chip is simply unusable as long as they don't fix this bug. Highpoint drivers suffered from the same problem - 2 years ago! They = have long since fixed them... Best regards, Afonso Infante. |