The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

[OT] Boot troubles on RAID array


  • Subject: [OT] Boot troubles on RAID array
  • From: "Semi Jon" <semi.jon@xxxxxxxxxxxxx>
  • Date: Tue, 16 Jan 2007 13:05:57 -0000

My PC has a striped array that when I first built it ~5 years ago it
booted
from happily.  A couple of years ago I added an extra disk (almost as fast
as the array!) copied the boot partition to that as a back-up and
re-installed W2k on the array.
On boot I was offered the opportunity to boot from either installation.
At the w/e I had a clean up and formatted the copy of the orginal boot
partition and have not been able to boot since :-(  Obviously the boot
information was on the new HDD rather than the array.

I have:
-Checked the array health and that confirmed that it is bootable
-disconnected the extra disk
-Run the recovery console automatic repair process(which sees the W2K
installation)
-copied from CD NTLDR, ntdetect.com
-Copied from another w2k installation a default boot.ini (see below)
- run fixboot from the recovery console

Still no joy - I now get the message "BOOT FROM ATAPI CD-ROM, DISK
BOOT
FAILURE, INSERT SYSTEM DISK AND PRESS ENTER" in caps, I am not
shouting ;-)

I suspect the boot.ini, but don't understand the syntax of the file ... can
anyone advise?
Also any tips on how to edit boot.ini in the recovery console - AFAICS it
doesn't seem to have an editor?

TIA
Jon
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT

[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000
Professional" /fastdetect






UKHA_D Main Index | UKHA_D Thread Index | UKHA_D Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.