Can no longer boot to OS 9.2.2 on a Dual Processor Mirrored Door G4?

Hope someone can put me out of my misery...
I've been running my Mirrored Door (MDD) Dual G4 for years and have always booted into OS 9, but today, the Mac has decided to boot to OSX.
From the Startup Disk Control panel in OSX, I have selected the OS9 system folder as the startup system, but after a restart, OSX still loads. However, on a restart, I notice that I get a quick OS 9 smiley face along with the question mark before it boots into OSX.
The thing is that when OSX is up and running, I can start Classic manually and OS runs OK so I presume the OS 9 Sytem Folder is OK.
Is there something I can do to get the boox booting back to OS9?
Thanks in advance.

If you still have issues after following Kenichi's excellent advice, let us know if you changed anything, ie. added a new disk, added a new application, moved disks, moved the OS9 System Folder, etc.
a guaranteed-to-work very last resort is to
let it boot into OSX,
backup the OS9 System Folder to a subdirectory (make sure it's not in the top level of the boot disk).
use the MDD restore cd's to perform a partial restore, in which you select to restore OS9.
You would then need to re-install any other updates to OS9 since 2003, usually iTunes, QuickTime, etc. There's a definitive list of 6 updates that we keep posting in these forums, but I just can't remember them just now.
- hang on ... Carbonlib v1.6, iTunes v2.0.4, QuickTime v6.0.3, Authoring Support v1.1.9, AppleScript v1.8.3 and MRJ 2.2.6 (Java).
Plus any printer / scanner drivers you may need. But all of these could probably be salvaged from the backup you made of the OS9 System Folder.
If you're like me, I backup the OS9 System Folder every week and keep 4 generations. Mine is about 300MB, 92MB compressed, worthwhile in these days of 120GB-500GB disks.

Similar Messages

Can no longer boot into Mavericks 10.9.5

My problem is that I can no longer boot into Mavericks 10.9.5 on my mid-2012 Macbook Pro. The problem arose suddenly without any known major changes to my software or hardware. The booting process freezes with the apple visible and the circle below it spinning endlessly. Every several seconds, the display very briefly gets brighter, then the circle starts spinning again and the process repeats itself. It never gets to the user login screen.
Other than keeping various apps up to date, I don't recall any recent major operating system or other major software updates, nor have I made any recent hardware changes. I've searched a multitude of threads and and tried any number of fixes without success. Here's what I've tried so far (and probably a few more that I can't remember): (1) Repaired the startup disk with both Recovery HD -> Disk Utility and single-user mode -> /sbin/fsck -fy; (2) Repaired the startup disk permissions with Recovery HD -> Disk Utility; (3) Reloaded the Mavericks 10.9.5 operating system twice; (4) deleted /Library/Preferences/com.apple.loginwindow.plist; (5) reset PRAM and NVRAM; (6) booted with "D" pressed and ran the Apple hardware test, which ran for about 40 minutes and reported no problems; (7) tried booting from a bootable clone of Mavericks 10.9.5 on an external hard drive, which also failed at the same place with the apple showing and the circle below it spinning endlessly. ***Oddly, I am able to boot from a bootable clone of Mountain Lion on an external hard drive. It's Mavericks that won't boot.***
Here is the part of the system log the repeats itself over and over and seems to correlate with the repeated failed attempts to complete the booting process. Any help would be appreciated beyond words:
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Server is starting up
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Session 256 retained (2 references)
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Session 256 released (1 references)
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Session 256 retained (2 references)
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: init_page_flip: page flip mode is on
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Found 54 modes for display 0x00000000 [54, 0]
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Found 1 modes for display 0x00000000 [1, 0]
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Found 51 modes for display 0x00000000 [51, 0]
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Found 1 modes for display 0x00000000 [1, 0]
May 2 12:49:01 --- last message repeated 1 time ---
May 2 12:49:01 SCH-MacBookPro kernel[0]: IOHIDSystem::registerScreenGated: Screen 0 recycled from pid 343
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: mux_initialize: Mode is dynamic
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Found 54 modes for display 0x00000000 [54, 0]
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Found 1 modes for display 0x00000000 [1, 0]
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Found 51 modes for display 0x00000000 [51, 0]
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Found 1 modes for display 0x00000000 [1, 0]
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: WSMachineUsesNewStyleMirroring: true
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: MPServiceForDisplayDevice: Invalid device alias (0)
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Display 0x04248378: GL mask 0x10; bounds (0, 0)[2560 x 1440], 51 modes available
Main, Active, on-line, enabled, Vendor 610, Model 9227, S/N 162f0ab5, Unit 4, Rotation 0
UUID 0x3ef17c2fc9ab601507ec022fbd95576c
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Display 0x003f003d: GL mask 0x2; bounds (0, 0)[4096 x 2160], 2 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 1, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Display 0x003f0041: GL mask 0x20; bounds (0, 0)[0 x 0], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 5, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Display 0x003f003f: GL mask 0x8; bounds (0, 0)[0 x 0], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 3, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Display 0x04280142: GL mask 0x5; bounds (2560, 0)[1680 x 1050], 54 modes available
Active, on-line, enabled, built-in, boot, Vendor 610, Model a005, S/N 0, Unit 2, Rotation 0
UUID 0xde23f9c1cf7b915b2afe83aecee77b54
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: WSSetWindowTransform: Singular matrix
May 2 12:49:01 --- last message repeated 1 time ---
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Display 0x04248378: GL mask 0x10; bounds (0, 0)[2560 x 1440], 51 modes available
Main, Active, on-line, enabled, Vendor 610, Model 9227, S/N 162f0ab5, Unit 4, Rotation 0
UUID 0x3ef17c2fc9ab601507ec022fbd95576c
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Display 0x003f003d: GL mask 0x2; bounds (3584, 0)[1 x 1], 2 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 1, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Display 0x003f0041: GL mask 0x20; bounds (3585, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 5, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Display 0x003f003f: GL mask 0x8; bounds (3586, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 3, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Display 0x04280142: GL mask 0x5; bounds (435, -1050)[1680 x 1050], 54 modes available
Active, on-line, enabled, built-in, boot, Vendor 610, Model a005, S/N 0, Unit 2, Rotation 0
UUID 0xde23f9c1cf7b915b2afe83aecee77b54
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: CGXPerformInitialDisplayConfiguration
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]:   Display 0x04248378: Unit 4; Vendor 0x610 Model 0x9227 S/N 372181685 Dimensions 23.50 x 13.23; online enabled, Bounds (0,0)[2560 x 1440], Rotation 0, Resolution 1
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]:   Display 0x003f003d: Unit 1; Vendor 0xffffffff Model 0xffffffff S/N -1 Dimensions 0.00 x 0.00; offline enabled, Bounds (3584,0)[1 x 1], Rotation 0, Resolution 1
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]:   Display 0x003f0041: Unit 5; Vendor 0xffffffff Model 0xffffffff S/N -1 Dimensions 0.00 x 0.00; offline enabled, Bounds (3585,0)[1 x 1], Rotation 0, Resolution 1
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]:   Display 0x003f003f: Unit 3; Vendor 0xffffffff Model 0xffffffff S/N -1 Dimensions 0.00 x 0.00; offline enabled, Bounds (3586,0)[1 x 1], Rotation 0, Resolution 1
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]:   Display 0x04280142: Unit 2; Alias(2, 0x5); Vendor 0x610 Model 0xa005 S/N 0 Dimensions 13.03 x 8.15; online enabled built-in, Bounds (435,-1050)[1680 x 1050], Rotation 0, Resolution 1
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: CGXMuxBoot: Boot normal
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: GLCompositor: GL renderer id 0x01024400, GL mask 0x00000003, accelerator 0x00004f2f, unit 0, caps QEX|MIPMAP, vram 1024 MB
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: GLCompositor: GL renderer id 0x01024400, GL mask 0x00000003, texture max 16384, viewport max {16384, 16384}, extensions FPRG|NPOT|GLSL|FLOAT
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: GLCompositor: GL renderer id 0x01022727, GL mask 0x0000003c, accelerator 0x00004907, unit 2, caps QEX|MIPMAP, vram 1024 MB
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: GLCompositor: GL renderer id 0x01022727, GL mask 0x0000003c, texture max 16384, viewport max {16384, 16384}, extensions FPRG|NPOT|GLSL|FLOAT
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: GLCompositor enabled for tile size [256 x 256]
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: CGXGLInitMipMap: mip map mode is on
May 2 12:49:01 SCH-MacBookPro.local loginwindow[353]: **DMPROXY** Found `/System/Library/CoreServices/DMProxy'.
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Display 0x04248378: Unit 4; ColorProfile { 2, "Thunderbolt Display"}; TransferFormula (1.000000, 1.000000, 1.000000)
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Display 0x04280142: Unit 2; ColorProfile { 3, "Color LCD"}; TransferTable (256, 12)
May 2 12:49:01 SCH-MacBookPro.local launchctl[356]: launchctl: Dubious permissions on file (skipping): /Library/LaunchAgents/com.adobe.AAM.Updater-1.0.plist
May 2 12:49:01 SCH-MacBookPro.local launchctl[356]: com.apple.findmymacmessenger: Already loaded
May 2 12:49:01 SCH-MacBookPro.local com.apple.SecurityServer[23]: Session 100021 created
May 2 12:49:01 SCH-MacBookPro.local UserEventAgent[357]: Failed to copy info dictionary for bundle /System/Library/UserEventPlugins/alfUIplugin.plugin
May 2 12:49:01 SCH-MacBookPro.local airportd[71]: _doAutoJoin: Already associated to “schuyler”. Bailing on auto-join.
May 2 12:49:01 SCH-MacBookPro.local loginwindow[353]: Setting the initial value of the magsave brightness level 1
May 2 12:49:01 SCH-MacBookPro.local loginwindow[353]: Login Window Started Security Agent
May 2 12:49:01 SCH-MacBookPro.local ManagedClient[362]: ApplePersistence=YES
May 2 12:49:01 SCH-MacBookPro.local SecurityAgent[363]: Failed to create agent mechanism, failing authentication!
May 2 12:49:01 SCH-MacBookPro.local com.apple.authd[84]: engine[353]: error creating mechanism agent
May 2 12:49:01 SCH-MacBookPro.local com.apple.authd[84]: engine[353]: evaluate returned -60008 returning errAuthorizationInternal
May 2 12:49:01 SCH-MacBookPro.local loginwindow[353]: Login Window - Returned from Security Agent
May 2 12:49:01 SCH-MacBookPro.local loginwindow[353]: ERROR | -[LoginApp performAuthPluginRequest:] | AuthorizationRef doesn't have a username. Exiting.
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: CGXRestartSessionWorkspace: session workspace exited for session 256 (on console)
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Session 256 released (1 references)
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: Session 256 released (0 references)
May 2 12:49:01 SCH-MacBookPro.local WindowServer[354]: loginwindow connection closed; closing server.
May 2 12:49:03 SCH-MacBookPro com.apple.launchd[1] (com.apple.loginwindow): Throttling respawn: Will start in 1 seconds
May 2 12:49:04 SCH-MacBookPro.local loginwindow[364]: Login Window Application Started
May 2 12:49:04 SCH-MacBookPro com.apple.launchd[1] (com.apple.WindowServer): Throttling respawn: Will start in 7 seconds

Hi
You got a prob I think, if you can boot a windows, MSconfig, startup options might restore the boot files.Only other thing is to try and either load a new windows and let it setup a boot file, or perhaps a win98 startup disk, and fdisk, then set active partiton, which will set an MBR. But that would leave a load of work to do, I think I'd opt for an install of XP, and let it repair existing installation, and make a new boot file.
Hope you don't need the info on disks. If you do, I would install another HDD, load XP, then copy original Disk to save place.
Good luck
Jocko

Can no longer boot to MacOSX after bootcamp install

Hello all, I have an issue to where I can no longer boot into the Mac OSX partition after what appears to be a failed Windows bootcamp install. As I was running the bootcamp assistant process, a reboot occurred and I was greeted with the "No bootable device -- insert boot disk and press any key". I have no idea how to get past this and boot back to OSX.
Things I have tried:
Holding down the "option" key does nothing, even using a USB keyboard
Resetting PRAM (CMD + OPT + P + R) does nothing, even with USB keyboard
I have put in a MAC OSX 10.7 Disk and cannot boot to disk using CMD + C on startup
I also pulled the hard drive out and connected it to another PC and wiped the drive completely. I put it back in the macbook and I am still presented with this error. It seems, even though I get the Mac startup tone, that it is stuck in which ever OS it tried to run previously, that being Windows. Not sure why I am still receiving this error even after wiping the drive completely clean.
As far as hardware goes, I am pretty sure its a late 2010 Alumn. Macbook Pro. I cant get the current model number since I cant boot the OS. Any help is appreciated.

Please reset SMC as well.
You can get the serial number from the back cover and use https://selfsolve.apple.com/agreementWarrantyDynamic.do to find the model.

FreeBSD didn't install, i can no longer boot into Windows

I unsuccessfully installed FreeBSD and I can no longer boot into an OS from the HD. I attempted to install BSD onto the "G" drive below however the the install gave me some kind of storage error and I can no longer boot into Windows. While going through the BSD installation process I opted to NOT install a boot manager (I incorrectly assumed that this would leave my existing boot manager intact).
Here's how I was partitioned pre-FreeBSD (these are all partitions on the same SATA 80GB drive):
C:\ Windows ME
D:\ Windows XP sp1a
E:\ Windows XP-64 beta
F:\ Longhorn 64 preview
[G]:\ unpartitioned 4GB
[F]:\ uformatted 4GB
H:\ NTFS Storage
I:\ FAT32 Storage
Before I attempted to install BSD, I used c:\boot.ini as my boot manager.
Now when I try to boot it says:
Code: [Select]
Invalid Partition
Invalid Partition
No /boot/loader
FreeBSD/i386 boot
Default: 0:ad(0,a)/kernel
boot:
Invalid Partition
No /kernel
FreeBSD/i386 boot
Default: 0:ad(0,a)/kernel
boot: _
Has anyone else ever had this happen to them? If so how can I reenable booting into Windows?

Hi
You got a prob I think, if you can boot a windows, MSconfig, startup options might restore the boot files.Only other thing is to try and either load a new windows and let it setup a boot file, or perhaps a win98 startup disk, and fdisk, then set active partiton, which will set an MBR. But that would leave a load of work to do, I think I'd opt for an install of XP, and let it repair existing installation, and make a new boot file.
Hope you don't need the info on disks. If you do, I would install another HDD, load XP, then copy original Disk to save place.
Good luck
Jocko

Can no longer boot to OS 9 with Mirrored Door Dual processor G4?

Hope someone can put me out of my misery...
I've been running my Mirrored Door (MDD) Dual G4 for years and have always booted into OS 9, but today, the Mac has decided to boot to OSX.
From the Startup Disk Control panel in OSX, I have selected the OS9 system folder as the startup system, but after a restart, OSX still loads. However, on a restart, I notice that I get a quick OS 9 smiley face along with the question mark before it boots into OSX.
The thing is that when OSX is up and running, I can start Classic manually and OS runs OK so I presume the OS 9 Sytem Folder is OK.
Is there something I can do to get the boox booting back to OS9?
Thanks in advance.

Hi-
You may need to repair your OS 9 volume, or, may need to rebless the OS 9 system folder.
Follow the instructions for OS 9 in this document.

[Solved again] Updated to linux-3.10.8; Can no longer boot

Hey everyone.
So, linux-3.10.2-1 just dropped to the [testing] repos, and I got it through a standard -Syu. Along with it were upgraded libxfont, linux-headers, lirc-utils (and I installed extundelete during the same command).
Here's the relevant bit of /var/log/pacman.log:
[2013-07-22 11:03] [PACMAN] Running 'pacman --color=always -Syu extundelete'
[2013-07-22 11:03] [PACMAN] synchronizing package lists
[2013-07-22 11:03] [PACMAN] starting full system upgrade
[2013-07-22 11:06] [PACMAN] installed extundelete (0.2.4-1)
[2013-07-22 11:06] [PACMAN] upgraded libxfont (1.4.5-1 -> 1.4.6-1)
[2013-07-22 11:07] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2013-07-22 11:07] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2013-07-22 11:07] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2013-07-22 11:07] [ALPM-SCRIPTLET] ==> Starting build: 3.10.2-1-ARCH
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-07-22 11:07] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-07-22 11:07] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2013-07-22 11:07] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-07-22 11:07] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2013-07-22 11:07] [ALPM-SCRIPTLET] ==> Starting build: 3.10.2-1-ARCH
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-07-22 11:07] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
[2013-07-22 11:07] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2013-07-22 11:07] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-07-22 11:07] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-07-22 11:07] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-07-22 11:07] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2013-07-22 11:07] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-07-22 11:07] [PACMAN] upgraded linux (3.10.1-1 -> 3.10.2-1)
[2013-07-22 11:07] [PACMAN] upgraded linux-headers (3.10.1-1 -> 3.10.2-1)
[2013-07-22 11:07] [PACMAN] upgraded lirc-utils (1:0.9.0-51 -> 1:0.9.0-52)
Then, because I am on a UEFI system, I copied the initrd images and the vmlinuz image over to my ESP (just like I've done many a time before), and now the system won't boot. It doesn't throw any errors; rather, as soon as UEFI selects the entry to run, the computer just sits there (there is nothing in the logs so far as I can find).
I've booted with a live medium and I've tried regenerating the images and recopying them (the checksums of the images changed, so I figured that might do the trick), but it's still a no-go. Is there something obvious that I'm missing? Has anyone else run into this problem?
[Edit]: Though this appeared to be solved with 3.10.3, the problem appears to have returned with 3.10.8. No actual solution has been found. As with before, a new kernel has been released (3.10.9) with which this issue does not exist…
All the best,
-HG
Last edited by HalosGhost (2013-08-21 17:01:46)

So I added /boot to my fstab with option "auto" to not rely on the systemd-efi-generator and /boot was mounted just fine. Then I set noauto,x-systemd.automount and the autofs mount point was created as expected. Then I removed the /boot entry in fstab again and the systemd-efi-generator seems to work fine again...
I'm seriously confused right now...
btw, I did all of this mit kernel 3.9.9 booted. 3.10.2 doesn't boot on my system, it's the famous ""EFI machine randomly hangs while loading kernel" bug again. But this shouldn't have anything to do with the kernel install problem...
edit: I just realized that my "btw" is actually what OP describes. I should have read the thread completely, sorry
Either way, as far as I can see these are two separate issues. The EFI bug with the long thread that I mentioned above and the fact that /boot seems to not mount in some cases. I did some more testing regarding this, but I still have no idea what is happening. I could have sworn there was no automount point set up by systemd at some point, which would have made sense. But I can't reproduce it anymore...
Last edited by 65kid (2013-07-23 21:54:55)

Ok, so after I upgraded to ML I can no longer Boot camp...

Ok, so I just reinstalled OSX 10.8(A clean install) and now I can't boot camp, when I open up the application it says "The startup disk cannot be partitioned or restored to a single partition. The startup disk must be formatted as a single Mac OS Extended (Journaled) volume or already partitioned by Boot Camp Assistant for installing Windows.". Why does it say this?

Here are the places to report bugs:
Get an account at
http://developer.apple.com/ then submit a bug report to http://bugreporter.apple.com/
Once on the bugreporter page,
   -- click on New icon
   -- See if you need to attach a log file or log files, clicking on Show instructions for gathering logs. Scroll down to find the area or application that matches the problem.
   -- etc.
Developers:
"Submitting Bugs and Feedback
Your feedback goes a long way towards making our products even better. With Apple Bug Reporter, you can submit bug reports or request enhancements to APIs and developer tools."
https://developer.apple.com/bug-reporting/
Enterprise support:
Call enterprise support (866) 752-7753 to create a case ID number

After resizing a disc partition using disk utilities, I can no longer boot windows. HELP! what is the best thing that I can do to fix this

Bare with me as Im no computer genius but ... This afternoon I wanted to create more disc space on my Windows partition as I am using CAD software and wanted to free up as much space as possible. So, I went into disk utility and reduced the size of the Mac partition, then clicked apply.
When I came to reboot the computer to use windows the windows OS, the option to use windows was no longer there.
After looking at some online forums, I've found that most people suggest reformatting the hard drive and re-installing mac OS and also windows from back up data.
Is there no easier way for which I will not lose any data? Please help! I really need to use Windows ASAP!

The only apps I know of that can backup a Windows partition and or resize a windows parttition on a Mac so you don't have to go through the wipeing out, resizing and reinstall is WinClone for backing it up and WinTune (I think that is the name) for resizing a Windows partition on a Mac.
Once you create a Windows partition, install Windows in that partition, you can't fool around with any partition on your drive with either Windows Disk Management or OS X Disk Utility and expect Windows to boot.
The only thing you can try is to run Boot Camp Assistant.app again and remove the Windows partition and then run it again to create a larger partition and then reinstall Windows. Once you remove the windows partition put all the space back into the OS X partition and start fresh.

Just installed OS X updates and can no longer boot into Bootcamp

Just installed the latest updates for OS X Yosemite and now I can't boot to my Bootcamp partition. It doesn't show up in Startup Disks and it's not an option when booting while holding Option. The partition still shows up in Disk Utility but it no longer says BOOTCAMP, it now says disk04s. Is this fixable? I just wrote some data to that partition last night that I really don't want to lose and it hasn't yet been backed up. Thank you.
diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *121.3 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:          Apple_CoreStorage                         91.0 GB    disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
   4:       Microsoft Basic Data                         20.0 GB    disk0s4
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS Macintosh HD           *90.0 GB    disk1
                                 Logical Volume on disk0s2
                                 2CC4DC13-C5C7-47E8-B005-3B8080275E8E
                                 Unencrypted
sudo gpt -vv -r show /dev/disk0
gpt show: /dev/disk0: mediasize=121332826112; sectorsize=512; blocks=236978176
gpt show: /dev/disk0: Suspicious MBR at sector 0
gpt show: /dev/disk0: Pri GPT at sector 1
gpt show: /dev/disk0: Sec GPT at sector 236978175
      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 177734368      2 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC
178144008    1269536      3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
179413544   18503128
197916672   39059456      4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
236976128       2015
236978143         32         Sec GPT table
236978175          1         Sec GPT header
sudo fdisk /dev/disk0
Disk: /dev/disk0 geometry: 14751/255/63 [236978176 sectors]
Signature: 0xAA55
         Starting       Ending
#: id cyl hd sec - cyl hd sec [     start -       size]
1: EE 1023 254 63 - 1023 254 63 [         1 -     409639] <Unknown ID>
2: AC 1023 254 63 - 1023 254 63 [    409640 - 177734368] <Unknown ID>
3: AB 1023 254 63 - 1023 254 63 [ 178144008 -    1269536] Darwin Boot
4: 0C 1023 254 63 - 1023 254 63 [ 197916672 -   39059456] Win95 FAT32L

Here is a table to validate your values.
GPT 3 Start
GPT 3 Size
GPT 3 End
NTFS Start
Sector Offset
NTFS Size
NTFS End
Sector Offset (MB)
178144008
1269536
179413544
179415040
1496
57561081
236976121
1
Leave your Testdisk display and start a new Terminal Window.
If you see any error messages during the following steps, please stop and post back here with the error message. The following steps have values from your Testdisk output (and you can verify) in Steps 7 and 8.
Rebuild GPT4 using start/end offsets
Sudo gdisk /dev/rdisk0
P (print the full list of parts)
D (delete)
4 (part 4)
N (new part)
4   (part 4)
179415040- Start offset in bytes (start point for Bootcamp part)
+57561081- (Size offset as opposed to End offset)
0700     (Windows part type)
P           (print list of all parts just to see what changes will be made)
W         (Write the new GPT)
Y           (Yes! really write the new GPT)
This will delete and re-write the GPT partition info for /dev/disk0s4.
Rebuild MBR to match the new GPT information thus resetting the Hybrid MBR. Use defaults for other questions (like partition codes). The only values that need modifications are the Boot flags and step 6. Accept all other defaults that Gdisk offers.
Sudo gdisk /dev/disk0
P (Print list of parts)
R   (Recover)
H (chooses Hybrid)
Partitions numbers to be hybridized: 2 3 4
Y (Good for GRUB question)
N (part 2 boot flag)
N (part 3 boot flag)
Y (part 4 boot flag make NTFS bootable partition)
W (Write the new MBR)
Y    (Yes! write the new MBR)
Reboot
Here is a sample Q&A from The GPT Fdisk. Notice the highlighted Press Enter/Return.
Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N): Y
Creating entry for GPT partition #2 (MBR partition #2)
Enter an MBR hex code (default AF): Press Enter/Return
Set the bootable flag? (Y/N): N
Creating entry for GPT partition #3 (MBR partition #3)
Enter an MBR hex code (default AB): Press Enter/Return
Set the bootable flag? (Y/N): N
Creating entry for GPT partition #4 (MBR partition #4)
Enter an MBR hex code (default 07): Press Enter/Return
Set the bootable flag? (Y/N): Y
Test 1 - Does Bootcamp Volume show up in Finder?
Test 2 - Can you see files in Bootcamp Volume?
Test 3 - Can you select Bootcamp in System Preferences -> Startup Disk?
Test 4 - If Test 3 is successful, select Bootcamp and Click Restart.

Can no longer boot from DVD or USB HD since installing Win10

5/2/15
I download and installed the latest Win10 last week and popped it on a spare HD I have in the system;
the mistake I made was to leave my SSD which has Win7 on it connected during the install.
Now I’m in a bit of a pickle. When I boot up with the Win10 disk disconnected I get a splash screen that tells me:
A required device isn’t connected or can’t be accessed. It offers me an option to press F9 to boot to another OS and indeed it does boot me into Win7 but insists all my hard drives need a chkdsk. They are fine
So I thought I’d simply boot from a DVD or USN drive and “fix” the Win 7 install.
Lol , it won’t boot from a DVD or the USB HD. If I pull the Sata cable from the SSD containing Win7 it boots right up from either the DVD or the USB HD.
I’d really not like to do a clean install of Win7 on my SSD just to get around this.
When the drive I loaded Win10 is connected it still won’t boot from a DVD but does allow me to boot into 7 or 10.
Yeah, yeah I know I should have installed it in a VM but I didn’t. Any suggestions?
Mobo ASUSTeK Computer INC. P8P67 Rev 1.xx
12G Ram
CoreI5-25K
Win7 Ultimate on the SSD
Last weeks build of Win10 on a spare HD in the system

press Windows+R then in the box, msconfig
this will allow you to modify the boot settings as desired
this tool works as well to clean up programs that want to load with windows unnecessarily
Place your rig specifics into your signature like I have, makes it 100x easier!
Hardcore Games Legendary is the Only Way to Play!
Vegan Advocate How can you be an environmentalist and still eat meat?

Updated BIOS - Can no longer boot arch in any shape or form

So, I updated my BIOSrecently. After that, when I tried to boot into arch the boot screen says
'waiting 10 seconds for device /dev/sda6'
and eventually 'could not find root device'
which is when it drops me into a basic ramfs commandline.
I tried to boot with the fallback image with the same result and when I try to run the arch livecd it gives the same output (except it waits 30 seconds for /dev/archiso). I tried it with both an i686 image and a x86_64 one.
At first, I thought it was an issue with the BIOS update itself, but I can still boot just fine into vista and ubuntu. Nothing arch related seems to work now however.
Any idea as to what it is about arch that causes it to fail now and what I can do about it?

I looked into the BIOS settings and couldn't find any new features added or settings changed, so I don't think that's an option. No installed OS options either.
Id prefer not to have to downgrade my BIOS, since the problem is clearly arch related and should be possible to resolve via arch.
May be nothing, but when I log in out of X in Ubuntu I get this message I haven't noticed before:
Your CPU appears to be lacking expected security protections.
Please check your BIOS settings, or for information run:
/usr/bin/check-bios-nx --verbose
When I run this, I get:
This CPU is family 6, model 22 and has NX capabilities but is unable to use these protective features because the BIOS is configured to disable the capability. Please enable this in your BIOS. For more details see: https://wiki.ubuntu.com/Security/CPUFeatures.
I couldn't find any setting for this in my BIOS. On the Ubuntu page, the relevant information is:
Some BIOS manufacturers have released firmware updates for their BIOS to allow enabling NX (e.g. Lenovo IdeaPads) so make sure to install the latest BIOS if the NX option is missing.
Since I have a Lenovo 3000 n200 (type 0769) , but I this update didn't include it.
Again, I don't know if this is related at all, but if it is, I thought it might provide a clue to the solution.

Messed up bootloader, can no longer boot computer with CD in drive

I'm trying to dual boot Arch Linux and Windows 8.1, on a Lenovo Y580 that already has Windows on it. I went through the whole installation mostly following the Beginner's Guide, picked the Syslinux bootloader and tried to set it to chainload Windows, everything seemed to go smoothly. When I restarted the computer, it just skipped straight to Windows. I figured I must have messed up the bootloader so I put the live CD back in to try to fix it, but now nothing will boot while a CD is in the drive. It hangs at the Lenovo splash screen; I can't get to the boot menu, I can't get to the BIOS, I can't do anything. When I take the CD out and restart it boots into Windows.
Presumably I messed up setting the boot flag, or something? I have absolutely no idea how to diagnose this problem, I don't even know how to investigate it because I can't boot anything besides Windows. Please let me know if you need more information, I wasn't really sure what details would be relevant to this issue.

What is odd is that the system reacts to a CD being in the device (i.e. it doesn't boot Windows while it does if there is no CD in the device). This is why I think that the boot order is probably fine. Nevertheless, I don't see why it wouldn't boot the Arch CD. I could imaging some potential reasons none of which is either likely or common or easy to resolve.
(So for now, the interesting questions about that would be:
1. How did you get the Computer to boot from the Arch CD when you tried to install Arch? Did you just reboot with the CD in the drive or did you do anything specific with your Windows and/or BIOS first; if so, what?
2. If you put another CD (say, your favorite audio CD) into the drive, does it still hang at the Lenovo splash screen? Normal behavior would be that it just boots Windows.
3. Following henk's advise and checking the boot sequence in the BIOS, what exactly do you see, what is the exact boot sequence?)
burkaman wrote:Is there any other way to get to my stranded Arch installation
Sure. Just none that would be easier than from the Arch CD. You could for instance write the Arch ISO to a USB flash memory and boot from USB, like so: https://wiki.archlinux.org/index.php/US … In_Windows
If your problems booting from CD persist, this might be worth a try. (However, you will still have to make sure that your boot order lists USB before the hard drive.)
burkaman wrote:maybe change the boot flags some other way?
Sure. But it is
(1) overwhelmingly unlikely that your problem with Arch has anything to do with boot flags and
(2) without a deeper understanding of how partition tables are designed and how disk partitioning utilities work, you are much more likely to seriously damage your other (Windows) partition(s) than to fix your Arch Linux partition(s).
If you feel compelled to try nevertheless, have a look at wikipedia's list of disk partitioning software: https://en.wikipedia.org/wiki/List_of_d … g_software
One more thought on your Arch installation and its non-working bootloader: If you by any chance set the default boot option to Windows and the timeout to 0 the behavior you describe (booting Windows instead of showing the bootloader) would be the expected one. If not, the bootloader has not been installed to the harddisk since the bootsector is obviously still occupied by Windows' own bootloader. (Otherwise, there would be no way for Windows to boot.)
Last edited by gay (2014-06-02 15:47:18)

Windpad 110W Win 8.1 upgrade can no longer boot under AHCI

I recently upgraded my 110W to Win 8.1, but then discovered that it would not boot after the first reboot. As found in some forums, changing to IDE mode in BIOS allows it to boot, but performance is somewhat slower. I have tried chaning the storahci registries and restarting under AHCI (as suggested in numerous forums) but it didn't work. I think it is possibly related to some driver issue as there were issues when I tried to update to drivers newer than those on the MSI site (I now have the MSI drivers loaded). Any suggestion as to how that can be solved?
Also, shutdown and restart seems strange. The screen would go dark pretty quickly (as usual), but the power light on the side would stay on for about 2 minutes before it would reboot / shutdown. As suggested by some, I have turned off quick boot, but it is still the case.
Thanks.

It's possible that the driver isn't compatible for windows 8.1, so either you can try to find the driver for windows 8.1 or I would suggest to roll back to windows 8.

Can no longer boot from ANY OS disc on MBP

I recently purchased a 15" 2.16ghz Core Duo Macbook Pro. It came with the original 10.4.5 discs. The previous owner installed 10.6 on it using a retail disc, then upgraded to 10.6.6. I had planned on upgrading the original hard drive. However, I cannot get the laptop to boot from the original discs or my own retail 10.6 disc. I've tried a number of different approaches (booting from an external DVD, holding down "C", holding down "option", attempting to mount in on the desktop first, etc.). Either the machine hangs or it ejects the disc (when using the internal drive). Nothing seems to work. Both the internal drive and external drive have been tested and work fine. Is it possible that when upgrading to 10.6.6 a firmware upgrade was done that won't allow the machine to boot from a disc containing an earlier version? I don't know what else could be causing the issue. The laptop has not displayed any other issues. Thanks for any suggestions or explanations.

I don't know how much help I'll be to you. Seems to have a lot of posts lately about not being able to start up from the install disks.
I assume you can still boot up from the internal drive.
When you hold the option key to start, does the screen come up with the option to choose a startup disk and is your Install Disk in when you attempt this?
While booted up normally, does the Install Disk open up with the install OSX menu? If so, does going through the install menu reboot the computer from the CD automatically?
Even if there were a firmware upgrade, seems like you would be able to use the 10.6 Install Disk to boot from.

I can no longer boot up in osx after installing windows 7 with bootcamp

After installing windows 7 with boot camp I am no longer able to access my osx side, I do not receive an option when holding alt when turning on my MacBook

What options do you get? If you don't get any options then you may not be pressing and holding the option key long enough or you are pressing it too early or too late.

Can no longer boot to OS 9.2.2 on a Dual Processor Mirrored Door G4?

Similar Messages

Maybe you are looking for