New Install Won't boot after GRUB

I have been using ArchBang for the past year and a half so I finally thought that I knew enough about Linux to try installing a true Arch Linux system. 
I followed the beginner instructions carefully and was able to successfully install my system (or at least I thought) and GRUB.  I am currently running my system on a Dell inspiron with two separate hard drives.  The primary drive is the one I am trying to install Arch on while I have Windows 7 installed on the second drive.
The drive I installed Arch on is /dev/sde.  I think that I successfully installed GRUB given that when I boot my computer it goes into GRUB and shows both my Arch Linux install and my Windows 7 system and when I select Windows 7 in GRUB it successfully boots.
But when I selected my Arch install in GRUB the system does not boot.  It just shows:
/dev/sda1: clean, 31087/3751936 files, 478966/15000685 blocks
and then I am left with a blinking cursor and after a few minutes I get:
Welcome to emergency mode. Use "systemctl default" or ^D to enter default mode.
Give root password for maintance:
Anyone one how I fix this?  Do I need to reinstall?  As I said before I didn't receive any errors during the install and GRUB seems to be working correctly. Please remember that I am a newbie but please help!

Trilby wrote:
No you don't need to reinstall, you do need to fix your grub configuration though.  It sounds like it is not properly pointing to the root partition.
Post your grub config and your partitioning scheme.
Partition Scheme from lsblk output:
Name         MAJ:MIN        RM        SIZE        RO        TYPE        MOUNTPOINT
sda             8:0                  0           931G       0            disk       
  sda1         8:1                  0           57G         0            disk           /
  sda2         8:2                  0           7G           0            disk
  sda3         8:3                  0           866G       0            disk
sdb             8:16                0           111G        0            disk
  sdb 1        8:17                0           111G        0            disk
sr0             11:0                 1           1024M     0            disk
I don't now if this output of the partition table is what you want given that the lsblk is the only command I am familiar with.   The sdb disk is where the windows install is.
Here is the /boot/grub/grub.cfg file:
### 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}"
      saved_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='hd4,msdos1'
if [x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos1 --hint-efi=hd4,msdos1 --hint-baremetal=ahci4, msdos1 9fd0e01-89b1-494c-908f-e89db34d80e0
else
      search --no-floppy --fs-uuid --set=root 9fd0e01-89b1-494c-908f-e89db34d80e0
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 GNU/Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-9fd0e01-89b1-494c-908f-e89db34d80e0' {
        load_video
        set gfxpayload=keep
        insmod gzio
        insmod part_msdos
        insmod ext2
        set root='hd4,msdos1'
        if [ x$feature_platform_search_hint = xy ]; then
            search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos1 --hint-efi=hd4,msdos1 --hint-baremetal=ahci4, msdos1 9fd0e01-89b1-494c-908f-e89db34d80e0
        else
             search --no-floppy --fs-uuid --set=root 9fd0e01-89b1-494c-908f-e89db34d80e0
        fi
        echo 'Loading Linux core repo kernel ...'
        linux /boot/vmlinux-linux root=UUID=9fd0e01-89b1-494c-908f-e89db34d80e0 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_memtext86+ ###
### END /etc/grub.d/20_memtext86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows 7 (loader) (on /dev/sdf1)' --class windows --class os $menuentry_id_option 'osprober-chain-44F084A6F0849FB2' {
       insmod part_msdos
       insmod ntfs
       set root="hd5,msdos1'
       if [ x$feature_platform_search_hint = xy ]; then
           search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos1 --hint-efi=hd4,msdos1 --hint-baremetal=ahci4, msdos1 44F084A6F0849FB2
      else
           search --no-floppy --fs-uuid --set=root 44F084A6F0849FB2
      fi
      chainloader +1
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This files 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 ###
Last edited by johnnymike (2012-10-15 01:52:09)

Similar Messages

  • Mac Pro new update won't boot after 10.8.2 Update 1.0

    It just stays on the apple screen during boot after entering pw for account.
    Its been over 5 min that it just stays in that screen. Anyone else seeing this after doing 10.8.2 Supplemental Update 1.0?

    Reinstalling Lion/Mountain Lion Without Erasing the Drive
    Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
    Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
    When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.
    Reinstall Lion/Mountain Lion: Select Reinstall Lion/Mountain Lion and click on the Continue button.
    Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.

  • New Windows Server 2012 install won't boot after installing Hyper-V role.

    I have just installed Windows Server 2012 onto a Dell PowerEdge R310.  Everything worked okay until I installed the Hyper-V role.  After that, when it tries to boot, I get "Your PC ran into a problem and needs to restart. We're just collecting
    some error info, and then we'll restart for you. (0% complete)" for a split second, then the system reboots into Automatic Repair mode.
    In Automatic Repair mode, my options are Refresh your system (which tells me the drive that Windows is on is locked), Reset your system (which tells me there is no partition), and Automatically Fix your PC (which tells me it can't fix it).
    I have updated to the latest version of the BIOS (1.11.0, which Dell states adds Windows Server 2012 support).
    I'm at a loss.. I've tried everything I can think of.  Has anyone run into this issue and figured out a solution?  The only references I can find to this issue talk about Gigabyte motherboards with USB 3.0, but this server pre-dates USB 3.0 by
    quite a bit.

    Hi,
    Not only the BIOS but the iDRAC and storage part also need to ne up date check, have a look at the following list to see what you need for Server 2012:
    http://en.community.dell.com/techcenter/os-applications/w/wiki/3868.dell-bios-support-for-windows-server-2012.aspx
    If any info was collected during the error then have a look in the event viewer or look for a kernel/memory dump file so you can try to find the issue, in many cases a driver, anti-virus sofware or 3rd part service can cause these kind of issues.
    When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer
    MCSE:Server Infrastructure, MCSE:Desktop Infrastructure, MCSA Server 2012, Citrix CCIA & CCEE, Cisco CCNA, VMware VCP 3/4/5 Blog: http://www.citrix-guru.com and http://www.rds-support.eu Twitter: @dnyvandam

  • New Air won't boot after failed Migration

    New MacBook Air arrived this afternoon.
    First thing I did was run Software Update to apply the lates OS patches.
    Second thing I did was run Migration Assistant to transfer data from a Time Machine backup on an external USB disk. The old computer was small. Backup is only about 25GB. It is from a MacBook running Snow Leopard.
    After about half an hour of running, Migration Assistant reached the "less than a minute remaining" stage and hung there for more than an hour. Finally I quit it. My computer then became unresponsive. I had to hold down the power key and restart.
    Computer won't restart. Bong is heard, Apple appears, spinner appears, no progress after that. Unplugged the external disk, rebooted, same thing.
    I rebooted to the recovery partition and ran Disk Utility, did the integrity check and the permission repair on the main volume, no improvement.
    Finally I gave up and started the Reinstall Lion option. I'd read about this, figured it was something I might need someday, never imagined I'd be running it within hours of getting the computer. Display says I have 5 hours and 45 minutes to wait.
    What went wrong here? What should I do when it is done reinstalling? I'd like to have my old stuff back, but I don't want to kill my computer again.
    Frank

    For what it's worth, booting stops at the "Waiting for DSMOS" step.

  • New L440 won't boot after weird video problem

    My new Thinkpad L440 just stopped working at the worst imaginable time. I hope someone here will be able to help, though I suspect it may be irretrievably broken in some stupid fluke. Let me give you the details: Maybe five hours before this happened, I removed the battery since I don't lug my laptop around much anyway and wanted to preserve it. I used to do this with my Macbook too, and everything seemed fine, until I started watching this video while downloading some totally legal material in the background using a file-sharing application. The screen would go black, and the computer would be completely irresponsive until I started closing the lid, at which point it would resume functioning. When this first happened, I was able to log on and start working again; it happened again, and I fixed it in the same way. Maybe ten minutes later, the screen went black again and I could not get it to respond no matter what angle I bent the lid. I tried shutting it and opening it again, to no avail. I removed the power connection and reconnected it, to no avail except for the fact that there were two short flashes of the green light at the center of the power button. I re-inserted the battery and nothing changed. So what on earth do I do? I can't believe this is happening right now -- I have so many deadlines!
    In any event, it's a Thinkpad L440 bought maybe ten days ago. 64-bit Windows 8.1 (it came with Windows 7, but I installed 8.1 from the DVDs that came with it).
    My educated guess would be that it's either my bad luck (and possibly some overheating issue, though I certainly don't think what I was doing was outside of what you could expect a brand new laptop to cope with), or that removing the battery led some internal backup battery to discharge and now it won't start again until it has been recharged.
    Grateful for any suggestions.

    Hi Ews,
    I am sorry to hear that you are facing the issue with no POST, and I understand the frustration what you are going through. If the issue still persists after performing the provided troubleshooting, then it might be issue with the system hardware.
    I strongly suggest you to visit the nearby service center for further assistance on the issue.
    Click here to open a link where you can select the country and get the exact contact support number. I’m sure they will be a great help.
    Hope this helps!
    Best regards,
    Hemanth Kumar
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
    Follow @LenovoForums on Twitter!

  • [SOLVED] Fresh Install, won't boot past grub

    I did a fresh install of Arch (GPT partitioning table) with a 8 GB root directory, 138 GB home directory, 4 GB swap, and a 1007 KB bios boot partition. Everything went well, I got through the installation with no problems, but when I rebooted the computer. It showed this after the grub menu: https://lh6.googleusercontent.com/-UM-3 … 2014-06-22
    So now my question is, was I supposed to do anything extra during the installation process? Or is this a hardware problem? Linux Mint, Ubuntu, Lubuntu, and Zorin OS works fine so I'm assuming I need to do something extra during installation...
    Last edited by ryukiri (2014-07-03 21:44:44)

    Trilby wrote:
    ryukiri wrote:That only tells me how to make it a boot option...I assume I need to be chrooted from the install CD to do this.
    You can do it one of two ways: boot the install cd/usb, mount all the partitions as in the original installation process, then chroot.  From there you can just use pacman to install packages as it it were a normal system: `pacman -S linux-lts`.
    There is, however, no need for the chroot.  The alternative, and somewhat simpler, approach would be to boot the install media and mount the partitions as above, then use the pacstrap tool just like you did when installing the 'base' group: `pacstrap -i /mnt linux-lts`.
    I think it is safer to arch-chroot because you still need to be chrooted to generate your grub.cfg "grub-mkconfig -o /boot/grub/grub.cfg"
    Last edited by ugjka (2014-07-03 08:24:30)

  • 10.3 Server new install won't boot from Mirrored RAID - HELP!!

    Hi all,
    I had 10.3 Server running fine on a 450 MHz B&W G3 (home server use, nothing too demanding), when I decided to add a 2nd HD and run the server from a RAID mirror (both 80GB drives). I had problems enabling RAID on the boot drive with diskutil in Terminal, so I decided to rebuild the server. I didn't have much besides the system on it, so backing up data and re-installing isn't a big ordeal (or so I thought).
    No problems creating the mirror set once I re-formatted the drives. The install seemed to go fine (10.3.4 on install disk), but upon restart, I got the flashing system folder/question mark. When booting from the install disk, Disk Utility recognizes the RAID, and Startup Disk recognizes the mirror as a viable boot drive and allows me to select it and restart. Same problem, no system found.
    When I run diskutil info for the mirror, it lists the mirror volume as Not Bootable.
    I've checked the disks with both Disk Utility and DiskWarrior - all looks OK. I've reset PRAM and NVRAM, taken out added PCI cards, and disconnected all FW and USB devices (besides kbd and mouse).
    Unfortunately, B&W G3 can't boot from an external FW drive, so I'm stuck with booting from a CD/DVD for troubleshooting.
    My next step is to re-install on a single drive again and try to enable RAID and mirror, but I'd sure like to avoid that if I could.
    I've searched through this board and didn't really see this particular situation. Any of you smart server folks seen this before -- any ideas or suggestions??
    TIA,
    Brad
    B&W G3   Mac OS X (10.3.4)   450 MHz, 10.3 Server, 80GB RAID mirror

    if you backup your data from a NON-RAID Drive (Single drive), create a RAID array and then Restore from the backup you created... you will find you cannot boot from the drive.
    Apparently the sector or drive header information in a non-RAID drive is different than in a RAID array... so when you restore the backup data from the non-RAID drive to the new RAID Array; you effectively corrupt the RAID array not allowing it to be booted from.
    The solution is to create the RAID array and then re-install your system from scratch... copying over the data you want to keep from your initial backup one file at a time (don't do a complete system copy or you will once again, corrupt your new RAID install).
    I had the same problem and it took me a great deal of time to figure it out.
    Joe

  • New install won't boot

    I got a new laptop a couple of days ago and wanted to install Arch on it. Everything went fine until I tried booting it. I'm not sure where it gets stuck but I believe it's at the step where it waits for UDev uevents to be processed. Why I believe this is, is because that's also the point where it takes a fairly long while to get past when booting the install CD.
    I took some pictures and a video of my laptop trying to boot into Arch which you can find here: http://yuri.vm.madoka.be/arch/
    The first picture is where it gets stuck when booting normally, the next pictures are taken when booting from the CD.
    If anyone could help me it'd be greatly appreciated.

    JokerBoy wrote:adding nomodeset to the kernel boot line helps?
    That one worked. Before this I also tried blacklisting nouveau by booting System Rescue CD. On that CD I also noticed I couldn't boot into a graphical environment so is it nouveau not playing nicely with my hardware or my hardware acting up? (New laptop...)
    I also just tried installing the official NVidia driver and so far I have successfully started an X server which seems to work perfectly.
    So basically I'm just wondering if there's a way to get Nouveau working in case I need it. I'll be using the official drivers when using Arch but if I ever need a GUI on my System Rescue CD I'm pretty much f'ed at the moment...

  • Macbook pro won't boot after installing update 10.9.3

    macbook pro won't boot after installing update 10.9.3

    Please read this whole message before doing anything.
    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode.
    Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.
    Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
    The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    Test while in safe mode. Same problem?
    After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

  • MacBook Pro won't boot after trying to install 10.7.3 update. Start up stalls at Apple logo and spinning gear.

    MacBook Pro won't boot after trying to install 10.7.3 update. Start up stalls at Apple logo and spinning gear. Computer won't even start in safe mode.

    My daughter's MacBook Pro was doing exactly the same thing.  I don't know if it had anything to do with the latest update.  She called me about a week ago saying that her MacBook began running slower by the day .  She then called me Friday and told me that it wouldn't get past the gray screen and the gear just kept on spinning.  I did everything I could over the phone including Safe mode which it wouldn't go into and thought maybe it was the hard drive.  She took it to the Apple store.  Originally, they also thought it was the hard drive.  It ended up being a corrupted operating system (Lion).  Apple genius simply re-installed Lion and she's back up and running.  Good thing she backed up right before it crapped out.  She'll be restoring everything tonight.  Don't know if re-installing Lion will help your situation, but it did the trick for my daughter.

  • Computer won't boot after installing latest iTunes update

    Won't boot after the apple screen.  Turns black and disk stops  Help!  Was running Mavericks.

    Hi Neodoc,
    Welcome to the Apple Support Communities! I understand that your MacBook Pro will not boot past the Apple logo. There may be a few troubleshooting steps I would recommend for this situation. The following article outlines the steps to perform to get this resolved for you.
    Mac OS X: Gray screen appears during startup
    http://support.apple.com/kb/ts2570
    I hope this helps,   
    -Joe

  • My Mac Pro won't boot after installing the latest update

    Im running the latest OSX on my mac and recenty did a small updated that i believe contain a few security thing and bug fixs but when restarting the machine after the update it would not boot again after the apple logo has appeard apple script is displayed on the screen contain what i think is boot script failing to run. I have been able to boot the system in safe mode. does anyone have and solution for this as i realy don't want to reinstall the OS
    Thanks

    The most common cause for "Won't boot after software Update" is Directory Damage that existed before the Update, but was made worse by adding files during the Update.
    The most common cure for that Directory Damage problem is to boot in Safe Mode, which takes five minutes to repair the disk, then comes up demanding your username and password, even if you normally auto-login.
    Rarely, third-party add-ons are made obsolete by an update. In this case, booting in Safe Mode (with few Apple extensions and NO third-party extensions loaded) works fine, even if normal mode does not work.
    Have you tried normal mode again after your Safe Boot?

  • [SOLVED] Arch won't boot after I created a separate /var parition

    Arch won't boot after I created a separate /var parition on an existing installation.And let me confess: it was maybe stupid trying to do it on an existing install.
    I edited the fstab correctly, copied the files using rsync preserving permissions. Then I kept a backup of /var using tar. Then went on to delete everything under /var, ie /var/*, the /var folder is still there. All this I did from a live CD. After that I booted into my arch linux. Here I get messages about systemd successfully finishing fsck on each of my partitions, then the screen starts blinking. And there is no more output. Pressing Ctrl+Alt+Delete causes systemd to stop its services and reboot.
    Having realized I had borked my system, I removed the /var line from fstab and restored /var from the tar file I made earlier. Again I did this from a live cd. Rebooted into my arch system, and again similar issues, namely that after fsck and messages informing a few services had started, the screen keeps blinking.
    The live cd I used for reorganizing my partitions was elementary OS freya. They have GParted in there. I also have an arch install iso lying aroung from May 2013. If necessary, I can download the latest version. I am currently typing from a Windows installation I dual boot from.
    I don't know how to extract any boot logs as I am locked out of the system. Here is my fstab in any case:
    # Filesystem information
    # /dev/sda5 LABEL=fs_root
    UUID=b9d739cf-fd8c-46dd-a919-bd827dc47c66 / ext4 rw,noatime,data=ordered 0 1
    # /dev/sda9 LABEL=fs_var
    UUID=ec0f7a49-dccd-43ab-8651-9aa3fdb41cc7 /var ext4 rw,noatime,data=ordered 0 2
    # /dev/sda2 LABEL=fs_boot
    UUID=0e8ab31a-3bda-4b85-a901-a36f21b1583d /boot ext2 rw,noatime 0 2
    # /dev/sda6 LABEL=fs_home
    UUID=d9e63c47-274e-447f-ad01-0d97afe0fd34 /home ext4 rw,noatime,data=ordered 0 2
    # /dev/sda7 LABEL=fs_swap
    UUID=7301227c-e9f3-41b8-9d0f-4cf3c159491c none swap defaults 0 0
    # /dev/sda3 LABEL=fs_win
    UUID=12B639D1B639B5D7 /fs_win ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,nofail,noauto,x-systemd.automount 0 0
    # /dev/sda3 LABEL=fs_share
    UUID=D272269772268079 /fs_share ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,noauto,nofail,x-systemd.automount 0 0
    I would greatly appreciate any help.
    Last edited by richcocoa (2015-05-03 18:04:44)

    Have you moved everything from /var to /new_var (i named it for learning purpose)? You shoud copy content from /var but not on the fly but booting from arch iso cd, and than you shoud mount your / into arch-chroot environement, mount all of your mount points and than copy content from default /var to new /var. The copying should be done with this
    cp -rax
    and you can add -v switch to verbose output. I have my own /var moved the same way.
    The simples way is:
    -boot the arch iso cd
    -mount all of your mount point (i created here in this step /new_var to move /var to a new place, and this /new_var i put in /etc/fstab as /var later)
    -copy /var to /new_var with -rax or -vrax (recursive, archive, this filesystem or verbose, recursive, archive, this filesystem switches)
    -umount all of it
    -reboot.
    Last edited by firekage (2015-05-02 07:49:20)

  • Mac mini won't boot after RAM upgrade.

    Tried installing new RAM in my Mac Mini, 512MB stock to 2GB of Crucial. Followed the directions to a T, grounded myself the whole time.
    Things I've tried so far:
    1. Resetting the PRAM, no luck.
    2. Holding option at start-up, shows no icon.
    3. Holding shift, no luck.
    4. Holding X, nothing.
    How do I get it to accept a CD if it won't boot?

    Welcome to Apple Discussions!
    You clearly have a problem, but you don't describe exactly what that is other than that your mini won't boot after the upgrade. What happens when it starts up? Does it attempt to start and hang up on the grey or blue screens, or does it start beeping at you almost immediately after you try and start it up, and also flash the power light?
    If the former, then you may have dislodged a connector while working inside the system, in which case opening it up and checking that everything is firmly connected would be the first thing to do. If the latter, then the beeping/light flashing is the system telling you it has failed the power-on self test and the pattern of beeps/lights indicates why. In your case likely the system can't find workable memory. In that instance, opening the system and ensuring that the RAM is firmly and fully seated would be a good step, and if the mini continues to fail, then replacing the new RAM with the original to test that the system will then start.
    It is not likely that anything had damaged your MacOS install in the process of upgrading, thus normally no reason to need to boot to CD as a result of a RAM issue.

  • Mac Mini won't boot after update

    I have a Mac Mini that won't boot after the most recent software update. Since the Mini has only a bluetooth keyboard and mouse, a number of the usual options (hold down shift, etc.) won't work. I've tried a reset, also no luck. At the moment, I can't locate my Tiger install CD either.
    When holding the power button on during boot, I get a series of flashes from the status light on the front (a set of very rapid flashes, followed by a slower set, followed by a slow set) but no startup chime, or fan, or video. My display and power source are both known-good (work fine with my Powerbook)
    Any suggestions, other than buying a hardwired keyboard/mouse?

    Welcome to Apple Discussions!
    The 'newer version of OS X" error occurs because the installer on the DVD you have booted to has by default been set to update the version of MacOS on the hard drive, which of course it can't do because the version of MacOS it is installing is newer. The only way to install in this situation is to select a different option. However, that isn't what you want to do at this point, because as it says, you'll loose your data if you do an 'erase and install'.
    Instead, you should see menus at the top of the screen when it's booted to that install disk. Click the Utilities menu, select Disk Utility, and then click the top entry for the internal hard drive on the left. Once done, click on the 'Repair Disk' button (not Repair Permissions). This will test the drive to make sure it's OK. If it reports errors, and then reports 'error or exit' with the drive not repaired, you will either need a 3rd party application such as Alsoft's Disk Warrior, or to perform an erase and install (which of course you don't want to do at this point because your data is not backed up).
    If the Repair Disk process completes with no errors, next select Repair Permissions, and let that process complete, then reboot the system as normal to see if you can now access the drive.

Maybe you are looking for