Problem with boot after expanding RAID0.

[Konrad Klar]

Two day ago I have decided to buy new identical SATA HD and expand existing 1 disk RAID0 to 2 disk RAID0. RAID0 has been expanded without problem (i.e. MediaShield -converting program, doest not respond, that there is problem). NVIDIA nForce(tm) RAID Class Controller was obviously installed.
Data on disks does not seems to be broken. There are two installations of OS on RAID. One of OS installation on the disk (WindowsXP x32) does not boot completely. Boot logo is displayed and probably at least some of drivers are loaded (because LEDs on my Thomson ADSL modem are ligting green - i.e. initialized). However login window is never displayed.
WindowsXP x64 starts and works without problem.

Question is: is any method/chance of repairing problem with XP x32 without reinstalation. (Boot in Safe Mode or in VGA mode does not work).
My config: Athlon64 3000, 1.5GB RAM, Gigabyte K8NS-939 (nForce3Ultra), 2x WD2500JS.

Thanks in advance.

[squid_80]

How long have you left it to make sure it doesn't boot? Since I added/removed some drives on my system, it sometimes sits at the windows boot logo screen (appearing to do nothing) for up to four minutes.

[foxyshadis]

Squid_80, that sounds like the PNP failure I had on the original drive in my old system. The drive itself might not be failing but its IDE interface might be, or the controller perhaps (had to be the interface on mine, same act on different systems). System would always run fine after the excruciating wait for the PNP timeout, until I found some hack to reduce the wait time, though the event logs still got spammed with warnings. (I replaced it anyway, so I don't know if it was really on the verge of dying or not.)

Never fixed software/chipset raids so I can't help the OP. You might get something out of a bootlog though.

[squid_80]

There's no problem in the logs, I think it's just confused because there's a cd drive connected where a hard drive used to be. A clean install of XP works fine.

[Konrad Klar]

How long have you left it to make sure it doesn't boot? Since I added/removed some drives on my system, it sometimes sits at the windows boot logo screen (appearing to do nothing) for up to four minutes.

squid_80@25 minutes and more of waiting.

There is one (significant or meaningless) detail: XP x64 was installed originally on 1disk SATA RAID0, XP x32 was installed on IDE drive and whole IDE disk has been copied 1:1 onto 1disk RAID0, obviously after installation SATA and RAID drivers in system.

Maybe this is reason for which XP x64 works without problem and XP x32 does not boot correctly after expanding RAID?

Any thoughts, ideas?

[Blue_MiSfit]

A note,

RAID of any kind cannot be done with only one hard drive. So not sure what you mean when you say a 1 drive RAID 0.

You might want to try a repair installation. Just some suggestions.

I hate troubleshooting stuff like this :)

~MiSfit

[Konrad Klar]

A note,

RAID of any kind cannot be done with only one hard drive. So not sure what you mean when you say a 1 drive RAID 0.



I know that this sounds funny: "1 disk RAID0", although this is required that 1 disk configuration was configured as RAID0 in order expanding it to the real RAID0 by adding additional disks in future. At least in case of RAIDs on nVidia chipsets .

Cheers.

[Blue_MiSfit]

I see. That's cool that you can do that - just add another drive and automatically have the nvraid build the stripe.

Apparently there are issues though! :)

~MiSfit