Phenomenon as described below is being observed after Mavericks (latest) was upgraded to Sierra (10.12.6).
I like to ask if someone got in touch with these problems too or is familiarized with problem in some extent.
Directly before Mavericks to Sierra upgrade was started once yet full backup was made on external disk (USB 3.0) beside of those been generated with regularity during whole Mavericks usage cycle. Additional backup mentioned in the beginning is a bootable clone made using CCC. That external disk has no other purposes nor any backup depth (history), however clone of Recovery HD was made on it too, also by using CCC. It was tested yet while Mavericks on production disk internal to mac. Test was conducted by surfing clone content using Finder, test boot Mac from clone, booting from Recovery HD clone - all these three tests were conducted with addressed external disk (USB 3.0) as testee. All worked fine.
Then mac-internal production startup disk was subsequently upgraded to Sierra 10.12.6. From that point of time Mavericks bootable clone does not work any more. It generates panic up to appx 2 secs after clone selection was made in Boot Startup Manager. Panic stresses amongst others "Unable to find driver for this platform.... ACPI......SourceCache/xnu/xnu-2422.115.15/iokit/Kernel/IOPlatformexpert.cpp" then some dumps follow.
Same probs if to put this disk into some other external disk dock - yes the build factor is rather "USB 3.0 disk dock with SATA III internal disk inside, WD Caviar 320GB". Actually the goal was to have one additional bootable Mavericks clone just for the case something runs wrong on upgrade to Sierra.
If to take other bootable clone, also made using CCC also on USB 3.0 external disk in same dock - no problems. Recovery HD clone on it boots properly. It is possible also to attach that disk to running Sierra and surf its content using Finder. Disk Utility Verify disk and volume complete successfully under Recovery HD clone on same disk (means Mavericks) as well as in DU on production Sierra. It was possible to shrink on addressed clone disk bootable system volume about half of its initial size, it is just only Mavericks Recovery HD clone on same disk this operation can't complete that operation under - problems with final unmount. CCC on Sierra claims that clone it should be able to boot. Also permissions verification and repair or First Aid (on Sierra) complete with success.
Bombich guys can't help.
I like to ask if someone got in touch with these problems too or is familiarized with problem in some extent.
Directly before Mavericks to Sierra upgrade was started once yet full backup was made on external disk (USB 3.0) beside of those been generated with regularity during whole Mavericks usage cycle. Additional backup mentioned in the beginning is a bootable clone made using CCC. That external disk has no other purposes nor any backup depth (history), however clone of Recovery HD was made on it too, also by using CCC. It was tested yet while Mavericks on production disk internal to mac. Test was conducted by surfing clone content using Finder, test boot Mac from clone, booting from Recovery HD clone - all these three tests were conducted with addressed external disk (USB 3.0) as testee. All worked fine.
Then mac-internal production startup disk was subsequently upgraded to Sierra 10.12.6. From that point of time Mavericks bootable clone does not work any more. It generates panic up to appx 2 secs after clone selection was made in Boot Startup Manager. Panic stresses amongst others "Unable to find driver for this platform.... ACPI......SourceCache/xnu/xnu-2422.115.15/iokit/Kernel/IOPlatformexpert.cpp" then some dumps follow.
Same probs if to put this disk into some other external disk dock - yes the build factor is rather "USB 3.0 disk dock with SATA III internal disk inside, WD Caviar 320GB". Actually the goal was to have one additional bootable Mavericks clone just for the case something runs wrong on upgrade to Sierra.
If to take other bootable clone, also made using CCC also on USB 3.0 external disk in same dock - no problems. Recovery HD clone on it boots properly. It is possible also to attach that disk to running Sierra and surf its content using Finder. Disk Utility Verify disk and volume complete successfully under Recovery HD clone on same disk (means Mavericks) as well as in DU on production Sierra. It was possible to shrink on addressed clone disk bootable system volume about half of its initial size, it is just only Mavericks Recovery HD clone on same disk this operation can't complete that operation under - problems with final unmount. CCC on Sierra claims that clone it should be able to boot. Also permissions verification and repair or First Aid (on Sierra) complete with success.
Bombich guys can't help.
