Hello everyone, the first time i installed SuSe 8.0 everything went just fine, i had some hardware problems involving a new HD so i find myself with the chance of installing linux again. Partitioning wise the linux dedicated hdb has a hdb1swap partition and hdb2 is the root partition, LILO was supposed to be on a floppy disk and default office with KDE desktop and the linux documentation where the packages i selected to be installed. It went fine during partitioning, package installation but, when it got to writing LILO to the floppy disk the system rebooted spontaneously. Any way i think i managed to complete installation by booting from the Cd and using the manual installation option in yast2 (LILO step was completly ignored) and then the boot installed system option, at least a password for root was set and a user was created. Once linux was loaded (working just fine) i went to the bootloader module in Yast 2 and to my surprise i find that lilo was configured to be installed in the MBR. Anyway, i changed that and configured linux to be booted from a floppy disk. Checked SuSE's support database in search for help but i cant seem to find a reference to the Kernel panic: VFS: Unable to mount root fs on 03:42 error message. Can somebody enlighten this lost and searching soul? José Gabriel Arnewi
On Wed, 23 Jul 2003, Josarn wrote:
Once linux was loaded (working just fine) i went to the bootloader module in Yast 2 and to my surprise i find that lilo was configured to be installed in the MBR. Anyway, i changed that and configured linux to be booted from a floppy disk. Checked SuSE's support database in search for help but i cant seem to find a reference to the Kernel panic: VFS: Unable to mount root fs on 03:42 error message.
I don't know whether your question is in the right place on this e-mail list, because suse-autoinstall deals with isssues of configuring AutoYast to do unattended installs of computers. But anyway, I will have a guess about what went wrong: It looks as if your root filesystem type is not supported by the booting kernel. This is the case for ext3 (and probably reiserfs and others as well), since SuSE kernels have these filesystems compiled as a module. Thus, you have to prepare an initial ramdisk (initrd) which provides the drivers for your harddisk (if necessary) and for the root filesystem. This ramdisk has to be specified as an boot option at the boot prompt to be loaded. Volkmar -- Volkmar Glauche Department of Neurology E-Mail glauche@uke.uni-hamburg.de UKE Hamburg Phone 49(0)40-42803-5781 Martinistr. 52 Fax 49(0)40-42803-9955 20246 Hamburg
participants (2)
-
Josarn -
Volkmar Glauche