B&W G3 No Longer Boots into OS 9

I consider myself a pretty savvy Mac guy, but this one has me stumped...
At work, I use a B&W G3/350 with 1 GB of RAM and two hard drives - one with OS 9.2.2 installed on the original HD, and a 40 GB internal drive with OSX 10.3.9 installed. I've used it for the past year for editing video and creating graphics in OS 9 (the only OS the editing software will work in), while using OSX for networking, Safari, etc. It has given me very little trouble, until this morning.
While working in Photoshop 5.5 and After Effects 3 in OS 9, a message appeared that my hard drive needed to be repaired. I saved my work and restarted the B&W. Just as the "Welcome to Mac OS 9.2" splash screen appeared, a system error "bomb" message came up: "System Error 102 - Restart with Extensions Off and Try Again."
Tried to reboot with shift key down - got the same bome and error message. Tried to start up with Norton SystemWorks, then my OS 9 disk - STILL got the bomb. Bybassed the OS 9 drive, and was finally able to boot up in OSX. Erased the OS 9 drive and reinstalled the system software from OSX - STILL won't boot in OS 9!
Unless I disconnect the original drive, now if I try to start in OS 9, the dreaded folder with the flashing question mark appears, followed by a folder with the finder icon for about a minute; then the flashing question mark reappears, then the finder icon, etc.
I've had this happen with failing drives before, but I could always boot from a System Disk or a Norton's CD. But this one's got me stumped. It simply will no longer recognize OS 9 for startup. Anyone have any suggestions?
Thanks,
Highway Zero
B&W G3/350 MHz/1GB/6 GB + 40 GB Mac OS 9.2.x also OSX 10,3,9
B&W G3 350MHz/1GB/6 GB + 40 GB   Mac OS 9.2.x   also OSX 10.3.9

Oh, how I wish it got as far as loading extensions... It would first only go as far as the "Welcome..." splash sreen, then would give me the "bomb". No extensions have the time to load. I even get the "bomb" when I try to restart with Extensions Off.
That's the thing that's got me stumped. It won't boot from an OS 9 startup disk at all! It doesn't seem to want to recognize OS 9. I've had hard drives go bad before, and have always been able to start from a OS CD or Norton disk using the "c" key. I still get the flashing ?/Finder icon. The disk will show up on the desktop in OSX, so I don't think it's the optical drive.
Oh, and here's the kicker - the lone screw that holds the HD tray in the case is stripped. I can't even physically take the drive out to test it! (Grrr!)
Sorry that these explanations are so long. But this problem's had me buzy all day.
iBook G4, PM8500/G3, Mac Classic, IIcx, LCIII, PM7200 Mac OS X (10.3.9)

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

  • 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

  • A late 2007 Mac Pro (2,1) no longer boots into 64-bit Snow Leopard

    In Snow Leopard 10.6.7, my late 2007 Mac Pro (2,1/3.0 GHz/Dual Quad-Core Intel Xeon) no longer seems to be booting into 64-bit mode. I've tried holding down the 6 and 4 keys during startup and even used a Terminal sudo command to force the machine to always boot into 64-bit mode. No matter what I try, an About This Mac>More Info>Software check only reports the following:
         64-bit Kernel and Extensions: No
    Before I upgraded  from Leopard 10.5 to Snow Leopard 10.6, I carefully researched this, and this Mac Pro model specifically was listed by Apple as being capable of 64-bit booting — meaning that it would utilize at least some extra memory. At the time, under OS 10.5 and early versions of 10.6, when I used this Terminal command...
         ioreg -l -p IODeviceTree | grep firmware-abi
    ...my Mac Pro 2,1 returned this response:
         "firmware-abi" = <"EFI64">
    As a result of my tests and research, I upgraded the installed SDRAM from 4MB to the theoretical maximum Apple indicated this model could support (16MB) so that Adobe Photoshop 12 (CS 5) would fully utilize extra installed memory under Snow Leopard. While using the first versions of 10.6 Snow Leopard, the machine worked fine in 64-bit mode. Now, in the wake of the 10.6.6 or the 10.6.7 update (I didn't notice which), I find that this model no longer even reports itself as being 64-bit capable, though it once did.
    Now, the aforementioned Terminal query returns this response:
          "firmware-abi" = <"EFI32">
    Also, the Library>Preferences folder does even not contain a file called "com.apple.boot.plist," which some owners have reported editing to force 64-bit booting.
    The thing is, I spent a fair amount of money upgrading this machine to the maximum amount of SDRAM supported. I purchased it because it was advertised as being 64-bit capable and I upgraded it because Apple originally reported it as being a 64-bit model. Now, I'm not sure if the extra memory I added is being fully utilized, though Photoshop does report seeing 15547MB of available memory.
    Have any other owners of these second-generation Intel Mac Pro's encountered this? Does anyone know what's going on? Am I doing something wrong when checking for the 64-bit installation or architecture? Is Snow Leopard 10.6.7 mis-reporting the architecture for this model? Or did Apple silently withdraw 64-bit support for this machine in a recent OS update?

    Hatter: Thanks for the feedback and links. Well, as described in one of the threads you linked to, the document below reinforces your assertion that only Mac Pro's 3,1 or later (early 2008) support 64-bit booting in Snow Leopard:
    http://support.apple.com/kb/HT3770
    However, if you asked me in court, I would swear on a stack of Bibles that sometime in the past, I read an Apple document indicating that the Mac Pro 2,1 supported 64-bit booting and I really thought I recalled booting this particular machine into 64-bit mode under early versions of Snow Leopard.
    I guess I'm mistaken. Certainly, this issue can be confusing. When I read them out loud to myself, even perfectly-written, accurate explanations on the subject can sound like a circular, non-sensical George Bush rationalization being delivered by comic Will Ferrell. I must not be correctly recalling the details of booting into 64-bit mode with this machine. And I guess that since Photoshop has its own memory management scheme, and I only have 16 gigabytes of SDRAM installed anyway, it doesn't matter that much. Furthermore, in one of your links, Jason Snell of Macworld writes:
    "...If you’re running a Mac powered by an Intel Core 2 Duo processor or an Intel Xeon processor, your Mac is 64-bit capable. And Snow Leopard runs 64-bit-capable applications in 64-bit mode regardless of whether it’s booting into a 64-bit or 32-bit kernel. In fact, the only big advantage of booting into a 64-bit kernel would be the ability to use more than 32 gigabytes of RAM..."

  • MBP no longer boots into Mac OS 10.9 Mavericks

    After installing Mavericks on launch day and using it successfully for the past few days, my MBP stopped shutting down - system would freeze. I would have to turn it off by holding down the power switch.
    I booted into Recovery mode to Repair Disk - process aborted with error saying it cannot be completed and I must reinstall Mac OS.
    Now each time I boot I get a grey Apple screen with a progress bar...when the progress bar completes, the MBP turns itself off.
    Does anyone have instructions for how I can return to using Mountain Lion / 10.8.5 until Apple has resolved all its technical issues with Mavericks?

    My two cents-- I'm a fan of Red Giant and have a bunch of their products but Universe has been a dud in my opinion.  Didn't upgrade to the premium version but kept it installed just to kick the tires and it's been a total headache.  Finally uninstalled it.
    May not be Red Giant's issue per se, but for whatever reason all my Adobe stuff runs better without it.

  • IMAC will no longer boot into Windows 7 with Boot camp

    I can see the partition on the Mac destop and can access it.
    The windows options is available when I hold down the option key when booting but the computer appears to just hang.
    I have been unable to get the Imac to boot off the Windows 7 dvd or a repair disk.  I just get a white screen.
    I could sure use some help trying to get the computer to boot back in Windows.
    Thanks in advance.

    Oddly enough I turned off the computer for a bit and turned it back on and it boot right into windows.......
    I did have my Samsung phone plugged into the usb hub.....I wonder if that was causing some issues...weird.

  • 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.

  • During an update my Mac turned off and will no longer boot into the user interface.

    The situation is that I don't have an os disk with me - traveling abroad - and would like to be able to create one using my PC.
    - First is this possible?
    - Second, will I lose my personal data upon system reinstall!
    As far as the boot sequence goes is the apple logo and the spinning wheel...
    Just thought of this, is there a "last good bootup" option available as an option or some other way to recover without reinstalling?
    The situation was that I have a bad battery and the chord was accidentally unplugged... Pretty bummed at this point... :(
    Thank you in advance!

    So far I have tried to use the option, and a few other keys on startup, but no-go...
    I found a snow leopard install .dmg file download on the apple site, since my MacBook is from 2005, but only have a PC to create the disk image from - if that will even work at all...
    Will keep updating as I move forward... Any help is appreciated!

  • Z77A-GD65 no longer boots with 4 RAM modules

    I had 4 x 8GB Cosair Vengeance LP that used to work fine, but no longer boots into Windows with 4 but only with 2 RAM modules.  Any help in solving the issue would be appreciated. ( I need 32 GB as I run many virtual machines )
    The 4 modules worked fine for few months until couple weeks ago,  when I saw issues with booting into Windows 7. The workaround was to "warm up" by leaving the PC in BIOS for about 5 minutes and it would boot fine.  Since couple days ago, it would POST but not boot into Windows or into live Linux on USB, so I started troubleshooting with bare bones first ( MB, CPU, 1 RAM, PS ) and then starting adding more and more components until I found that  1 and 2 RAM modules worked in either black or blue rail but with 4 RAM modules, it will POST, but not boot at all into either USB based live system or into Windows 7.
    Memtest with 2 separate sets of modules pass with flying colors. Mixing the sets work fine too, but add 2nd set (i.e. 4 modules) and it fails to boot.  I am leaning more toward believing the issue is with the MB than with the RAM since mixing them doesn't throw any memory error.
    Any suggestion on how to check if it's the RAM or MB ?

    Quote from: PirateDog on 25-November-13, 00:23:30
    If these were 2 kits mixed, ...
    These were 2 mixed kits.
    Quote from: XFM on 25-November-13, 07:01:42
    What voltage is the RAM running? A slight bump up in voltage might help.
    As to voltage, I started with standard 1.5 and then incrementally upped it to 1.65v. At 1.6v and above, it does boot into Windows, but intermittently goes into BSOD... Works perfect with 1.5v with 2 RAM modules.
    I'll save the money for next build instead of going for 32GB kit.  ... guess I'll live with 16GB for now. 
    Thank you all for the advice.

  • 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.

  • Is it possible to bypass the number of partitions limitation (no more than 2) when trying to boot into windows by not using boot camp assistant, and instead just partitioning the drive manually?

    I can't find a specific answer to this question.
    I did have a functioning Windows 8 installation on my MacBook Pro previously. I tried to make a third exFAT partition so as to have a drive mutually readable/writable to both operating systems. This made it so I could no longer boot into my Windows installation.
    I know I'll need the boot camp drivers installed on the Windows installation after the fact, but would manually creating a partition and installing the OS without Boot Camp Assistant work? And would I be able to boot from it while having a total of 3 partitions?

    That's the spirit! 
    Just be sure to have your OS X junk safe in a tested backup, in case the whole thing craps out and you end up having to do a low-level partition and erase of the entire drive.
    And like I said, the problem is not OS X. I've set up mine at least once with 4 partitions holding as many flavors of OS X as can run on the hardware, all perfectly bootable on demand.

  • Keyboard and mouse no longer work when booting into Rhapsody

    I still have a bootable partition with the last release of Rhapsody (aka Mac OS X Server) on my Power Mac G4 but it's been a while (years!) since I actually booted it up. The G4 also has bootable partitions with Mac OS X 10.2, 10.3 and 10.4 (and is in daily use running 10.4.11).
    I used to boot into Rhapsody occasionally, mostly for interest's sake, occasionally to test Unix software on legacy systems; I haven't tried to do so since installing 10.4 until now.
    When I booted up from the Rhapsody partition today, all went well -- the system started up fine, and the login screen appeared -- but the keyboard and mouse no longer work. I even got out the original keyboard and mouse that came with the G4, with no luck.
    I assume that recent firmware updates have bypassed support for Rhapsody. I guess I'm not surprised -- it was a developer-only release, after all. But has anyone a solution?

    Adding to the above: I also tried plugging in an Microsoft USB keyboard at the point when Windows freezes at the Windows log-in screen. The keyboard is not recognized and the only way I can leave this screen is to power-off the computer.

  • No longer able to boot into OSX

    My Mac Mini will only boot to Windows XP (I realise this situation is not without some degree of irony).
    Bootcamp has been installed for several months and I have had no problems booting between OSX and XP. I have not booted into XP recently only OSX and there have been no problems.
    Today I booted up from a shutdown and found that my Mac Mini booted into XP. I wasn't too worried so went into the Boot Camp control panel and selected "Restart in OSX". As Windows was shutting down, I noticed that it was installing several updates. My Mac Mini proceeded to boot back into XP and continued to install the remaining components of whatever updates it had previously been installing.
    So I repeated the Boot Camp control panel drill several times...each time, despite selecting to restart in OSX, it would restart in XP.
    I then tried holding down the Option key and was duly presented with the two partitions - "Hard Drive" or "Windows"...I selected Hard Drive (i.e. OSX)...and the system booted into Windows! Repeated this exercise but this time trying the second partition (i.e. Windows)...and the system booted into Windows (as you would expect).
    I have not done anything to the partitions/hard drive in recent months...the only thing I can think of is that I may have installed some Mac OSX updates earlier today...
    Any assistance to help me boot back into OSX would be appreciated (I realise my worst case scenario is a reinstall).
    Thanks
    Darren

    Thanks Stefan.
    I followed your instructions which did detect some errors in both the disk and permissins which I have repaired. I then reran the verify to check that there were no more errors. Following that I selected the Mac OSX startup volume and initiated a restart...it still boots into Windows!
    Understanding how to use the repair features of the OSX DVD was useful but unfortunately I am still looking for a solution.
    As a last effort, I tried rebooting while holding down the 'X' key...this did produce an onscreen log for a split second...from what I can make out in the short time it is onscreen...it appears to be trying to load the mac kernel and there is an error message saying "Read file failed: status"
    Any further ideas would be appreciated.
    Thanks
    Darren

  • New partition & windows no longer boots

    Hey all, up until now i have had 3 partitions on my drive - Snow leopard, General media and Windows 7. I decided to add a linux partition and made a new partition using disk utility. I boot up to the choose disk screen to install ubuntu to find that windows is no longer an option for boot up, so i deleted the new partition and it still won't boot into windows anymore.
    How can i restore the booting function? Doing it with a linux partition too would be preferable but it isn't necessary.
    Thanks,
    Brad

    Hi Brad and welcome to Discussions,
    Hi John,
    A later done partitioning to add additional partitions to a harddisk alters the position of the BootCamp partition in the partition table so that the Windows Bootloader can not 'find' the Windows partition.
    With Windows XP it helped to simply edit the Boot.Ini file and point it to the WIndows partition.
    With Vista and Windows 7 there no longer is a boot.ini but EasyBCD http://neosmart.net/dl.php?id=1 can do the same.
    One thing to remember though is, that even Vista and Windows 7 'suffer' from the limitation of four partitions on one harddisk immenent to the Master Boot Record (MBR) since Apples EFI/GPT/MBR emulation can not handle Extended Partitions and Logical Partitions inside an Extended Partition.
    Regards
    Stefan

  • SATA drive no longer boots

    The PC was running fine for about two weeks with a single 160GB SATA drive.
    One morning, with no hardware changes, the PC refused to boot. A blue screen of death flashed very quickly past as the PC rebooted. Windows suggested safe mode, and when I booted into safe mode the PC stopped loading drivers immediately after mup.sys. I've had this problem before with mup.sys on other PCs (I believe the real problem is the ACPI driver loaded immediately after mup.sys). In any case the solution is usually to remove any hardware or, in the worst case, re-install XP.
    Running windows XP setup from CD it will no longer re-install onto the SATA hard drive. Even the recovery console will not work, claiming there is a problem with the drive. I know that the drive is not dead, because it gets as far as trying to install the ACPI driver.
    Install a ATA HDD, installing XP on to it. Ran SP1 and all the updates. The ATA HDD worked OK until I plugged in the SATA HDD, which caused the new version of XP to hang at the mup.sys driver again.  Disabled the SATA controller, and then everything works again. Ran all the updates for the motherboard and BIOS but that did not help. Switched SATA cables but did not help. Tried the SATA RAID controller but that did not make any difference. Variously tried disabling everything I could in the BIOS setup but that made no difference.
    Now, I know that my no-name RAM might be a bit dodgy, and the PSU a little wimpy, but the PC works fine as long as the SATA HDD is either disabled or not plugged in. It actually ran perfectly for two weeks, and I was surprised how cool the CPU runs.
    I looks like the next step is to try another SATA HDD, then PSU, then motherboard, but is there anything else which might help my situation before I go out and buy those items?

    Well, it turns out it was the SATA HDD, and it seems to be repaired.
    The method was to boot Windows XP from another HDD into safe mode and repair the drive. Windows would not boot from the SATA HDD at all, nor run in safe mode. When booted from the other HDD Windows would not access the SATA HDD normally, but would for some reason in safe mode. There must be a difference between the SATA drivers used in safe mode vs regular mode.
    CheckDisk found many cross linked files and fixed them (took about an hour) and now the SATA HDD looks like it is working.
    How did the file system get damaged? Good question, since I have never seen NTFS get messed up like this. In any case I'm probably going to replace the HDD in case it was the controller.

Maybe you are looking for

  • Performance(statspack) related problem

    Anybodyu can suggest me how to improve the database performance as many uiser are complaining that they are getting data very slow........ i have also used statspack analyzer....... STATSPACK report for DB Name DB Id Instance Inst Num Release Cluster

  • Error while installing Oracle 10g r2 on Centos

    Hi, when i run ./runInstaller -silent -responseFile /home/oracle/standard.rsp it exit with the following error.Any idea of what can be? Thanks,Riccardo [oracle@Oracle02 ~]$ database/runInstaller -silent -responseFile /home/oracle/standard.rsp Startin

  • Cannot select Technical Usage "Learning Solution - ABAP only" on ECC Server

    Dear Gurus,         My environment are         a SAP ERP System(ABAP only) in SMSY with                Product Version = "SAP ERP 6.0"                Main Instance = "SAP ECC Server" (as Relevant)                        Note When I select another Rel

  • Creating IRs from digital sources...READ THIS ;-)

    THE BEST WAY TO CREATE AN IMPULSE RESPONSE: This technique ONLY works if your staying in the digital domain...... eg: IRing a Lexi 960 or similar that is hooked up over spdif / etc... or (WAVES, Altiverb libraries This Technique WILL NOT yield result

  • Restoring my iPhone after backing it up

    Hi, I have backup up everything to the iCloud and resotred my phone, I saved all my apps to the cloud but after my iPhone 4S being restored only 2 apps reinstalled. I can see things on the cloud still all my apps and things but there not installed on