Can't boot anything after deleting C partition in order to install Windows 8.1

I have a ASUS X55VD notebook, wich had a Windows 7 64-bit (and a dual booted Ubuntu, but with Windows bootloader). Yesterday I tried to install a Windows 8.1, so I inserted a disc and restarted.
The window to manually select the partition, on wich it will be installed, came up so I formated C partition where Windows 7 was installed. It did not allow me to install to that partition because, a new format (GPT) had to be used. So i chose to delete the
partition. Deleting was quite long, after wich the computer restated, and after that it only showed black screen.
The Windows DVD is still spinning, but nothing shows. Can't acces the BIOS (none of the keys work).
Tried:
- Hardware reset (battery out>hold power button fro 10-20 sec>put battery inside>start) - No change
- Put a Live Linux DVD to boot from it - No change
- Put a hirens boot cd - No change
- USB boot - No change
- Connect a external keyboard and tried accessing BIOS - Nothing happened
I would suffice with just gettng some of my data from him, and sending him to repair Can't tinker with harware, or it will void my varrancy
Please help. The problem is really urgent.

Hi,
It seems a hardware issue, you can first try to reset the CMOS - remove the cell battery from the motherboard for at least half hour, re-insert it, boot up. The BIOS settings should be reset to defaults. But for better solution, I
 suggest you contact the manufacture.
Regards,
Yolanda
Yolanda
TechNet Community Support

Similar Messages

  • Can't boot anything after attempting to Bootcamp

    Hi,
    I have an Intel Macbook Pro (can't think what year off the top of my head right now) running Snow Leopard and I attempted to Bootcamp with a standard Windows XP disk a few hours ago. A few minutes before the attempt I finished reformatting and reinstalling Snow Leopard, as I'd been having disk utility problems. I set the partition for 50GB (of 200GB) in the Bootcamp Utility, but when it restarted, I was presented with only a single partition to choose from, which was 130GB. I couldn't see the 50GB, so decided to exit. After exiting the MBP attempted to load the disk again, but failed. From then on I can't load any operating system (not that I expect I could load XP), and it boots to a black screen with a flashing cursor in the top left corner. I can't load the original Snow Leopard install disk, or any disk, and I also can't boot into safe mode. When I use the alt/option key boot, I'm faced with a semi-large grey lock with a password field.
    If anyone needs more info, I'll try find it.
    Thanks,
    chunks01

    Hi and welcome to Discussions,
    the single partition of 130GB phenomenon usually indicates that you used a Windows XP CD that does not match the requirements of BootCamp.
    Usually a XP CD which is not at SP2 (Service Pack 2) level, but a prior one.
    To make yourself an XP SP2 (or SP3) install CD you can use these instructions http://www.winsupersite.com/xp/sp3_slipstream.asp
    As for your second but foremost problem, have a look here http://support.apple.com/kb/TS1978
    Hope it helps
    Stefan

  • [Solved] Can't boot arch after merge linux partition

    Before this i have issue with my partition table, but i can fix it with testdisk.
    After that, i merge all my linux partition into one. I mean like this
    Before i merge my linux partition:
    / >> /dev/sda3
    /var >> /dev/sda4
    swapfile >> /dev/sda6
    /home >> /dev/sda7
    My new partition
    / >> /dev/sda3
    swapfile >> /dev/sda6
    i can't boot my arch after i backup and moved my home and var directory to /dev/sda3 with livecd.
    How to fix this issue?
    Last edited by nizar (2009-03-28 04:18:29)

    Solved by myself! LOL
    I edit and remove /dev/sda4 and /dev/sda7 in my /etc/fstab file with livecd.
    Now, arch boot without /dev/sda4 and /dev/sda7

  • Slow reboot after deleting bootcamp partition

    Hello,
    I was just told by a tech store that my bootcamp partition was slowing down my computer incredibly. I no longer need this partition so I went into Disk Utility, clicked the partition, and deleted it. I also had my RAM updated from 4GB to 8GB. I have an Early 2011 Macbook Pro, operating on Yosemite.
    The only question I have is, when I rebooted my computer for the first time after deleting the partition, the restarting process took much longer than normal. Without the bootcamp startup, I figured the startup time would be less, when in reality, it was longer. Is there something I missed while deleting my partition, and is there a way to fix this and speed up the reboot time? If not, will this slow reboot be a one time issue?
    Any comments would be appreciated!
    Thanks,
    Rachel

    There is a hidden Recovery HD between the OS X and the deleted BC partition, which you can verify using
    sudo gpt -vv -r show /dev/disk0
    in OSX Terminal.
    BCA does a better job by also relocating the Recovery HD appropriately and giving you a contiguous partition.
    The only other method is to subsume Recovery HD in OS X partition and then re-install OS X which will rebuild Recovery HD. This does not modify any of you files, but just the OS.
    You will also need to clean the Hybrid MBR which is now dangling and inappropriate for your case.

  • [SOLVED]Can't boot Arch after installation-grub use wrong uuid in bios

    Hello I would like to ask for Your help and say hello. I'm new here.
    I have one big problem with Arch. Can't boot it after base installation. The same problem with Arch, that was mentioned in this topic:
    https://bbs.archlinux.org/viewtopic.php … 7#p1294597
    I have the same problem and the same error:
    No such Device: ad4103fa-d940-47ca-8506-301d8071d467.
    Loading Linux core repo kernel ...
    error: no such partition.
    Loading initial ramdisk ...
    error: you need to load the kernel first.
    Press any key to continue..._
    I'm new here, and with Arch, could you explain me how to fix it? I tried the solution given in the link above, several times but with each time i have errors and warnings from the post 1 in mentioned topic. I installed my Arch from usb thumb drive. Maybe this is something to do with it? Also, my hard drive that Arch is installed on is being connected to a "raid card" named Adaptec, but during installation my disk is being found so i think that drivers is present and works ok, so it is not related to this, also there is no raid present, i use it only as a mean to connect to motherboard because there is not enough sata port, and because:
    https://bugs.archlinux.org/task/35626
    he wrote that this error is also on virtualbox, so it is not my fault and Adaptec related issue.
    I haven't tried this yet:
    Sotanaht,
    I had the exact same problem as you, but I was able to fix it by replacing the bad grub.cfg file with the grub.conf file found in the same directory. If you try this do not forget to back up your original file (just in-case smile)
    because i don't know much about it, don't want to destroy data on my hard disks or to destroy my other distros (i use Ubuntu with derrativates such as Mint, Kubntu, Lubuntu, Xubuntu, and Slackware 13.37 and 14.00).
    If you could explain it in details i would be really happy.
    I could post something about my setup, please write what. My computer is:
    -AMD X4 PII 955 runinng at 3.2GHz
    -4GB DDR2 runinng at base clock (800 if i remember correctly)
    -about 7 hard drive disk connected to a sata ports, one adaptec drive that i mentioned above and one dvd-rom
    -nvidia GTX260
    -850W PSU Chieftec
    Last edited by firekage (2013-07-02 08:11:29)

    Yes, of course. I did it several times with
    grub-mkconfig -o /boot/grub/grub.cfg
    and the result is always the same - Error posted above.
    Here is my grub.cfg file:
    # DO NOT EDIT THIS FILE
    # It is automatically generated by grub-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    ### BEGIN /etc/grub.d/00_header ###
    insmod part_gpt
    insmod part_msdos
    if [ -s $prefix/grubenv ]; then
    load_env
    fi
    set default="0"
    if [ x"${feature_menuentry_id}" = xy ]; then
    menuentry_id_option="--id"
    else
    menuentry_id_option=""
    fi
    export menuentry_id_option
    if [ "${prev_saved_entry}" ]; then
    set saved_entry="${prev_saved_entry}"
    save_env saved_entry
    set prev_saved_entry=
    save_env prev_saved_entry
    set boot_once=true
    fi
    function savedefault {
    if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
    fi
    function load_video {
    if [ x$feature_all_video_module = xy ]; then
    insmod all_video
    else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
    fi
    if [ x$feature_default_font_path = xy ] ; then
    font=unicode
    else
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos5'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 ad4103fa-d940-47ca-8506-301d8071d467
    else
    search --no-floppy --fs-uuid --set=root ad4103fa-d940-47ca-8506-301d8071d467
    fi
    font="/usr/share/grub/unicode.pf2"
    fi
    if loadfont $font ; then
    set gfxmode=auto
    load_video
    insmod gfxterm
    set locale_dir=$prefix/locale
    set lang=en_US
    insmod gettext
    fi
    terminal_input console
    terminal_output gfxterm
    set timeout=5
    ### END /etc/grub.d/00_header ###
    ### BEGIN /etc/grub.d/10_linux ###
    menuentry 'Arch Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-ad4103fa-d940-47ca-8506-301d8071d467' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos5'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 ad4103fa-d940-47ca-8506-301d8071d467
    else
    search --no-floppy --fs-uuid --set=root ad4103fa-d940-47ca-8506-301d8071d467
    fi
    echo 'Loading Linux core repo kernel ...'
    linux /boot/vmlinuz-linux root=UUID=ad4103fa-d940-47ca-8506-301d8071d467 ro quiet
    echo 'Loading initial ramdisk ...'
    initrd /boot/initramfs-linux.img
    menuentry 'Arch Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-ad4103fa-d940-47ca-8506-301d8071d467' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos5'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 ad4103fa-d940-47ca-8506-301d8071d467
    else
    search --no-floppy --fs-uuid --set=root ad4103fa-d940-47ca-8506-301d8071d467
    fi
    echo 'Loading Linux core repo kernel ...'
    linux /boot/vmlinuz-linux root=UUID=ad4103fa-d940-47ca-8506-301d8071d467 ro quiet
    echo 'Loading initial ramdisk ...'
    initrd /boot/initramfs-linux-fallback.img
    ### END /etc/grub.d/10_linux ###
    ### BEGIN /etc/grub.d/20_linux_xen ###
    ### END /etc/grub.d/20_linux_xen ###
    ### BEGIN /etc/grub.d/20_memtest86+ ###
    ### END /etc/grub.d/20_memtest86+ ###
    ### BEGIN /etc/grub.d/30_os-prober ###
    ### END /etc/grub.d/30_os-prober ###
    ### BEGIN /etc/grub.d/40_custom ###
    # This file provides an easy way to add custom menu entries. Simply type the
    # menu entries you want to add after this comment. Be careful not to change
    # the 'exec tail' line above.
    ### END /etc/grub.d/40_custom ###
    ### BEGIN /etc/grub.d/41_custom ###
    if [ -f ${config_directory}/custom.cfg ]; then
    source ${config_directory}/custom.cfg
    elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
    source $prefix/custom.cfg;
    fi
    ### END /etc/grub.d/41_custom ###
    It is wrong, the root partition is different than in this, we can see that this grub leads to wrong root partition, i posted my root partition at the bottom from /etc/fstab. I don't know how to fix it - i'm not familiar with the dos names (hd 0,5 and so on).
    Here is my /etc/fstab:
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/sdb2
    UUID=59603166-5d8a-4aaf-81f7-5a822fd630e5 / ext4 rw,relatime,data=ordered 0 1
    # /dev/sdb1
    UUID=20028674-d7e8-4bf4-8551-64f133641962 none swap defaults 0 0
    (END)
    Last edited by firekage (2013-07-01 06:26:59)

  • I want to triple boot Have Snow Leopard and XP on separate drives and I want Windows 7 on another drive, can it be done by temporarily removing the xp drive and installing windows 7 on another internal drive?

    I want to triple boot my Mac Pro I have Snow Leopard and XP on separate drives (osx on drive 1, xp on drive 2) and I want Windows 7 on another drive (drive 4, drive 3 is used by osx for storage), can it be done by temporarily removing the xp drive and installing windows 7 on drive 4?
    I realise bootcamp only allows 2 operating systems and refit could change the size of my current xp drive to accomodate W7, that is not an option here for various reasons one being the drive is pretty much at capacity with only about 30gig free (I work with video so that free space fluctautes quite a bit). I have a brand new drive 4 with 1TB set aside ready for W7 but I'm unsure how to go ahead?
    any help or advice would be really appreciated, thanks

    Boot Camp is used to support Windows on the same drive.
    You can have a different OS on every drive.
    You could have Windows 7, Vista, and XP all on one drive if you so choose.
    I recommend not putting Windows and OS X on the same dirve when talking about Mac Pro - unless you just need something small and lite.
    Remove all your other drives while you install Windows 7.
    You could even relocate XP - if you need it even - or recover the hard drive space.
    You should always keep 30% free for Mac OS; same for data/media drives.
    Considering 1.5TB WD Black $110.... and you want OS X to be on a fast high performance drive as well.

  • HT3986 This what my boot camp says , when ever i am trying to instal windows 7 ''There is no USB drive connected to the system. Please insert a USB drive to continue.    "' Can someone help me . ?

    This what my boot camp says , when ever i am trying to instal windows 7 ''There is no USB drive connected to the system. Please insert a USB drive to continue.

    pump

  • According to the apple website I need to upgrade Boot camp 3.0 to at least 3.1 in order to install Windows 7 on my iMac currently running Snow Leopard. I download the 3.1 version but it is only a text file and there doesn't appear to be any way to upgrade

    In order to install Windows 7 on my iMac I need to upgrade bootcamp to at least 3.1  I currently have 3.0.4 After downloading from the website there is no way to install it - it is just a text file? What should I do?

    You have to start with 3.0, which is on the OSX disc that came wih your Mac.

  • I purchased my first iMac n I installed parallel how can I transfer my pc document? Do I need to install window 7?, I purchased my first iMac n I installed parallel how can I transfer my pc document? Do I need to install window 7?

    I purchased my first iMac n I installed parallel how can I transfer my pc document? Do I need to install window 7?, I purchased my first iMac n I installed parallel how can I transfer my pc document? Do I need to install window 7?

    Your post is very confusing. It sounds like you want to run Windows 7 using Parallel's software. If so yes you need a full license of Windows 7 and will need to purchase it. Please follow the instructions in the manual you got when you bough Parallel's and if you have difficulty following them you can find support for their product on the Parallel's forums at:
    http://forum.parallels.com/forum53.html
    Roger

  • Repairing Boot Camp after deleting partition

    Hello,
    During the bootcamp installation by mistake I erased the macintosh HD partition, but before continuing the installation of windows I stopped the process.
    Using a bootable live cd I saw that all the partitions are still there. I changed the boot options and managed to see the mac HD partition on the boot screen (when pressing alt).
    After booting I could see all the information on mu mac and the present partitions information is like these:
    Andres-MacBook-Pro:~ arlourenco$ sudo gpt -r -vv show disk0
    Password:
    gpt show: disk0: mediasize=750156374016; sectorsize=512; blocks=1465149168
    gpt show: disk0: Suspicious MBR at sector 0
    gpt show: disk0: Pri GPT at sector 1
    gpt show: disk0: Sec GPT at sector 1465149167
           start        size  index  contents
               0           1         MBR
               1           1         Pri GPT header
               2          32         Pri GPT table
              34           6        
              40      409600      1  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
          409640  1385344952      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
      1385754592     1269536      3  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
      1387024128         256        
      1387024384    78123008      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
      1465147392        1743        
      1465149135          32         Sec GPT table
      1465149167           1         Sec GPT header
    Andres-MacBook-Pro:~ arlourenco$ sudo fdisk /dev/disk0
    Disk: /dev/disk0          geometry: 91201/255/63 [1465149168 sectors]
    Signature: 0xAA55
             Starting       Ending
    #: id  cyl  hd sec -  cyl  hd sec [     start -       size]
    1: EE    0   0   1 - 1023 254  63 [         1 -         39] <Unknown ID>
    2: 0B 1023 254  63 - 1023 254  63 [        40 -     409600] Win95 FAT-32
    *3: AF 1023 254  63 - 1023 254  63 [    409640 - 1385344952] HFS+       
    4: AF 1023 254  63 - 1023 254  63 [1385754592 -    1269536] HFS+
    I tried to re-run  Boot Camp Assist again, but it gives me the following error:
    The startup disk must be formatted as a single Mac OS Extended (Journaled) volume or already partitioned by Boot Camp Assistant for installing Windows.
    Can you help me to fix the problem?
    Andre

    Everything was fine... Issue started when I tried to increasec the size of my bootcamp partition (from 100gb to 200gb).
    I did the following:
    1. I decreased my mac hd by 100gb using disk utility
    2. Then I loaded bootcamp and used the "mini partition wizard" to increase the size of the partition by 100gb (unallocated space I free on mac hd)
    3. I rebooted and everything went poof!!!!!! (Just for bootcamp)
    Then, since bootcamp was not staring I found the solution you posted at the beginning:
    ·         sudo fdisk -e /dev/disk0
    p
    setpid 4
    07
    flag 4
    p
    write
    y
    After this os x was still fine but windows was jus getting stuck at boot (black screen with blinking cursor)
    Then I decided to do the following:
    ·         sudo fdisk -e /dev/disk0
    p
    setpid 1
    07
    flag 1
    p
    write
    y
    After this everything brok! Mac HD disapeared and windows was showing "missing os"

  • Can't boot up into OS X after attempting to partition the hard drive from Windows

    I recently installed Windows 7 on a partition of the hard drive in my iMac. In an attempt to make the Windows partition bigger I did something to the OS X partition and now I do not recieve the option to start up in OS X when I hold option down on the boot up screen. Is there any way I can fix this? I checked the hard drive and ~300mb (the size of the OS X partition) is still being used but I can't access it.

    Your question seems to be a MS Windows question. If you use Boot Camp then post there. If you use Parallels or another virtualtization app to run Windows please post in those forums. Most users on this forum don't use Windows, some do but most do not.
    Best of luck.

  • Error 0x80070057 After Deleting Bitlocker Partitions

    I'm in the process of configuring OSD through SCCM 2012 R2 U1 and am having issues getting the task sequence to format the drive again after the drive was encrypted with BitLocker.
    I've read on multiple sites that Windows is able to install right over a BitLocker'd drive through PE without needing to disable BL through windows first if the partitions are gone. As such, I've setup the following to run in diskpart prior to the Partition
    Disk 0 - BIOS step:
    select disk 0
    select partition 1
    delete partition override
    select partition 2
    delete partition override
    exit
    This works, however the Partition Disk 0 - BIOS step fails at formatting C: with
    Error 0x80070057 The parameter is incorrect. 
    It formats the system reserved partition just fine, but leaves the remainder of the drive as "raw" and usually unreadable by diskpart which requires me to boot to gparted to delete the partitions on the drive to do anything with it again.
    I've:
    verified SCCM boundaries
    tried assigning a variable to save the drive letter to
    disabled quick format
    disabled all Bitlocker steps
    disabled the diskpart steps I added
    format the drives prior to the task sequence with:
    Select Disk 0
    Clean
    Create Partition Primary Size=350
    Active
    Format FS=NTFS Label="System Reserved" Quick Override
    Assign Letter=S
    Create Partition Primary
    Format FS=NTFS Label=OS Quick Override
    Assign Letter=C
    Nothing will get the SCCM task sequence past this. This happens for both Windows 7 and 8.1 task sequences.
    What's interesting is, if I load up the Windows 7 media via flash drive and install through that, Windows installs without issue. I've then been able to bitlocker the drive and unencrypt it as expected. Attempting to run the task sequence after this results
    in the same error.
    My question is, what is different between the default windows installer and the windows install through SCCM when it comes to partitioning the drive and how do I get the SCCM task sequence to match the default Windows install process so this will install?

    I've tried with that and numerous other labels and it still fails.
    If I've gotten Win7 / 8 installed through the default media, it seems like the drive can be partitioned correctly and working fine. When the "Partition Disk 0 - BIOS" task runs, SCCM doesn't give me the ability to specify the exact diskpart commands; it
    sorts that out on its own. The diskpart commands above were my troubleshooting steps. SCCM wipes them away once the Task Sequence runs.
    There's something that SCCM doesn't like about drives that have been bitlocker'd and not properly unencryped through the OS prior to wiping the drive. 
    Does the default Windows 7/8 media run different diskpart commands during install than SCCM would run for install? One works - the other doesn't.
    Below are the settings that are configured for this step - which I believe are default for an auto generated task sequence.

  • Can't Boot Up After Software Update -- Advice Appreciated.

    Hi all,
    I've experienced what seems to be a relatively common problem -- after installing the latest Tiger software update, my machine can't boot up. If I try to log in, it just freezes on the blue background screen. Holding 'shift' to enter Safe Mode just makes the computer shut down. I've tried the advice from Apple listed here:
    http://support.apple.com/kb/TS1417
    I just got a variety of messages, all of which say effectively the same thing: 'Macintosh HD cannot be repaired.'
    What can I do from here, bearing in mind I don't have an install disk. Is there anything I can do without it?
    If I were to borrow a friend's Install Disk (they have Leopard), could I delete everything on my computer and re-install Leopard, and have it work? Or will the problems with my iMac carry over to a new installation?
    (I suspected something was wrong the morning before my iMac was able to boot -- I was getting 'page in/page out' errors when I tried to extract .rar files, or move large files to an external HD, so thankfully I took the chance to make back-ups of everything).
    Any hints or ideas would be unbelievably appreciated -- I'd hate to have to buy a new iMac (for the expense, not because I don't want a new one).

    You can erase everything and start over, but you should Zero the Disk first, but also you need an Install Disc, you can buy Sno/10.6 online, for Leo/10.5 you have to call Apple, who may also supply you with a replacement disk for the original if you have your Serial# handy.
    For other sources of Tiger/10.4, See Tom's, (Texas Mac Man), great info on where/how to find/get Tiger...
    http://discussions.apple.com/thread.jspa?messageID=9755670&#9755670
    You might try this a few times to see if you can fix your Disk...
    Tough without a Tiger Disk, but try fsck...
    To use fsck, you must run it from the command line. Unlike using your mouse to open an application to do something, you'll need to type a text command at the prompt (#) to tell fsck what to do. The Terminal application (/Applications/Utilities) and single-user mode are two examples of command-line interfaces in which you can type such commands. To use fsck:
    1. Start up your computer in single-user mode to reach the command line. Hold CMD+s keys down at bootup.
Note: If necessary, perform a forced restart as described in the Emergency Troubleshooting Handbook that came with your computer. On desktop computers, you can do this by pressing the reset/interrupt button (if there is one) or holding down the power button for several seconds. On portable computers, simultaneously press the Command-Control-power keys. If your portable computer doesn't restart with this method, you may need to reset the Power Manager.
    2. At the command-line prompt, type /sbin/fsck -fy
    (space between fsck and -fy important)
    3. Press Return. fsck will go through five "phases" and then return information about your disk's use and fragmentation. Once it finishes, it'll display this message if no issue is found:
** The volume (nameofvolume) appears to be OK 
If fsck found issues and has altered, repaired, or fixed anything, it will display this message:
*** FILE SYSTEM WAS MODIFIED *** 

Important: If this message appears, repeat the fsck command you typed in step 2 until fsck tells you that your volume appears to be OK (first-pass repairs may uncover additional issues, so this is a normal thing to do).
    4. When fsck reports that your volume is OK, type reboot at the prompt and then press Return.
    http://docs.info.apple.com/article.html?artnum=106214

  • Lost Windows 7 boot option after creating new partition

    First of all im new to Mac os.
    i have installed windows 7 using boot camp and after it i tried to create a new partition from the main mac partition and it was created successfullly however now the windows 7 boot option is not available for some reason.
    how can i have this option back?

    You broke it by adding the extra partition, remove Boot Camp (read the directions as to how) and start again. Do not add partitions next time.
    Do not use Disk Utility to remove the Boot Camp Partition, use it to remove any extra partitions.
    Backup your machine now.

  • Can't boot up after installing 10.4.10 + security update

    I got the automatic update yesterday (5/26) and installed the system & security updates onto my G5 as usual. Got the box that says to either shut down or restart. I clicked restart, and now all my computer will do is get to the blue screen that says loading OSX and then it stays on that forever. I've disconnected all peripherals, reset the pram -- no luck. Then I booted up from the disk tools CD and ran the permissions/repairs, but on all of them it stops about 3/4 of the way through the process and won't go any further. Out of desperation I even tried to do an archive/install and it wouldn't complete. My computer was working fine before this. Any suggestions would be MOST appreciated.
    G5   Mac OS X (10.4.10)  

    To emdh & the others:
    If you hard drive has certain kinds of problems, they will be exacerbated by the updates (any updates, not just these). This can lead to an inability to restart.
    These problems can be revealed by running Disk Utility's "Verify Disk" test (not the same as permissions repair). If that test shows any problems, you must restart from another disk with the OS & Disk Utility on it to repair them -- drives must be unmounted for this kind of repair to be made. Typically, people use the installer disk that came with their Mac for this.
    Obviously, if your computer will not restart from an already damaged drive, you will have to restart from another one to perform the test or repair.
    If the repair fails, you can try a more powerful disk repair utility like DiskWarrior, but some problems are too severe for any repair to succeed. In this case you must erase & reformat the drive, then reinstall the OS from scratch from your Tiger installer disk.
    Since some disk problems are caused by failing hardware, it is a good idea to run the Verify Disk test again at this point. If your internal drive supports S.M.A.R.T. self-monitoring (& most do), you can check its status at the bottom of the Disk Utility window as another confirmation of your drive's health.
    Assuming everything appears to be working correctly, you are now ready to perform any desired updates. Download a fresh copy of the Combo updater for your model (PPC or Intel) that takes you to the desired version number.
    It is important not to install any third party software until this is done: anything that alters the basic operation of the OS can & usually will interfere with the update process, & since developers do not always make it evident their software does this (or sometimes claim incorrectly that it will have no effect), it is best to play it safe & avoid all of it until you can establish that the updated OS is working correctly. Add your third party stuff a little at a time, checking for proper operation after each addition. If you encounter any problems, consult the software's documentation for the best way to remove it, do so, & contact its maker to see if they have a later, compatible version.
    Some users feel it is important to verify permissions before & after each install. I do not, but it can't hurt anything so do so if it makes you feel better.
    There are other causes for updates to fail, but file system problems are among the most common, so the Verify Disk check is a good place to start.
    Good luck!

Maybe you are looking for