At 11:59 AM -0400 6/25/07, Christopher Waltham wrote:
...has anyone seen this kind of behavior before?
I have a G5 Xserve running 10.4.8 Server, with a pair of 80GB drives
in a RAID1 array. One of the disks became degraded this morning, but
diskutil didn't fix it automatically. This seems to be because the
array was created in 10.3.9 Server (i.e. Panther), and thus was made
with AppleRAID version 1.
Yes.
So, I booted off a 10.4 install DVD and ran "diskutil convertRAID"
to convert the array to AppleRAID 2 so that I could repair it. The
logs from diskutil say that everything went flawlessly and it only
took a couple of minutes to complete. However, upon rebooting the
Xserve after that, the RAID array exists but the volume it contains
has seemingly disappeared.
You performed this operation against a "bad" array? That would not
sound like a very wise idea.
What do you mean by the RAID array exists but the volume doesn't.
Either it has an entry in the device table or it doesn't.
If you are referring to the volume mounting, rather than existing,
then refer your commentary above where you tell us it was "bad".
I'm back to booting off the install DVD, because OS X can no longer
find it's boot partition.
Well probably can't mount it, from your comments above, so it
wouldn't be able to boot from a disk that's bad and can't be mounted.
Disk Utility, when launched from the DVD, says that the array is
Online but both disks that used to house the array are Offline.
Strangely, it reports the name of the volume as being "Macintosh HD"
instead of "pinkham", which was the name of the volume before I ran
diskutil on it.
Sounds like the volume has been modified.
When I run the "Verify Disk" command in Disk Utility on the RAID
volume, I get this error:
"Invalid volume header
Invalid b-tree node size"
Again, you took a bad volume and made it worse.
Short of buying a copy of DiskWarrior, does anyone have a fix for this?
It was very simple from the beginning. Reformat your RAID to a new
Apple RAID v2 partition and restore the RAID from your last known
good backup.
DIskWarrior, FWIW, is highly invasive and generally not recommended
[MNSHO] as it will "repair" the volume creating "lost" files that are
probably corrupted. If this is your boot disk this can result in
unbootable volumes since files can be screwy. If you do use it
realize that the volume that's been repaired is highly suspect.
Or has anyone even seen this happen before?
Which, someone trying to manipulate and convert bad arrays or volumes
with bad headers and/or invalid b-trees?
fsck will repair the latter two, your CIO can fix the former ;)
--
-dhan
------------------------------------------------------------------------
Dan Shoop AIM: iWiring
Systems & Networks Architect http://www.ustsvs.com/
email@hidden http://www.iwiring.net/
1-714-363-1174
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden
