Unmountable_boot_volume
Hi,
I'm hoping that some of you hardware enthusiasts can shed some light on a problem I'm currently having with a rig.
The current situation is that while booting Windows XP Proffessional, the computer will go directly to blue screen before finishing booting, claiming
UNMOUNTABLE_BOOT_VOLUME
*** STOP: 0x000000ED (0x8239AB98, 0xc00000A3,0x00000000,0x00000000)
Upon closer inspection with the Safe Mode start, it seems to be hangin at Mup.sys, at least thats the last thing that pops up efore the BSOD.
I had a quick look on the Microsoft Knowledge Base for information about the problem and it seems that this type of problem is related to cahce writing on NTFS format drives, which would make sense. I wasnt around th last time the computer booted, but the way I understand it the computer was in-game, and froze and was almost immediatly restarted, which would explain if perhaps the cache had not fully cleared and then some crucial bootable data had been left there and not written back the hard drive.
For whatever reason windows is not automatically starting chkdisk when it boots to try and deal with the problem. On the Microsoft Knowledge Base, it says to use the WinXP cd to do a commandline restore from the boot cd. I tried this, but unfortunatly, I'm using 2 80gb dirves in stripping raid, and my raid controller disk doesnt seem to want to cooperate in WinXP start up.
The current situation is basically that i cant get to any of my data, because no standard MS Dos boot disk will see the raid hdds, and WinXP in all start up modes blue screens. Also the WinXP Boot CD cant go any further without the Promise RAID controller drivers.
What I think i need to do is just be able to run chkdisk on the raid array, i think. I'm really not sure if i'm going up the right avenue at all.
Is it possible that some other peice of hardware could be causing the problem?
If it is the raid array, will chkdisk be able to do anything for it?
Is there any floppy bootdisk out there that will just give me a command prompt to run chkdisk from and will be able to see the RAID hdds?
I'd appreciate any thoughts you had on this at all, as its really naging at me. Even if its just to say you read through and have absolutely no idea, or you've had the same problem before and just had to trash the hdds.
THANKS a bunch everyone.
For My full Sys Stats, pls see
http://www.susu.org/~andrewc/sysstat.html
Hi,
I'm hoping that some of you hardware enthusiasts can shed some light on a problem I'm currently having with a rig.
The current situation is that while booting Windows XP Proffessional, the computer will go directly to blue screen before finishing booting, claiming
UNMOUNTABLE_BOOT_VOLUME
*** STOP: 0x000000ED (0x8239AB98, 0xc00000A3,0x00000000,0x00000000)
Upon closer inspection with the Safe Mode start, it seems to be hangin at Mup.sys, at least thats the last thing that pops up efore the BSOD.
I had a quick look on the Microsoft Knowledge Base for information about the problem and it seems that this type of problem is related to cahce writing on NTFS format drives, which would make sense. I wasnt around th last time the computer booted, but the way I understand it the computer was in-game, and froze and was almost immediatly restarted, which would explain if perhaps the cache had not fully cleared and then some crucial bootable data had been left there and not written back the hard drive.
For whatever reason windows is not automatically starting chkdisk when it boots to try and deal with the problem. On the Microsoft Knowledge Base, it says to use the WinXP cd to do a commandline restore from the boot cd. I tried this, but unfortunatly, I'm using 2 80gb dirves in stripping raid, and my raid controller disk doesnt seem to want to cooperate in WinXP start up.
The current situation is basically that i cant get to any of my data, because no standard MS Dos boot disk will see the raid hdds, and WinXP in all start up modes blue screens. Also the WinXP Boot CD cant go any further without the Promise RAID controller drivers.
What I think i need to do is just be able to run chkdisk on the raid array, i think. I'm really not sure if i'm going up the right avenue at all.
Is it possible that some other peice of hardware could be causing the problem?
If it is the raid array, will chkdisk be able to do anything for it?
Is there any floppy bootdisk out there that will just give me a command prompt to run chkdisk from and will be able to see the RAID hdds?
I'd appreciate any thoughts you had on this at all, as its really naging at me. Even if its just to say you read through and have absolutely no idea, or you've had the same problem before and just had to trash the hdds.
THANKS a bunch everyone.
For My full Sys Stats, pls see
http://www.susu.org/~andrewc/sysstat.html