You are not logged in.
Pages: 1
I did a pacman -Syu today which installed kernel 2.6.32 and after rebooting it immediately said
list of all partitions:
could not mount root with any filesystem: --error syncing unknown block(0,0)
kernel panic -- bla bla bla............
more or less something like above...
I just want to know what might be causing this kernel panic, and I've done a pacman -Scc recently so should i have to rollback to the kernel that came with the arch installation cd ?
Last edited by Soumyadeep (2010-01-01 02:44:36)
Offline
if you have lilo you should have run lilo before reboot. run lilo again or install grub. I remember having similar problem before I switched to grub
Offline
no I have grub and i also tried to boot it opensuse's grub installed in another partition but the result the same
Well another thing is bugging me, I booted with with the arch install cd and 3 out of 5 times it also had a kernel panic during booting which is very weird to me....... so is this issue related to my HDD? but opensuse on 2.6.31 seems to be running fine at the moment
Offline
i had no problems with the new kernel. because you are not the only one with this problem, it makes it unlikely something is wrong with your configuration. it might be issue with your hardware. in that case rollback to the previous kernel version seems to be a good idea. post lspci output for everyone with similar problem and check the kernel & hardware issues section for updates. unless, of course, someone has a better solution
Offline
Well the most weird thing is now I CANNOT even boot with the install cd, the kernel is giving a panic everytime, it now says something like:
I/O errror, /dev/sr0
squashfs error: cannot read block 0x0
squashfs error: cannot read superblock
what's /dev/sr0 ?
but i can boot with opensuse without a single prob or warning.
Offline
http://bugs.archlinux.org/task/17649
i think this ones related to me(but my arch is 32 bit), its gives almost the same warning except that it warns about killing init
but now i'm unable to chroot and enable the testing repo as booting from the install cd is failing
Last edited by Soumyadeep (2009-12-30 16:40:56)
Offline
/dev/sr0 is your cd/dvd device. your cd is damaged. try burning it again and if that doesnt work try with different iso. you can also download usb image and make bootable usb.
Offline
I have a 64 bit usb image right now, thinking bout removing the old 32 bit install and giving arch64 a try
@ontweld: can u help me with another issue?
whenever i chroot using my boot cd or i login from another distro i cannot see any folder or file in my /home partition of my arch, why is that so?
Offline
depends on what directories you mount before you call chroot. example (from wiki):
mkdir /mnt/arch
mount -t ext4 /dev/sda1 /mnt/arch
mount -t proc proc /mnt/arch/proc
mount -t sysfs sys /mnt/arch/sys
mount -o bind /dev /mnt/arch/dev
and you can see your /home normally, because in the second line you've mounted whole partition into /mnt/arch including /home. (change ext4 to fs of your partition)
Offline
Perhaps check the CD performance in another OS.
Perhaps the cabling to the CD is misconnected causing corruption of the interface.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Installed arch64 and did a pacman -Syu, which updated kernel to 2.6.32.xxx, and guess what no panics !!!
Offline
Pages: 1