Jump to content

RAID 0 - unmountable_boot_volume


Recommended Posts

I've got two raptors (00FLA0 and 41FLC2) on SATA 1 and 2. In BIOS, under Genie Bios Config I have Internal Phy SATA 1/2 Enabled. Under Integrated Peripherals I have RAID Config Enabled with Internal Phy SATA 1 and 2 RAID Enabled. I also turned off all overclocking.

 

When I hit F10 for the RAID Array I see 1 Healthy NVIDIA Stripe 138.49G consisting of 2 raptors, 1 on channel 1 and the other on 0. I'm also using 16KB stripping.

 

During Windows XP Pro (no SP slipstream) installation I hit F6 and choose NVIDIA RAID CLASS DRIVER and NVIDIA nForce Storage Controller. Installation continues to quick format the 138GB drive and copy the installation files. After reboot I enter the cd key, user name, machine name and date/time and continue with the installation. Windows completes its installation process and reboots. During final boot process is when I get the error UNMOUNTABLE_BOOT_VOLUME with technical information 0x000000ED.

 

This is as far as I've gotten. I'm going to try different stripe sizing, although I can't imagine that would make a difference. I've run benches on both drives and they seem to be fine. i'm going to install windows on the new one to make sure it works alright. It's bizarre windows can complete the installation in RAID but can't boot. I feel like it's a drivers issue or something. I got the latest ones off nVidia's website.

 

Please help as RAID was the only reason I bought the second raptor!

 

Thanks!

Share this post


Link to post
Share on other sites

Um wait a mo i know this is basic but i gotta ask, one of your hdd had an os on it previous, if so i would zero the drive with kill disc or something like that first, in fact do it on both hdd's.....then recreate your stripe......

Do you use a 3rd party partition and format proggy? I use Partition Magic 8.5 works a charm,,,,i dont like winblows touching my partitions at all......

 

Logan

Share this post


Link to post
Share on other sites

well, when i created the raid array it asked if i wanted to clear the disks, and i said yes. i assume it's doing a high level 0 to wipe out any partitioning. plus, the problem isn't booting. the problem arises halfway during windows loading, so i can't imagine a partition getting in the way. it's past any partitions and on its way to starting windows when it fails. i'm gonna try the slipstream fist and see if that does the trick before mucking with partitions.

Share this post


Link to post
Share on other sites

douirc,

 

your best bet is to use your drive manufacturer's hard disk utilities and do a low level format on each of the drives. however, make sure to break your array via the raid bios before you perform the low level format. the low level format will write zeros to your entire drive now, including the boot sector and this is what you'll need to accomplish. after that you'll be good to go.

Share this post


Link to post
Share on other sites

ok, i've got a new problem. the good news is i got the system up and running. the bad news is the performance is horrible. i'm not sure how relative this is but, i experienced this same problem when running a single drive and i resolved it by running a previous version of the platform drivers. When using a single drive, platform drivers 6.86 slowed the drive down considerably and driver 6.70 worked like a charm. i'm using the 6.86 drivers for raid, and again, the performance sucks, so i decided to create a second slipstream with the 6.70 drivers assuming that would fix the problem. well, i'm back to square one with the 6.70 drivers in raid since windows won't boot anymore. i get the BSOD during the final load of windows to complete the installation. this time i don't get the same error, actually, worse yet, i get no error, just a BSOD.

 

anyway, i don't understand why the system is so finicky about the driver version. can the bios version have something to do with that?

Share this post


Link to post
Share on other sites

""can the bios version have something to do with that?"" << certainly it can.

 

RGone...:confused:

 

ok, i've got a new problem. the good news is i got the system up and running. the bad news is the performance is horrible. i'm not sure how relative this is but, i experienced this same problem when running a single drive and i resolved it by running a previous version of the platform drivers. When using a single drive, platform drivers 6.86 slowed the drive down considerably and driver 6.70 worked like a charm. i'm using the 6.86 drivers for raid, and again, the performance sucks, so i decided to create a second slipstream with the 6.70 drivers assuming that would fix the problem. well, i'm back to square one with the 6.70 drivers in raid since windows won't boot anymore. i get the BSOD during the final load of windows to complete the installation. this time i don't get the same error, actually, worse yet, i get no error, just a BSOD.

 

anyway, i don't understand why the system is so finicky about the driver version. can the bios version have something to do with that?

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...