linux-kernel - Panic booting 2.6.30

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 19 Jun 2009 15:23:24 -0400
From:	David Ronis <ronis@...ispc.chem.mcgill.ca>
To:	linux-kernel@...r.kernel.org
Subject: Panic booting 2.6.30

I've just upgraded an older machine (a P3 running slackware 11.0) from
2.6.26.5 to 2.6.30; the build was uneventful.  However, on reboot (using
lilo) I get:

VSF:  Cannot open root device "hda2" or unknown-block(0,0)
Please append a correct root= boot option; here are the available
partions:     <====== nothing shows here...
Kernel-Panic - not syncing.

I had rebooted with and without root=hda2.   The old kernel is still
usable.

Lilo.conf looks like:

boot = /dev/hda
lba32
message = /boot/boot_message.txt
prompt
timeout = 300
vga = normal
# Linux bootable partition config begins
image = /bzImage-2.6.30
  root = /dev/hda2
  label = Linux-2.6.30
  read-only
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /bzImage-2.6.26.5
  root = /dev/hda2
  label = Linux-2.6.26.5
  read-only
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /memtest86
  root = /dev/hda2
  label = memtest86
  read-only
# Linux bootable partition config ends

Any ideas?  Please CC me directly.

Thanks in advance

David

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/