Slashdot Mirror
Manually-Confirgured Software RAID Under NT?
Mandoric asks: "I recently had a RAID-0 array die due to the controller refusing to recognize it as anything but a pair of single drives. Are there any software RAID programs (preferably under NT, as it's an NTFS partition I'd be restoring) that allow manual entry of a preexisting array's stripe size, rather than forcing all stripe data to be rewritten before reading from an array? Or ways to modify the volume data of an existing program to do this?" Are there decent RAID tools, for either NT or for Unix, that will allow one to recover from errors such as this?
conFIGured.
i know its petty but...
That man tried to kill mah Daddy
I'm pretty sure Win2K server has this feature built in.
This is one of the several reasons why software RAID, especially under NT is a bad idea. While there may be an obscure utility out there, chances are slim. Your likely only hope is going to be a disk editor.
With RAID 0, software or hardware, your best solution is going to be tape. But, it sounds like you don't have that option. Treat the incident as a learning experience and move on.
NT4 and above have always supported software RAID, most commonly RAID-0, and in the server editions RAID-1 too (I think it did some others, I'm not sure).
Neither of these will help since you are having to recover the data, and even so the hardware controller may have a differant format to the NT one etc (same goes for any controller).
I think the best solution, if you dont have a backup is talk to the people like Ontrack - they can recover almost anything.
FTedit from the NT/2k resource kit can do manual stuff with a striped set. Unfortunately I'm sure this won't help you recovering from a hardware RAID misconfiguration since software and hardware RAID don't mix, they simply use different formats
Well, it's probably not the easiest approach but one that is definately looking into IMHO:
;-)
/dev/hd?? > hexdump to see how data is arranged on the disks. Hardware RAID does usually not put special data blocks on the disks that make it unaccessible for these tools.
;-)
- pop the disks into a linux or un*x system on a free controller port
- pop in an extra empty disk to salvage the data to. preferable larger than both disk together
- try to figure out the block size of the stripes (usually a multiple of 512 bytes)
- write a simple script that reads block n from broken RAID disk 1, and writes it to block 1 in the empty disk, then block 1 from broken RAID disk 2, to block 2 in the empty disk (ask your local unix guru)
You can fiddle with mount, df and cat
As an example, I run a software RAID and unmounted it cleanly, then remounted only one of both disks at the same point (so without the mirroring). Worked like a charm, also a nice way to continue working when one disk completely fails or you want to make copies fast
good luck
You didn't mention anything about your hardware, but I had the exact same thing happen to me with the Highpoint 370 controller on a KT7-RAID motherboard. I rebooted one day to find that the HPT BIOS would say only "broken stripe." I figured my NTFS partition was toast. But there is a utility, raidrb, which I think is written by either Via or Highpoint. Anyway you just boot from a floppy and run it and it "reassures" the controller that the stripe is really ok.
a ds/utils/raidrb.zip
http://download.viahardware.com/faq/kg7kr7/downlo
There is some discussion of other methods to try if this one does not work in the Raid section on Paul's KT7 page. (Google search for "kt7 faq" for the url.)
I am curious as to what the job of the server that the raid card was in was. After all, if he truly meant Raid 0, then that is striping without fault tolerance. If you had one drive fail, then the whole raid array would fail and he'd be in the same situation. Now there is an advantage in speed when it comes to drive access, but still, a single disk failure would take out the whole array. That is not unlike what happened here in that the raid array failed when the controller bombed.
That being the case, he should have backups somewhere to restore the data from. I wouldn't trust anything mission critical to a raid 0 array. Besides, when the controller went down, who's to say that it didn't basically shred the data on the disk apart? If the data is being spread across 2 disks, and now the computer sees them as two separate disks instead of one larger disk, then the data on the two disks is probably toast to begin with. (with the exception of going to those companies that do sector by sector data recovery from a hard drive for ungodly sums of money)
I guess the only thing I could suggest is to redo the server with Raid 1 minimum, and hope that your backups are good. There's no telling what that raid card did to your system when it failed.
-Through the server, over the router, off the firewall... Nothing but 'Net!
Veritas Volume Manager for NT/2000 can do this.
t De tail.jhtml?productId=volumemanagerwin
http://www.veritas.com/products/category/Produc
Only one problem. It is very expensive.
Conformity is the jailer of freedom and enemy of growth. -JFK
There was a resource kit utility to open up software RAID sets and fix them under NT/2000. I have played with it only to see what it does, and that was years ago. It was made for exactly what you're talking about doing.
However...
I don't think that's a good idea. I don't think you're going to get done in software what the hardware was doing for you. If the data is truly sacred, I think one of the other posters was correct: go to a data-recovery service and let a professional do it. If the data is only partly holy, then try finding a utility from the controller maker.
dk
Acts 17:28, "For in Him we live, and move, and have our being."
Because your array was in hardware raid you may need to replace the the controller card. It may just get picked back up as it was if the drives or data didnt sustain any dammage.
use ghost or dd to back the contents of the drives up anyways incase the hardware solution has to re initialize the array from scratch.
you maybe able to find a controller that will work with software that can help fix your problem but i wouldnt count on software raid doing it.
shoulda used raid 0+1 maybe even 3 or 5
on Tom's Hardware entitled: "RAID without additional hardware: Do It Yourself With Windows 2000"
i nd ex.html
http://www4.tomshardware.com/howto/01q3/010906/
This sounds like a issue with the hardware, most likely one that tech support will tell you how to fix, or if not, how to recover your data. At least you would hope they would know...
Slackware: old school feel, new school gear.
haha!
NT matters?
./ should increase their microsoft how to topics. After all it is in the spirit of ./ right?
I say
Wondering what the hell all of this RAID stuff is about, don't worry...your plants are safe!!! To calm you further, I thought I would be generous and give you a brief description of the various levels.
But first, in case you road the "short bus" to school, we are not discussing the bug spray or what the Feds do to your dope stash... RAID is a commonly used acronym for Redundant Array of Inexpensive Disks!!!
Now, on to the various levels of RAID... The most common are as follows:
o RAID 0 : Striping without redundancy (a.k.a. no fault tolerance)
o RAID 1 : Transparent Mirroring
o RAID 3 : Striping with Parity for High Data Transfers
o RAID 4 : Striping with Parity for High Data Transfers
o RAID 5 : Striping with parity for High I/O transaction rates
Beer is proof that God loves us and wants us to be happy. -- Benjamin Franklin
I hope this teaches you to purchase quality products in the future.
How does NT stripe? Some blocks on the first disk, some blocks on the next, some on the first, ... without any metadata at the beginning?
Then this should be fairly easy. Find out which block size is used, boot from some linux rescue CD and initialize a software raid without persistent superblock. After that you should be able to mount the NTFS partition (at least for reading) and copy everything off it.
If there is some data before the actual partition, you can use the loop device with the offset parameter to skip the junk.
So if I have a raid 1 setup, that is the exact same stuff on both disks that I would have on a single disk, right? So if I decided to pop out one disk and put it into another box, it could be used normally, i.e. there isn't weird stuff on the disk because it's raid 1, right?
Spoon not. Fork, or fork not. There is no spoon.
That is the utility in the resource kit that will allow you to manually edit fault tolerant sets.
Hopefully it will do the trick for you.