RAID Degraded - how mount the disk as standard bootable disk
The chase: I have removed two disks from a 10.3.9 software mirror RAID
set using the 10.4GM diskutil.
One now has a partition map with slice 4 of type "Apple_RAID", the
other disk has slice 4 of type "Apple RAIDOfflineV2". How do I get one
or both back to being normal Journaled HFS+ volumes without wiping their
data?
At the very least, I need technical doc for Software RAID - a google for
Apple_RAID
yields absolutely no hits - nor does a search on Developer Connection.
---
Disclaimer: I know what I did here was wrong and that I need to go back
to a backup. No need for anyone to waste their time on a helpful post to
tell me this - but thanks in advance for the thoughts anyway.
The detail:
It started out as a sunny day in Sydney, Australia. Life seemed good.
The night before I had upgraded a 2x2Ghz G5 PowerMac from Panther Server
to Tiger Server successfully.
Kerberos, AFP, DHCP, DNS were all smoothly up and running, as was Samba,
Apache and even JBoss.
I had gotten IMAP and POP running where others had failed - Apple
includes an invalid TLSNames attribute in the cyrus config file that
needs to be deleted to allow mail delivery to kick off.
The jewel in the crown... My HP5510 printer was even behaving properly
with the new server and print serving was finally working again using
IPP - it had been broken under Panther.
So, I thought, before I go to bed I had better just check the world is
good with disk utility.
Alas, I found that my software mirror was in a 'degraded' state. I had
forgotten that before I did the Tiger upgrade I had attempted to split
one drive from the array and leave it powered off Just In Case.
The array failed to boot with the missing disk, so I had reluctantly
plugged it back in, intending to rebuild the array before the Tiger
upgrade. Mistake #1 - I forgot to do so.
In any case, to its credit, the Tiger Server installer happily upgraded
the OS on the degraded array and left it in the same state.
So, I thought, I know I can't repair that array volume because it is the
startup disk. I'll have to reboot with the Tiger Server DVD and rebuild
the array then.
Once booted with the Tiger DVD, I found Disk Utility to be a little
whacked. (I later learned that there is a difference between Panther
RAIDsets and Tiger RAIDsets but at the time I was ignorant). It was
unable to rebuild the array or do anything with the existing
configuration - except show little padlock icons next to each disk. I
now attribute ths to differences between Tiger and Panther RAID.
So, I thought, this can't be right. And off I trundled into the Terminal
app to hunt down the problem with Disk Utility.
I determined my only option was to attempt to rebuild the RAIDset using
diskutil repairMirror <mirrorname> <offlinediskname>.
I kicked this off - no dice.
Figured it didn't 'take' - so kicked it off again.
Nothing. No activity whatsoever. Mistakes #2 and #3 had just happened.
Figured it might be like some old Promise RAID implementations I've used
in the past and that rebuild might start only on reboot.
Rebooted the system (that had never previously failed to boot).
It failed to boot - with a big "no" symbol where the Apple normally is.
(That's 'no' as in 'no smoking' but without the cigarette)
So, I thought, time to boot the server install DVD again.
Once more, the graphical Disk Utility was useless. Back to terminal.
Sure enough, a quick diskutil showRAID revealed that there was one
"online" disk, one "offline" disk and two unknown disks - a total of
four drives - now involved in my 2-physical-disk mirror RAID set.
No amount of checking, removing, or otherwise could do anything to get
rid of the "unknown" disks from the RAIDset - I now suspect these were
created by trying to rebuild a 10.