From: hans <har...@m0...> - 2005-02-17 22:36:24
|
hi all i did compile smartmontools-5.33 successfully on solaris 9 ultra sparc IIIi ( sun v240 ) if i key in "smartctl -a /dev/rdsk/c1t0d0s0" i get usefull values (see below), but on the console i get the following message: scsi: WARNING: /pci@1c,600000/scsi@2/sd@0,0 (sd0): Error for Command: <undecoded cmd 0x4d> Error Level: Informational scsi: Requested Block: 0 Error Block: 0 scsi: Vendor: SEAGATE Serial Number: 0438B964RN scsi: Sense Key: Illegal Request scsi: ASC: 0x24 (invalid field in cdb), ASCQ: 0x0, FRU: 0xa it looks for me, that command x4d couldn't be understood independent the used harddisk. is there a way to modify source, so that x4d isn't sent and recompile smartctl ? best regards hans --------------------- result of smartctl ------------------------------------------------- smartctl version 5.33 [sparc-sun-solaris2.9] Copyright (C) 2002-4 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Device: SEAGATE ST373307LSUN72G Version: 0507 Serial number: 3HZ964RN0000751072N8 Device type: disk Transport protocol: Parallel SCSI (SPI-4) Local Time is: Thu Feb 17 23:25:37 2005 CET Device supports SMART and is Enabled Temperature Warning Enabled SMART Health Status: OK Current Drive Temperature: 22 C Drive Trip Temperature: 68 C Vendor (Seagate) cache information Blocks sent to initiator = 739812597 Blocks received from initiator = 270156189 Blocks read from cache and sent to initiator = 791737140 Number of read and write commands whose size <= segment size = 104837229 Number of read and write commands whose size > segment size = 0 Vendor (Seagate/Hitachi) factory information number of hours powered up = 2569.75 number of minutes until next internal SMART test = 28 Error counter log: Errors Corrected by Total Correction Gigabytes Total EEC rereads/ errors algorithm processed uncorrected fast | delayed rewrites corrected invocations [10^9 bytes] errors read: 4572251 0 0 4572251 4572251 7266.191 0 write: 0 0 0 0 0 180.442 0 Non-medium error count: 9509 Error Events logging not supported SMART Self-test log Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ] Description number (hours) # 1 Background short Completed - 2 - [- - -] # 2 Background short Completed - 2 - [- - -] Long (extended) Self Test duration: 1488 seconds [24.8 minutes] |
From: Bruce A. <ba...@gr...> - 2005-04-20 06:54:29
|
Casper, Keiji, Doug, Any ideas about this? Cheers, Bruce On Thu, 17 Feb 2005, hans wrote: > > > hi all > > i did compile smartmontools-5.33 successfully > on solaris 9 ultra sparc IIIi ( sun v240 ) > if i key in "smartctl -a /dev/rdsk/c1t0d0s0" > i get usefull values (see below), but on the console i > get the following message: > > scsi: WARNING: /pci@1c,600000/scsi@2/sd@0,0 (sd0): > Error for Command: <undecoded cmd 0x4d> Error Level: Informational > scsi: Requested Block: 0 Error Block: 0 > scsi: Vendor: SEAGATE Serial Number: 0438B964RN > scsi: Sense Key: Illegal Request > scsi: ASC: 0x24 (invalid field in cdb), ASCQ: 0x0, FRU: 0xa > > it looks for me, that command x4d couldn't be understood > independent the used harddisk. > is there a way to modify source, so that x4d isn't sent > and recompile smartctl ? > > best regards > hans > > > --------------------- result of smartctl ------------------------------------------------- > smartctl version 5.33 [sparc-sun-solaris2.9] Copyright (C) 2002-4 Bruce Allen > Home page is http://smartmontools.sourceforge.net/ > > Device: SEAGATE ST373307LSUN72G Version: 0507 > Serial number: 3HZ964RN0000751072N8 > Device type: disk > Transport protocol: Parallel SCSI (SPI-4) > Local Time is: Thu Feb 17 23:25:37 2005 CET > Device supports SMART and is Enabled > Temperature Warning Enabled > SMART Health Status: OK > > Current Drive Temperature: 22 C > Drive Trip Temperature: 68 C > Vendor (Seagate) cache information > Blocks sent to initiator = 739812597 > Blocks received from initiator = 270156189 > Blocks read from cache and sent to initiator = 791737140 > Number of read and write commands whose size <= segment size = 104837229 > Number of read and write commands whose size > segment size = 0 > Vendor (Seagate/Hitachi) factory information > number of hours powered up = 2569.75 > number of minutes until next internal SMART test = 28 > > Error counter log: > Errors Corrected by Total Correction Gigabytes Total > EEC rereads/ errors algorithm processed uncorrected > fast | delayed rewrites corrected invocations [10^9 bytes] errors > read: 4572251 0 0 4572251 4572251 7266.191 0 > write: 0 0 0 0 0 180.442 0 > > Non-medium error count: 9509 > > Error Events logging not supported > > SMART Self-test log > Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ] > Description number (hours) > # 1 Background short Completed - 2 - [- - -] > # 2 Background short Completed - 2 - [- - -] > > Long (extended) Self Test duration: 1488 seconds [24.8 minutes] > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Smartmontools-support mailing list > Sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support > > |
From: Casper.Dik@Sun.COM - 2005-04-20 07:00:02
|
>Casper, Keiji, Doug, > >Any ideas about this? > >Cheers, > Bruce Why not supress the error message on the console with the USCSI_DIAGNOSE (I think) which causes the errors to be only returned to you and not written to the console. Casper |
From: Bruce A. <ba...@gr...> - 2005-04-20 15:33:18
|
> >Casper, Keiji, Doug, > > > >Any ideas about this? > > > >Cheers, > > Bruce > Why not supress the error message on the console with the > USCSI_DIAGNOSE (I think) which causes the errors to be only returned > to you and not written to the console. Casper, apologies, I don't know anything about this. Is USCSI_DIAGNOSE a flag that one needs to set in the low-level ioctl()s or is it something else, for example an environment variable? Cheers, Bruce |
From: Casper.Dik@Sun.COM - 2005-04-20 16:08:24
|
>> >Casper, Keiji, Doug, >> > >> >Any ideas about this? >> > >> >Cheers, >> > Bruce > >> Why not supress the error message on the console with the >> USCSI_DIAGNOSE (I think) which causes the errors to be only returned >> to you and not written to the console. > >Casper, apologies, I don't know anything about this. Is USCSI_DIAGNOSE a >flag that one needs to set in the low-level ioctl()s or is it something >else, for example an environment variable? Sorry, it may have been USCSI_SILENT; it's a flag you or into the uscsi_flags field to prevent errors from being generated as console messages. Casper |
From: Bruce A. <ba...@gr...> - 2005-04-20 19:10:36
|
> >> Why not supress the error message on the console with the > >> USCSI_DIAGNOSE (I think) which causes the errors to be only returned > >> to you and not written to the console. > > > >Casper, apologies, I don't know anything about this. Is USCSI_DIAGNOSE a > >flag that one needs to set in the low-level ioctl()s or is it something > >else, for example an environment variable? > > Sorry, it may have been USCSI_SILENT; it's a flag you or into the > uscsi_flags field to prevent errors from being generated as console > messages. Code is here (you wrote it!): http://cvs.sourceforge.net/viewcvs.py/smartmontools/sm5/os_solaris.c?rev=1.25&view=markup Is it just a matter of changing uscsi.uscsi_flags = USCSI_READ; uscsi.uscsi_flags = USCSI_WRITE ; uscsi.uscsi_flags |= USCSI_ISOLATE; to read uscsi.uscsi_flags = USCSI_READ | USCSI_SILENT; uscsi.uscsi_flags = USCSI_WRITE | USCSI_SILENT; uscsi.uscsi_flags |= USCSI_ISOLATE | USCSI_SILENT; Cheers, Bruce |
From: Casper.Dik@Sun.COM - 2005-04-20 19:19:23
|
>> >> Why not supress the error message on the console with the >> >> USCSI_DIAGNOSE (I think) which causes the errors to be only returned >> >> to you and not written to the console. >> > >> >Casper, apologies, I don't know anything about this. Is USCSI_DIAGNOSE a >> >flag that one needs to set in the low-level ioctl()s or is it something >> >else, for example an environment variable? >> >> Sorry, it may have been USCSI_SILENT; it's a flag you or into the >> uscsi_flags field to prevent errors from being generated as console >> messages. > >Code is here (you wrote it!): >http://cvs.sourceforge.net/viewcvs.py/smartmontools/sm5/os_solaris.c?rev=1.25&view=markup > >Is it just a matter of changing > > uscsi.uscsi_flags = USCSI_READ; > uscsi.uscsi_flags = USCSI_WRITE ; > uscsi.uscsi_flags |= USCSI_ISOLATE; > >to read > > uscsi.uscsi_flags = USCSI_READ | USCSI_SILENT; > uscsi.uscsi_flags = USCSI_WRITE | USCSI_SILENT; > uscsi.uscsi_flags |= USCSI_ISOLATE | USCSI_SILENT; I believe so, yes. Casper |
From: hans <har...@m0...> - 2005-04-23 20:25:37
|
hi thanks to all followed the thread. > > uscsi.uscsi_flags = USCSI_READ | USCSI_SILENT; > > uscsi.uscsi_flags = USCSI_WRITE | USCSI_SILENT; > > uscsi.uscsi_flags |= USCSI_ISOLATE | USCSI_SILENT; > > I believe so, yes. > > Casper i have changed the source described above and the messages on console and /var/adm/messages did disappear. best regards hans -- |