Disk Utility - delete RAID killed data on drives before server install

OK. Here's the scenario.
I had a Dual 1G G4 with a fully functioning RAID 1 installed. So I attempted to do an install of Leopard Server. It came up with a message that said something like "OS X could not prepare disk for installation." After reading some forum posts, one guy said that he was able to install Leopard by deleting the RAID, thus splitting the RAID into two volumes. So I booted from the DVD again, and this time it reports that the RAID is degraded, and that the second drive in the RAID set is a "spare."
This seemed odd, but I figured if I delete the RAID set it would keep the section that had all the good data on it. That's when my world went to ****.
Once it deleted the RAID set, and the message came up prompting me that I would NOT lose my data, it went ahead and deleted all my data. Perhaps replacing the good volume with the so-called spare. So I have been trying in vain to get the data back. The one product that I own, DiskWarrior, does not see the drives as volumes. So it won't work. Anyone have any ideas?
There was not a LOT of data on the drive, but there was a lot of complicated web shares and a few IMPORTANT websites that I need to get back. And, yes, I do not have a current backup of the volume. I was riding the RAID 1 cushion way too hard.

It would seem that I have the answer, and I believe that this is a MAJOR problem that Apple should address with some kind of warning to its customers. The RAID set I deleted was an Apple RAID 1.0 set. Upon reading further into the documentation, I see that RAID 2.0 sets can be deleted, and the volumes split into two. But with RAID 1.0 sets, the data is lost when you delete a volume.
So, even though I was deleting the set in 10.5, it seems to have applied the rules for RAID 1.0.
http://docs.info.apple.com/article.html?path=RaidUtility/1.0/en/s1ru11.html
I am hoping that there is a way to recover my data, but i'm not too hopeful.

Similar Messages

Hi, I have a hard disk failure so to recover my data I am using disk utility to restore the data on an external drive while booting from a second external hard drive. When I perform the operation it gives me an input/output error and stops. Any tips?

Hi, I have a hard disk failure so to recover my data I am using disk utility to restore the data on an external drive while booting from a second external hard drive. When I perform the operation and after having selected both my destination and source drives, the operation begins but soon fails due to input/output error. If I try to create an image of the drive it gives me the same error message. Any help would be much appreciated.

Disk Utility only creates a image of the drive, so it's no help getting exactly what you want, which is your files. If the file structure is messed up or the drive is failing then it's no help.
If you have a external boot drive and you can't access the internal non-booting drive though the typical Finder and windows to transfer your files via drag and drop methods, then you need to install Data Rescue on the external boot drive and it will do as best as it can to recover your files. (works on non-encrypted/non-Filevaulted drives only)
.Create a data recovery/undelete external boot drive
Are you sure you have hard drive failure, or that OS X isn't merely not booting?
Because if the drive is working physically, then there is a host of fixes
..Step by Step to fix your Mac
https://discussions.apple.com/community/notebooks/macbook_pro?view=documents#/

Disk Utility : Partition / Raid or Raid / Partition ?

I have two external USB drives that I'm attempting to set up using Disk Utility.
I'd like to create either
- one RAID1 set with two partitions, or
- two RAID1 sets with one partition
however I'm not having much luck with either option. Is either scenario possible?

After some experimentation, I seem to have come up with a kludge ...
Partition both disks into identical volumes (A1 = B1, A2 = B2)
Using Disk Utility :
- create RAID Set 1 ( A1 + B1 = RAID1)
- create RAID Set 1 ( A2 + B2 = RAID2)
Error message 'Creating RAID set failed'
Restart ...
Using Disk Utility :
- click on partition A2 (now renamed RAID Slice)
- Erase partition
Upon erasing the partition / RAID slice will remount and the Disk Utility should show two RAID sets. A cursory examination of each RAID set's behavior leads me to believe it is simply a bug in Disk Utility that prevents the creation of two RAID sets on the same disk pair.

Disk Utility won't initialize second Maxtor drive

My first hardware upgrade has not gone too well. I just got a Maxtor 6L250S0 drive to fill empty second bay of my dual 1.8 PowerMac G5. (Drive specs: 250 GB SATA Ultra 16, DiamondMax, 16 MB cache, 7200 RPM) Installation was a breeze, but I can't get my Mac to erase, format, partition or otherwise initialize the drive for use. When I rebooted, I got the message about needing to initialize the new hardware. I clicked "Initialize", and Disk Utility came up. Disk Utility lists "Maxtor SABRE" as a drive on the left and lists the following details at the bottom:
Disk Description : Maxtor SABRE
Total Capacity : 0 Bytes
Connection Bus : Serial ATA
Write Status : Read/Write
Connection Type : Internal
S.M.A.R.T. Status : Not Supported
Connection ID : Device 0, "B (lower)"
The Capacity and SMART status lines are a bit troubling. Is that normal when a drive is first installed?
I go to the ERASE tab and can only select "Mac OS Standard" or "UNIX File System" for the volume format. I select the Mac OS Standard and press the Erase button, but I get a message "Disk erase failed with the following error: The chosen size is not valid for the chosen file system."
I go to the PARTITION tab and can't do anything there either. When it lets me edit the form and press the Partition button, it gives an error saying "Device not configured." Usually as soon as I do anything on this form (e.g., select the Format dropdown), all the choices are grayed out with the notice "the disk is too small to contain partitions".
Based upon research here and elsewhere, I know this is a compatible drive. Am I missing a step? Could the drive be bad?
PowerMac G5 dual 1.8 Mac OS X (10.4.5) 2.5 GB RAM

My first hardware upgrade has not gone too well. I
just got a Maxtor 6L250S0 drive to fill empty second
bay of my dual 1.8 PowerMac G5. (Drive specs: 250
GB SATA Ultra 16, DiamondMax, 16 MB cache, 7200 RPM)
Installation was a breeze, but I can't get my Mac
to erase, format, partition or otherwise initialize
the drive for use. When I rebooted, I got the
message about needing to initialize the new
hardware. I clicked "Initialize", and Disk Utility
came up. Disk Utility lists "Maxtor SABRE"
Hi,
I have never seen a Maxtor come up as "Maxtor SABRE" in disk utility. Your post says the Maxtor 250GB hard drive is mounted internally. If so, I would guess that the drive is damaged. I would take it back for a working drive.
Or you could call Maxtor at (800) 262-9867. I have had two Maxtor drives fail in the last 5 months and the techs at Maxtor sent me replacements and then I returned the damage drives in their shipping boxes.
The Maxtor tech guys are very helpful and give Mac users the benefit of the doubt when it comes to warranty returns. At least that was my experience.
The drive should display Maxtor 6L250S0 in the disk utility window and Smart Drive status should be active.
I hope this helps,
Michael

Disk utility can't find iMac hard drive

I had to power off my iMac by Pressing the power key and holding it several times over the last few weeks. The last time it wouldn't reboot - I'd just get an apple icon. When I tried a safe boot I'd get the icon and it would change to a no entry sign.
Next I started up from the snow leopard installation disk with the intent of repairing the iMac disk. The installation disk worked but when I opened disk utility it only found the installation disk. It didn't find the iMac disk.
Do I need to make a trip to the Apple store or is there something else to try?

Version:1.0 StartHTML:0000000105 EndHTML:0000004136 StartFragment:0000001438 EndFragment:0000004100
Oh Gosh, I am having this same problem too. I normally do not shut down ever, I reboot often because I have to due to bad wireless reception. Last month, I did a full shut down and unplug due to a terrible storm coming in. When I went to boot up, it took very long and I had booted from my external bootable drive. My saving grace is that since crashing my emac in 2006, I am a rabid "backerupper" (made up my own word). I have been using lacie’s Silverkeeper to make bootable back ups just in case. So When I tried disk utility, it did not see my drive. I used my third party software "Disk Warrior" by Alsoft, it saw my drive, and then I unplugged my external and then booted again from the Snow Leopard DVD and was able to repair. All was well until this weekend. We had a storm come trough quickly and we lost power, now I have the same problem you do but this time Disk Warrior does not see the disk either. I am going to dig around for a while before I hit the Genius bar. I fear the drive is fried. And for me I am not certain this will be worth the dollar amount to replace since this is a 2006 and not upgradeable, but I will check with an outside vendor for price for the drive so I know what I want to do if in fact the Genius bar cannot see the drive either. I do hope you have a back up version, and would suggest having third party software to take a chance to see if you can find your disk. My imac is an Intel duo core 2 GHZ and from what I can tell model number A1174. To get help from the smart people here it would be useful for you to post the rest of your specs. If you don't know the exact model, you can check everymac.com and plug in your serial number. Under the computer stand you will find the serial number and the emc number and you can find out from everymac.com what exact model you have. If I find anything I will come back to this thread and report in. Good luck to you.

Disk Utility not finding new internal hard drive

Hi All
My internal hard drive died recently and I replaced with a western digital drive from newegg..
All the cables are hooked up correctly, including the orange cable attached to the hard drive. Problem is that when I go to install OS X, Disk Utility doesn't even list the drive. Is there something I need to do beforehand? Anyone have any ideas as to why Disk Utility isn't even seeing the drive? Jumpers maybe?
Thanks in advance.
-Aaron

I doubt that any jumpers are needed, since this is the only (master) drive in the system. WD's site has pretty good info on this. Verify for yourself however.
Also, from their site:
How to partition and format an internal slave drive or an external drive in a Mac OS X (all versions).
Answer
In Mac OS X, you can use the built in Disk Utility to partition and initialize the drive so it will appear on the desktop.
1. Open the main drive (the drive that contains the operating system).
2. Open the Applications folder.
3. Open the Utilities folder.
4. Select Disk Utility.
5. The drives are displayed on the left side of the window. Click on the drive that you wish to partition (the top drive listing for the hard drive that you want to work with).
6. Once the drive is selected click on Partition.
7. Click on the Options button to select the partitioning scheme.
8. Click on Apple Partitioning Scheme or Apple Partitioning Map and then click on the OK button.
9. You will see several options for setting up the drive. Once you have selected the number of partitions, the format type you want, and a volume label, click the Partition button.
10. Following the completion of this process, the drive will appear on the desktop.
Joe

HT4848 how to erase the disk utility from my usb portbalbe flash drive

how do I erase the disk utility from my usb portbalbe flash drive. I need the flash drive for other stuff and it isn't allowing me to do so.

Here is information on the recovery partition, includin how to remove it from a drive: http://reviews.cnet.com/8301-13727_7-20083166-263/managing-the-os-x-10.7-lion-re store-drive/

Can I use Disk Utility to erase Apple TV hard drive?

Can I use Disk Utility to erase Apple TV hard drive?

I don't know, but I doubt it can be done using Disk Utility. I suggest you consult the user manual for it or see if there is a Reset option in the onscreen menues. If you don't have a manual, then you will find one at http://support.apple.com/manuals.

I am getting error message "Disk Not Ejected Properly Eject "FreeAgent GoFlex Drive" before disconnecting or turning it-" randomly.

I'm getting a "Disk Not Ejected Properly Eject “FreeAgent GoFlex Drive” before disconnecting or turning it…" message at random times. I have seen other comments about this happening after the iMac wakes from sleep. However, this is happening to me throughout the day even when I am working on the iMac.
The iMac is up to date with OS X Version 10.9. I had recently switched from a 500GB to a 3TB Drive, both are Seagate. I have never had this issue prior to the switch.
Has anyone else experienced this issue?
I verified/repaired in the Utility Disk and a message popped up indicating the GoFlex looks "OK".

No, I am not on the USB3 interface. I contacted Seagate and they indicated that there is no known issue with OS X 10.9. In my case, they are willing to send me a new Drive, since I just received the GoFlex on 12/06. Will post an update when I install the new one. Hopefully this will solve my issue.
I suggest you contact Seagate, if you haven't already, directly. The representatives are very helpful. Good luck.

I am trying to find out how to copy the image on my existing hard drive to my new hard drive before I install it so it will be like I didn't do anything.

I am trying to find out how to copy the image on my existing hard drive to my new hard drive before I install it so it will be like I didn't do anything. Thanks for the info. on changing it.

Format is found in the Erase Tab:
The Disk Image is found on the Restore Tab:

Disk utility says "RAID STATUS: Disk missing"?

When I boot up OS 10.3.9 there is error message "detected volume OS X cannot read - initialize, ignore or eject" - then it dissappears and the system drive behaves normally. But in disk utitlity it says "RAID STATUS: Disk missing".
The disk is not partitioned and it will not let me repair permissions. Any ideas?

Disk Utility monitors the status of the disks in a RAID set. If you see a message indicating that a disk is missing or has failed, try these troubleshooting steps:
If you are using a striped RAID set, delete the damaged RAID set. Your data may be lost. Be sure to back up your RAID sets and other data regularly.
If you are using a mirrored RAID set, there may have been an error writing data to the disk. Click Rebuild in the RAID pane of Disk Utility.
If a problem persists, replace the damaged disk and click Rebuild to rebuild the RAID set.
Use the First Aid pane to repair the RAID disk, then check the RAID set to see if it still reports an error. If the problem is still present, quit and reopen Disk Utility, select the RAID disk, and click RAID. Check the RAID set to see if it still reports an error. You may need to restart your computer.
iBook G4 Mac OS X (10.3.9)

Failed Disk Utility Software Raid

My external RAID hasn't been mounting as easily as normal so I opened Disk Utility to repair disk or whatnot and it shows one drive as failed. Not sure what this means or how I should proceed. I'd be surprised if that drive is dead. What does the Rebuild button do? I have backed up all the data on the mirror, but am not sure how to proceed. I'd like to keep this info on the RAID if possible.
Dual2 G5 & Powerbook G4 Mac OS X (10.4.4)

From Disk Utility's Help:
A disk in a RAID set has failed or is missing
Disk Utility monitors the status of the disks in a RAID set. If you see a message that a disk is missing or has failed, there are several things you can try to solve the problem.
If a disk is missing, make sure it is connected to power and turned on, and that it's connected to your computer. If you are using a FireWire or USB disk, you may need to disconnect it then connect it again.
Use the First Aid pane to repair the disks in the RAID, then check the RAID set to see if it still reports an error. You may need to unmount the RAID set to repair the disks.
In some cases, you might need to quit and reopen Disk Utility or restart your computer and then check the RAID set.
If you are using a mirrored RAID set, there might be an error while writing data to the disk. Click Rebuild in the RAID pane of Disk Utility.
If you are using a striped RAID set, delete the damaged RAID set. Your data may be lost. Be sure to back up the disks in your RAID set and other data regularly.
If you have a persistent problem with a disk in a mirrored RAID set, you may need to replace it. After you replace the damaged disk, click Rebuild to rebuild the RAID set.[/i[
G4 450 MP Gigabit Mac OS X (10.4.7)

Disk Utility / diskutil RAID Mirror rebuild fails: mistakenly thinks disk is too small

Has anyone else had this issue?
I've just migrated my Lion Server install to a slightly upgraded Mac Mini running Mavericks and am running into horrible trouble rebuilding my Apple RAID disk, which I established on Lion and would like to repair using Mavericks. The drives being used are the same units; the RAID got out of sync due to a power outage, and rather than wait to migrate until the old machine was done rebuilding the array like a week later, I just figured I could repair the RAID after migration.
Not so, however. Disk Utility, when I attempt to rebuild the raid using the second drive, tells me that it is too small.
When I look in diskutil, here's what it shows me:
<blockquote>
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *3.0 TB     disk2
   1:                        EFI EFI                     314.6 MB   disk2s1
   2:         Apple_RAID_Offline                         3.0 TB     disk2s2
   3:                 Apple_Boot Boot OS X               134.2 MB   disk2s3
/dev/disk3
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *3.0 TB     disk3
   1:                        EFI                         209.7 MB   disk3s1
   2:                 Apple_RAID                         3.0 TB     disk3s2
   3:                 Apple_Boot Boot OS X               134.2 MB   disk3s3</blockquote>
Notice that the EFI partition on disk3 -- the intact RAID slice -- is the correct size, 209.7MB or 200MiB. The EFI partition disk2, however, which was created moments earlier by Disk Utility in its failed attempt to rebuild the array, is 100MiB too many. As a result, the Apple_RAID partition is about 100MiB smaller than the one on disk2. Hence, this error.
So my question is: what the **** is going on here, and what can I do about it? Is this just a Mavericks bug, that it creates EFI partitions of the wrong size? The disks are seen as identical in diskutil. Is there anything I can do to rebuild my array?
I've considered rebuilding it on the old server, but then next time it gets messed up I'm just going to run into the same problem, as whichever slice fails will have a correctly-sized EFI partiton, and if Disk Utility insists on creating an incorrectly-sized one during the rebuild process it's just going to fail again.
Please halp! Thank you!

OK, so here is the solution for my problem
what i did was the following:
- as i wrote before, i erased the disk with command line (diskutil zeroDisk disk1), then the pending sector was gone.
- i decided to rebuild the raid in recovery mode to prevent further system crashes. so i added the previously zeroed disk1 to the degraded raid. when disk utility finished adding the disk it stalled but showed the raid ONLINE. so i decided to hard shutdown my mac mini - because it wasn't possible to restart via the interface of the recovery mode.
after staring the mac the system loaded and everything was working again properly! including disk utility still showing raid1 online.
btw, time machine was working correctly again when i deleted the .inprogress-file on the backup-disk.
maybe someone else is able to use this information - that would be great!

Disk utility can't repair external hard drive

A couple months back, I had to get a whole new hard drive case for my external because the power cord broke. Anyway, It's worked fine until now...
The hard drive doesn't show up with the other volumes.
It does show up on Disk Utility. When I try to repair or verify the drive, it works up until the end, but then it automatically quits and it says this:
Verifying volume “FIREWIRE”
** /dev/disk1s1
** Phase 1 - Read FAT
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
Unable to read directory (Input/output error)
Error: The underlying task reported failure on exit
1 non HFS volume checked
Volume needs repair
Anyway, I have 45GB of music as well as movies and photographs that mean a lot to me so I hope I don't have to erase the drive or anything...
Thanks to anyone who helps me out.

Hmm, I can't seem to find anything on Windows (XP) that will fix my exact problem...
Then again, I am the crappiest Windows user ever so, once again, any help would be great.
I searched "disk repair" on the help and support center, and it gave me a bunch of ways to fix the drive depending on the problem. The thing is, none of the problems seemed to match mine...
Your personal data files are missing or have been corrupted, or you want to revert to a previous version of a file.
After updating a device driver, you can log on, but the system is unstable.
After installing a new device, the system is unstable.
Changes made to your system or application settings are causing your computer to run poorly and you do not know how to restore the previous settings.
After installing an application, the system is unstable or an application is not working properly.
Operating system does not start (the logon screen does not appear)
I'm not really sure what the exact problem is, I just know that it isn't working on the Mac, but it is on the PC.

Disk Utility error when verifying DIY fusion drive

Hi,
It has been a while since I had to post a problem, but I need others advice on this if you can help. When 10.8.3 came out I installed an M4 512gb ssd in my main drive bay of 2008 unibody aluminium macbook and put a 1tb spinner in the optibay. Created a fusion drive, migrated data and all has been great. Decided to run disk utility today to check for any errors as I had a sleep issue with the 10.8.4 update which I ended up solving by changing the sleep settings in terminal - the issue had caused a few forced shutdowns. I have Disk Utitliy Version 13 (450). The Fusion drive is shown as the logical volume group followed by the volume disk. When I run a verify disk on the volume itself it is all ok:
Verifying volume “Cybernet”
Checking storage systemChecking volume.
disk0s2: Scan for Volume Headers
disk1s2: Scan for Volume Headers
disk0s2: Scan for Disk Labels
disk1s2: Scan for Disk Labels
Logical Volume Group 0DAE76E1-A325-4925-902F-1015B270B84C spans 2 devices
disk0s2+disk1s2: Scan for Metadata Volume
Logical Volume Group has a 2170 MB Metadata Volume with double redundancy
Start scanning metadata for a valid checkpoint
Load and verify Segment Headers
Load and verify Checkpoint Payload
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Incorporate 6 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Load and verify Metadata Superblock
Load and verify Logical Volumes B-Trees
Logical Volume Group contains 1 Logical Volume
Load and verify 309877EC-EA53-443C-A75C-63C159B04EF3
Load and verify 5388E543-6974-4251-BDBD-FA850C121897
Load and verify Freespace Summary
Load and verify Block Accounting
Load and verify Live Virtual Addresses
Newest transaction commit checkpoint is valid
Load and verify Segment Cleaning
The volume 0DAE76E1-A325-4925-902F-1015B270B84C appears to be OK.
Checking file systemPerforming live verification.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking volume bitmap.
Checking volume information.
The volume Cybernet appears to be OK.
When I run it on the LVG it comes up as:
Verifying partition map for “M4-CT512M4SSD2 Media”
Checking prerequisites
Checking the partition list
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Checking all HFS data partition loader spaces
Checking Core Storage Physical Volume partitions
Checking storage system
Checking volume.
disk0s2: Scan for Volume Headers
disk1s2: Scan for Volume Headers
disk0s2: Scan for Disk Labels
disk1s2: Scan for Disk Labels
Logical Volume Group 0DAE76E1-A325-4925-902F-1015B270B84C spans 2 devices
disk0s2+disk1s2: Scan for Metadata Volume
Logical Volume Group has a 2170 MB Metadata Volume with double redundancy
Start scanning metadata for a valid checkpoint
Load and verify Segment Headers
Load and verify Checkpoint Payload
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Incorporate 40 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Load and verify Metadata Superblock
Load and verify Logical Volumes B-Trees
Logical Volume Group contains 1 Logical Volume
Load and verify 309877EC-EA53-443C-A75C-63C159B04EF3
Load and verify 5388E543-6974-4251-BDBD-FA850C121897
Load and verify Freespace Summary
Load and verify Block Accounting
Load and verify Live Virtual Addresses
Newest transaction commit checkpoint is valid
Load and verify Segment Cleaning
The volume 0DAE76E1-A325-4925-902F-1015B270B84C appears to be OK.
Incorrect size for volume “Cybernet”
Problems were found with the partition map which might prevent booting
Error: Incorrect size for logical volume.
Verifying partition map for “WDC WD10JPVT-00A1YT0 Media”
Checking prerequisites
Checking the partition list
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Checking all HFS data partition loader spaces
Checking Core Storage Physical Volume partitions
Checking storage system
Checking volume.
disk0s2: Scan for Volume Headers
disk1s2: Scan for Volume Headers
disk0s2: Scan for Disk Labels
disk1s2: Scan for Disk Labels
Logical Volume Group 0DAE76E1-A325-4925-902F-1015B270B84C spans 2 devices
disk0s2+disk1s2: Scan for Metadata Volume
Logical Volume Group has a 2170 MB Metadata Volume with double redundancy
Start scanning metadata for a valid checkpoint
Load and verify Segment Headers
Load and verify Checkpoint Payload
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Incorporate 43 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Load and verify Metadata Superblock
Load and verify Logical Volumes B-Trees
Logical Volume Group contains 1 Logical Volume
Load and verify 309877EC-EA53-443C-A75C-63C159B04EF3
Load and verify 5388E543-6974-4251-BDBD-FA850C121897
Load and verify Freespace Summary
Load and verify Block Accounting
Load and verify Live Virtual Addresses
Newest transaction commit checkpoint is valid
Load and verify Segment Cleaning
The volume 0DAE76E1-A325-4925-902F-1015B270B84C appears to be OK.
Incorrect size for volume “Cybernet”
Problems were found with the partition map which might prevent booting
Error: Incorrect size for logical volume.
I got the same when I did a safe boot and when rebooted from the recovery partition.y question is, do I repair or could it damage my setup? eg is Disk Utility being accurate and it can repair the error, or is it a phantom issue that should be ignored bearing in mind it's a DIY fusion drive and it could end up getting mashed?
Thanks!

Hi,
The computer's running fine since I sorted the sleep issue. No issues as far as I can tell, which is why I was surprised to see the error. What does the error actually mean - is it saying that the volume is a different size than the computer thinks it should be and therefore it'll just change a few values? In which case I suppose a repair is harmless? I just don't want to repair and then reboot to find the volume corrupted.

Disk Utility - delete RAID killed data on drives before server install

Similar Messages

Maybe you are looking for