>>That puzzled me, as it is dead easy to build a version identifier or
>>something similar into something like a RAID header, so I checked it up -
>>and sure enough Apple *does* build a version number into the header, which
>>changed from AppleRAID 1 (pre-Tiger) to 2 (Tiger). So it would appear to be
>>merely a matter of checking the version number - hardly onerous?
>
>And since a corrupted disk may have headers which are unreadable...
If so, it would have been an independent issue.
All the Apple RAID volumes we have rescued for (new to us) customers had
simple partition map damage, with no damage inside the volume. This meant
that standard tools like Disk Warrior were useless, but the data or
volume structure was fine. The disks just needed a new partition map.
Sometimes we do it as a favor, other times we charge a modest fee. But
the fact we have recovered volumes multiple times means this is not an
isolated incident, unfortunately.
SoftRAID has gone through 3 partition map transitions, and we have not
had any problems with the transition from the older partition map to the
newer format. There was a lot of planning to do to make it work properly,
but we did it, and each was bulletproof.
BTW: (ad alert) We released 3.6.2 today, which is a great intel milestone
for us, as we now have 98% of intel booting issues solved. Intel (GPT
format) drives now behave the same way as PPC drives do, as far as
booting and converting existing disks to Mirrors. There are still
occasional boot-cache issues, but we got most of them out of the way with
this release.
Mark James
mjames@ softraid.com
"It would be wrong to say an operating system is more secure because
nobody is attacking it." Bill Gates, doublespeak 2004
_______________________________________________
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
This email sent to email@hidden
