Re: Kernel panic: VFS: Unable to mount root fs on 03:01
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Manuel Soukup schrieb: | Leute ich hab meine Paketliste zurück gespielt. Dabei hat er ein Paket | entfernt (konnte leider nicht sehen welches) und nun kommt beim booten: | | Kernel panic: VFS: Unable to mount root fs on 03:01 Naja, ich würde mal sagen, dass aus irgendeinem Grund plötzlich nicht mehr der richtige root=/dev/... Kernel-Parameter vom BootLoader übergeben wird - sprich ein falscher wird übergeben und der verweist auf eine Partition, die es gar nicht gibt/die er nicht mounten kann/dessen fs er nicht kennt/... | Was kann man da tun ? (Ich würde neu installieren oder gibts da ne | Möglichkeit mit Knoppix was zu ändern an der Bootreihenfolge oder sonst | wo?) Würde also mal sagen: GRUB bzw. Lilo Konfiguration überprüfen, ob denn da das richtige root-Device drinsteht. Das sollte mit Knoppix machbar sein. ~ Joachim -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBSTS3ZY86bR8HqNwRAlfvAJ9BfFC3QeHET5Pgyqt2g4UWWZEKIwCguNxW zZhbKO6NCIov+B+Pta1mIKE= =uB+4 -END PGP SIGNATURE- -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Kernel panic: VFS: Unable to mount root fs on 03:01
Manuel Soukup [EMAIL PROTECTED] writes: Hi Leute ich hab meine Paketliste zurück gespielt. Dabei hat er ein Paket entfernt (konnte leider nicht sehen welches) und nun kommt beim booten: Kernel panic: VFS: Unable to mount root fs on 03:01 Mit den Paketen direkt hat das nichts zu tun, sondern mit deiner Kernel-Konfiguration. 03:01 ist hda1. Wenn das nicht deine root-Partition ist, ist was an der lilo- oder grub-Konfiguration faul. Ansonsten musst die IDE-hd-Treiber und die fürs dortige Filesystem fest einkompilieren (Module gehen nur dann, wenn du eine initrd verwendest). Gruß, Heike -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Kernel panic: VFS: Unable to mount root fs on 03:01
Hi Leute ich hab meine Paketliste zurück gespielt. Dabei hat er ein Paket entfernt (konnte leider nicht sehen welches) und nun kommt beim booten: Kernel panic: VFS: Unable to mount root fs on 03:01 Was kann man da tun ? (Ich würde neu installieren oder gibts da ne Möglichkeit mit Knoppix was zu ändern an der Bootreihenfolge oder sonst wo?) Thx for any Help. cu Manuel -- .''`. Ich nutze Debian Sarge. --- GNU/Linux : :' : Mach Dir das Betriebssystem untertan! `. `'` Nicht, weil die Dinge schwierig sind, wagen wir sie nicht, sondern weil wir sie nicht wagen, sind sie schwierig. `-
Re: Kernel Panic: VFS Unable to mount root fs on 03:01
On Sat, Sep 19, 1998 at 11:41:24PM +0200, Miquel van Smoorenburg wrote: In article [EMAIL PROTECTED], [EMAIL PROTECTED] wrote: VFS: Can't open root device 03:01 Kernel Panic: VFS unable to mount root fs on 03:01 Sounds like you didn't compile in the driver for your harddisk. You did compile in (not as module) the IDE driver right? And support for the ext2 filesystem? Looks like missing IDE support was my problem. I had read only the beginning of the help on the Enhanced IDE support: ... the full-featured IDE driver to control up to four IDE interfaces ... and had figured that, since I have only two IDE drives, I did not need this full-featured driver. If I had read further: ... If you have one or more IDE drives, say Y ... I could have spared us this thread. Well, problem solved, and thanks for your help. Lesson learned: R(all)TFM. Matt Miller
Kernel Panic: VFS Unable to mount root fs on 03:01
My Hamm system is a couple weeks old, and I'm trying to roll my own kernel. The first few trys seemed to work, (removing PCI support, setting processor type to 486, etc...), but now, no matter how simple of a kernel I try to build, the system won't reboot. The kernel loads, then, after about 3/4 of a screen of normal startup messages, the system halts with: VFS: Can't open root device 03:01 Kernel Panic: VFS unable to mount root fs on 03:01 What do these messages mean, what have I done to myself, and how can I undo it? I installed the 2.0.34 kernel source package. I think I'm following the instructions in /usr/doc/kernel-source-2.0.34/README. I do: make mrproper make menuconfig make dep make clean make zImage make modules make modules_install cp /usr/src/linux/arch/i386/boot/zImage /boot/vmlinuz-2.0.34 lilo Here is some other potentially relevant info: $ less /etc/lilo.conf boot=/dev/hda1 root=/dev/hda1 install=/boot/boot.b map=/boot/map vga=normal delay=20 image=/vmlinuz label=Linux read-only $ ls -l /vmlinuz lrwxrwxrwx 1 root root 19 Sep 7 15:01 /vmlinuz - boot/vmlinuz-2.0.34 $ ls -l /boot total 295 -rw-r--r-- 1 root root 512 Sep 7 15:27 boot.0301 -rw-r--r-- 1 root root 4536 Nov 21 1997 boot.b -rw-r--r-- 1 root root 300 Nov 21 1997 chain.b -rw--- 1 root root 6656 Sep 15 23:12 map -rw-r--r-- 1 root root 444 Dec 12 1997 mbr.b -rw-r--r-- 1 root root 308 Nov 21 1997 os2_d.b -rwxr-xr-x 1 root root 281865 Sep 15 23:12 vmlinuz-2.0.34 Thanks, Matt Miller Software is never finished, it is only released Mike Gancarz, The Unix Philosophy
Re: Kernel Panic: VFS Unable to mount root fs on 03:01
[EMAIL PROTECTED] wrote: My Hamm system is a couple weeks old, and I'm trying to roll my own kernel. The first few trys seemed to work, (removing PCI support, setting processor type to 486, etc...), but now, no matter how simple of a kernel I try to build, the system won't reboot. The kernel loads, then, after about 3/4 of a screen of normal startup messages, the system halts with: VFS: Can't open root device 03:01 Kernel Panic: VFS unable to mount root fs on 03:01 You might be making your kernel too simple if you don't include support for the minix fs then it cannot mount the root partiton. Try remaking your kernel and be sure to include ext2 support. What do these messages mean, what have I done to myself, and how can I undo it? Next time also try to use the kpkg utility, all you do is enter the source directory enter kpkg and it creates a .deb of the kernel (well almost you'll have to read the doc's or ask me for more info if you want it). When you do a dpkg -i kernel-XX.deb it does everything for you, even runs lilo! I installed the 2.0.34 kernel source package. I think I'm following the instructions in /usr/doc/kernel-source-2.0.34/README. I do: make mrproper make menuconfig make dep make clean make zImage make modules make modules_install cp /usr/src/linux/arch/i386/boot/zImage /boot/vmlinuz-2.0.34 lilo Here is some other potentially relevant info: $ less /etc/lilo.conf boot=/dev/hda1 root=/dev/hda1 install=/boot/boot.b map=/boot/map vga=normal delay=20 image=/vmlinuz label=Linux read-only $ ls -l /vmlinuz lrwxrwxrwx 1 root root 19 Sep 7 15:01 /vmlinuz - boot/vmlinuz-2.0.34 $ ls -l /boot total 295 -rw-r--r-- 1 root root 512 Sep 7 15:27 boot.0301 -rw-r--r-- 1 root root 4536 Nov 21 1997 boot.b -rw-r--r-- 1 root root 300 Nov 21 1997 chain.b -rw--- 1 root root 6656 Sep 15 23:12 map -rw-r--r-- 1 root root 444 Dec 12 1997 mbr.b -rw-r--r-- 1 root root 308 Nov 21 1997 os2_d.b -rwxr-xr-x 1 root root 281865 Sep 15 23:12 vmlinuz-2.0.34 Thanks, Matt Miller Software is never finished, it is only released Mike Gancarz, The Unix Philosophy -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Kernel Panic: VFS Unable to mount root fs on 03:01
VFS: Can't open root device 03:01 Kernel Panic: VFS unable to mount root fs on 03:01 strange maybe you compiled the root fs as a module (which is not to be done), but how would you boot?... ah there's the answer: I installed the 2.0.34 kernel source package. I think I'm following the instructions in /usr/doc/kernel-source-2.0.34/README. I do: make mrproper make menuconfig make dep make clean make zImage make modules make modules_install cp /usr/src/linux/arch/i386/boot/zImage /boot/vmlinuz-2.0.34 lilo dear mister, that's the orginal doc from de kernel source, not the Debianized one. well, with Debian there are some more files that are necessary for the kernel to work (e.g. : /boot/SystemMap) you have to use the make-kernel package tools, or whatever is its name : # cd /usr/src/linux # make-kpkg clean # make xconfig /* sorry I like it :) */ # make-kpkg -r custom.1.0 binary which buils all you need in /usr/src then # cd /usr/src # dpkg -BRGiE kernel-image 2.0.34_custom.1.0.deb but before : $ man make-kpkg $ cd /usr/doc/kernel-(uh what's its name? look for it!) and rtfd :) you're welcome -- Samuel Landau
Re: Kernel Panic: VFS Unable to mount root fs on 03:01
In article [EMAIL PROTECTED], Samuel Landau [EMAIL PROTECTED] wrote: dear mister, that's the orginal doc from de kernel source, not the Debianized one. well, with Debian there are some more files that are necessary for the kernel to work (e.g. : /boot/SystemMap) That's nonsense. I have never used the Debian style and always installed my own kernels. /boot/System.map is not essential for the boot process either. Remember.. Debian is just Linux .. there's nothing special about the kernel. Mike. -- Did I ever tell you about the illusion of free will? -- Sheriff Lucas Buck, ultimate BOFH.
Re: Kernel Panic: VFS Unable to mount root fs on 03:01
In article [EMAIL PROTECTED], [EMAIL PROTECTED] wrote: VFS: Can't open root device 03:01 Kernel Panic: VFS unable to mount root fs on 03:01 Sounds like you didn't compile in the driver for your harddisk. You did compile in (not as module) the IDE driver right? And support for the ext2 filesystem? make modules make modules_install cp /usr/src/linux/arch/i386/boot/zImage /boot/vmlinuz-2.0.34 lilo You might want to cp System.map /boot/System.map-2.0.34. ps uses this (l option) and klogd to decode OOPSes if you get one. Mike. -- Did I ever tell you about the illusion of free will? -- Sheriff Lucas Buck, ultimate BOFH.
Re: Kernel Panic: VFS Unable to mount root fs on 03:01
On Sat, Sep 19, 1998 at 03:41:47PM -0500, Mark Panzer wrote: What do these messages mean, what have I done to myself, and how can I undo it? Next time also try to use the kpkg utility, all you do is enter the source directory enter kpkg and it creates a .deb of the kernel (well almost you'll have to read the doc's or ask me for more info if you want it). When you do a dpkg -i kernel-XX.deb it does everything for you, even runs lilo! Thanks. I should have figured Debian had a wrapper around kernel building. Matt Miller.
