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.

Similar Messages

BRAND NEW Mac Pro won't boot from Leopard DVD, kernel panics!

I just received my brand new Mac Pro today. It's a BTO machine with the upgrade to the NVIDIA 8800GT, a second optical drive and a Mac OS X Server license. The system has Mac OS X server installed on the default 320GB drive. I decided to use the server license as a virtual machine running in Leopard client. So, I installed 2 new 500GB Seagate 7200.11 (Retail) drives in the machine, zeroed them out in prep for installing Leopard client.
At this point, I pop in a freshly-purchased retail copy of the Leopard DVD and restart. When I try to boot from the DVD and install Leopard to one of the new Seagate drives, I get kernel panics - need to restart the machine. Also tried booting from the Mac OS X Server DVD and this too only caused kernel panics. The DVD's read perfectly from within Mac OS X Server and boot from hard disks is flawless.
I spent an hour on the phone with a level 2 tech at Apple - Tried swapping out the RAM and moving around the DIMMS to no avail. I am at a loss to what this could be. Seems to be a hardware issue and the tech thought it was likely a problem with one of the memory risers but couldn't send replacements. Anyone else with a similar issue?
This is my first Mac and it looks like this Mac Pro is going back for an exchange and I'll have to wait yet another 10-12 days for a replacement to arrive. Bummer.
Am I missing something simple here? Does this seem to be a hardware issue?
If anyone has any ideas before I ship this one back, please write!!!

New Mac Pros will not install the Leopard retail disc. They will only install the Leopard disc which shipped with them labeled Mac Pro. That has always been true. Macs can only boot the system that ships on DVD in the box that came with them, and newer retail releases. They can never boot from an older retail release than what shipped in the box.

[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 Pro won't boot up, not even in safe mode.

Problem: Mac Pro having severe lag issues. Added more ram, removed Kona3, etc., nothing. Tried repairing with disc warrior but unable to repair startup disc unless booted from disc warrior disc. Won't boot up from disc warrior disc so set startup disc to the disc warrior disc. Now comp won't boot up, not even from safe mode. Any suggestions?

Boot from your OS X install DVD.
You always need to have a 2nd backup you can boot from, or an emergency (only) boot drive.
Disk Warrior does not have 10.5.2+.
If you can't do anything, zap pram, see if that helps. Or pull your drives and boot from your DVD. Setup OS X on a FW drive.
And of course, always always have at least two backup sets of your system; and sets of your data - so one set at least is always off line.
http://www.geocities.com/texas_macman/pram.html
http://docs.info.apple.com/article.html?artnum=2238
http://www.apple.com/support/macpro/
http://www.thexlab.com/faqs/datacorruption.html
Issues with OS X and with Installing
http://support.apple.com/kb/TS1541
http://support.apple.com/kb/TS1388

Laptop won't boot, will not do a windows repair, received a hdd error 0303.

laptop won't boot, will not do a windows repair, received a hdd error 0303.

Hi,
The error code is a short Disk Self Test failure and would indicate that the Hard Drive is failing and needs to be replaced. This is also consistent with the start-up issue.
If your notebook is still under warranty, contact HP and arrange to have the drive replaced - you can check your warranty status Here.
If you live in the US, contact HP Here.
If you are in another part of the world, start Here.
If you are out of warranty and would like a guide on replacing the Hard Drive yourself, please let me know - include the full Model No. and Product No. of the notebook - see Here for a further explanation.
Regards,
DP-K
****Click the White thumb to say thanks****
****Please mark Accept As Solution if it solves your problem****
****I don't work for HP****
Microsoft MVP - Windows Experience

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)

Intel D2700DC + Arch won't boot without display

I've faced really wierd (to me) problem running Arch as mini webserver on the Intel D2700DC mini-ITX board with Atom D2700 integrated and NM10 Express chipset.
I successfully installed the system, configured network and started sshd to continue setting up other services remotely via ssh console. Then I disconnected the keyboard and display from the case and put it under the table. After that I was quiet surprised that the system was not starting up anymore.
After some investigation I've found that the system is not booting if no display is attached to the DVI port of the motherboard. If I start the system with display disconnected, I can hear one beep that notifies about successful BIOS POST, HDD led blinks 2-3 times, and then just nothing happens. System isn't booting up. If I attach the display right after that - nothing is seen on the screen, and display is immediately falling into sleep mode. Keyboard is still active though, and if I press ctrl+alt+del - the system is restarting, and, if display was just connected, it boots ok then. Also it boots fine from the cold state if the display was attached to the DVI port at the time of powering on.
As I can assume from the timings and HDD led blinking, the boot process stops right after GRUB is loaded. There's nothing in system log, cause it seems that boot hangs just before the kernel is loaded by GRUB. I'm really stuck and don't know how to work around this situation, because if the display was disconnected when system was powered on - then there's no way to see anything on the screen until next reboot, and if the display was connected - then the system boots OK.
One more thing to notice:
There was an old CentOS installation on the HDD, to which I installed Arch Linux. I've tried to boot it once or twice before installing Arch, and, as I could remember, it could boot up without display connected, on the very same hardware. So I suppose it's definitely something in Arch that is preventing the system to boot without the display.
I guess that when no display is connected at boot time, NM10 chipset completely disables onboard video, and because of this we can't see anything on the display until the system is restarted. But this somehow affects Arch, so it can't boot without any video hardware present.
Last edited by rand256 (2012-05-10 10:23:28)

I'm afraid there's no such option, but it looks like arch isn't booting just because no graphics card is detected in the system when display it disabled during powering up.
There is a couple of similar topics about some other linux distros can't boot without video card inserted ([1], [2]) with some recommendations on what to do in such a case.
I've followed them - including enabling serial console in /etc/inittab, setting nomodeset in kernel line in grub's menu.lst, checking for enabled splash-screens... but that didn't help.
Does anyone know what options should be tuned in order to boot Arch without any active graphics card present in the system hardware?

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 0.8 CD - "Could not find kernel image: linux"

I only get
Unknown keyword in config file.
Unknown keyword in config file.
Could not find kernel image: linux
when I try to boot the arch 0.8 base installer.
I checked md5 of the iso I downloaded and it seems to be correct:
1e0e9f3715d3c51129395570e01b9bc2 Archlinux-i686-0.8-Voodoo.base.iso
What can be done?
Last edited by Galdona (2007-04-13 18:34:53)

I wonder if the CD is defective or if it was burnt at a high speed that your CD cannot read.
In other words, may be you are reading from a coaster.
R

Arch won't boot on Virtual Box afted updating

I instaled Arch as guest on Vbox, after updating, it won't boot any more. It prints the message "Loading udev...SCSI subsystem initialized" and then the VM crash and the window is inmediately closed.
I searched on the Vbox forum and others have the same problem.
See: http://forums.virtualbox.org/viewtopic. … 890#p83890
Probably is an issue with Arch, because a clean install from core iso does work, but does not after updating.

What do you mean under updating ? pacman -Syu ? And what packages was installed?
Isn't there any virtualbox log or something ?

[SOLVED] Enabled AHCI - Arch won't boot

I have switched the SATA preference to AHCI from IDE in the BIOS. Now Arch refuse to boot with following warning:
ERROR: device '/dev/sda2' not found. Skipping fsck.
ERROR: Unable to find root device '/dev/sda2
[rootfs /]#
I have checked the WIKI and it has a remedy with 'mkinitcpio'; looks outdated. I have also found about adding one moule to initrd with mkinitrd on the www. However, I am not sure and need some guidance regarding this.
By the way, I dual-boot with Ubuntu and it booted just fine after the switch to AHCI.
Thanks.
Last edited by fantab (2013-04-21 22:27:38)

Thanks guys I fixed it from Ubuntu with 'chroot'. I added "ahci" to MODULES in /etc/mkinitcpio.conf and ran mkinitcpio.
I can boot Arch now.
Do I have to re-install the kernel? Do I have to add "ahci" to mkinitcpio.conf at every kernel upgrade and run mkinitcpio? Or am I OK.
Out of curiosity, regarding 'fallback image', how is it "even simpler"? Would love to know, for future reference, any pointers?
Last edited by fantab (2013-04-21 21:39:57)

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.

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?

Can't boot from OSX cd - Kernel Panic or bad CPU?

Greetings, All! I've looked at all the articles related to this that I can find, here and on other sites, but have not been able to solve the problem. Here's a list to briefly describe my issue:
-Got Prohibitory sign on my MDD Dual 867 when I tried booting into OS X (10.3).
-Tried all the resets (PRAM, PMU), re-seated RAM, took out RAM, etc.
-Trashed OS, and tried to re-install, but Mac won't boot from DVD (10.3) or CD (10.2) - just get the spinning wheel and finally Prohibitory sign...
-Ran Hardware test to loop for about 17 hours; nothing, all fine.
Then I just recently noticed that when I run Digital Performer 3 (OS9), it usually shows 2 usage indicators for CPU performance (1 for each processor) but now only shows one. So, I'm thinking a processor may have died, or become unseated, or something. But I read somewhere, on one of the forums, that it isn't likely for one of a pair of processors to go, or if it did, the other wouldn't be able to function solo. But if that weren't the case, and the Mac can run on 1 processor, why would that keep the Mac from booting from the OSX disk?
The Mac still runs fine in OS9, though it does seem to be a little slower when I do processor-intensive operations in DP, and sometimes hangs on startup, and seems to have some "sleep" issues (won't wake back up sometimes...). I don't know of any way to check if both processors are functioning in OS9. Does anyone know of a utility that will do that? Or if there's one in the OS (The Profiler only shows processor speed)? And would that cause the Kernel Panic and keep the Mac from booting in OSX? It's very frustrating. I appreciate any help or tips anyone may have to offer. Peace, Gelon

Hey Guys!
I think I know the "why", but not the solution...
I have a PowerMac G4 400Mhz Dual Processor, and some day I had the same troubles. No boot on OS X, but I can in OS9. Checking the Open Firmware commands, I saw one of the processor marked as "dead". So, (dont't ask how) I removed one processor from the logic board. Now I got the same "Processor dead", I can boot on OS9, (with an alert for the processor) but is stable. No boot in OS X.
So, what I suposse (having the same reports in PC computers trying to run OS X) is that the OS X checks for the compliance of the System for running. When a processor fails, the OS X can not recognize the system as valid (as in some PC computers happens) and can not boot. I also suposse if we can get a "patched" OS X for PowerPC or patch the firmware in any way, we can work with just one processor. Or, buying a new processor for the Mac.
Pls. send me your comments.
LY

MDD Dual 1.0GHz Power-up chime, NO BOOT or video after Kernel Panic

My MDD DP 1.0 (FW400) suffered a recent kernel panic on startup, and since then it has failed to boot...
It chimes and the power light stays on, fans run, but seems not to access the hard drive, and or power the DVD drives, USB/keyboard, or Video.
I Can't reach her via ARD either.
I have tried:
Reset PMU Power cord in.
Reset PMU Power cord out
Replaced the Battery,
Left battery out for 48hrs
Started up holding X key
Started up holding Space bar
etc. etc.
Any ideas? I really don't to loose this trusty old server.
Other details.
Hard Drives Are 2 month old Hitachi 7k250 have been tested as working in a D2 enclosure
Video Stock Radeon 9000 as new
PSU was replaced as part of the PSU replacement programme
Extra 1GB (2x512) Crucial installed when new.
Thanks In advance
Henrik

With care, you can manually open the optical drive tray. Pull open the outer door and use a good light to look at the front face of the drive beneath the hinged door. Somewhere there is a small hole, often under the tray, just slightly larger than a large paper clip's wire diameter.
Partially straighten a large paper clip and GENTLY insert the wire STRAIGHT into the hole. You should feel resistance after about 1/4 inch. Apply a little more pressure and the tray will start to move out. Grab it with your fingers and gently extend it all the way. I had to do this when I had the boot problems I mentioned.
Once you insert the System CD/DVD, push the tray closed and try to start, this time holding down the "C" key on your keyboard to force the computer to start from the optical drive.
BTW, be sure to check all internal cables for secure connections. As you're not even getting a gray screen, I'm getting a little concerned that your power supply has taken the long trail. When my MDD did the boot craziness, I at least got a gray screen.

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

Similar Messages

Maybe you are looking for