On Thu, Oct 24, 2013 at 4:02 AM, Mark Phillips <[email protected]> wrote: > On Wed, Oct 23, 2013 at 6:10 AM, Tom H <[email protected]> wrote: >> On Wed, Oct 23, 2013 at 3:54 AM, Mark Phillips >> <[email protected]> wrote: >>> >>> I ran apt-get update and apt-get upgrade this morning on an old server >>> (Debian Squeeze) and the system won't boot now. I get the error >>> >>> kernel panic not syncing: VFS: unable to mount root fs on unknown >>> -block(0,0) >>> >>> One of the updates was to kernel 2.6.32-5-686. I can boot in to safe >>> mode with this kernel, and the upgrade wiped out the older version of the >>> kernel. >>> >>> I have googled for possible solutions, but nothing helpful is popping >>> up. I am also running grub, and not grub2, but that is OK for this kernel >>> according to debian.org. >> >> Are the "root" and "kernel" lines of the regular and recovery lines >> diffeent (other than the recovery kernel line having "single" added)? > > Yes, I looked in /boot/grub.cfg and the lines for the menu entries for both > normal boot and recovery mode are identical except regular boot says quiet > and recovery says single. > > Still can't get it to boot.
Please bottom-post. Since you're using grub1, I hope that you mean "/boot/grub/menu.lst". "grub.cfg" is grub2's menu configuration file and it's in "/boot/grub/". I'm having trouble understanding how you can mount "/" when booting with "single" and cannot mount "/" when you boot without it since the same initramfs is used for both (unless your "initrd" lines in "menu.lst" are different in the regular and recovery cases). -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/CAOdo=Sx7uS5pvracxeycYQE5PF1be_o5Rr9=b8oeqtaftql...@mail.gmail.com
