Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Stuart Levine <stuart@reveltech.com>
To: linux-raid@vger.kernel.org
Subject: Help!  Head crash on IDE Seconday Master.  Slave has all the data but wont boot
Date: Sat, 23 Nov 2002 07:38:32 -0500	[thread overview]
Message-ID: <3DDF76C8.8070605@reveltech.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]

Hi,

So I build this great new P4 2.53GHz server.  I had two WD 100GB Caviar 
Special editions running in a RAID1 format.  All seemed fine except one 
drive was very noisy and caused excessive vibrations.  Thought nothing 
of it because it's less than a month old.  Well, I was wrong, very 
wrong.  Last night the drive failed and the next boot up sequence left 
me with sound I will never forget.  Anyway, until I get a new drive to 
rebuild and supplant the array, I was going to boot from /dev/md0 (/boot 
partition) but to no avail the system does not want to recognize it as a 
boot disk.  If I boot up in rescue mode, it says there are no partitions 
on the disk (/dev/md0).  However, if I use the fdisk -l I get what you 
would expect including a BOOT partition.  Luckily, I did make the 
emergency boot floppy and I am able to boot the system on from that 
floppy for the ROOT partition on the disk /dev/md2.  So, how do I tell 
the boot loader to look at /dev/hdd instead of /dev/hdc (the dead disk 
in the raid pair) without loosing my installed data?  I now new to RAID, 
however, I am new to software RAID in Linux.  Any help and advise would 
be greatly appreciated.

Thanks in advance,

Stuart

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3253 bytes --]

             reply	other threads:[~2002-11-23 12:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-23 12:38 Stuart Levine [this message]
2002-11-24  1:01 ` Help! Head crash on IDE Seconday Master. Slave has all the data but wont boot Massimiliano Masserelli

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=3DDF76C8.8070605@reveltech.com \
    --to=stuart@reveltech.com \
    --cc=linux-raid@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