I pulled one of my mirrored-RAID hard disks out of my xserve before
applying 10.5.3.
After I found that 10.5.3 worked fine after the update (but, boy did
that upgrade take a while -- it was 10+ minutes of reboots and grey
screens), I put the other hard disk back in to rebuild the mirror.
In doing so, I found that "Disk Utility" -- the app -- still didn't
work. system.log showed this (just like under 10.5.2):
May 30 21:49:49 devo Disk Utility[719]: Rebuilding RAID
May 30 21:49:49 devo Disk Utility[719]: Filesystem: Mac OS Extended
(Journaled)
May 30 21:49:49 devo Disk Utility[719]: RAID type: Mirrored RAID Set
May 30 21:49:49 devo Disk Utility[719]: RAID set name: "Server HD"
May 30 21:49:49 devo Disk Utility[719]: RAID set status before rebuild: ""
May 30 21:49:49 devo Disk Utility[719]: RAID chunk size: 32K (default)
May 30 21:49:49 devo Disk Utility[719]: Mirror Auto Rebuild:
Disabled (default)
May 30 21:49:49 devo Disk Utility[719]: 2 members
May 30 21:49:49 devo Disk Utility[719]: RAID Slice (disk2s2) - Online
May 30 21:49:49 devo Disk Utility[719]: ST3750640NS P Media
(disk4) - New
May 30 21:49:50 devo Disk Utility[719]: Unable to find the member
disks for this RAID set.
May 30 21:49:50 devo Disk Utility[719]: Error rebuilding RAID:
Unrecognized Filesystem.
May 30 21:49:50 devo Disk Utility[719]: RAID failed: Unrecognized Filesystem.
May 30 21:49:50 devo Disk Utility[719]:
So, pulled the drive out and "diskutil listraid" showed this:
Name: Server HD
Unique ID: BB3AC631-7029-4AA6-8FCD-A922AFC7B024
Type: Mirror
Status: Degraded
Size: 749812383744 B
Device Node: disk3
Apple RAID Version: 2
-------------------------------------------------------------------------------
# Device Node UUID Status
-------------------------------------------------------------------------------
0 disk2s2 D98E4413-2F0C-4A54-A65B-D63DB1B728B3 Online
0 -none- 1BD7BABF-5D04-46C2-9C88-0E5F670A0D1B Missing/Damaged
I put the disk back in and got this:
Name: Server HD
Unique ID: BB3AC631-7029-4AA6-8FCD-A922AFC7B024
Type: Mirror
Status: Degraded
Size: 749812383744 B
Device Node: disk3
Apple RAID Version: 2
-------------------------------------------------------------------------------
# Device Node UUID Status
-------------------------------------------------------------------------------
0 disk2s2 D98E4413-2F0C-4A54-A65B-D63DB1B728B3 Online
1 disk4s2 1BD7BABF-5D04-46C2-9C88-0E5F670A0D1B Failed
Which I was expecting at this point.
So, I thought I could do what I did what I had to do after rebuilding
the mirror when I did my 10.4.11--> 10.5.2 update:
h-3.2# diskutil repairmirror disk3 disk4
Note: Syncing data between mirror partitions can take a very long time.
Note: The mirror should now be repairing itself. You can check its
status using 'diskutil listRAID'.
sh-3.2#
But, when I do this (and I've tried a couple of times now), all that
system.log says about this is:
May 30 21:50:54 devo kernel[0]: AppleRAID::restartSet - restarting
set "Server HD" (BB3AC631-7029-4AA6-8FCD-A922AFC7B024).
May 30 21:50:55 devo kernel[0]: AppleRAID::completeRAIDRequest -
write error 3758097101 detected during rebuild for set "Server HD"
(BB3AC631-7029-4AA6-8FCD-A922AFC7B024) on target member
A1179088-DB66-40CC-BC7D-631430D2E507, set byte offset = 588854349824.
May 30 21:50:55 devo kernel[0]: AppleRAIDMirrorSet::rebuild: copy
failed for set "Server HD" (BB3AC631-7029-4AA6-8FCD-A922AFC7B024).
and the rebuild never actually starts. It's still "degraded" and
disk4 is "failed"
"diskutil list" shows:
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *698.6 Gi disk2
1: EFI 200.0 Mi disk2s1
2: Apple_RAID 698.3 Gi disk2s2
3: Apple_Boot Boot OSX 128.0 Mi disk2s3
/dev/disk3
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS Server HD *698.3 Gi disk3
/dev/disk4
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *698.6 Gi disk4
1: EFI 200.0 Mi disk4s1
2: Apple_RAID 698.3 Gi disk4s2
3: Apple_Boot Boot OSX 128.0 Mi disk4s3
devo:~ admin$ diskutil listraid
Is my only real recourse what I did last time -- I pulled "disk4" out
-- reformatted it as an NTFS volume on a Windows box -- and *then*
try "diskutil repairmirror" again?
I'm open for alternate command-line suggestions if anybody has any...
This *should* work this way, shouldn't it? Pop one drive out and
"repairmirror" when I put it back in? Nothing about actually
running the "Disk Utility" application should have messed this up,
should it?
- Steve
_______________________________________________
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
