Arch Won't boot after lockup: "Failed to read file" [SOLVED]

So like many stories, this one begins with a "Sudo pacman -Syu".
Everything was updating fine, but then my system locked up. I let it set for awhile, but when I couldn't even get a console, I finally rebooted (yes, bad, I know).
I was about half-way through the upgrading process.
Now my system will not boot, and I only get a "Failed to read file" error.
I chrooted into my system through the live disk, and managed to finish the upgrade (I had to fix a few files, and reinstall some manually). I tried a "mkinitcpio -p linux," but no luck.
Is there anything else I could post that might be helpful? This error does not tell me a whole lot.
Thanks!
Last edited by thewooster (2014-06-18 16:11:51)

I did a little more looking around, and found a few more problems.
When I run a "mkinitcpio -p linux" now, I get:
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
It also appears I have a number of "empty" directories "pacman -S linux"
resolving dependencies...
looking for inter-conflicts...
Packages (1): linux-3.14.6-1
Total Installed Size: 70.27 MiB
Net Upgrade Size: 0.00 MiB
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
reinstalling linux...
>>> Updating module dependencies. Please wait ...
depmod: ERROR: failed to load symbols from /lib/modules/3.14.6-1-ARCH/extramodules/fglrx.ko.gz: Invalid argument
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> ERROR: Unable to write to /boot/initramfs-linux.img
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> ERROR: Unable to write to /boot/initramfs-linux-fallback.img
ldconfig: File /usr/lib/libclamunrar_iface.so is empty, not checked.
ldconfig: File /usr/lib/libfontforgeexe.so.2.0.0 is empty, not checked.
ldconfig: File /usr/lib/libfontforgeexe.so.2 is empty, not checked.
ldconfig: File /usr/lib/libgunicode.so.4 is empty, not checked.
ldconfig: File /usr/lib/libfontforgeexe.so is empty, not checked.
ldconfig: File /usr/lib/libcord.so is empty, not checked.
ldconfig: File /usr/lib/libgdraw.so.5 is empty, not checked.
ldconfig: File /usr/lib/libgdk_pixbuf_xlib-2.0.so is empty, not checked.
ldconfig: File /usr/lib/libgnome-menu-3.so is empty, not checked.
ldconfig: File /usr/lib/libgdk_pixbuf-2.0.so is empty, not checked.
ldconfig: File /usr/lib/libgccpp.so is empty, not checked.
ldconfig: File /usr/lib/libhunspell.so is empty, not checked.
ldconfig: File /usr/lib/libgdk_pixbuf-2.0.so.0.3000.8 is empty, not checked.
ldconfig: File /usr/lib/libgccpp.so.1 is empty, not checked.
ldconfig: File /usr/lib/libwbclient.so.0 is empty, not checked.
ldconfig: File /usr/lib/libhunspell-1.3.so is empty, not checked.
ldconfig: File /usr/lib/libgioftp.so is empty, not checked.
ldconfig: File /usr/lib/libgdk_pixbuf-2.0.so.0 is empty, not checked.
ldconfig: File /usr/lib/libgdraw.so is empty, not checked.
ldconfig: File /usr/lib/libX11-xcb.so.1 is empty, not checked.
ldconfig: File /usr/lib/libgioftp.so.2 is empty, not checked.
ldconfig: File /usr/lib/libclamunrar.so.6 is empty, not checked.
ldconfig: File /usr/lib/libfontforge.so is empty, not checked.
ldconfig: File /usr/lib/libX11.so.6 is empty, not checked.
ldconfig: File /usr/lib/libgdk_pixbuf_xlib-2.0.so.0 is empty, not checked.
ldconfig: File /usr/lib/libclamav.so.6 is empty, not checked.
ldconfig: File /usr/lib/libgutils.so.2.0.0 is empty, not checked.
ldconfig: File /usr/lib/libgnome-menu-3.so.0.0.1 is empty, not checked.
ldconfig: File /usr/lib/libgunicode.so is empty, not checked.
ldconfig: File /usr/lib/libtalloc.so.1 is empty, not checked.
ldconfig: File /usr/lib/libclamunrar.so is empty, not checked.
ldconfig: File /usr/lib/libclamunrar_iface.so.6.1.23 is empty, not checked.
ldconfig: File /usr/lib/libpytalloc-util.so.2 is empty, not checked.
ldconfig: File /usr/lib/libcord.so.1 is empty, not checked.
ldconfig: File /usr/lib/libX11-xcb.so is empty, not checked.
ldconfig: File /usr/lib/libgccpp.so.1.0.3 is empty, not checked.
ldconfig: File /usr/lib/libtalloc.so.2 is empty, not checked.
ldconfig: File /usr/lib/libtalloc.so is empty, not checked.
ldconfig: File /usr/lib/libwbclient.so is empty, not checked.
ldconfig: File /usr/lib/libX11.so.6.3.0 is empty, not checked.
ldconfig: File /usr/lib/libfontforge.so.2 is empty, not checked.
ldconfig: File /usr/lib/libgutils.so is empty, not checked.
ldconfig: File /usr/lib/libclamunrar.so.6.1.23 is empty, not checked.
ldconfig: File /usr/lib/libclamunrar_iface.so.6 is empty, not checked.
ldconfig: File /usr/lib/libhunspell-1.3.so.0.0.0 is empty, not checked.
ldconfig: File /usr/lib/libtalloc.so.2.1.1 is empty, not checked.
ldconfig: File /usr/lib/libgutils.so.2 is empty, not checked.
ldconfig: File /usr/lib/libfontforge.so.2.0.0 is empty, not checked.
ldconfig: File /usr/lib/libtalloc-compat1-2.1.1.so is empty, not checked.
ldconfig: File /usr/lib/libgc.so.1 is empty, not checked.
ldconfig: File /usr/lib/libpytalloc-util.so is empty, not checked.
ldconfig: File /usr/lib/libcord.so.1.0.3 is empty, not checked.
ldconfig: File /usr/lib/libgunicode.so.4.0.0 is empty, not checked.
ldconfig: File /usr/lib/libX11.so is empty, not checked.
ldconfig: File /usr/lib/libpytalloc-util.so.2.1.1 is empty, not checked.
ldconfig: File /usr/lib/libgc.so is empty, not checked.
ldconfig: File /usr/lib/libhunspell-1.3.so.0 is empty, not checked.
ldconfig: File /usr/lib/libgdk_pixbuf_xlib-2.0.so.0.3000.8 is empty, not checked.
ldconfig: File /usr/lib/libgdraw.so.5.0.0 is empty, not checked.
ldconfig: File /usr/lib/libX11-xcb.so.1.0.0 is empty, not checked.
ldconfig: File /usr/lib/libwbclient.so.0.11 is empty, not checked.
ldconfig: File /usr/lib/libgioftp.so.2.0.0 is empty, not checked.
ldconfig: File /usr/lib/libgc.so.1.0.3 is empty, not checked.
ldconfig: File /usr/lib/libclamav.so is empty, not checked.
ldconfig: File /usr/lib/libgnome-menu-3.so.0 is empty, not checked.
ldconfig: File /usr/lib/libclamav.so.6.1.23 is empty, not checked.
Gummiboot will not reinstall "gummiboot -path=$esp install":
Failed to check file system type of : no such file or directory
I have considered doing a reinstall, but I have so many customizations that I would prefer not to lose them. I do have an rsync backup, but it is a little old, and do have separate home/root partitions, but wouldn't I still lose a fair amount of customizations?

Similar Messages

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

Arch won't boot after rEFInd update

I've followed https://wiki.archlinux.org/index.php/UEFI_Bootloaders as closely as I can, but still can't get Arch to boot. It doesn't even get to the boot loader.
uname -m
x86_64
Partitions:
Device Type Name
/dev/sda1 Linux filesystem root
/dev/sda2 Linux filesystem boot
/dev/sda3 EFI System efi
/dev/sda4 Linux filesystem var
/dev/sda5 Linux filesystem home
lsblk
Name Type Mountpoint
sda disk
sda1 part /
sda2 part /boot
sda3 part /boot/efi
sda4 part /var
sda5 part /home
Directory tree:
/boot/
efi/
EFI/
arch/
initramfs-arch-fallback.img
initramfs-arch.img
refind_linux.conf
vmlinux-arch.efi
refind/
icons/
refind.conf
refind_x64.efi
initramfs-linux-fallback.img
initramfs-linux.img
vmlinuz-linux
/boot/efi/EFI/arch/refind_linux.conf:
"Default boot" "root=PARTUUID=d368616d-a423-4511-88df-f2f645079bab ro rootfstype=ext4 add_efi_memmap system.unit=graphical.target"
"Boot to terminal" "root=PARTUUID=d368616d-a423-4511-88df-f2f645079bab ro rootfstype=ext4 add_efi_memmap system.unit=multi-user.target"
ls -l /dev/disk/by-partuuid/
lrwxrwx 1 root root Jan 30 1:08 d368616d-a423-4511-88df-f2f645079bab -> ../../sda1
efibootmgr -v
BootOrder: 0018, ...
Boot0018* Arch Linux (rEFInd) HD(3,0,0,74930800)File(EFI\refind\refind_x64.efi)
Anything else I'm missing? By the way, I think this is related to the Jan 27. update to refind. Today was the first time I've rebooted my computer since then.
Also - I tried both commenting and uncommenting scan_all_linux_kernels in refind.conf. No dice.
Thank you very much!
EDIT: Some updates...
I was poking around the UEFI shell. The following commands caused my computer to hang (I had to hard-restart):
Shell> fs0:
FS0> ls
I could ls just fine using shell 1.0, but shell 2.0 caused a hang. Then, after the hard restart, more strange behavior:
Shell> bcfg boot add 0 fs0:\EFI\refind\refind_x64.efi "Test"
Error. The file 'fs0:\EFI\refind\refind_x64.efi' did not open.
Also, I can "bcfg boot dump" just fine, but if I want to scroll through the output, I get an error, and it hangs, so I have to hard restart again.
Shell> bcfg boot dump
// bunch of output
Shell> bcfg boot dump -b
// after printing five boot entries...
Press ENTER to continue or 'Q' to break:
ASSERT_EFI_ERROR (Status = Not Ready)
ASSERT c:\dev\edk2top\ShellPkg\Library\UefiShellLib\UefiShellLib.c(3223) : !EFI_ERROR (Status)
Not sure if any of that last but is relevant. Thanks again.
Tried downgrading kernel to 3.6, still won't boot.
Last edited by MitchellSalad (2013-01-30 20:05:10)

MitchellSalad wrote:
Partitions:
Device Type Name
/dev/sda1 Linux filesystem root
/dev/sda2 Linux filesystem boot
/dev/sda3 EFI System efi
/dev/sda4 Linux filesystem var
/dev/sda5 Linux filesystem home
/boot/efi/EFI/arch/refind_linux.conf:
"Default boot" "root=PARTUUID=d368616d-a423-4511-88df-f2f645079bab ro rootfstype=ext4 add_efi_memmap system.unit=graphical.target"
"Boot to terminal" "root=PARTUUID=d368616d-a423-4511-88df-f2f645079bab ro rootfstype=ext4 add_efi_memmap system.unit=multi-user.target"
ls -l /dev/disk/by-partuuid/
lrwxrwx 1 root root Jan 30 1:08 d368616d-a423-4511-88df-f2f645079bab -> ../../sda3
Shouldn't that be sda1? Your root-partition is /dev/sda1.

Arch Won't Boot After Kernel Upgrade

I installed Arch on VirtualBox, but after upgrading the Kernel to 2.6.30 it wouldn't boot. It gets to "Loading udev...." and then VirtualBox crashes.

Hello, I'm having this same problem, except I'm not using VirtualBox or VMWare, I have Arch installed to the hard drive. It worked fine after upgrading to 2.6.30, but after upgrading kernel-headers to 2.6.30.1-1, neither Arch NOR Arch-Fallback will boot! I don't even get to Udev or the part where the two arch logos are on top. It just starts up a little bit, then restarts my computer.
I don't even know if my system has been wiped or something, but I doubt that; I think it's just the booting process. I do have a 2009.2 Live CD, but it's an FTP installation. Is there any way to start up my live CD and do a pacman -U for the old kernel version with the cache on my hard drive? How would I do this?
Last edited by Allamgir (2009-07-07 00:32:12)

Arch won't boot after -Syu: /etc/rc.sysinit can't execute things

Hello,
I was not getting any updates for about a week or two so I checked my mirrors and added a few more. I ran yaourt -Syu, there were 30 updates.
I shutdown my computer and when booting I got several messages saying "cannot execute binary file" from /etc/rc.sysinit.
Here is the first of such messages:
/etc/rc.sysinit: line 45: /bin/dmesg: cannot execute binary file
rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one month, y3k, 114 bytes nvram
/etc/rc.sysinit: line 84: /sbin/hwclock: cannot execute binary file
Arch Linux Fallback has the same problems. I also tried to get to my files with the Arch livecd but I could not mount them:
mount: can't find /dev/sda3 in /etc/fstab or /etc/mtab
Any help on this would be greatly appreciated. I have some things on there that I don't want to lose.
Thanks,
Andreas

From a knoppix disk I mounted sda3 and other partitions to their respective mount points and used chroot.
I ran pacman -S base but many of packages did not install correctly according to the messages.
The reboot with the hard drive fails and I am dropped to a recovery shell.
I can't chroot in again after this because of "Exec format error" however both the Knoppix disk and the Arch install are both i686. Maybe x86_64 base was being installed by pacman.

[SOLVED] Arch won't boot after install - "GRUB" on black screen

I've installed arch on my 1000H from usb stick using zeneee kernel as described in wiki. Right after install everything was fine - wireless and ethernet were working normally, so i've done reboot.
Now it shows me black screen with "GRUB" text (sic! not "grub>", no error messages) on it. keyboard is not working.
I've tried reinstalling completely again - with full repartitioning of HDD and this time without installing eee kernel - just stock kernel26. Everithing went ok, i've checked grub settings and partitions - ok, but after reboot - again "GRUB" and non-working keyboard.
I'm completely out of ideas.
EDIT: turns out i misplaced GRUB or something. reinstalled placing GRUB on /dev/sda. works fine now.
Last edited by glas01 (2008-11-29 12:46:15)

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)

Arch won't boot after trying ususepnd

I wanted to try suspension to disk so I installed uswsusp and hibernate-script, added the ususpend hook in mkinitcpio.conf just before filesystems, mkinitcpio -p kernel26 and after some configuration issued the command "hibernate" as root.
Thigs seemed to work, but after the screen turned off, it instantly turned on again and I was back in my desktop (I suppose the modules were loading again because my wifi card was reconnecting).
I rebooted, and then the mkinitcpio hook seemed to start working and restored my desktop, just where I was when I tried the "hibernate" command. Tried to reboot again, but the KDE reboot buttons didn't did anything. Seconds later, all the desktop hanged, and I had to force a cold reboot.
After that, every time I try to boot, both with the "Archlinux" and the "Archlinux Fallback" entries in Grub, I get a really nasty kernel panic.
I tried to load a LiveCD, delete ususpend from the hooks array and rebuild the initcpio image, but nothing seems to hange.
My system is updated to the present day, including stable kernel26.
I think I really fucked it up this time. Any idea?

Heh, posting from Archlinux LiveCD.
I was trying to check what happened in a chroot, and I realized that every now and then I couldn't access directories I normally can access even from chroot, like some subdirectories of /var. When I tried to read some files the console threw "Permission denied" and "IO Error" errors. However, the majority of the filesystem seems to be accesible.
I'm performing a reiserfsck on my root partition, and the things seems to be quite screwd up. I'm getting "block ******: The level of the node (******) is not correct, (1) expected the problem in the internal node occurred (******), whole subtree skipped". Does this have fix :\?
What do you think could have caused theese issues? Failed hibernation? Just the cold reboots?

Arch won't boot after switching to ext4

Hi,
Yesteday I converted my partition to ext4 sucesfully, and I managed to boot once after that, but when I tried to reboot, GRUB2 would say:
error: invalid magic number
while trying to load the kernel. I already chrooted from my Ubuntu partition and tried to fix by reinstalling kernel and fsck'ing, but no luck. ideas? I can't even boot from fallback :S

Ok, here's my grub.cfg
# Config file for GRUB2 - The GNU GRand Unified Bootloader
# /boot/grub/grub.cfg
# DEVICE NAME CONVERSIONS
# Linux Grub
# /dev/fd0 (fd0)
# /dev/sda (hd0)
# /dev/sdb2 (hd1,2)
# /dev/sda3 (hd0,3)
# Timeout for menu
set timeout=5
# Set default boot entry as Entry 0
set default=0
#Colors
set menu_color_normal=light-blue/black
set menu_color_highlight=light-cyan/blue
#modules insert
insmod linux
# (0) Arch Linux
menuentry "Arch Linux" {
set root=(hd0,5)
linux /boot/vmlinuz26 root=/dev/sda5 rootfstype=ext4 ro quiet
initrd /boot/kernel26.img
# (1) Arch Linux recovery
menuentry "Arch Linux Fallback" {
set root=(hd0,5)
linux /boot/vmlinuz26 root=/dev/sda5 ro quiet
initrd /boot/kernel26-fallback.img
menuentry "Kubuntu 8.10, kernel 2.6.27-7-generic" {
set root=(hd1,5)
linux /boot/vmlinuz-2.6.28-4-generic root=/dev/sdb5 ro quiet splash
initrd /boot/initrd.img-2.6.28-4-generic
menuentry "Kubuntu 8.10, kernel 2.6.27-7-generic (recovery)" {
set root=(hd1,5)
linux /boot/vmlinuz-2.6.28-4-generic root=/dev/hda1 ro single
initrd /boot/initrd.img-2.6.28-4-generic
## (1) Windows
#menuentry "Windows" {
#set root=(hd0,3)
#chainloader +1
BTW, if I change "linux" command for "multiboot", I get this:
alloc magic is broken at 0x19710
Any ideas on what may be causing this? Perhaps changing to GRUB-legacy would help?

Arch won't boot after update and force shutdown because of freeze

OK, I am typing this message on my tablet because the arch system isn't working. It freezes on systemd-fsck dev/sda3 clean a bunch ofmfile and blocks.

Okay guys so I have done some research and what I think I need to do is get into chroot and from what I have gathered chroot (correct me if i'm wrong) simulates the real computers terminal from a live Arch or other distro's cd with chroot installed on it? So I would do mount /dev/sda3 /mnt, as sda3 is my home folder, wait nope some more research says I need to do mount /dev/sda1 /mnt then /dev/sda3 /mnt/home then do arch-chroot /mnt. Now it shows sh-4.3 and a command blinker thing. I am stuck on what to do now

Arch won't boot, FS not detected, Kernel Panic.

Ok so here is the situation. I have arch linux installed on sda1, which is a sata drive, samsung. Seems lately I been having problems getting arch to boot because it doesn't know what type filesystem my root device has. It goes on and tells me that I can use the kernel parameter rootfstype= to solve the issue, but yet when I try this, it does nothing. I stop getting the error, about unknown FS type, but arch still won't boot. Init fails...
I have tried everything on these forums to fix the problem and not one thing in general has solved the issue. What seems to be most consistent about this problem, is it takes me at least 20 - 30 times of rebooting before it will finally go through and boot. But, even then this is not foolproof. Last night I tried at least 30+ times of rebooting, powering off and still it would not boot.
So after reading the forums some more I found an article somewhat related to my problem and it was suggested that I add my root FS type as a module and then remove the filesystem hook in mkinitcpio.conf. I tried this approach and at the same time downgraded to 2.6.24.2-1 kernel26 so mkinitcpio would generate the new image. Then I rebooted and arch loaded just fine. So then I rebooted and again, unknown fs type on root device error.
So I retraced my steps and tried the same process again, only this time when I rebooted I got same problem. So as it seems, nothing I did to mkinitcpio.conf did anything to alleviate my problem.
As of right now, I managed to get the fallback image to work(but fallback does not load all the time, just this last time I tried it it worked), but I am scared to death to turn off my machine because I know it's not gonna reboot without a lot of hassle.
So can anyone help me diagnose this problem? What can I do to get the kernel to boot and mount the root device with ext3 and pass init on boot up? I am completely lost when it comes to this...
here is my mkinitcpio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES="ext3 pata_amd ata_generic sata_nv"
# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
# This is identical to the above, except the old ide subsystem is
# used for IDE devices instead of the new pata subsystem.
# HOOKS="base udev autodetect ide scsi sata filesystems"
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev pata scsi sata usb filesystems"
# This setup assembles an pata raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev pata raid encrypt filesystems"
# This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect pata sata"
here is my fallback.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
# BusLogic is added to support VMWARE arch booting in fallback image
MODULES="BusLogic"
# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
#BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm, or encrypted root is needed.
# HOOKS="base"
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect ide scsi sata filesystems"
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev ide scsi sata usb filesystems"
# This setup assembles an ide raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev ide filesystems raid encrypt"
# This setup loads an LVM volume group on a usb device.
# HOOKS="base udev usb filesystems lvm"
HOOKS="base udev ide pata scsi sata usbinput raid filesystems"
modules I need
sudo mkinitcpio -M
Password:
Modules autodetected:
ata_generic
libata
pata_acpi
pata_amd
sata_nv
cdrom
ide-core
amd74xx
generic
forcedeth
sd_mod
sr_mod
usbcore
ehci-hcd
ohci-hcd
jbd
ext3
Last edited by jacko (2008-04-15 19:53:35)

I had a similar issue (I think, can you post the exact error the kernel panics with to check?) and it seemed grub or the kernel had difficulties with finding my root device which was specified as a device node in /dev. The solution for me was to change the root parameter in my kernel line in grub's menu.lst to root=/dev/disk/by-label/<label>, I'm sure UUID and such will work fine too. After doing that I haven't encountered a single such kernel panic. More info about persistent device naming can be found here.

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 OS won't boot after 2007-009 1.1 update

Hi all
Fairly major problem here. Mac OS X won't boot after the 2007-009 1.1 security update.
What I am left with is the mac boot screen, and not a lot happening. No rotating loading animation.
Any help would be really appreciated.
Thanks

I have been booting up for...2.45 hours now
Good grief!
Here are a few hints about what you should have done:
There are no guarantees, but following this procedure when installing updates and upgrades on your Mac will go a long way towards avoiding unpleasant after effects and ‘post-update stress disorder’.
It is also worth noting that it is an extreme rarity for updates to cause upsets to your system, but they may well reveal pre-existing ones, particularly those of which you may have been unaware. If you are actually aware of any glitches, make sure they are fixed before proceeding further.
So before you do anything else:
If you can, make a full backup first.
Turn off sleep mode for both screen and hard disk.
Disconnect all peripherals except your keyboard and mouse.
1. Repair Permissions (in Disk Utility)
2. Verify the state of your hard disk using Disk Utility. If any faults are reported, restart from your install disk (holding down the C key), go to Disk Utility, and repair your startup disk. Restart again to get back to your startup disk.
At least you can now be reasonably certain that your system does not contain any obvious faults that might cause an update/upgrade to fail.
3. Download the correct version of the COMBO update from the Apple download site. If your car runs on gasoline you would not want to fill the tank with diesel, so don’t try to install the PPC updater on an Intel Mac!
If you prefer to download updates via Software Update in the Apple menu (which would ensure that the correct version for your Mac was being downloaded), it is not recommended to allow SU to install major (or even minor) updates automatically. Set Software Update to just download the updater without immediately installing it. There is always the possibility that the combined download and install (which can be a lengthy process) might be interrupted by a power outage or your cat walking across the keyboard, and an interrupted install will almost certainly cause havoc. Once it is downloaded, you can install at a time that suits you. You should make a backup copy of the updater on a CD in case you ever need a reinstall.
Using the Combo updater ensures that all system files changed since the original 10.4.0 are included, and any that may have been missed out or subsequently damaged will be repaired. The Delta updater, although a temptingly smaller download, only takes you from the previous version to the new one, i.e. for example from 10.4.9 to 10.4.10. Software Update will generally download the Delta updater only. The preferable Combo updater needs to be downloaded from Apple's download site.
Now proceed as follows:
4. Close all applications.
5. Unplug all peripherals except your keyboard and mouse.
6. Install the update/upgrade. Do not under any circumstances interrupt this procedure. Do not do anything else on your computer while it is installing. Be patient.
7. When it ask for a restart to complete the installation, click restart. This can take longer than normal, there are probably thousands of files to overwrite and place in the correct location. Do nothing while this is going on.
8. Once your Mac is awake, repair permissions again, and you should be good to go!
If your Mac seems slightly sluggish or ‘different’, perform a second restart. It can’t hurt and is sometimes efficacious!
9. Open a few of your most used applications and check that all is OK. In this connection please remember that not all manufacturers of third party applications and plug-ins, add-ons, haxies etc, will have had time to do any necessary rewrites to their software to make them 10.4.10. compliant. Give them a weeks or two while you regularly check their websites for updates. This applies particularly to plug-ins for Safari 3.
N.B. Do not attempt to install two different updates at the same time as each may have different routines and requirements. Follow the above recommendations for each update in turn.
Lastly, Apple's own article on the subject of Software Update may also be useful reading:
http://docs.info.apple.com/article.html?artnum=106695
If you are updating Safari (or just have):
Input Managers from third parties can do as much harm as good. They use a security loophole to reach right into your applications' code and change that code as the application starts up. If you have installed 10.4.11 and Safari is crashing, the very first thing to do is clear out your InputManagers folders (both in your own Library and in the top-level /Library), log out and log back in, and try again.
So, disable all third party add-ons before updating Safari, as they may not have been updated yet for the new version. Add them back one by one. If something goes awry, remove it again and check on the software manufacturer's website for news of an update to match your version of Safari. Remember: Tiger up to 10.4.10 used Safari 2.0.4 or, if you downloaded it, Safari 3.0.3 beta. Safari 10.4.11 uses Safari 3.0.4 which is not a beta. If Safari 3.0.4 on 10.4.11 is not the fastest browser you have ever used, then something is wrong!
Moreover, trying to revert to Safari 2 when running 10.4.11 can have repercussions, as Safari 3.0.4 uses a completely different webkit on which other applications like iChat, Mail and Dashboard Widgets etc also rely.
Most errors reported here after an update are due to an unrepaired or undetected inherent fault in the system, and/or a third party ad-on. Two such add-on that have been frequently mentioned here for causing such problems are Piclens and Pithhelmet. If you have them, trash them.
Additional tips on software installation here:
http://docs.info.apple.com/article.html?artnum=106692

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?

My Itunes won't open after a failed attempt at upgrading.

My ITunes won't open after a failed attempt at upgrading. Keep getting the error message...Failed to start because MSVCR80.dll was not found. I have tried uninstalling and reinstalling and notheing works. Help!

See Troubleshooting issues with iTunes for Windows updates.
tt2

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.

Arch Won't boot after lockup: "Failed to read file" [SOLVED]

Similar Messages

Maybe you are looking for