Re: 2.4.19, don't "hdparm -I /dev/hde" if hde is on a Asus A7V133 Promise ctrlr, or...

[John Bradford <john@bradfords.org.uk>]

> man, the Magic SysReq key didn't work ( at all ):
> it were DEAD
> The drive-light stayed on for 10+ hours, nothing happening ( that I could 
> figure out ) the whole time.  It /stayed/ dead.
> 
> /dev/hde is part of a RAID-5 in my system ( because I no longer trust 
> anything else ), and this only happens on drives connected onto the 
> Promise controller.
> 
> Oh, yeah, I forgot to include this:
> trying to touch/activate/read the S.M.A.R.T. in any drive on the Promise 
> kills it, too.  Can't activate the reliability-system without killing 
> the kernel? /that's/ ironic, eh?
> 
> 
> As for having another terminal connected to my home machine...
> 1. if the kernel's dead, then how's that gonna work, and

Maybe just the console was not responding.

If I start X with /dev/null as the core pointer, the console locks
completely, but I can still log in on a serial terminal.

I have seen machines which will mostly stop responding when you issue
a sleep command to a disk, E.G.

hdparm -Y /dev/hda

you can't terminate the process with control-C, for example, but if
you are logged in on another virtual terminal, or have another
terminal window open in X, you can reset the interface, and the
machine will respond again.

> 2. why have 2 terminals on one machine when I'm a hermit?

Why not?  I read and write a lot of E-Mail on a serial terminal right
next to my main console, and what about debugging SVGALIB applications?

> I /do/ thank you for the interface-reset tip, though, I hope I never need 
> that info  : )

It can be useful for recovering from a spun-down disk that won't spin
up again :-)

John