Thanks for this suggestion - doesn't work. The result is the information
about disk hardware problem and suggestion to check Windows documentation. I
found out that the RAID 5 volume is the first accessible volume, then
follows RAID 1 volume with the system. I can't swap it in BIOS. In this
configuration, the first accessed MBR should be on the RAID 5 volume, which
might be corrupted, therefore it hangs - would be this plausible?
I also tried to add one disk, where I wanted to install another copy of
Windows Server, to backup the original MBR before I'd try to fix it in a
recovery console - but after the installation, the same message about
hardware problem pops up.
Do you (or anyone!) have any suggestion?
One additional information - the system is x64. The message, when I try to
boot from another device, is exactly:
"Windows could not start because of a computer disk hardware configuration
problem.
Could not read from the selected boot disk. Check root path and disk
hardware."
But when go to the recovery console, I see all disk content and chkdsk says
there is no problem at all (!).
Robert
"Pegasus (MVP)" <> wrote in message
news:...
>
> "Robert Goldwein" <> wrote in message
> news:...
>> Hello all,
>>
>> Our server board Intel SE7221 died, so I replaced it - and the RAID
>> controller - Intel SRCS16, also known as LSI MegaRaid 6 - ceased to work.
>>
>> The configuration is 4 SATA disks in RAID 5 with backup battery - when I
>> start Windows Server recovery console, the logical partition is
>> "visible",
>> data there are "visible", but it's not accessible - Windows Server
>> doesn't
>> recognize it as a Windows NT partition (weird, how it could be visible
>> then?).
>>
>> I ran chkdsk (in the recovery console), it says the entire partition is
> OK.
>> When I try to boot, it doesn't boot at all - ntloader hangs (the cursor
>> keeps blinking and the only option is reset). When I tried to install
>> side
>> installation of Windows Server, the installer displays correct NTFS
> logical
>> partition, but when I select it, it says that this partition is not
>> recognized by Windows.
>>
>> I ran memory tests, CPU tests, S.M.A.R.T. tests.
>>
>> Now I run consistency check, it seems it will take many many hours, but
> the
>> result is quite uncertain... Any suggestions what's wrong?
>>
>> Robert
>>
>>
>
> Try booting it with a Windows boot disk. Here is how to
> make one:
> - Format a floppy disk on some Win2000/XP PC.
> Don't do it on a Win9x PC - it won't work.
> - Copy these hidden files from your system disk to A:
> C:\ntldr
> C:\ntdetect.com
> C:\boot.ini
> - Check out boot.ini. If it makes reference to some driver file,
> copy that one too.
>
>
|