Repairing bootcamp core storage issue

I am having an issue with my iMac. It is a late 2013 model with a 3 TB fusion drive. While trying to remove and start over on a windows bootcamp partition, there was a crash on the windows side and now I can not remove the partitions or run bootcamp.
I have tried running all the terminal commands in all the different threads I could find.

This looks like it might be heading in the right direction. It now says it is a bootcamp partition. Bootcamp instead of crashing now says it is a partition that was made in another tool and can not work with it. Still the same errors when I try to run the list of commands you gave.
Last login: Tue Oct 28 20:52:12 on console
Jamess-iMac:~ jamesrobertson$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *3.0 TB     disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:          Apple_CoreStorage                         1.7 TB     disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
   4:          Apple_CoreStorage                         517.9 GB   disk0s4
   5:                 Apple_Boot Boot OS X               134.2 MB   disk0s5
   6:          Apple_CoreStorage                         801.4 GB   disk0s6
   7:                 Apple_Boot Boot OS X               134.2 MB   disk0s7
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS BOOTCAMP               *517.5 GB   disk1
                                 Logical Volume on disk0s4
                                 D5472200-7459-4A63-9C1A-31782B061B8A
                                 Unencrypted
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS Macintosh HD           *2.5 TB     disk2
                                 Logical Volume on disk0s2, disk0s6
                                 8889BBFD-9D4D-4863-AA26-581BCE19A6BC
                                 Unencrypted
/dev/disk3
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *3.0 TB     disk3
   1:                        EFI EFI                     314.6 MB   disk3s1
   2:                  Apple_HFS My Book                 3.0 TB     disk3s2
/dev/disk4
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *15.9 GB    disk4
   1:                 DOS_FAT_32 WININSTALL              15.9 GB    disk4s1
Jamess-iMac:~ jamesrobertson$ diskutil cs list
CoreStorage logical volume groups (2 found)
|
+-- Logical Volume Group 76834525-0EEA-4DCB-82E2-37B79D6FDCF2
|   =========================================================
|   Name:         04
|   Status:       Online
|   Size:         517865467904 B (517.9 GB)
|   Free Space:   3137536 B (3.1 MB)
|   |
|   +-< Physical Volume 9BF97AD2-1540-4424-94EA-92F99DCCBEF9
|   |   ----------------------------------------------------
|   |   Index:    0
|   |   Disk:     disk0s4
|   |   Status:   Online
|   |   Size:     517865467904 B (517.9 GB)
|   |
|   +-> Logical Volume Family 48C77F7E-9923-421F-A154-229AC852BF1F
|       ----------------------------------------------------------
|       Encryption Status:       Unlocked
|       Encryption Type:         None
|       Conversion Status:       NoConversion
|       Conversion Direction:    -none-
|       Has Encrypted Extents:   No
|       Fully Secure:            No
|       Passphrase Required:     No
|       |
|       +-> Logical Volume D5472200-7459-4A63-9C1A-31782B061B8A
|           ---------------------------------------------------
|           Disk:                  disk1
|           Status:                Online
|           Size (Total):          517510004736 B (517.5 GB)
|           Conversion Progress:   -none-
|           Revertible:            No
|           LV Name:               BOOTCAMP
|           Volume Name:           BOOTCAMP
|           Content Hint:          Apple_HFS
|
+-- Logical Volume Group F7493DDD-725F-4A2A-A5BD-782C14AAAC76
    =========================================================
    Name:         Macintosh HD
    Status:       Online
    Size:         2481599021056 B (2.5 TB)
    Free Space:   0 B (0 B)
    |
    +-< Physical Volume CD029AC3-A4CA-4E27-B8B9-E80A3E4D40B3
    |   ----------------------------------------------------
    |   Index:    0
    |   Disk:     disk0s2
    |   Status:   Online
    |   Size:     1680162480128 B (1.7 TB)
    |
    +-< Physical Volume 2D2B9426-8862-4597-A54F-12981D2095D2
    |   ----------------------------------------------------
    |   Index:    1
    |   Disk:     disk0s6
    |   Status:   Online
    |   Size:     801436540928 B (801.4 GB)
    |
    +-> Logical Volume Family 65027EE9-CB03-41CF-A2B7-FF2E7E9ED7A0
        Encryption Status:       Unlocked
        Encryption Type:         None
        Conversion Status:       NoConversion
        Conversion Direction:    -none-
        Has Encrypted Extents:   No
        Fully Secure:            No
        Passphrase Required:     No
        |
        +-> Logical Volume 8889BBFD-9D4D-4863-AA26-581BCE19A6BC
            Disk:                  disk2
            Status:                Online
            Size (Total):          2480978251776 B (2.5 TB)
            Conversion Progress:   -none-
            Revertible:            No
            LV Name:               Macintosh HD
            Volume Name:           Macintosh HD
            Content Hint:          Apple_HFS
Jamess-iMac:~ jamesrobertson$ sudo gpt -vv -r show /dev/disk0
Password:
gpt show: /dev/disk0: mediasize=3000592982016; sectorsize=512; blocks=5860533168
gpt show: /dev/disk0: Suspicious MBR at sector 0
gpt show: /dev/disk0: Malformed MBR at sector 0
gpt show: /dev/disk0: Pri GPT at sector 1
gpt show: /dev/disk0: Sec GPT at sector 5860533167
       start        size index contents
           0           1         MBR
           1           1         Pri GPT header
           2          32         Pri GPT table
          34           6
          40      409600      1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
      409640 3281567344      2 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC
3281976984     1269536      3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
3283246520         584
3283247104 1011455992      4 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC
4294703096      262144      5 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
4294965240 1565305744      6 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC
5860270984      262144      7 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
5860533128           7
5860533135          32         Sec GPT table
5860533167           1         Sec GPT header
Jamess-iMac:~ jamesrobertson$ sudo gpt -vv -r show /dev/disk1
gpt show: unable to open device '/dev/disk1': Resource busy
Jamess-iMac:~ jamesrobertson$ sudo fdisk /dev/disk0
Disk: /dev/disk0 geometry: 97451/255/63 [1565565872 sectors]
Signature: 0xAA55
         Starting       Ending
#: id cyl hd sec - cyl hd sec [     start -       size]
1: EE 1023 254 63 - 1023 254 63 [         1 - 4294967294] <Unknown ID>
2: 00    0   0   0 -    0   0   0 [         0 -          0] unused
3: 00    0   0   0 -    0   0   0 [         0 -          0] unused
*4: 07    0   0   0 -    0   0   0 [         0 -          0] HPFS/QNX/AUX
Jamess-iMac:~ jamesrobertson$ sudo fdisk /dev/disk1
fdisk: /dev/disk1: Resource busy
Thanks
Jimmy

Similar Messages

Unable to delete the core storage logical volume

So I get the grey loading bar on the apple logo screen on bootup that get's to the end and then my iMac turns off. This happens everytime. I went into disk utility (CMD-R) and tried to format the partition and get the error message: Unable to delete the core storage logical volume - I should also mention that the OS X partition is greyed out and is marked as having 0GB free (which is false) and I can't select that partition to do a fresh install of OS X on.
I should mention that on my HDD I have a OS X partition and a bootcamp partitiion and this is the second time I have this issue. How can I fix my OS X partition without having reinstall bootcamp as I have 1TB of stuff on it.
Any ideas?

I have taken some screenshots of the error I get and the state of my HDD in Disk Utility. I did have a weird thing happen after trying to repair using single user mode, where I reopened disk utility and the partitions were NOT greyed out and displayed the correct info concerning space available etc, although after verifying it then reverted back to greyed out with no info.

Volume encrypt and erase failed; unable to delete core storage logical volume

I was attempting to slowly migrate [MI-***] from early 2013 MBPRO to New iMac 5K w/Ceiling Level components.
Kept going through LONG process and then told me it couldn't create [MBPRO HD Home Username] "Jim" on volume or whatever. NO FileVault enabling/ still skittish from White iMac Encrypting Nightmare days... I don't even know -- I guess it's encrypted on Airport, but not on MBPRO.
Moved over Applications from outside User account fine; anything inside any User account NOT FINE.
Hooked up Thunderbolt cable between two macs and restarted MBPRO in T mode... displaying the lightning BOLT on screen that moves around to reduce Burn-in.
Was able to go onto desktop and use windows to drag n drop 190G of movies over to iMac... wondering how I was going to get all right settings over form FCP...
Bottom Line: I only have 16G left on MBPRO and need to MOVE video editing to be exclusive on 3T Fusion on Maxed out iMac 5K.
> Have concluded through whole process that I just want to clone the MBPRO and then delete most of the Larger Videos from MBPRO to recover some of my 760G SSD back.
So, I grabbed my 2T Airport Extreme and Hooked up the Cat5 LAN port to Cat5 input on back of NEW iMac; Now my MBPRO doesn't have to be locked up for days, because i can use TimeMachine backup to restore or clone the two macs... i hope.
Went into recovery mode and selected sub-Macintosh HD and attempted to erase; Result time after time after time: "Volume Encrypt and Erase failed." Reason: "Unable to delete the Core Storage logical volume." It dismounts it and I have to restart computer to get it back on. Funny thing is I don't have to use R anymore... which by the way, Command+R appears to be same as just plain old R when restarting... why is that?
This has become a "since Christmas" runaround session for me and I am sick of it.
Please help. I would've called Apple Care [and I did last night while driving... just to get advice on direction. I'm usually a pretty savvy PowerUser but this is driving me crazy.] but have to get things done for a meeting tomorrow. Can work on it after hours if someone can advise today on this post.
Thx,
Jim

I have taken some screenshots of the error I get and the state of my HDD in Disk Utility. I did have a weird thing happen after trying to repair using single user mode, where I reopened disk utility and the partitions were NOT greyed out and displayed the correct info concerning space available etc, although after verifying it then reverted back to greyed out with no info.

Can't remove Core Storage from hard drive

I wanted to erase a backup drive and start over again but somehow it's gotten converted to "Core Storage" I'm told.
I managed to erase the drive by first listing the Core Storage devices, using the following command in the OSX Terminal:
diskutil cs list
Then erasing the drive:
diskutil cs delete "Backup2"
This made everything look OK in Disk Utility, because now the drive appears as having a volume in addition to the drive icon, and there are also 4 tabs available (First Aid, Erase, Partition, RAID, Restore), but if I erase the drive something strange happens: it says "Switching disk1s1 to Core Storage", and after that the two drive icons in Disk Utility get the same name (all my other drives show an icon with the drive brand/model while the second icon shows the volume name). And the main drive icon only has 2 options now: First Aid and Partition. The volume icon has 3 options in DIsk Utility: First Aid, Erase, Restore.
The obvious thing to do at this stage is select "Erase", but this only results in the volume icon changing its name separately from the drive itself.
I've also tried booting with my OSX 10.6 installation DVD and erasing the drive from there, but the result is the same when I try to erase it once again. Seems like my OSX has somehow decided that this specific drive must be a Core Storage device regardless of what I've done to the actual drive itself.
What do I need to do in order to make the drive "normal" again? I'm using OSX 10.9.5.

Kappy: thanks, but I have to explain that I'm not in the process of upgrading from OSX 10.6 Snow Leopard (I grabbed the OSX 10.6 installation DVD because it allows me to boot from another media than the computer's boot drive -Mavericks doesn't come on a DVD of course and I haven't taken the time to figure out how to install it on a USB thumb drive).
I actually did a clean install (backup everything, reformat the drive, install OSX from scratch) of OSX 10.9 Mavericks recently, and the reason for reformatting the problematic drive in the first place was to do a completely new backup since I don't want to risk keeping keep bits of 10.6 mixed in there with 10.9.
I somehow messed up the drive which made it Core Storage and now it refuses to act as a normal drive.
My Mac consists of several drives where the abovementioned drive acts as a bootable backup.
Keg55: Thanks for your suggestions but I'm still running into the same issue as before: after doing the terminal commands my drive seems fine, but when I open Disk Utility (DU) and format ("erase") the drive gets converted back into Core Storage. I erase it in order to test if things have really gotten back to normal or if the Core Storage thingy still sticks with my system somehow (which it does). I'd never even heard of Core Storage until now (and still don't understand what it really is as most of the documentation I've found is highly technical), but could it be that OSX 10.9 Mavericks is supposed to do this while 10.6 Snow Leopard isn't (hence what Kappy is saying in the last part of the reply above about Yosemite creating Core Storage volumes automatically? Is this what applies here, or have I misunderstood?
OK, let me explain what happens step by step... The goal of course is to format the drive so as to act as a normal "Mac OS extended (journaled)" drive (as I said I don't even know what Core Storage is and don't know why I would be wanting this), so here goes....
1) At the first stage I have the drive freshly deleted using the diskutil cs delete LVG_UUID command (diskutil cs delete "volume_group_name" appears to be doing the same thing), so it's just like my other drives as far as I can see in DU (showing the drive brand/model and a partition icon underneath as seen in the screenshot below).
2) Now I want to verify if my drive has really become "normal" again or if it acts up once more by becoming a Core Storage drive again.
I click on the drive's (not its partition) icon in DU, select the "Erase" tab and finally press the erase button.
3) After pressing the erase button, messages pop up at the bottom part of DU very quickly. Luckily I can do screenshots faster than I can read, so here's what I've captured DU telling me. First it's converting the drive to Core Storage:
4) next it switching the drive to Core storage:
5) and finally it's formatting the file system for logical volume (whatever that means):
and as you can see in the top left corner the drive now only shows a single icon (unlike every time I've formatted a drive in the past it shows the drive and a partition icon, where the drive icon is followed by the drive's brand/model name).
So what's going on here and why can't I get my drive back to normal when erasing it?

Safe Boot Mode Freeze and Mavericks and Core Storage

I was having a problem booting into Safe Mode on a new iMac. It froze and restarted continuously.
Eventually I was told by engineering (after the Senior Tech) that...
"It’s expected behavior from any disc formatted with core storage and that includes discs encrypted with File Vault, a Fusion drive, or any internal disc larger than 2.2 Terabytes."
They also went on to say...
"They are investigating and improving the performance for future releases of OSX Mavericks."
FYI to those reported to have these problems. Don't waste time with it...it won't work. I reinstalled a clean OS, the Apple Repair depot installed a clean OS and when I got it back, I reinstalled it again.
It still doesn't work.
No reported fixes on the horizon at this time.
FYI
Dave

Not every iMac will have this problem, only the ones with the hardware as specified.
I think you should look around a little more on the net and you will find that there are others who have had this problem. Apple Tech also noted that they were aware of the problem.
One mitigating factor is that many Mac users have no idea what Safe Mode is anyway so they'd never notice it. My own iMac runs just fine, no probs and I calculated that I must had this problem for over 6 months until I stumbled on it. If I hadn't I'd still be using it and it might have gotten fixed by an update, in which case, I would have never known that I even had it to begin with. If you own an iMac that has not been formatted for disk spanning, then you won't have this problem either. All my other Macs run Mavericks and I have no problem with any of them.
I don't believe that there are that many people out there who actually own iMacs with 3 TB drives combined with a Fusion drive, sorry. We'll have to agree to disagree here. There are multiple factors at work here.

Why OS X Yosemite change primary volume name (core storage)

Hi to everyone,
I have several Macs. I like to make fresh installs. My experience tell me that fresh installs makes everything work better.
On my iMac, making the fresh install of OS X Yosemite don't change primary volume name (has a not HDD fusion). O my macbook pro retina (late 2013) OS X Yosemite change the primary volume name and equal to the partition name, that is, change it to a core storage disk. I could understand if it was a fusion disk, but in this case it is just an SSD of 256 GB. It is a bug of OS X Yosemite installer? If this shouldn't happen, anyone could tell how can I solve that, that is, make a fresh install on my macbook pro retina without change the primary volume name.
Thanks in advance.
Regards.

Safe boot your computer.
Turn off computer. Hold shift key. Turn on computer. Keep holding shift. Once progress bar starts moving let go. If you can then login and use your computer it is not the OS it is some other application installed on the computer that is causing the issue.

Do I need to re-enable Core Storage after cloning and swapping out my HDD?

I swapped out the internal hard drive of my mid-2012 13" MacBook Pro for an SSD. I'm very pleased with the performance gains so far — it feels like a whole new Mac. I cloned my HDD to the SSD before installing using Carbon Copy Cloner and I also created a Recovery partition using the same software. Now after doing the hardware swap, verything is working perfectly — no issues at all. Here's my question:
I know that when I upgraded to Yosemite, my hard drive was converted from old-fashioned GUID partitions to the new Core Storage and a logical volume group partition. After the clone and hardware swap, I'm back to old-fashioned partitions, no more Core Storage. Do I need to manually re-enable Core Storage? (I've read about how to do this, and I feel confident I can follow the steps.) What are the benefits of this? Will a future Yosemite (hypothetical 10.10.3?) update put it back for me? Or is it fine to proceed the way I am now? I'm not currently using FileVault 2, which I know also uses Core Storage.
Thanks.

No, you don't have to convert to CoreStorage unless you decide to create a Fusion drive out of your SSD and HDD.

Yosemite "problem resizing Core Storage" upgrade error?

Not a great amount of luck upgrading from Mavericks to Yosemite here.
Download and start install, restart, see the progress bar, then the install screen with "about 18 minutes remaining". It moves along, and then boom...
OS X could not be installed on your computer
A problem occurred while resizing Core Storage physical volume structures.
Quit the installer to restart your computer and try again.
Restarting several times, as well as returning to Mavericks and trying again has so far failed. Live Chat suggestions of verifying and repairing disks and trying in Safe Mode also unsuccessful.
3TB Fusion Drive has over 450GB free space, just the single "iMac" partition within the Macintosh HD.
Any help greatly appreciated! Otherwise looks like it's a wait to see if a fix appears...
iMac 27-inch, Late 2012
3TB Fusion Drive
3.4GHz Intel Core i7
16GB Memory

http://de.wikipedia.org/wiki/Fusion_Drive
Fusion Drive is a technology developed by Apple Computer Engineering, with a SSD and a mechanical hard drive be connected to a logical drive. [1]
Description and function [Edit]
Fusion Drive called Apple a technique in which an SSD and a mechanical hard disk are transparently connected to a logical drive. The user sees the combination as a single drive. [2] With Fusion Drive is also in large storage volume can be benefited at a moderate price of the speed of the SSD.
Fusion Drive connects not only two physical drives into one logical, but still used in addition to a technology that tiering is called. When tiering, in German as "staggering", data on frequently accessed, the fastest drive (SSD here) saved, the other to the slower, here on the mechanical drive. What data is stored where, the operating system decides on the basis of a thorough analysis of the data access itself and can not be influenced by the user. Optionally coated the operating system in the background to data. The operating system itself is always on the SSD. [3] [4] tiering is used in mainframe computers for some time, with Fusion Drive this technology now comes for the first time in a personal computer for use.
Fusion Drive must not be confused with conventional hybrid drives. While in the latter case the SSD part only serves as a data buffer and all data is ultimately always stored on the mechanical disk in Fusion Drive SSD is a full-fledged part of the logical drive (except a small part of 4 GB [3], which also serves as a buffer).
Fusion Drive is since November 2012 integrated with all new Macs with SSD and mechanical hard drive. [5] The first corresponding Macs were equipped with a 128 GB SSD and a 1 TB or 3 TB of mechanical hard disk. [6] Currently (April 2013 ), Apple provides no utility available with which Fusion Drive install on older Macs could. But this can be done via the terminal, this requirement is OS X 10.8 Lion Mountain. [7]

Partition failed with the error: The target Core Storage volume is locked

partition failed with the error: The target Core Storage volume is locked
Hello everybody!
Please help me.
I'm using MacBook Pro (Retina, 13-inch, Mid 2014), Processer:2.6 GHz Intel Core i5, Memory: 8 GB 1600 MHz DDR3.
my computer i have divided in 3 drives: 1-Machintosh HD (Mac OS) 2-Bootcamp (Window OS) & 3-Data (drive for data storage).
I don't want to use Window OS on my computer anymore so I decided to delete drive Data (the third drive) & Window OS (the second drive).
I want my hard drive become a single drive back but when I was formatting, there were some problem display:
then i clicked ok and it displayed like this:
then i try to format or create new partition, it's nothing happen when press button apply.
my computer has storage space 256GB but now when it is happened like this my storage space is only 127GB only.
so please help me.. what so I do with this problem.
Thank you.!

arajs wrote:
I used Boot Camp Assistant (for instaling Windows XP) and there was Partition error:
+*The disc cannot be partioned because some files cannot be moved.*+
+Back up the disk and use Disk Utility to format it as a single Mac OS Extended (journaled) volume. Restore your information to the disk and try using Boot Camp Assistand again.+
so I tried Yasu, verified permission, verified disk, and everything was ok, but in Disk Utility I was trying to split or change size of my disk but there is one error again:
+*Partition failed.*+
+Partition failed with the error: No space left on device+
but I have 64GB free space!
how must I "+Restore your information to the disk+" or what else can I do?
thanks!
This is a standard error message.
If you would have checked into the bootcamp forum you would have instantly found the solution.
http://discussions.apple.com/forum.jspa?forumID=1244&start=0
All that error message means is that you do not have enough conguous disk space available. No big deal at all for an older system. You have bits of files strewn over the "free space."
The solution as you would find in the bootcamp forum is to clone your HD, using a file-file clone, then test the clone to be sure it is working and then to erase your HD and clone back.
Works every time.
Message was edited by: Theodore

Core storage is unable to begin volume reversion

Hello there.
I have an external hard drive, and in finder I right clikced it to encrypt it.
Now I am trying to decrpyt it by opening it up in finder and its gives me Core Storage is unable to begin volume reversion error or sometimes : Unable to decrypt the Core Storage logical volume
I tried decrypting it in finder, in disk utlities, I tried earsing the hd completly, and multiple restarts on my computer.
My hd is pretty much useless at this point. I cannot view my content stored on that drive, copy or paste anything on and to that drive. It takes a long time for the content to load into the drive also before I can see it.
Does anyone have a solution for this?

I also have the same issue. In my case the system hangs during normal login, and stays there forever in about 40% of login progress. I am not able to access any file, or do anthing in the Mac Book pro.
I have Yosemite 10.10.2 installed.
I went into safemode and tried to turn off filevault, in attempts of fixing the hang. But I get "Core Storage is unable to begin volume reversion". Anyone any ideas on how to fix this and turn off filevault successfully?

Hello I don't know who to complain to as you do not appear to have a complaints department, despite searching the web, I trust you can pass this to relevant department for action, as I'm very angry over my recent repair. Following my issue relating to a

Hello
I don't know who to complain to as you do not appear to have a complaints department, despite searching the web, I trust you can pass this to relevant department for action, as I'm very angry over my recent repair.
Following my issue relating to a blank screen 2 weeks ago, your advisor arranged for my iMac to collected by Amsys, for repair and return, this was done and it was returned to me last Tuesday, onWednesday I set up my iMac again and instantly realised I had problems, much worse than before. I called Amsys to inform them of the issue of the computer being very very slow and unable to open iPhoto and pages, and document listing would not show up, plus I had no sound on the mac.They informed me that they had only replaced the video card and what they had done would have not affected the computers performance. He suggested I reinstall OSX again which I did, but this made no difference to the programs, so I called you.
Your technician on the phone was very good as they have always been, and made an appointment for me to go into the Milton Keynes Apple store the next day at 1 pm, which I did.
The gentleman on the Genius Bar was very good and was able to run tests on the iMac in my presence, and diagnosed immediately an issue with the sound problem, and advised me that this could not be fixed while I wait and I would need to leave it for repair. I made him aware of the previous repair, and he was able to see via your system, the list of logged issues I have had with this since purchasing in September 2012. I'm sure you can see from the way you record all calls and issues the problems I have had.
Today I called to ask if my iMac would soon be ready for collection, I was told the repairs had been completed and it was being tested. However to my dismay, I learned of another serious issue relating to the repair carried out by Amsys. I was informed that 6 screws were missing from the the iMac internally, which caused me much distress and concern, they also told me I had to wait even longer as the screws had to be ordered and installed on arrival before I could collect it.
My issues here are: I trusted the Amsys repairer as it was arranged and recommend by you, it is very evident they are not competent to repair, as they have caused more problems with my iMac on its return, despite enclosing a checklist, fully ticked showing everything working well, it clearly wasn't ! Plus the issue of missing parts (screws) during the repair, I have already expressed my disgust with Amsys, by email and had a response, within the hour, apologising and told me they were looking into this.
This where I stand on this, I have not had my iMac for almost two weeks and I do not know when I will get it back. I'm also very worried about what other damage has been caused by Amsys and the quality of my iMac now. I want to know what you, Apple is going to do about this ? I have already been very inconvenienced by this and until now I have been a very loyal apple customer with 2 iPads, and 4 iPhones in our household, not to mention the iMac.
I feel I have been very let down by this experience, on my iMac, which cost a lot of money, I have also lost a lot of money with lost work and unable to carry out my business without it, and I will be seeking compensation.
I trust you will take this complaint seriously and pass it to the relevant department for action.
Yours sincerely
Des Withey
Sent from my iPad
On 26 Feb 2014, at 11:44, Apple Support <[email protected]> wrote:
Thanks for contacting us.
Thanks for contacting Apple Support. If you need more help later, you can open the case below or start a new support request online.
Case ID:
Open this case
Sincerely,
Apple Support
Get help online
Visit Apple Support to learn more about your product, download software updates, and much more.
Join the conversation
Find and share solutions with Apple users around the world.
TM and copyright © 2014 Apple Inc. 1 Infinite Loop, MS 96-DM, Cupertino, CA 95014.
All Rights Reserved / Privacy Policy / Apple Support / Give us feedback
On behalf of Apple Distribution International

Call Apple Customer Relations - 1-800-275-2273. Ask politely & firmly that you want to be transferred to Customer Relations. Tell them exactly what you stated in your post.
GOOD LUCK!
These are user-to-user forums where everyday folk (volunteers) post questions and offer answers (technical support) to each other.

Oracle 10g RAC using ASM - Storage Issue

I’ve an issue related to Oracle 10g RAC.
I’ve 2 node cluster each being Dell 2850 Server with RHEL 4.0
I’ve EMC CX300 SAN storage with following partitions
/orasoft     10 Gb          OCFS2 File system
/oracrs          2 Gb          OCFS2 File system
/orabackup      100 Gb          OCFS2 File system
The datafiles are on ASM which is not directly visible in OS.
I’ve common Oracle Home installed in /orasoft/db_1 which is shared by both nodes in cluster.
I’ve faced an issue recently related to EMC storage.
The /orasoft partition displays 1.4 Gb space available using df command.
With both nodes sharing the common Oracle Home (/orasoft/db_1), when ever I try to touch a file I get an error as No Space left on device. I’m unable to start any service with the same reason.
Is this setup correct ??
Can anyone help me with this storage issue ??

Need a clarification here...what do you mean by "Storage System"...do you mean a server/node or the SAN storage system. If you are referring to a server/node's local storage, then it would NOT be possible for use by RAC, since the disk space has to be shared among the nodes.
Here is what you can do:
- Create two partitions/devices (for example Disk_1 and Disk_2) in the SAN storage
- Create a ASM disk group which would mirror Disk_1 to Disk_2.
Again, please note that the partitions have to be visible and be accessible read/write from both the nodes/servers.
HTH
Thanks
Chandra Pabba

Oracle 10g RAC+ASM - Storage Issue

I’ve an issue related to Oracle 10g RAC.
I’ve 2 node cluster each being Dell 2850 Server with RHEL 4.0
I’ve EMC CX300 SAN storage with following partitions
/orasoft     10 Gb          OCFS2 File system
/oracrs          2 Gb          OCFS2 File system
/orabackup      100 Gb          OCFS2 File system
The datafiles are on ASM which is not directly visible in OS.
I’ve common Oracle Home installed in /orasoft/db_1 which is shared by both nodes in cluster.
I’ve faced an issue recently related to EMC storage.
The /orasoft partition displays 1.4 Gb space available using df command.
With both nodes sharing the common Oracle Home (/orasoft/db_1), when ever I try to touch a file I get an error as No Space left on device. I’m unable to start any service with the same reason.
Is this setup correct ??
Can anyone help me with this storage issue ??

Hi,
If you create a new diskgroup you may be to add the same diskgroup to parameter file or spfile and which will be needing down time.
sugestion: Instead of creating new diskgroup you should to add disk to existing group.if you add asm disk to existing group your all problem will be solved and Oracle itself will be managing all.And than i am sure no need to add entry in the parameter or spfile like +db_create_file_dest=.....
regards,
Sher khan

ICloud storage issue; Restoring iPhone calendar from iMac after accidental iCloud deletion

I set up iCloud to back up calendars and contacts and for find my phone. Initially, it seemed to work alright. Then I got messages on iPhone that there wasn't enough iCloud storage, even though the storage tab showed that I had used none of my iCloud storage at all. So I turned off iCloud/contacts. In iTunes I switched back from iCloud backup to backup from my iMac.
Later I got the same message about not enough room in iCloud even though only calendars involved. So I truned off iCloud/calendar on my iPhone and was given the choice of keeping the calendars from the iCloud or deleting them (a foolish choice without a failsafe!!!). I clumsily and mistakenly hit delete. My calendars have most recently been synced with my new iMac and appear on the iMac and should also be in TM. But right now there is no data in my iPhone calendar.
When i go to calendars within the iiphone calendar there is a check next to Calender under "from MY Mac" and no reference to iCloud. (There are no separate calendars for me, my wife, and joint. Does this mean somehow these calendars have been merged because of iCloud?)
I don't want to do another sync until I can make sure that the sync with the iMac will resotre the calendar(s) to the iPnone. How do I do this?
Do I have to do anything on the iMac before I try a sync?
How do I avoid these problems in the future? The only thing I really would like from iCloud is "find my phone". How do I keep that capability without backing up or su=yncing otherwise anything through iCloud?
Is iCloud still Beta?

Apple walked me through this and helped me revert to backing up on my iMac, using iCloud only for find my iPhone and iMac. The process, however, is not straightforward and what the respective mac and iPhone support people (yes, they have that kind of specialization) led me through was clearer, if somewhat convoluted, than any instructions on Apple's support or community pages.
Since my main concern was not losing my calendar and contacts information, the key was saving that, via export, to my desktop. Sorry I didn't write down all the other steps - but I see that as Apple's job. Back in the days of the IIC, Apple's manual was a model of clarity and completeness at the same time.
Bottom line is while my immediate concerns were resolved, the underlying iCloud storage issue was not. On my iPhone, I was being told that my attempts to backup to the iCloud failed because I didn't have enough storage, even though I determined almost none of my alloted space was used. This issue is not helped by the multiplicity of settings relating to iCloud, or the interfaces (such as the iCloud on the iMac through Mavericks) which present a screen of icons without additional information.
For my purposes, iCloud remains Beta.

Error message when installing Yosemite OS: this core storage operation is not allowed on a sparse logical volume group

I was updating my Macbook Air (i7, 4mb RAM, 256 gb) to Yosemite OS when the process was interrupted. After retry, my computer is showing the following message: "this core storage operation is not allowed on a sparse logical volume group". I tried to restart several times, but the problem goes on with error. It would be my computer damaged?

If you don't already have a current backup of all data, back up before proceeding. There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
Start up in Recovery mode. When the OS X Utilities screen appears, select Disk Utility.
In the Disk Utility window, select the icon of the startup volume from the list on the left. It will be nested below another disk icon, usually with the same name. Click the Unlock button in the toolbar. When prompted, enter the login password of a user authorized to unlock the volume, or the alternate decryption key that was generated when you activated FileVault.
Then, from the menu bar, select
File ▹ Turn Off Encryption
Enter the password again.
You can then restart as usual, if the system is working. Decryption will be completed in the background. It may take several hours, and during that time performance will be reduced.
If you can't turn off encryption in Disk Utility because the menu item is grayed out, you'll have to erase the volume and then restore the data from a backup. Select the Erase tab, and then select
Mac OS Extended (Journaled)
from the Format menu.
You can then quit to be returned to the main Recovery screen. Follow these instructions if you back up with Time Machine. If you use other backup software, follow its developer's instructions.
Don't erase the volume unless you have at least two complete, independent backups. One is not enough to be safe.

Repairing bootcamp core storage issue

Similar Messages

Maybe you are looking for