I have a server with software-mirrored
drives (using the Windows Disk Administrator). Yesterday it suddenly
shutdown and would not boot back up. It would start to load Windows and get
as far as the blue screen that shows the NT version at the top but then
after a few seconds it would reboot itself. It would just keep looping this
way until being powered off. No errors appear on the screen. Safe Mode and
and
the Last Known Good do the same thing. To get around it for now I went into
the server's BIOS and switched it to boot from Disk1 rather than Disk0. Now
it boots up fine. (This surprised me -- I didn't have to edit the boot.ini
or anything).
I checked the mirror when it came up. I have two partitions
mirrored on these two disks, C: and D:. The D: partition was fine, the C:
partition was "broken", with the C: partition on Disk0 highlighted in red.
So I broke the mirror of C:, rebooted (from Disk1
again), deleted the C: partition on Disk0, rebooted again, temporarily
created a new partition with the free space on Disk0 and did a full format
on it (as a precaution), deleted that partition, then created a mirror of
the C: partition on Disk1 and the free space on Disk0. I committed the
changes and waited for it to finish initializing. When it said "healthy"
I rebooted and switched the BIOS back to Disk0. I also ran diagnostics on
both disks at this point and all the tests passed successfully.
Unfortunately, the boot problem didn't go away. The server still loops and
never boots successfully from Disk0. I can still boot off Disk1,
and the now the mirror of C: always says Healthy, but it doesn't seem like
the mirror is doing me much good if I'll never be able to boot off Disk0.
Any help would be greatly appreciated. Thanks!
xe77 - 26 Feb 2005 18:47 GMT
Sounds like either a problem with the disk or the controller hardware.
>I have a server with software-mirrored
>drives (using the Windows Disk Administrator). Yesterday it suddenly
[quoted text clipped - 24 lines]
>the mirror is doing me much good if I'll never be able to boot off Disk0.
>Any help would be greatly appreciated. Thanks!
Jiri Tuma - 28 Feb 2005 11:13 GMT
Is it possible to start from NT boot floppy when disk 0 is primary?
NT boot floppy you can make if you format floppy under any NT system and
copy to it following files from root of C:
NTLDR., NTDETECT.COM, BOOT.INI and, if exist, also NTBOOTDD.SYS
Using of NT floppy will avoid all MBR and primary boot codes and local NT
loader files and will bring control just to NT kernel on boot partition.
Check content of mbr sector on disk 0, it is possible to have something
wrong here causing effect you described. Either wrong MBR code or invalid
MBR table record can affect success of booting NT system. For example old
boot sector viruses residing in MBR code will cause the same behavior of NT
system you described (even I do not believe you can get such type of virus
today, they are practically dead). Use dskprobe.exe tool from NT resource
kit to check content and order of records in MBR table (if you have not any
better commercial tool). MBR code on primary (first physical) disk can be
usually replaced by IBM compatible code by running "FDISK /MBR" command from
MS-DOS system floppy (any version from 5 to 6.22), see www.bootdisk.com for
good prepared floppy image (in case you have not any). Always make checked
backup of MBR before you try to do changes in it! If you have proprietary
designed server, it is possible it needs proprietary boot code on primary
disk, check server documentation. To save MBR, you can use disksave or
dskprobe tools from NT resource kit.
> I have a server with software-mirrored
> drives (using the Windows Disk Administrator). Yesterday it suddenly
[quoted text clipped - 24 lines]
> the mirror is doing me much good if I'll never be able to boot off Disk0.
> Any help would be greatly appreciated. Thanks!