On Fri, Feb 26, 2010 at 9:27 AM, Alex Schuster <[email protected]> wrote: > Mark Knecht writes: > >> On Fri, Feb 26, 2010 at 8:01 AM, Alex Schuster <[email protected]> >> wrote: > >> > Okay, but it still states: >> >> * SMART error logging >> >> * SMART self-test >> > >> > So maybe smartctl -t long /dev/hda still works? Just give it a try. >> >> No, -t long fails the same way. Basically every time I try to use >> smartctl on the drive it seems to issue one of these 3-line reports >> about SectorIDNotFound in dmesg. My other machines don't do this. Not >> a good sign I think... >> >> hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error } >> hda: task_no_data_intr: error=0x10 { SectorIdNotFound }, >> LBAsect=16777008, sector=18446744073709551615 >> hda: possibly failed opcode: 0xb0 > > Uh-oh. Okay, I guess it just won't work then. > > >> Could this have ANYTHING to do with kernel configuation? Is there >> anything required at the kernel level that I might not have turned on? > > I'm pretty sure it has nothing to do with the kernel, but with your drive > being incapable of the SMART commands. > > But I guess using badblocks is not that different in the end. The SMART > selftest runs in the background and does not create disk I/O, but I think > it does nothing so much different from badblocks. > > Wonko > >
The machine _mostly_ crashed while running badblocks. I say mostly because the mouse is still alive but I can no longer ssh in and cannot open a terminal on my wife's desktop or get to the console. I tried to Ctrl-C out out of badblocks here (this is running shelled in) before I figured out it was a total crash which messed up the terminal a bit but you can see what it was reporting before the crash dragonfly ~ # badblocks -sv /dev/hda Checking blocks 0 to 156290903 Checking for bad blocks (read-only test): 89360960done, 35:00 elapsed 89360961done, 35:09 elapsed 89360962 89360963 ^C^C18% done, 35:27 elapsed So, there seem to be problems, possibly with the drive, or maybe it's some sort of overheating problem on the processor and this was just the way the processor failed before the crash? I ran memtest86 night before last for 8 hours and had no memory problems. I'll remove memory and PCI cards, reseat everything, and then see what happens. - Mark
