11-13-2008
Mac OS X: How to rebuild a software RAID mirror
Note: This article applies to Mac OS X 10.2 or later and Mac OS X Server 10.2 and later. Occasionally, Disk Utility may report that a software mirror has become degraded and that it must be rebuilt. In such a situation, one drive has become out of sync with another. To rebuild the software mirror, follow these steps below. Warning: Before proceeding, you must back up of all data, because failure to follow the steps correctly may result in data loss.
More from Apple OS X Support ...
7 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Hi there,
I'm not sure if this is possible, but here is what I'd like to do..
I have an existing 160GB drive in my Redhat 9.0 server that I would like to add an additional 160GB drive to and create a mirrored RAID of the first disk to the new disk. I would like to do this without having to... (2 Replies)
Discussion started by: sysera
2 Replies
2. Solaris
Hi ,
I am new to SVM .when i try to learn RAID 1 , first they are creating two RAID 0 strips through
metainit d51 1 1 c0t0d0s2
metainit d52 1 1 c1t0d0s2
In the next step
metainit d50 -m d51
d50: Mirror is setup
next step is
metaattach d50 d52
d50 : submirror d52 is... (7 Replies)
Discussion started by: vr_mari
7 Replies
3. UNIX for Dummies Questions & Answers
Hi
Can someone tell me what are the differences between software and hardware raid ?
thx for help. (2 Replies)
Discussion started by: presul
2 Replies
4. Ubuntu
Hi,
I have an Ubuntu system which I have an faulted mirror.
I trying to replace the disk, but I'm stuck on that it boots and only showing GRUB
GRUB
## ## End Default Options ##
title Ubuntu 8.04.4 LTS, kernel 2.6.24-26-server
root (hd0,0)
kernel ... (0 Replies)
Discussion started by: jld
0 Replies
5. Solaris
Server Model: T5120 with 146G x4 disks.
OS: Solaris 10 - installed on c1t0d0.
Plan to use software raid (veritas volume mgr) on c1t2d0 disk.
After format and label the disk, still not able to detect using vxdiskadm.
Question:
Should I remove the hardware raid on c1t2d0 first?
My... (4 Replies)
Discussion started by: KhawHL
4 Replies
6. SCO
SCO UNIX 5.0.7, IBM x-series 235 w/ LSI controller. I can't for the life of me find any documentation for an OS level application, or an entry in scoadmin to rebuild the array or even find logs within the OS.
Is my only option to rebuild the array from the BIOS tool before boot up? (2 Replies)
Discussion started by: psytropic
2 Replies
7. Linux
Hello,
I am trying to convert a single-drive Centos 7.2 installation with LVM into a two-disk mdadm mirror with mrrored LVM. I was able to follow the excellent instructions at:
http://www.dgoradia.com/creating-a-raid1-mirrored-on-an-existing-centos-on-lvm/and did create a two-disk mirror... (1 Reply)
Discussion started by: Clovis_Sangrail
1 Replies
LEARN ABOUT OSX
reportcrash
ReportCrash(8) BSD System Manager's Manual ReportCrash(8)
NAME
ReportCrash -- Generates crash reports
SYNOPSIS
ReportCrash
DESCRIPTION
ReportCrash analyzes crashing processes and saves a crash report to disk. A crash report contains information that can help a developer
diagnose the cause of a crash. ReportCrash also records the identity of the crashing process and the location of the saved crash report in
the system.log and the ASL log database.
ReportCrash is invoked automatically by launchd when a crash is detected. For applications and other processes running in the per-user
launchd context, ReportCrash runs as a LaunchAgent and saves crash reports in the user's ~/Library/Logs/DiagnosticReports/ directory. For
daemons, other processes running in the system launchd context and other privileged processes, ReportCrash runs as a LaunchDaemon and saves
crash reports in the system's /Library/Logs/DiagnosticReports directory where they are only readable by admin users. If there are too many
crash reports saved for a particular process, older reports will automatically be removed in order to conserve disk space.
launchtl can be used to disable and re-enable crash reporting. To disable crash reporting:
launchctl unload -w /System/Library/LaunchAgents/com.apple.ReportCrash.plist
sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.ReportCrash.Root.plist
To re-enable crash reporting:
launchctl load -w /System/Library/LaunchAgents/com.apple.ReportCrash.plist
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.ReportCrash.Root.plist
For application crashes (but not background process crashes) ReportCrash will display a dialog notifying the user that the application unex-
pectedly quit and offering to reopen the application or send the report to Apple. For developers, the behavior of this dialog can be
adjusted using /Developer/Applications/Utilities/CrashReporterPrefs.app which is installed as part of the developer tools.
Crash reports which are sent to Apple are submitted anonymously by the SubmitDiagInfo process. The reports are used by Apple to improve its
products. Users who need support should use http://www.apple.com/support or other authorized support channels. Developers who are ADC mem-
bers should report bugs using http://bugreporter.apple.com in order to allow for two way communication between Apple and the bug reporter.
More information about interpreting the contents of crash reports can be found in Technote 2123: http://developer.apple.com/tech-
notes/tn2004/tn2123.html
SEE ALSO
launchd(8), launchd.plist(8), launchctl(8), spindump(8), SubmitDiagInfo(8)
Mac OS June 1, 2019 Mac OS