Re: Bootmgr installed on wrong drive in SBS 2008 Installation

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Probably wrong terminology on my part - the machine bios has a disk order, seperate from the raid bios.

--
Les Connor [SBS-MVP]


____________________________
<anton.hopen@xxxxxxxxx> wrote in message news:5db16136-4d31-4c9c-916e-50eec64bcc79@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I did try switching the boot order between the two arrays. The new
server #3 is only using a single disk array for drive C and another
single disk for drive D (just for testing). However, since the RAID
is done at at the BIOS level I don't think it should matter. Windows
should just see them as two volumes, right? I also went in and did
NTFS formats on server #3 drives C and D so I can see them after I
boot up the SBS 2008 DVD. However, before I try the failed restore,
the SBS 2008 software warns me it is going to format and repartition
them anyway. I found the following comment that relates to your at
http://social.technet.microsoft.com/forums/en-US/itprovistasetup/thread/bf0d6f28-f2f6-4610-9edd-5ba5e9b9a8a2/:
------------------------------***
I had a RAID array failure and tried with Windows Complete PC Restore
as I regularly made backups on external drive, booted with Vista DVD
and tried but the restore operation failed at start with 0x80070490
(Element not found). I then entered the BIOS and did find out that the
RAID volumes order used under BOOT section was changed. There wasn't
anymore as primary Disk my first drive Volume of the array, but the
second. That made the Restore refusing the operation. I switched back
the first Volume of the array to the top of the list and tried again:
the operation went on smoothly. I strongly suggest checking your bios
for HDD boot priority (not just peripherals), the volume Windows was
using as first on your Backup must be re-set at first in the list
after (as in my case) physical disk exchange in order for the restore
procedure to work out.
------------------------------***

I try that one more time and post the results. Just to recap, the
hardware between server #2 (source) and server #3 (destination) are
very close. Both are Dell 2970s. Both have two RAID volumes. Both
have the same RAID controller, etc....

On Dec 17, 10:03 am, "Les Connor" <les.con...@xxxxxxxxxxxx> wrote:
Could it be that the 4 drive array is listed first in the bios boot order?
SBS 2008 will always install to the c: drive, but if the 4 drive array is
listed first then perhaps that's the cause. Just a guess though.

.

Relevant Pages

  • Re: Gigabyte New Build Issue
    ... hard drives and the SB600 raid controller. ... Digital drives in a RAID 0 configuration, but I cannot use the latest F4 BIOS with ... to wipe parts of the disk. ...
    (alt.comp.hardware.pc-homebuilt)
  • Re: Hard disk failing check > mobo strange behaviour
    ... I ran the Seatool test and result confirm that all the ide connectors are ok but the hard disk is failing. ... as long as one of the drives is a Seagate etc. ... The BIOS has the ability to store info in two places. ... If the flash chip is wearing out, ...
    (microsoft.public.windowsxp.hardware)
  • Re: Grub hangs - two hard drives and a CD
    ... > What you wrote is all based on a wrong assumption that grub numbers drives ... > that the BIOS will call to boot an OS. ... The Bios calls to read disk require the register DL to ...
    (comp.os.linux.setup)
  • Re: Building a file server - advice please
    ... > connecting up 5 drives in a RAID5 system does not affect the Mean Time To ... > important reason to use a RAID system. ... Hardware controllers generally can have an additional spare disk configured ... Hardware raid presents each raid array to the host as one disk, ...
    (comp.os.linux.setup)
  • Re: I give up on RAID
    ... Three of them are 1.5TB drives and about two weeks ago I tied them together into a single 4.5TB RAID 0 set which I partitioned for storage of various types of data. ... Not only had the one drive become non-RAID, but BIOS had changed a bit too. ... end of the disk. ...
    (alt.comp.periphs.mainboard.asus)