Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Caution - Yosemite may screw up partitions.
- Thread starter yjchua95
- Start date
- Sort by reaction score
It must be the handle that you have
I guess if it's not physically bolted/welded to a stationary object it qualifies as portable...
Why and for how long. It has an impact on updates, # of possible partitions and tools functionality.
+1
to the people who considered log files.
There may be other criteria, not yet observed in logs, that cause the full installer to not prefer Core Storage if the Mac is not a notebook.
For Apple's rationale, I doubt that you'll find any hints in the logs, or elsewhere in public or private.
So, for yourselves, think logically about the essential natures of desktops compared to notebooks. Essential differences, with a focus on storage. It's relatively easy to add local storage to a desktop, relatively difficult with a notebook.
iCloud is good but still, we probably have many people thinking about where best to store something. Because storage in a notebook is limited. Occasional weeding exercises when there's too little free space.
Imagine a technology that reduces the need to weed. For some use cases, that technology might allow the user to never again think about weeding from a notebook.
Hint (for all readers)
Use the advanced editor when drafting posts. There's an option to paste as code. A much easier way to share content from log files.
Maybe related
Location independent files (patent application by Apple)
to the people who considered log files.
There may be other criteria, not yet observed in logs, that cause the full installer to not prefer Core Storage if the Mac is not a notebook.
For Apple's rationale, I doubt that you'll find any hints in the logs, or elsewhere in public or private.
So, for yourselves, think logically about the essential natures of desktops compared to notebooks. Essential differences, with a focus on storage. It's relatively easy to add local storage to a desktop, relatively difficult with a notebook.
iCloud is good but still, we probably have many people thinking about where best to store something. Because storage in a notebook is limited. Occasional weeding exercises when there's too little free space.
Imagine a technology that reduces the need to weed. For some use cases, that technology might allow the user to never again think about weeding from a notebook.
Hint (for all readers)
Use the advanced editor when drafting posts. There's an option to paste as code. A much easier way to share content from log files.
Maybe related
Location independent files (patent application by Apple)
This smells like a tight online storage integration on filesystem level. HFS+ or it's successor and iCloud Drive as one filesystem. The LVM joins the drives and OS X decides what will be stored local and what will be stored online, in the "cloud". Encrypted. Just speculating ...
Last edited:
So I filed it as a bug with the bug reporter tool at Apple and the issue was closed saying this is normal behaviour for the installer on notebooks, which explains why my Mini wasn't affected. I guess they feel FileVault is more a necessity on notebooks than desktops.
I was prompted after installation to turn FileVault on with the Air and not the Mini, so I guess the core storage conversion's aim is to speed up the process of turning it on if the user decides to enable it as is by default during the install.
I was prompted after installation to turn FileVault on with the Air and not the Mini, so I guess the core storage conversion's aim is to speed up the process of turning it on if the user decides to enable it as is by default during the install.
Checksum errors
Loaded Yosemite on external drive on my 2012 iMac with a fusion drive in recent past, and kept getting checksum errors in Disk Utility. Has anyone found out why that is the case? Still have not loaded the current version of Yosemite (OS X 10.10 (14A389)) on computer with the fusion drive...though would attempt to load it again on external drive when the "coast is clear" meaning future iterations of Yosemite.
Loaded Yosemite on external drive on my 2012 iMac with a fusion drive in recent past, and kept getting checksum errors in Disk Utility. Has anyone found out why that is the case? Still have not loaded the current version of Yosemite (OS X 10.10 (14A389)) on computer with the fusion drive...though would attempt to load it again on external drive when the "coast is clear" meaning future iterations of Yosemite.
Core Storage, fsck_cs and checksum errors: no in-depth explanation (sorry)
Relevant information was removed from Apple Support Communities, but the explanation for removal was not suitably explicit.
I do have web archives of parts of the topic but – sorry, Al – in the absence of a reasonable explanation for its removal, I can't share what I knew. To the best of my current knowledge, what I knew was not specific to Yosemite. I don't imagine making any future contribution to Apple Support Communities.
I know, that's not the answer that you would have liked, but I literally don't know what to say (don't know what I'm allowed to say).
Relevant information was removed from Apple Support Communities, but the explanation for removal was not suitably explicit.
I do have web archives of parts of the topic but – sorry, Al – in the absence of a reasonable explanation for its removal, I can't share what I knew. To the best of my current knowledge, what I knew was not specific to Yosemite. I don't imagine making any future contribution to Apple Support Communities.
I know, that's not the answer that you would have liked, but I literally don't know what to say (don't know what I'm allowed to say).
Well
This is Apple we are talking about not the CIA....cryptic response. Heck if Apple software is at fault then it needs to be explored, explained, and corrected. These checksum errors are not a problem on my 2010 iMac with a rotational drive.
This is Apple we are talking about not the CIA....cryptic response. Heck if Apple software is at fault then it needs to be explored, explained, and corrected. These checksum errors are not a problem on my 2010 iMac with a rotational drive.
Maybe relevant (or maybe I'm paranoid): the topic was removed after I complained about lack of documentation from Apple, and how that type of thing made it unnecessarily difficult for customers to know, or guess, what actions to take in response to what's logged by the operating system … mysteries of fsck_cs … words to that effect. Maybe I drew too much attention to something. Maybe I truly misbehaved. It's an Apple-provided service, I can't argue with their decision to remove the topic but it would have been nice to know exactly where boundaries had been crossed.
Back on topic, Core Storage and checksum mismatches. In my own case, I suspect a transient hardware issue, maybe not limited to (or not involving) the third party internal sshd of my MacBookPro5,2. If you like, try the HDAT2 that's included with UBCD; run the most powerful non-destructive test to tell whether your disk in its entirety behaves flawlessly in response a read-write-read-compare routine. That R/W/R/C routine may be extraordinarily time-consuming, but (given the constraints of HFS Plus in Core Storage) the end results of such routines may prove satisfying.
HTH and apologies for acronyms, as midnight approaches I'm becoming lazy!
Back on topic, Core Storage and checksum mismatches. In my own case, I suspect a transient hardware issue, maybe not limited to (or not involving) the third party internal sshd of my MacBookPro5,2. If you like, try the HDAT2 that's included with UBCD; run the most powerful non-destructive test to tell whether your disk in its entirety behaves flawlessly in response a read-write-read-compare routine. That R/W/R/C routine may be extraordinarily time-consuming, but (given the constraints of HFS Plus in Core Storage) the end results of such routines may prove satisfying.
HTH and apologies for acronyms, as midnight approaches I'm becoming lazy!
Checksum errors
Thanks for the explanation but after the checksum errors occurred I checked the disk and it came back no disk problems and no bad sectors identified. As soon as I deleted Yosemite from the external HD attached to my 2012 iMac with fusion drive and then repaired the disk with single user mode the checksum error was resolved and has not recurred (note these errors occurred X2 and in both cases after the deletion of the Yosemite partition and repairing the disk the errors have not resurfaced). So it appears to me that the checksum error and the loading of Yosemite are true-true and related.
Thanks for the explanation but after the checksum errors occurred I checked the disk and it came back no disk problems and no bad sectors identified. As soon as I deleted Yosemite from the external HD attached to my 2012 iMac with fusion drive and then repaired the disk with single user mode the checksum error was resolved and has not recurred (note these errors occurred X2 and in both cases after the deletion of the Yosemite partition and repairing the disk the errors have not resurfaced). So it appears to me that the checksum error and the loading of Yosemite are true-true and related.
Did you briefly test the disk by writing, reading and verifying every single sector of the disk, maybe multiple times ? This is what grahamperrin recommended. If you just partition and format, not every sector will be tested.
Later, while storing data, this data can be written to undetected bad sectors and then it will show up as a problem.
Checksum errors
I have ML 10.8.5 loaded on the main hard drive with windows 7, and on the external hard drives I have Mavericks and variations on the ML operating system plus CC clones for each and time machine backups for all operating systems and I have never had a checksum error until I loaded Yosemite. In fact, I loaded all the Mavericks beta's on my 2012 iMac with the fusion drive from the first release and never had a disk error. So, although, I see what you are suggesting my feeling is that if there are disk errors/problems abounding why has it not occurred before or since the deletion of Yosemite?
I have ML 10.8.5 loaded on the main hard drive with windows 7, and on the external hard drives I have Mavericks and variations on the ML operating system plus CC clones for each and time machine backups for all operating systems and I have never had a checksum error until I loaded Yosemite. In fact, I loaded all the Mavericks beta's on my 2012 iMac with the fusion drive from the first release and never had a disk error. So, although, I see what you are suggesting my feeling is that if there are disk errors/problems abounding why has it not occurred before or since the deletion of Yosemite?
I cannot answer your question but I highly doubt that Yosemite corrupts a disk. There can be many contributing factors resulting in disk problems.
However, those problems are serious and should not be ignored based on a guess. It does not cost you anything except computing time to check your disk seriously and after that you can be sure to have a good hard drive. Priceless.
However, those problems are serious and should not be ignored based on a guess. It does not cost you anything except computing time to check your disk seriously and after that you can be sure to have a good hard drive. Priceless.
Checksum errors
If you search the forums for disk errors occurring after the loading of Yosemite you will find quite a few. Either we all have disk problems or Yosemite is a super diagnostic tool for uncovering them. What everyone must concede is that operating systems evolve and are not perfectly formed and complete when released. The other concession that we need to make is that although Apple is successful they are not perfect.
Sometimes I feel like I am in the movie the "Wizard of Oz", were, like Dorothy and her merry band, I am sent on a quest for the witches broom which in point of fact is simply a red herring.
If you search the forums for disk errors occurring after the loading of Yosemite you will find quite a few. Either we all have disk problems or Yosemite is a super diagnostic tool for uncovering them. What everyone must concede is that operating systems evolve and are not perfectly formed and complete when released. The other concession that we need to make is that although Apple is successful they are not perfect.
Sometimes I feel like I am in the movie the "Wizard of Oz", were, like Dorothy and her merry band, I am sent on a quest for the witches broom which in point of fact is simply a red herring.
+1
With respect: it's far more complex (and frustrating) than either/or.
Recently, in a topic unrelated to storage I wrote:
Those contributions from me, typically in Apple Support Communities, were fairly often in storage-oriented topics – Disk Utility, fsck_hfs, HFS Plus, Core Storage, fsck_cs and so on – where many "me too" responses were inappropriate (whatever problem was in the opening post, those "me too" replies were from people whose problems were different); where people wrongly imagined that problems with storage following an installation were due to a bug in the installation package; and so on.
Without going into detail, I became focused on the (then) fitness for purpose of things such as HFS Plus, fsck_hfs and (most noticeably) Disk Utility. A frustratingly huge amount of time can be wasted by individual customers, and by groups of customers, as a result of the combined inadequacies of those three things. After long and careful consideration:
https://alpha.app.net/grahamperrin/post/23338278 and what happened next is probably overwhelmingly, painfully obvious but for those of you who haven't noticed: not only does the latest OS X have what's almost certainly a legacy file system (Mac OS
With apologies (again) to Al: that combination of 'legacy + worst' is not an incentive, from Apple, for me to offer storage-related advice where that advice is most urgently required/desired by a few customers. For the greater long-term good, I find it necessary to focus my efforts on the problems with appearance.
Still, I'll occasionally dip into topics such as this … good luck, y'all.
Hello Guys,
i wanted to do a Yosemity clean install today and got the error message
"this partition map modification would make a windows partition unbootable"
which broughts me here.
It seems i'm not the only one with issues.
On my Macbook i have three Partitions, OSX, Bootcamp and a DATA Partition
I made this configuration nearly a year ago, and i remember that it was not so easy to get. I remember something that it's only possible to have 3 or 4 Partitions on a Mac.
I read this Thread from the start 'til end, but i havent found out what could help.
Thanks for every help in andvance.
i wanted to do a Yosemity clean install today and got the error message
"this partition map modification would make a windows partition unbootable"
which broughts me here.
It seems i'm not the only one with issues.
On my Macbook i have three Partitions, OSX, Bootcamp and a DATA Partition
I made this configuration nearly a year ago, and i remember that it was not so easy to get. I remember something that it's only possible to have 3 or 4 Partitions on a Mac.
I read this Thread from the start 'til end, but i havent found out what could help.
Thanks for every help in andvance.
Hello Guys,
i wanted to do a Yosemity clean install today and got the error message
"this partition map modification would make a windows partition unbootable"
which broughts me here.
It seems i'm not the only one with issues.
On my Macbook i have three Partitions, OSX, Bootcamp and a DATA Partition
I made this configuration nearly a year ago, and i remember that it was not so easy to get. I remember something that it's only possible to have 3 or 4 Partitions on a Mac.
I read this Thread from the start 'til end, but i havent found out what could help.
Thanks for every help in andvance.
I believe it is more a limitation of Bootcamp and not Mac/OS X. Bootcamp wants to be the fourth partition. There are workarounds where you make the Bootcamp partition then add the other ones later. I think this is what you are running up against.
Yosemite wants to create a recovery partition.
It cannot, because you have too many partitions already.
Now, I cannot advice what you need to do, it's up to you what you decide. I ended up with a clean installation, installed BootCamp from scratch as well and skipped my 3rd partition for the sake of an OS X recovery partition.
It cannot, because you have too many partitions already.
Now, I cannot advice what you need to do, it's up to you what you decide. I ended up with a clean installation, installed BootCamp from scratch as well and skipped my 3rd partition for the sake of an OS X recovery partition.
Last edited:
Yes that could be.
But is there a way to install Yosemity without setting everything up new.
I'm still able to boot the windows partition.
On the OSX partiotion i deleted everything for the clean install, and when i start with the Yosemity installation i get the error message.
I remember i deleted the recovery partiotion for this setup.
Is there a way to solve this problem?
Kind regards
But is there a way to install Yosemity without setting everything up new.
I'm still able to boot the windows partition.
On the OSX partiotion i deleted everything for the clean install, and when i start with the Yosemity installation i get the error message.
I remember i deleted the recovery partiotion for this setup.
Is there a way to solve this problem?
Kind regards
Me too, thats why I said I think it's a rumor. It was my last option to give you a hint that you maybe could avoid installing everyting from scratch and need to reduce the number of partitions.
IMO it's time for backup now. You should be able to clone the Windows partition after a first clean Windows "dummy" install. If you clone, be prepared that Windows will not boot after you cloned it, because the partition # where it needs to boot from changed ( !!! do not restore the MBR when you restore the clone !!! ). Booting can be fixed.
IMO it's time for backup now. You should be able to clone the Windows partition after a first clean Windows "dummy" install. If you clone, be prepared that Windows will not boot after you cloned it, because the partition # where it needs to boot from changed ( !!! do not restore the MBR when you restore the clone !!! ). Booting can be fixed.
Last edited: