[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)

Similar Messages

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)

Cisco UCS C220 MS SFF won't boot past BIOS screen with 2x1.2TB SAS drives installed

We have been running a few of these servers with only a 500GB 6GB SATA 7.2K drive installed with all VM's (Hyper-V) sitting on an attached SAN.
For various reasons we needed some local storage on the server and installed 2 1.2TB SAS drives (10K 2.5"). They hot installed okay but the server had to be brought down to enter the MegaRaid software to configure the RAID.
Unfortunately with the drives installed, the server won't boot past the initial BIOS screen and certainly doesn't get to the RAID screens.
Does anybody have any idea why this would happen? Is there some BIOS update required to support these drives and/or MegaRaid software upgrade?
The servers are up and running at the moment so I can't find the version of the RAID software running.
Thanks
Larry

Hi Lauren,
If you don't have a PCI or a mezzanine based controller and you are using the embedded raid controller you need a chip for the embedded raid controller to support SAS drives. By default the embedded controller only supports SATA drives. See page 9 of the link below
Please let me know if you are not using the embedded controller
http://www.cisco.com/c/dam/en/us/products/collateral/servers-unified-computing/ucs-c-series-rack-servers/C220M3_SFF_SpecSheet.pdf

HP8540w (540M) ram upgrade, won't boot past bios

I have recently acquired new RAM. First it was 2 x 8 gb but I found out later this is not supported by my specific model.
But now I switched it with 2 x 4gb PC12800 CL11, from a newer hp model and it still won't boot past the BIOS, which has been upgraded to the latest version.
The Bios recognizes the RAM perfectly but still it won't boot into windows. When I see the windows 8.1 logo it gives a sudden shutdown which is followed by a restart. In theory the pc12800 should work, albeit clocked down to 10600 to match the motherboard & processor.
It feels inadequate to have a 3 year old laptop which is not able to go past the 4gb, especially because I bought it since it was the elitebook version and military graded. I wanted to have something future proof, not a machine that needs to be replaced after 3 years. It feels like just threw 150 dollars out of the window.
So I'm hoping that there's another solution that I might have overlooked.
This question was solved.
View Solution.

Well the recommended memory is PC3-10600 aka DDR3-1333. On some models it actually downclocks to DDR3-1066 speed. I think the memory you have installed from a newer model is just not compatible. If it is DDR3-1600 it might even be low voltage memory which is almost certain not to work.

PowerBook G4 won't boot past blue screen

I've read a couple of posts with similar problems. The jist is, I did a security update/restart earlier and now my laptop won't boot past the blue screen after the white screen with the gray apple. I think I'm on Mac OS 10.4.11 but I had it on auto-update so that could be incorrect.
I've booted from the install disk and run a diagnostic from the First Aid bit in the Disk Utility. It says that there are no errors found and the S.M.A.R.T. status says "verified" as well. It won't let me boot into Safe Mode (although, I could be doing that wrong as I'm not exactly clear on how to do it - pressing S doesn't seem to do anything, but if I press Command + S it takes me to a text listy thing and I've run the "fsck -f" system check (which seems like the same as the disk utility check?) from there and also gotten the "volume is ok" message. There was also a suggestion to run some kind of diagnostic after booting with the D key from the install disk, but I was never able to get the disk to boot from the D key, only the C key.
I'm sure that this is kind of the "same song, different verse," kind of post, but I've not read about volumes registering as okay. I'm a little wary of a archive-and-reinstall as I've not ever done that before (so, if that's the suggestion you have, I would really appreciate loads of specifics on how that works so I don't mess up!)
I've read in several instances suspicion of a hard drive problem but I've not had any slow downs or any crashing. I did travel to the UK for about 10 days, but I didn't even change the time zone on my laptop while there, so I don't think that's it (but I suppose it could be.)
Lastly, I did recently replace my keyboard. A few keys had become non-responsive so I replaced it and have had the new keyboard for a bit over a month.
Suggestions? Ideas? Sorry if it's a repeat post -- just felt like the circumstance was a teensy bit different. And also, thanks very much for any info you can give.

Linsey:
If you can boot your computer into Firewire Target Disk Mode and you have access to a second Mac that supports firewire, you may be able to back up items that have not been backed up previously.
If you are able to back everything up successfully, and you have tested your backup to be sure it is sound, then we can proceed with re-installation of the OS. The best option is to completely reformat and erase the HDD and then install the OS from disk. (I will post complete step by step directions). This will enable you to start with a clean slate/HDD. Your other option would be to use the Archive and Install option. Think it over and let me know how you want to proceed.
cornelius

G4 won't boot past grey apple screen

Hi. I have been having the same issues with my G4 15". I'm frustrated. The whole thing started with stalling during applications. So I decided to reinstall my OS X 10.5. After reinstall, I copied my saved files from my "My Book" drive back to my hard drive. Stalling issues returned. I reinstalled again. still had some stalling issues, so I performed disk utilities. I repaired permissions. SMART status is verified. System still ran extremely slow. So, I followed directions on apple support for resetting the PRAM and NVRAM. After I did this, the computer won't boot past the grey apple screen. I have reset the PRAM and the NVRAM again. Still nothing. I rebooted up from OS install disk. I performed disk utilities repairing permissions and repairing HD. I did this for both my drive and the computers drive. I choose restart and again the grey apple screen. I have been trying to get this thing going for a week now. I'm near tears. Cornelius or anyone, can you help me? It says no errors are found, SMART is verified. But I can't get the computer to boot unless it is from the CD. Is the computer confused on where to boot from? Or is it shot? HELP ME PLEASE, before I play frisbee with my dear beloved mac!!!! It seems like this ALL started happening after I installed the update 10.5.8. I had ZERO problem prior to any software updates!!!

There have been report of some external drives/enclosures that do not work as a boot device. Not sure if the MyBook is in that category or not, just make sure that there is nothing else plugged into the Powerbook then try again.
Does the WD need its own power to be plugged into an AC power source? Try the other firewire port
I have one more question for ya... You were able to load OSX on this EHD using the OSX install disk in the Powerbook? And the installer saw the EHD with no problems?
If non of the above works try booting while holding down the x-key, this should force it to look for an OSX volume, not sure if it works the same on an EHD but worth a shot.

10.4.11 Server won't boot past hfs mount

Any ideas how to repair an OS X Server 10.4.11 system that won't boot past the gray Apple logo/spinning bars? Verbose mode stalls after the line "hfs mount: enabling extended security on <startup volume name>"
The machine will boot from the OS X Server install DVD (10.4.7 Universal). Disk Utility permissions and repair indicate no problems with the startup volume.
If I am unable to resolve the problem with the existing system, what is the best method for re-installing the server OS without having to manually re-construct the network configuration, accounts and permissions? I have a configuration settings file and a relatively recent Open Directory Archive disk image.

I have been unable to find any way to get past the boot stall, so I re-installed OS X Server 10.4 and restored from my Open Directory archive. Had to recreate shares.
Any tips on what plists or other System components should be cleaned out to try recovering from boot problems like this were there is nothing wrong with the disk and you can't boot into single user mode?

My iMac won't boot past grey screen and it didn't come with a os x disk

My iMac won't boot past grey screen with apple. I've tried booting in safemode but that didn't help and my iMac didn't come with a os x disk.

Take each of these steps that you haven't already tried. Stop when the problem is resolved.
Step 1
The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.”
b. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
c. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Step 2
If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use either of the techniques in Steps 1b and 1c to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
Step 3
Sometimes a startup failure can be resolved by resetting the NVRAM.
Step 4
If you use a wireless keyboard, trackpad, or mouse, replace or recharge the batteries. The battery level shown in the Bluetooth menu item may not be accurate.
Step 5
If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
Step 6
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
Step 7
If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
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. Post for further instructions.
Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 10. If you ever have another problem with the drive, replace it immediately.
If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 8
Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
Step 9
Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 10
Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
Step 11
This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
Step 12
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

IBook G4 suddenly won't boot past the "booting OSX" screen.

My iBook G4 suddenly died and now won't boot past the "Starting OSX" screen. The blue bar goes all the way across but never moves to the next screen. I have my original disks, containing OS 10.4.5. I am trying to boot from the disk, but just keep getting the Installer program. When I try to choose a startup disk, it still won't start. Any help or ideas? This is urgent.
BTW, I am a photographer and was workig in PhotoShop7 -- a program I use all day, every day.

Start from the install disc again and choose Disk Utility from the menu. Highlight the drive on the left and click Repair Disk. If it reports errors and repairs made, repeat the process until no errors are reported.
John

Macbook won't boot past main apple screen

I was using my computer this morning (13" black Macbook that I've had since December) and it was working fine until I closed it to go get something to eat.
When I got back and opened the lid again, the screen was black, as if it was off, but I could make out the outline of the Apple logo in the centre. So I turned it off, gave it some time and turned it back on. Now it won't boot past the main Apple screen, where the little timer thing spins and spins and spins while apparently nothing else happens.
I left it alone for a couple of hours, thinking maybe it was overheated, but that didn't make a difference. I tried taking the battery out and restarting it, but that didn't work either. I called Apple, but my parents opted for Future Shop's warranty instead of Applecare, so they told me to search the website as "the issue is well-documented," since I have no tech support with them.
I've searched around to see where this is posted or if it's been answered a billion times before, but it's 35C in here, and my rage/frustration are ruining my ability to be rational, haha.
Anyone experienced this before / is there a resolution that doesn't involve me being without my computer (which is like sweet, sweet crack to me) for an undisclosed amount of time?
Thanks in advance,
Emy
Oh, and I'm not sure about the operating system version beyond that it's OSX and I regularly install whatever updates they tell me to.

Maybe Disk Utility can repair the disk this way:
-Search your installation DVD's.
-Insert the disc 1 and sthut down your Mac
-Start your Mac again while holding down the C key
-Now your Mac should boot from the CD, this can take some time.
-After a while you will see a installation screen where you can chose a language.
-Chose English and continue.
-Then click some time's next and agree with the "Software Agreement".
-Open Disk Utility. Top menu bar --> Utilities --> Open Disk Utility.
-Select your hard disk in the list of disks and volumes on the left side
-Go to the First Aid (tab somewhere on the right).
-Click the button to verify the permissions.
-Then Click the button to repair the permissions.
-Click the button to verify the disk.
-Then Click the button to repair the disk.
-Exit the Disk Utility

Reset PMU and Powerbook won't boot past the blue screen with "Mac OSX" box

Hi-
Problem: I tried to reset my PMU, and now when my computer restarts it won't go past the blue screen with the "Mac OSX" logo in the box (and progress bar, that never fills up). I then also tried to reset PRAM, but it still won't boot properly.
Backstory--
I've had my 12-inch Powerbook G4 for about 3.5 years already, so things are starting to get a bit out of whack. I replaced my battery about 3 months ago, which has been great, but recently my power-cord has been wonky (having to unplug it and replug it in to make sure it actually charges the computer, the light flickers on and off, etc). Today it actually started producing SPARKS at the place where the thin white wire meets the white plastic power brick, so I decided it was time to get a new one. Brought it home, plugged it in, and since it seemed like the battery indication icon on the menu bar was all out of sync with the powercord colored-light, I tried restarting it a few times, but still the same. Then, I decided to reset the PMU, which may have been a huge mistake. And now it won't boot past the blue screen... Any advice? I'm going to try restarting it in "safe" mode, but I'd be so grateful for any recommendations. Hope I haven't done something irreversibly stupid with the PMU reset.
Thanks,
Samantha

Hello all,
Thanks for all of your great suggestions and info-- here are a few responses.
1) The disk I just borrowed from my friend appears to be the full retail version-- it looks just like the links that Ali B sent, and is in a large box saying "Mac OSX Tiger, version 10.4"... will this be the proper disk to do an Erase and Install? The only other disks I have came with my Powerbook when it was originally purchased, when it came Panther (I think, 10.3?). Would I use both sets of these disks to do erase and install? Or only the Tiger OSX disks?
2) I get the sense that Disk Warrior or Tech Tool might be necessary, but does it make sense to TRY to do erase-install before buying them? Also, are there any downloadable (for pay) versions of this, or would I need to track down the actual physical disks in Hong Kong or wait for them to be shipped?
3) I haven't yet tried the S.M.A.R.T. test, should I do that first? What is the procedure? Are there any results or ways to know if the drive is too far gone (so that I might instead replace the internal hard-drive) instead of pay 100 USD first to do the disk repair?
4) Cornelius said: "An alternative would be to completely reformat and erase the entire HDD, then re-install and restore your data from backup. If your backup is in the form of a bootable clone of the entire HDD, you can just clone it back." I use Super-Duper to back-up and the most recent one copied the whole thing-- what would be the later procedure of "cloning it back"?
5) As I'm able to use my computer pretty normally right now, but does it still mean that it might crash/die at any moment? Is there any way to tell?
Thanks so much!

IPod Nano Won't Boot Past Apple Logo...

Sup all?
...Got an interesting problem here. Replaced an LCD in a Nano for a friend, installation went smooth & without problems (or so I thought). After installation was complete, I put the Nano back together & started loadin' & playin music on the Nano. About 2 days later, I decided to update it w/the new iPod Updater (can't remember the date). Now the iPod Nano won't boot past the Apple Logo. I can tell that the "menu" has been loaded 'cuz you can hear the clickin' sound when you operate the wheel.
I've tried reformatting the iPod Nano (quick & full) & then trying to restore it, but it won't boot past the logo (after successful restoration?). Now I'm going to run the battery dead & then try to restore it again.
Any suggestions/comments on this?

The solution I see in your case is to go back and download an older iPod Updater.
See this link -> iPod Updaters
I suggest taking either the January 2006 iPod Updater, or March 2006 iPod Updater.
IMHO, Some of these freezing issues occur because of a fault in the latest iPod Updater.
I suggest going back to March (or January), and the nano could possibly work again for you.
-Kylene
If any post helps or solves your issue, please mark it that way accordingly. Thank you for helping the boards!

Powermac G4 (OS 10.4.11) won't boot past grey apple

1- My PowerMac G4 (running OS 10.4.11) won't boot past the grey screen with the apple. Any suggestions?

I found somewhere else how to hold down the mouse on starting, which opened the tray. I was able to startup with the disk, holding down the C and get to the Disk Utility window. Tried repairing the disk, but got this message:
Fist Aid failed:
Disk Utility stopped verifying "Macintosh HD" because the following error was encountered:
The underlying task reported failure on exit. <OK>
and in the info window it says,
"Verifying volume "Macintosh HD"
Checking HFS Plus volume.
Catalog file entry not found for extent
The volume needs to be repaired.
Volume check failed.
Error: The underlying task reported failure on exit (-9972)
1 volume checked
0 HFS volumes verified
1 volume failed verification
Sounds pretty ominous! Of course, the recommendation is that I backup everything , but how can I if I can't get to the desktop to back it up? (It hasn't had a lot of use for sometime, but is available as a film scanning station, and so that I can access scanned images on my iMac. I doubt that there is a whole lot on the drive that isn't backed up, but I would prefer to back it up for sure!)
Thank you again.

My MacBook won't boot past the grey screen.. help!

Today I was having a problem with Safari. For some reason, it kept restarting. This annoyed me, so I restarted my MacBook. Unfortunately, it won't boot past the grey screen, with the thing spinning in the middle. I've been into disk utility and it says my HDD is fine. I restarted from this, and yet it still won't boot. Can anyone suggest what's wrong/what to do?
Thanks in advance

Retrieving data using Target Disk Mode:
1) Shut down both computers
2) Connect the two computers using a Firewire cable
3) Start up the working computer.
4) Once the working computer is ready, startup your MacBook with the T key held down.
5) Your MacBook's hard drive should appear as an external hard drive on the working Mac. Drag & drop any files you want to save.
~Lyssa

G4 Power Mac won't boot past gray screen

I have a mirror door g4 power pc that had been having some issues with not turning on, and after testing the power supply, it failed miserably. We placed a refurbished power supply in it from a company in New York and the computer was working wonderfully. I went on a cruise last week and went to turn the computer on for the first time in a week and a few days. The CPU turns on, the unit chimes, the fan turns on and the computer starts to boot up, but it won't boot past the gray apple logo screen.
Actually, the first few attempts to boot it resulted in a blue screen with gaint apple logo and spinner; it wouldn't advance further. After several restarts and resets, I got it to come up into the normal gray screen. On several attempts it wouldn't boot further than this. On two occasions now though, it has moved past the gray screen to normal operation (it takes about an hour for it to get to that point though) but with some kind of errors. I get the side bar, but the gray panel on to with "file" ect is gone and my HD icon never comes up. The icons on the sidebar do not respond when clicked.
The computer will not boot from the OS X disc.
What's going on, hard drive? Virus? Something else?

You likely have hard drive directory issues or worse.
Virus is just a hopeful whimsy.
No virus.
I hope that you have a backup of your data.
Try a Safe Mode boot. This forces system repair of the directory (if possible).
Hold Shift while starting to enter Safe mode. Be patient, as it can take several minutes to complete.
Failure to boot to the OS X disc is not good. A severely damaged drive can prevent boot while connected.
Disconnect your boot drive and try booting to the OS X disc.

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

Similar Messages

Maybe you are looking for