yesterday i changed my hard drives from two sata wd 2500 in raid 0 to a single raptor 150. i did a fresh xp install on the raptor which went okay, but when i tried to use each of the wd 2500 as separate storage drives (not in raid 0) i could only format one of the drives. the drive i could not format reported an incorrect disc volume of around 450 gb which previously was the total striped raid 0 volume. the drive i could format reported a correct disc volume of around 250. i used disk manager in xp to re-format the drives.
has anybody encountered this when using drives previously in raid 0 as single storage drives? is there a way to salvage the drive that won't format? thanks.
unplug the raptor, plug the drive that you cannot format, start windows install, have the drive listed, delete all partition existing on that drive and you'll be fine. Normally, before removing an array, it is better to delete the array first and remove the disk after..
If that doesn;t work, try a low level format, or just rewriting the MBR and last tracks of the fisk.
The software is usually available form the hard drive manufacturers web site...
Low formatting a drive is something that to many peoples don't understand.
Low level formatting was usefull with old RLL disk interface and another one I forget, but has been make unavailable for IDE drive since ATA exist ...
Low level formatting meant redefining the sector, cluster... on the drive. Now, when you plug in the drive, everything is already done, and cannot be undone. Writting 0 to the drive or deleting MBR is not low level.. it is simply wiping..
Definitely don't ever low level format, it's completely and utterly unnecessary these days!
I had the same issue with my drives when I broke up my array, I just plugged the old driver into the ports they were connected to before and used the raid manager to delete the array. I do believe the raid partition info is in the MBR of the 0 drive.
Low level formatting HAS fixed problems for me when the MBR has become corrupt...... I dont understand why you are so ANTI it.....
Drives can become corrupted by changing the chipsets on which the Raid array operated. I know, because that is EXACTLY what happened to mine. The ONLY way to remedy that was to restore the drive to its new state. The only way I knew to do that was to Low Level it....
A low level format for fixing the MBR is like killing a fly with a sledge hammer. You can use the m$ recovery console and I believe Maxtor and Seagate make utilities for wiping the MBR.
I love you guys nostalgizing over the old, great, DOSasaurus days!
Just amazing stuff - the ground that was broken.
And, Fishmahn, I did the same thing with 40's. Small world.
Did you play with the debug app, to access hdd at BIOS level with INT13? I did long ago.. You could do anything to a drive. That was nice. Don't remember if it was with IDE or older interface thou... I did a small assembler app that was called "fast" that was putting a new value right into the some place and make the CPU to run faster.. I did one called "slow" for the inverse..
Too bad I forgot these .. Anyway, I could have a 16 MHz 286 running near 20 MHz with that.. Yup.. MHz
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.