From: Marko <mk-...@em...> - 2005-10-23 00:00:12
|
Hi, I have used smartd daemon already quite a while, but only today I noticed that I seem to have a problem with it!!! As you'll see below my 2nd HD (/dev/hdf) shows the required hourly entries in the selftest list, BUT the first HD (/dev/hde) DOES NOT [list entries #2]: Instead there is an unexplained gap of almost 100 (in words: one hundred) or exactly 98 hours here!!! How can this be? I appended my configuration file, log output of the starting smartd, as well as the outputs of "smartctl -l selftest" for both devices. As you will see there is ONE ODD POINT in the log entries of the just started smartd: --- Oct 22 21:51:18 obelix smartd[4718]: Device: /dev/hde, skip scheduled Short Self-Test; 60% remaining of current Self-Test. Oct 22 21:51:18 obelix smartd[4718]: Device: /dev/hdf, starting scheduled Short Self-Test. --- telling me that the scheduled Short Self-Test of the first HD got skipped. WHY? Well, there is already a Self-Test running (assumed being at 60%)... ????? In the logs you see the same thing happening half an hour later. Though smartd found the attribute "Temperature_Celsius" changed on /dev/hde it still persists on skipping the Self-Test... And as it turned out I was able to find also an EXTENDED selftest which got started today at 20:53. And scanning backwards in time through the log I found that this skipping started already in end of August, although through whole July until then both devices had been checked without trouble. !!! It somehow looks like that the ***SMART FIRMWARE GOT HUNG***, !!! OR that smartd itself misinterpreted something... Possibly the directly issued extended test using "smartctl -t long /dev/hde" today somehow was able to overcome smartd's barrier of the "still at 60% running current self-test"!!! Is this possible? I just restarted smartd and see: --- Oct 23 01:50:03 obelix smartd[5525]: Device: /dev/hde, starting scheduled Short Self-Test. Oct 23 01:50:03 obelix smartd[5525]: Device: /dev/hdf, starting scheduled Short Self-Test. --- both test start successfully again... Any ideas? Marko --- My smartd.conf: --- /dev/hde -a -o on -S on -s (S/../.././[0-2][1-9]|L/../../[1-7]/20) /dev/hdf -a -o on -S on -s (S/../.././[0-2][1-9]|L/../../[1-7]/20) --- My log: --- Jul 15 21:27:39 obelix smartd[4374]: Device: /dev/hde, starting scheduled Short Self-Test. Jul 15 21:27:40 obelix smartd[4374]: Device: /dev/hdf, starting scheduled Short Self-Test. Jul 15 22:27:39 obelix smartd[4374]: Device: /dev/hde, starting scheduled Short Self-Test. Jul 15 22:27:40 obelix smartd[4374]: Device: /dev/hdf, starting scheduled Short Self-Test. . . . Aug 24 18:36:35 obelix smartd[4884]: Device: /dev/hde, starting scheduled Short Self-Test. Aug 24 18:36:36 obelix smartd[4884]: Device: /dev/hdf, starting scheduled Short Self-Test. Aug 24 19:06:36 obelix smartd[5197]: Device: /dev/hde, starting scheduled Short Self-Test. Aug 24 19:06:36 obelix smartd[5197]: Device: /dev/hdf, starting scheduled Short Self-Test. Aug 25 21:46:03 obelix smartd[4918]: Device: /dev/hde, skip scheduled Short Self-Test; 60% remaining of current Self-Test. Aug 25 21:46:04 obelix smartd[4918]: Device: /dev/hdf, starting scheduled Short Self-Test. Aug 25 22:16:04 obelix smartd[5221]: Device: /dev/hde, skip scheduled Short Self-Test; 60% remaining of current Self-Test. Aug 25 22:16:04 obelix smartd[5221]: Device: /dev/hdf, starting scheduled Short Self-Test. . . . Oct 21 20:53:47 obelix smartd[4390]: Device: /dev/hde, skip scheduled Long Self-Test; 60% remaining of current Self-Test. Oct 21 20:53:47 obelix smartd[4390]: Device: /dev/hdf, starting scheduled Long Self-Test. . . . Oct 22 21:51:16 obelix smartd[4718]: smartd version 5.34 [i686-suse-linux] Copyright (C) 2002-5 Bruce Allen Oct 22 21:51:16 obelix smartd[4718]: Home page is http://smartmontools.sourceforge.net/ Oct 22 21:51:16 obelix smartd[4718]: Opened configuration file /etc/smartd.conf Oct 22 21:51:16 obelix smartd[4718]: Configuration file /etc/smartd.conf parsed. Oct 22 21:51:16 obelix smartd[4718]: Device: /dev/hde, opened Oct 22 21:51:16 obelix smartd[4718]: Device: /dev/hde, found in smartd database. Oct 22 21:51:16 obelix smartd[4718]: Device: /dev/hde, enabled SMART Attribute Autosave. Oct 22 21:51:16 obelix smartd[4718]: Device: /dev/hde, enabled SMART Automatic Offline Testing. Oct 22 21:51:17 obelix smartd[4718]: Device: /dev/hde, is SMART capable. Adding to "monitor" list. Oct 22 21:51:17 obelix smartd[4718]: Device: /dev/hdf, opened Oct 22 21:51:17 obelix smartd[4718]: Device: /dev/hdf, found in smartd database. Oct 22 21:51:17 obelix smartd[4718]: Device: /dev/hdf, enabled SMART Attribute Autosave. Oct 22 21:51:17 obelix smartd[4718]: Device: /dev/hdf, enabled SMART Automatic Offline Testing. Oct 22 21:51:17 obelix smartd[4718]: Device: /dev/hdf, is SMART capable. Adding to "monitor" list. Oct 22 21:51:17 obelix smartd[4718]: Monitoring 2 ATA and 0 SCSI devices Oct 22 21:51:17 obelix smartd[4718]: Device: /dev/hde, 4 Offline uncorrectable sectors Oct 22 21:51:18 obelix smartd[4718]: Device: /dev/hde, skip scheduled Short Self-Test; 60% remaining of current Self-Test. Oct 22 21:51:18 obelix smartd[4718]: Device: /dev/hdf, starting scheduled Short Self-Test. Oct 22 21:51:18 obelix smartd[5038]: smartd has fork()ed into background mode. New PID=5038. . . . Oct 22 22:21:18 obelix smartd[5038]: Device: /dev/hde, 4 Offline uncorrectable sectors Oct 22 22:21:18 obelix smartd[5038]: Device: /dev/hde, SMART Usage Attribute: 194 Temperature_Celsius changed from 184 to 148 Oct 22 22:21:19 obelix smartd[5038]: Device: /dev/hde, skip scheduled Short Self-Test; 60% remaining of current Self-Test. Oct 22 22:21:19 obelix smartd[5038]: Device: /dev/hdf, SMART Usage Attribute: 209 Offline_Seek_Performnce changed from 146 to 139 Oct 22 22:21:19 obelix smartd[5038]: Device: /dev/hdf, starting scheduled Short Self-Test. . . . Oct 23 01:50:03 obelix smartd[5525]: Device: /dev/hde, starting scheduled Short Self-Test. Oct 23 01:50:03 obelix smartd[5525]: Device: /dev/hdf, starting scheduled Short Self-Test. --- Output of list of selftests: --- obelix:/var/log # smartctl -l selftest /dev/hde smartctl version 5.34 [i686-suse-linux] Copyright (C) 2002-5 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF READ SMART DATA SECTION === SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 195 - # 2 Extended offline Completed without error 00% 194 - # 3 Short offline Completed without error 00% 96 - # 4 Short offline Completed without error 00% 95 - # 5 Short offline Completed without error 00% 95 - # 6 Short offline Completed without error 00% 95 - # 7 Short offline Completed without error 00% 95 - # 8 Short offline Completed without error 00% 94 - # 9 Short offline Completed without error 00% 93 - #10 Short offline Completed without error 00% 92 - #11 Short offline Completed without error 00% 91 - #12 Short offline Completed without error 00% 90 - #13 Short offline Completed without error 00% 90 - #14 Short offline Completed without error 00% 90 - #15 Extended offline Completed: read failure 00% 89 18800162 #16 Short offline Completed without error 00% 88 - #17 Short offline Completed without error 00% 88 - #18 Short offline Completed without error 00% 87 - #19 Short offline Completed without error 00% 86 - #20 Short offline Completed without error 00% 86 - #21 Short offline Completed without error 00% 86 - obelix:/var/log # smartctl -l selftest /dev/hdf smartctl version 5.34 [i686-suse-linux] Copyright (C) 2002-5 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF READ SMART DATA SECTION === SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 464 - # 2 Extended offline Completed without error 00% 463 - # 3 Short offline Completed without error 00% 462 - # 4 Short offline Completed without error 00% 461 - # 5 Short offline Completed without error 00% 460 - # 6 Short offline Completed without error 00% 460 - # 7 Short offline Completed without error 00% 459 - # 8 Short offline Completed without error 00% 458 - # 9 Short offline Completed without error 00% 457 - #10 Short offline Completed without error 00% 456 - #11 Extended offline Completed without error 00% 455 - #12 Short offline Completed without error 00% 454 - #13 Short offline Completed without error 00% 453 - #14 Short offline Completed without error 00% 453 - #15 Short offline Completed without error 00% 452 - #16 Short offline Completed without error 00% 450 - #17 Short offline Completed without error 00% 449 - #18 Short offline Completed without error 00% 449 - #19 Extended offline Aborted by host 40% 449 - #20 Short offline Completed without error 00% 448 - #21 Short offline Completed without error 00% 447 - --- |
From: Volker K. <lis...@pa...> - 2005-10-23 00:10:35
|
> Oct 22 21:51:18 obelix smartd[4718]: Device: /dev/hde, skip scheduled Short Self-Test; 60% remaining of current Self-Test. > telling me that the scheduled Short Self-Test of the first HD got skipped. > WHY? Because at the time, there was already a selftest running, of which 60% was remaining. Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me. |
From: Marko <mka...@we...> - 2005-10-23 00:19:10
|
On Sunday 23 October 2005 02:10, Volker Kuhlmann wrote: > Because at the time, there was already a selftest running, of which 60% > was remaining. As documented this hadn't happened all the time before!!! I can post the logfile where you'd see that whole July and August both HDs got checked as wanted and only then the trouble started. Right now - after having issued the check manually via smartctl - both HDs behave as in July, meaning that the checks get carried out: no "remaining" test anymore. This is a bit odd, isn't it?! Marko |
From: Volker K. <lis...@pa...> - 2005-10-23 01:45:09
|
> As documented this hadn't happened all the time before!!! I can post the > logfile where you'd see that whole July and August both HDs got checked as > wanted and only then the trouble started. I've seen this once too. Either the selftest got stuck forever (I have a disk like that, did I say Maxtor), or I turned the power off while the test was running, and the drive's firmware neither updated the status, nor cancelled or restarted the test. I think it was the latter (did I say Maxtor again?). It means that the automated monitoring facility in smartd falls over when the disk remains at "selftest running" forever, ie smartd changes to doing nothing. Bruce, can you add to todo: if scheduled selftest finds for a second time in a row that the test is already running, explicitly cancel the test, then start the test again. If it still fails because of "still running", create user alert. Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me. |
From: Marko <mk-...@em...> - 2005-10-23 09:03:04
|
On Sunday 23 October 2005 03:45, Volker Kuhlmann wrote: > I've seen this once too. Either the selftest got stuck forever (I have a > disk like that, did I say Maxtor), or I turned the power off while the > test was running, and the drive's firmware neither updated the status, > nor cancelled or restarted the test. I think it was the latter (did I > say Maxtor again?). I see. Looks like the same happened to me, but with a Samsung, as you see below > It means that the automated monitoring facility in smartd falls over > when the disk remains at "selftest running" forever, ie smartd changes > to doing nothing. Yes, so it behaves differently then smartctl!!! Because of this I removed logcheck's ignore-entry on "skipped tests" to be alerted from now on... > Bruce, can you add to todo: if scheduled selftest finds for a second > time in a row that the test is already running, explicitly cancel the > test, then start the test again. If it still fails because of "still > running", create user alert. Well, actually I think the percentage at which the test "currently is" could be used as an indicator that something went wrong in the SMART firmware. Marko ---- obelix:~ # smartctl -i /dev/hde smartctl version 5.34 [i686-suse-linux] Copyright (C) 2002-5 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: SAMSUNG SP0812N Serial Number: S00MJ10XC20460 Firmware Version: TK100-30 User Capacity: 80,060,424,192 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0 Local Time is: Sun Oct 23 11:00:00 2005 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled obelix:~ # smartctl -i /dev/hdf smartctl version 5.34 [i686-suse-linux] Copyright (C) 2002-5 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Model Family: Maxtor DiamondMax 16 family Device Model: Maxtor 4R080J0 Serial Number: R20Z97QE Firmware Version: RAMB1TU0 User Capacity: 81,964,302,336 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0 Local Time is: Sun Oct 23 11:00:03 2005 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled |
From: Bruce A. <ba...@gr...> - 2005-10-23 04:22:20
|
Looks like stuck SMART firmware. That's a new one for me. What type/brand= =20 of disk? Does explicitly aborting/cancelling the test in progress fix the= =20 problem? smartctl -X /dev/hde Cheers, =09Bruce On Sun, 23 Oct 2005, Marko K=E4ning wrote: > Hi, > > I have used smartd daemon already quite a while, but only today I noticed= that > I seem to have a problem with it!!! > > As you'll see below my 2nd HD (/dev/hdf) shows the required hourly entrie= s > in the selftest list, BUT the first HD (/dev/hde) DOES NOT [list entries = #2]: > > Instead there is an unexplained gap of almost 100 > (in words: one hundred) or exactly 98 hours here!!! > > How can this be? I appended my configuration file, log output of the star= ting > smartd, as well as the outputs of "smartctl -l selftest" for both devices= =2E > > As you will see there is ONE ODD POINT in the log entries of the just sta= rted > smartd: > --- > Oct 22 21:51:18 obelix smartd[4718]: Device: /dev/hde, skip scheduled Sho= rt Self-Test; 60% remaining of current Self-Test. > Oct 22 21:51:18 obelix smartd[4718]: Device: /dev/hdf, starting scheduled= Short Self-Test. > --- > telling me that the scheduled Short Self-Test of the first HD got skipped= =2E > WHY? > Well, there is already a Self-Test running (assumed being at 60%)... ????= ? > > In the logs you see the same thing happening half an hour later. > Though smartd found the attribute "Temperature_Celsius" changed on /dev/h= de it > still persists on skipping the Self-Test... > > And as it turned out I was able to find also an EXTENDED selftest which g= ot > started today at 20:53. > > And scanning backwards in time through the log I found that this skipping > started already in end of August, although through whole July until then = both > devices had been checked without trouble. > > !!! It somehow looks like that the ***SMART FIRMWARE GOT HUNG***, > !!! OR that smartd itself misinterpreted something... > > Possibly the directly issued extended test using "smartctl -t long /dev/= hde" > today somehow was able to overcome smartd's barrier of the > "still at 60% running current self-test"!!! > > Is this possible? > > I just restarted smartd and see: > --- > Oct 23 01:50:03 obelix smartd[5525]: Device: /dev/hde, starting scheduled= Short Self-Test. > Oct 23 01:50:03 obelix smartd[5525]: Device: /dev/hdf, starting scheduled= Short Self-Test. > --- > both test start successfully again... > > Any ideas? > > Marko > > > --- > My smartd.conf: > --- > /dev/hde -a -o on -S on -s (S/../.././[0-2][1-9]|L/../../[1-7]/20) > /dev/hdf -a -o on -S on -s (S/../.././[0-2][1-9]|L/../../[1-7]/20) > --- > > My log: > --- > Jul 15 21:27:39 obelix smartd[4374]: Device: /dev/hde, starting scheduled= Short Self-Test. > Jul 15 21:27:40 obelix smartd[4374]: Device: /dev/hdf, starting scheduled= Short Self-Test. > Jul 15 22:27:39 obelix smartd[4374]: Device: /dev/hde, starting scheduled= Short Self-Test. > Jul 15 22:27:40 obelix smartd[4374]: Device: /dev/hdf, starting scheduled= Short Self-Test. > . > . > . > Aug 24 18:36:35 obelix smartd[4884]: Device: /dev/hde, starting scheduled= Short Self-Test. > Aug 24 18:36:36 obelix smartd[4884]: Device: /dev/hdf, starting scheduled= Short Self-Test. > Aug 24 19:06:36 obelix smartd[5197]: Device: /dev/hde, starting scheduled= Short Self-Test. > Aug 24 19:06:36 obelix smartd[5197]: Device: /dev/hdf, starting scheduled= Short Self-Test. > Aug 25 21:46:03 obelix smartd[4918]: Device: /dev/hde, skip scheduled Sho= rt Self-Test; 60% remaining of current Self-Test. > Aug 25 21:46:04 obelix smartd[4918]: Device: /dev/hdf, starting scheduled= Short Self-Test. > Aug 25 22:16:04 obelix smartd[5221]: Device: /dev/hde, skip scheduled Sho= rt Self-Test; 60% remaining of current Self-Test. > Aug 25 22:16:04 obelix smartd[5221]: Device: /dev/hdf, starting scheduled= Short Self-Test. > . > . > . > Oct 21 20:53:47 obelix smartd[4390]: Device: /dev/hde, skip scheduled Lon= g Self-Test; 60% remaining of current Self-Test. > Oct 21 20:53:47 obelix smartd[4390]: Device: /dev/hdf, starting scheduled= Long Self-Test. > . > . > . > Oct 22 21:51:16 obelix smartd[4718]: smartd version 5.34 [i686-suse-linux= ] Copyright (C) 2002-5 Bruce Allen > Oct 22 21:51:16 obelix smartd[4718]: Home page is http://smartmontools.so= urceforge.net/ > Oct 22 21:51:16 obelix smartd[4718]: Opened configuration file /etc/smart= d.conf > Oct 22 21:51:16 obelix smartd[4718]: Configuration file /etc/smartd.conf = parsed. > Oct 22 21:51:16 obelix smartd[4718]: Device: /dev/hde, opened > Oct 22 21:51:16 obelix smartd[4718]: Device: /dev/hde, found in smartd da= tabase. > Oct 22 21:51:16 obelix smartd[4718]: Device: /dev/hde, enabled SMART Attr= ibute Autosave. > Oct 22 21:51:16 obelix smartd[4718]: Device: /dev/hde, enabled SMART Auto= matic Offline Testing. > Oct 22 21:51:17 obelix smartd[4718]: Device: /dev/hde, is SMART capable. = Adding to "monitor" list. > Oct 22 21:51:17 obelix smartd[4718]: Device: /dev/hdf, opened > Oct 22 21:51:17 obelix smartd[4718]: Device: /dev/hdf, found in smartd da= tabase. > Oct 22 21:51:17 obelix smartd[4718]: Device: /dev/hdf, enabled SMART Attr= ibute Autosave. > Oct 22 21:51:17 obelix smartd[4718]: Device: /dev/hdf, enabled SMART Auto= matic Offline Testing. > Oct 22 21:51:17 obelix smartd[4718]: Device: /dev/hdf, is SMART capable. = Adding to "monitor" list. > Oct 22 21:51:17 obelix smartd[4718]: Monitoring 2 ATA and 0 SCSI devices > Oct 22 21:51:17 obelix smartd[4718]: Device: /dev/hde, 4 Offline uncorrec= table sectors > Oct 22 21:51:18 obelix smartd[4718]: Device: /dev/hde, skip scheduled Sho= rt Self-Test; 60% remaining of current Self-Test. > Oct 22 21:51:18 obelix smartd[4718]: Device: /dev/hdf, starting scheduled= Short Self-Test. > Oct 22 21:51:18 obelix smartd[5038]: smartd has fork()ed into background = mode. New PID=3D5038. > . > . > . > Oct 22 22:21:18 obelix smartd[5038]: Device: /dev/hde, 4 Offline uncorrec= table sectors > Oct 22 22:21:18 obelix smartd[5038]: Device: /dev/hde, SMART Usage Attrib= ute: 194 Temperature_Celsius changed from 184 to 148 > Oct 22 22:21:19 obelix smartd[5038]: Device: /dev/hde, skip scheduled Sho= rt Self-Test; 60% remaining of current Self-Test. > Oct 22 22:21:19 obelix smartd[5038]: Device: /dev/hdf, SMART Usage Attrib= ute: 209 Offline_Seek_Performnce changed from 146 to 139 > Oct 22 22:21:19 obelix smartd[5038]: Device: /dev/hdf, starting scheduled= Short Self-Test. > . > . > . > Oct 23 01:50:03 obelix smartd[5525]: Device: /dev/hde, starting scheduled= Short Self-Test. > Oct 23 01:50:03 obelix smartd[5525]: Device: /dev/hdf, starting scheduled= Short Self-Test. > --- > > Output of list of selftests: > --- > obelix:/var/log # smartctl -l selftest /dev/hde > smartctl version 5.34 [i686-suse-linux] Copyright (C) 2002-5 Bruce Allen > Home page is http://smartmontools.sourceforge.net/ > > =3D=3D=3D START OF READ SMART DATA SECTION =3D=3D=3D > SMART Self-test log structure revision number 1 > Num Test_Description Status Remaining LifeTime(hour= s) LBA_of_first_error > # 1 Short offline Completed without error 00% 195 = - > # 2 Extended offline Completed without error 00% 194 = - > # 3 Short offline Completed without error 00% 96 = - > # 4 Short offline Completed without error 00% 95 = - > # 5 Short offline Completed without error 00% 95 = - > # 6 Short offline Completed without error 00% 95 = - > # 7 Short offline Completed without error 00% 95 = - > # 8 Short offline Completed without error 00% 94 = - > # 9 Short offline Completed without error 00% 93 = - > #10 Short offline Completed without error 00% 92 = - > #11 Short offline Completed without error 00% 91 = - > #12 Short offline Completed without error 00% 90 = - > #13 Short offline Completed without error 00% 90 = - > #14 Short offline Completed without error 00% 90 = - > #15 Extended offline Completed: read failure 00% 89 = 18800162 > #16 Short offline Completed without error 00% 88 = - > #17 Short offline Completed without error 00% 88 = - > #18 Short offline Completed without error 00% 87 = - > #19 Short offline Completed without error 00% 86 = - > #20 Short offline Completed without error 00% 86 = - > #21 Short offline Completed without error 00% 86 = - > > obelix:/var/log # smartctl -l selftest /dev/hdf > smartctl version 5.34 [i686-suse-linux] Copyright (C) 2002-5 Bruce Allen > Home page is http://smartmontools.sourceforge.net/ > > =3D=3D=3D START OF READ SMART DATA SECTION =3D=3D=3D > SMART Self-test log structure revision number 1 > Num Test_Description Status Remaining LifeTime(hour= s) LBA_of_first_error > # 1 Short offline Completed without error 00% 464 = - > # 2 Extended offline Completed without error 00% 463 = - > # 3 Short offline Completed without error 00% 462 = - > # 4 Short offline Completed without error 00% 461 = - > # 5 Short offline Completed without error 00% 460 = - > # 6 Short offline Completed without error 00% 460 = - > # 7 Short offline Completed without error 00% 459 = - > # 8 Short offline Completed without error 00% 458 = - > # 9 Short offline Completed without error 00% 457 = - > #10 Short offline Completed without error 00% 456 = - > #11 Extended offline Completed without error 00% 455 = - > #12 Short offline Completed without error 00% 454 = - > #13 Short offline Completed without error 00% 453 = - > #14 Short offline Completed without error 00% 453 = - > #15 Short offline Completed without error 00% 452 = - > #16 Short offline Completed without error 00% 450 = - > #17 Short offline Completed without error 00% 449 = - > #18 Short offline Completed without error 00% 449 = - > #19 Extended offline Aborted by host 40% 449 = - > #20 Short offline Completed without error 00% 448 = - > #21 Short offline Completed without error 00% 447 = - > --- > > > ------------------------------------------------------- > This SF.Net email is sponsored by the JBoss Inc. > Get Certified Today * Register for a JBoss Training Course > Free Certification Exam for All Training Attendees Through End of 2005 > Visit http://www.jboss.com/services/certification for more information > _______________________________________________ > Smartmontools-support mailing list > Sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support > |
From: Marko <mk-...@em...> - 2005-10-23 09:09:11
|
On Sunday 23 October 2005 06:22, you wrote: > Looks like stuck SMART firmware. Yes. > That's a new one for me. What type/brand > of disk? Does explicitly aborting/cancelling the test in progress fix the > problem? Well, I posted that already in my other thread, but for the sake of completeness I appended it below as well. > smartctl -X /dev/hde Yes, that might have the same effect, but I couldn't test it anymore, since only due to my "smartctl -t long /dev/hde" I really became aware of the problem. But of course one could try to force this error once again by shutting down the computer while it is doing a test. And, I will once again go through my /var/log/messages to see when I switched off my comp, perhaps at that moment a selftest had been running. Will report on this later. Marko --- obelix:~ # smartctl -i /dev/hde smartctl version 5.34 [i686-suse-linux] Copyright (C) 2002-5 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: SAMSUNG SP0812N Serial Number: S00MJ10XC20460 Firmware Version: TK100-30 User Capacity: 80,060,424,192 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0 Local Time is: Sun Oct 23 11:00:00 2005 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled |