From: "D.A.M. Revok" <marvin@synapse.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19, don't "hdparm -I /dev/hde" if hde is on a Asus A7V133 Promise ctrlr, or...
Date: Sun, 15 Dec 2002 17:25:57 -0500 [thread overview]
Message-ID: <200212151725.57046.marvin@synapse.net> (raw)
In-Reply-To: <200212152139.gBFLdI1p002059@darkstar.example.net>
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
2. why have 2 terminals on one machine when I'm a hermit?
I /do/ thank you for the interface-reset tip, though, I hope I never need
that info : )
On Sun 15 December, 2002 16:39, you wrote:
>> have to use the power-switch to get the machine back
>
>If you have another terminal accessible, you could try:
>
>hdparm -w /dev/hda
>
>to reset the interface. I can't guarantee that it wouldn't loose
>data, though.
>
>John.
--
http://www.drawright.com/
- "The New Drawing on the Right Side of the Brain" ( Betty Edwards,
check "Theory", "Gallery", and "Exercises" )
http://www.ldonline.org/ld_indepth/iep/seven_habits.html
- "The 7 Habits of Highly Effective People" ( this site is same
principles as Covey's book )
http://www.eiconsortium.org/research/ei_theory_performance.htm
- "Working With Emotional Intelligence" ( Goleman: this link is
/revised/ theory, "Working. . . " is practical )
http://www.leadershipnow.com/leadershop/1978-5.html
- Corps Business: The 30 /Management Principles/ of the U.S. Marines (
David Freedman )
next prev parent reply other threads:[~2002-12-15 22:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-15 20:49 D.A.M. Revok
2002-12-15 21:39 ` John Bradford
2002-12-15 22:25 ` D.A.M. Revok [this message]
2002-12-15 23:37 ` John Bradford
2002-12-18 18:19 ` Ross Biro
2002-12-18 18:17 ` Ross Biro
2002-12-18 21:10 ` Andre Hedrick
2002-12-18 21:19 ` Ross Biro
[not found] <233C89823A37714D95B1A891DE3BCE5202AB1B35@xch-a.win.zambeel.com>
2002-12-18 10:38 ` D.A.M. Revok
2002-12-18 10:44 ` Andre Hedrick
2002-12-18 21:35 ` D.A.M. Revok
2002-12-18 22:01 ` Andre Hedrick
2002-12-18 22:38 ` Alan Cox
2002-12-18 21:58 ` Andre Hedrick
2002-12-18 22:03 ` D.A.M. Revok
2002-12-19 1:11 ` Alan Cox
2002-12-19 14:40 ` Denis Vlasenko
2002-12-19 10:19 ` Andre Hedrick
2002-12-19 11:14 ` Tomas Szepe
2002-12-19 11:45 ` Andre Hedrick
2002-12-19 12:03 ` Tomas Szepe
2002-12-19 12:41 ` Andre Hedrick
2003-01-16 18:54 ` Ookhoi
2002-12-19 15:14 ` Denis Vlasenko
2002-12-19 10:33 ` Andre Hedrick
2002-12-19 18:12 ` Ross Biro
2002-12-19 6:47 ` Ross Vandegrift
[not found] ` <Pine.LNX.4.10.10212181359350.8350-100000@master.linux-ide. org>
2002-12-19 13:26 ` Stephen Satchell
[not found] <200212182204.gBIM48uD000332@darkstar.example.net>
2002-12-18 22:18 ` D.A.M. Revok
2002-12-19 2:02 ` Mike Dresser
2002-12-21 23:22 Jason Radford
2003-01-17 16:47 ` Paul Jakma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200212151725.57046.marvin@synapse.net \
--to=marvin@synapse.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome