You are not logged in.
Pages: 1
Messed up my Arch so that when I select it from the grub menu my laptop freezes with about 20 lines of text on the screen, mostly disk location numbers. Can't copy or do anything but shut down the machine. However, the first line says
"2.047599 CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.17.4-1 ARCH #1"
and the last line says
"2047773 ---[end kernel panic --not syncing: VFS: Unable to mount root fs on unknown-block (0,0)"
Perhaps those lines are a clue to how this can be fixed. Can it be done by a simple replacement or should I reinstall Arch?
I spent most of the day trying to see if grub is doing something wrong, but no, it mounts the other linux distros that are on the hard disk (sda), namely debian squeeze and wheezy and pclos. Looking at grub.cfg and grub.d I don't see anything wrong. The Arch was last updated two or three days ago so the kernel is 3.2something, not the 3.17 as above.
It seems to me that something in Arch is messed up and so is not being found by grub. That happened I believe because I attached an external usb drive that tried to boot itself probably while Arch was live.
Sorry if this is a nuisance newbie question - I am a bit lost here.
Offline
Have you tried booting with the fallback image?
There's linux 3.17.4 in the core repo and 3.17.6 in the testing repo.
Offline
Same result when booting the fallback.
Is it practical to mount the Arch OS that won't boot, overwrite the linux and initrd (in /boot) with backed-up copies, then umount it? Or is that too simplistic?
Offline
You'd need to downgrade the kernel modules (/lib/modules) too.
You could chroot (https://wiki.archlinux.org/index.php/Chroot) into your Arch installation and downgrade the kernel (install an older version) or install linux-lts.
Last edited by lucke (2014-12-09 19:08:32)
Offline
Thanks, lucke, you have given me a direction to try.
You are correct about the arch version that I have: 3.17.4
Offline
I'm having the same problem. Tried
* Downgrading the kernel to 3.16.4 - Didn' t work
* Downgrading the kernel to 3.16.1 - Worked
* Decided I wanted a cleaner solution. Replaced the linux package with linux-lts. - Work
For what I read somewhere else (can't find the link), this is a Kernel bug raised under certain hardware combinations. And I hope this gets fixed soon, so I can go back to the common kernel which had never raised any problems for me until now.
Offline
Pages: 1