jdff
asked on
Highpoint Raid Won't boot
Pretty big problem, after one year using a highpoint rocketraid 3120 with 2 ssd drives running raid 0 on windows 7 ultimate x64 today it froze on me and it stayed beeping until rebooted, so when the windows logo came up it showed a quick blue screen and it rebooted again, please help I need to get back on my system. The raid console states that the raid state is normal, so I'm no sure if it is crashing when it trys to load the raid driver, it may be possible I guess.
ASKER
It can't see the c partition when I try a system restore, I tried to load the raid drivers but still it does not see the c partition so the recovery won’t go any further. Do you think that I can use a different brand controller? Will the new controller see my raid 0? It still unclear to me if the controller went bad or if it is one of the ssd drives that went bad. I've also tried to boot with unbutun linux cd and when it try to load the controller it triggers the beeping alarm continually.
ASKER
I was able to read the blue screen:
UNMOUNTABLE_BOOT_VOLUME
0X000000ED
In safe mode it stoped at classpnp.sys
I guess it has to do with a raid corruption what do you think? Is the a repair feature out of the raid console, woudl that be the same as rebuild? Is this risky?
Thanks for your help, I realy need it.
UNMOUNTABLE_BOOT_VOLUME
0X000000ED
In safe mode it stoped at classpnp.sys
I guess it has to do with a raid corruption what do you think? Is the a repair feature out of the raid console, woudl that be the same as rebuild? Is this risky?
Thanks for your help, I realy need it.
You need to pray a little that the damage is not extensive; but, you also need to boot your Windows 7 DVD and use the repair options to chkdsk the raid. The first time, run it without the /F option to see what it says. If it reports unreadable sectors, you are in very deep kimchi. The stop 0x000000ED means you need to check the volume: http://www.windows7ultimate.windowsreinstall.com/repairwin7startup/index.htm
ASKER
I guess I could try checkdisk however on the image attached I can't sse the volume at all.
indexf5.jpg
indexf5.jpg
If there is data on that D partition you need to backup, you would do best to get another drive, install Windows on it, and use that to then copy thos files to a DVD or USB drive for backup. If you can disable the raid controller in the BIOS while doing so, it won't be at risk while you prepare.
Apparently, something has corrupted the boot record (not MBR) for C or the partition table. After Windows is working on another drive (or if you just want to be brave and pray) EASEUS partition manager might be able to recover it: http://www.partition-tool.com/partition-recovery-wizard/ (The FREE edition ought to be fine)
Apparently, something has corrupted the boot record (not MBR) for C or the partition table. After Windows is working on another drive (or if you just want to be brave and pray) EASEUS partition manager might be able to recover it: http://www.partition-tool.com/partition-recovery-wizard/ (The FREE edition ought to be fine)
ASKER
I gues I could try to connect the drives just as a regular sata drive not using the raid controller and see if I can retrive data out of it right? Will that cause any damage to the drive content?
Thanks
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok, so tomorrow I will buy a sata connect to the motherboard local controller instead of the highpoint controller, then install windows 7 plus the drivers for the highpoint controller and see if we can use the easeus as you said, does it make sense to you?
ASKER
A new raid controller has been ordered. I'm waiting on that.
Thanks
jdff
Thanks
jdff
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
Note which is the last driver to load before the system blue screens. My guess is with the alarm you probably had some kind of RAID failure that caused data corruption. The RAID might be healthy in the console but the data could have corrupted. RAID 0 offers no parity so the console can't tell if the data is ok.
You might be able to recover with System Restore. Press F8 before the windows logo and select Repair your computer or boot from your Windows 7 install CD and select Repair your computer.