After restarting the server (due to system instability), I was notified about a FOREIGN CONFIG.
LCD Showed a failure on disk 0:3.
The foreign drives appeared to be two drives that were previously configured in a RAID1 mirror (disks 0:10 and 0:11). They were no longer showing under the Controller in their previous Virtual Disk
I was unable to import the foreign config.
I was able to CLEAR the foreign config.
After clearing the config, the disks were marked in a READY state.
I was not given the option to REBUILD the disks.
After marking the disks as Global HotSpares I was still unable to REBUILD the disks.
I have now unmarked them as Global HotSpares.
How can I reinstate this disk structure (ideally without losing the data)?
You can only rebuild a 'failed' drive, which is why it won't let you rebuild anything. For one, the controller does not acknowledge the existence of the RAID array, so a drive cannot be rebuilt in it. And two, the drive would need to be assigned as a hot-spare to that [non-existent] array to start a rebuild.
The config needed to be imported, but since that did not work, that may mean the config was (or is now) too corrupt to use.
To do a retag, you will need to create a new Virtual Disk with EXACTLY the same parameters (stripe size, VD size, etc.), but leave the Advanced/Initialize boxes UNCHECKED.
There is no guarantee here that you will get anything useful back.
Thanks. It seems one of the drives has many bad sectors although SMART is not detecting this. I have replaced them with two new drives and am trying to recover the data from one of the disks.
Is there a way to retag just one drive (in case the recovery fails)?
Because of the bad sectors on the disk, I don't believe it is safe to RETAG the disk.
Okay, so following on from my original question:
I have sent one of the disks (the most recently failed disk) away for data recovery. They have given me the option of providing a sector by sector copy of the disk.
- If I put this new disk into the controller will it recognise the disk as part of an array?
- Does the restoration specialist need to write the old serial number from the original disk to the new disk?
- If not, how do I get the controller to see the disk without reinitialising it or making it part of a new array?
- Is RETAGGING the new disk my only option?
- Is there some way to find out / read the RAID configuration parameters (stripe size, VD size etc) ?
To complicate matters further, the server is actually running Citrix XenServer, so the disk doesn't have a simple file system that I can just read in any other computer. How do I get this data back and readable?
PS. Please don't lecture me about backups. :)
Our last two full weekly backups appear to have backed up successfully (from the logs and the data size of the backup file), but somehow they are corrupt too and we can't open them.
- If I put this new disk into the controller will it recognise the disk as part of an array?
That depends. The reason a retag becomes necessary is when the controller no longer recognizes the RAID configuration/metadata on the drive. Plug it in and turn it on ... if the drive shows up as part of the array OR if the drive is marked as foreign, then the controller at least recognized the configuration.
- Does the restoration specialist need to write the old serial number from the original disk to the new disk?
I don't know if they do, or if they can.
- If not, how do I get the controller to see the disk without reinitialising it or making it part of a new array?
The controller should see the disk, if the disk is healthy, regardless of the state of the RAID configuration on it. If the controller does not recognize the disk as having a valid configuration, then "retagging" the drive (which, again, simply writes a new configuration to the disk) is the only way to get the controller to see a config. There are utilities that can discover what the RAID configuration is supposed to be (RAID Reconstructor is one - free to try, pay to recover).
- Is RETAGGING the new disk my only option?
See above.
- Is there some way to find out / read the RAID configuration parameters (stripe size, VD size etc) ?
See above.
To complicate matters further, the server is actually running Citrix XenServer, so the disk doesn't have a simple file system that I can just read in any other computer. How do I get this data back and readable?
At this point, if simply plugging it in doesn't work, then you'll need to try a DYI RAID recovery (RAID Reconstructor) ... or professional data recovery.
Thanks theflash1932. Looks like I'll have to give that a go.
Just to confirm, I should be following these steps:
1. Add the disk back to the controller and see if the controller picks it up.
2. Failing that, try retagging the disk (without initialising it) to see if that allows the controller to identify it correctly.
3. Failing that, use RAID Reconstructor (although it doesn't seem to work with RAID1???) to reconstruct the RAID array. Then attempt phase 1 and 2 again.
Step one is great. Step two may work, but if you retag the disk by itself, you will be retagging it as the sole member of a RAID 0, not a RAID 1, so I don't know if this can be successful. Step three ... I've only heard of RR from others and have never used it myself, so I am not completely familiar with how it is used (or about RAID 1 not being supported, although it may be unnecessary, given the drives are just mirrored), but my impression is that RR analyzes the disks for a config, then allows you to copy the disk data - assembled as a RAID array - onto a single drive for the purpose of accessing/recovering the data. After using RR, it will not work for steps one and two ... RR is for recovering data, not for repairing RAID arrays.
"They have given me the option of providing a sector by sector copy of the disk."
This is just one of the options they should offer, which is the easiest for them as they do it with a hardware based cloning device . They should offer the option to recover the files to another disk with a non raid format.
Should the retag fail and RR failes to resurrect, get a single disk or 2 disks, setup as raid 0 or raid1, get a basic OS on it, get decent file recovery software (not the freeware junk) (Knoll/Seagate), and try to recover the files on the defaunct raid disk(s). If the sector by sector copy of the disk is reasonably priced go for it before playing with the original raid drive. Knoll/Seagate software is a read only program so it will not damage the data.
theflash1932
11 Legend
•
16255 Posts
1572
0
Posted October 18th, 2012 23:00
You can try what is called a retag.
You can only rebuild a 'failed' drive, which is why it won't let you rebuild anything. For one, the controller does not acknowledge the existence of the RAID array, so a drive cannot be rebuilt in it. And two, the drive would need to be assigned as a hot-spare to that [non-existent] array to start a rebuild.
The config needed to be imported, but since that did not work, that may mean the config was (or is now) too corrupt to use.
To do a retag, you will need to create a new Virtual Disk with EXACTLY the same parameters (stripe size, VD size, etc.), but leave the Advanced/Initialize boxes UNCHECKED.
There is no guarantee here that you will get anything useful back.