Re: Is there a log file containing the kernel parameters used?

From: Andreas Janssen (andreas.janssen_at_bigfoot.com)
Date: 01/20/04 

Date: Tue, 20 Jan 2004 17:46:47 +0100

Hello

RAG (<ragatgt@Yahoo.Com>) wrote:

> My question is way below, if you are in a hurry... ;-)
>
> I am currently trying to install SuSE 9.0 on some old HW (Pentium
> 133MHz, 48MB RAM)to have a firewall internet-router-computer at home.
> To get the OS onto the computer was quite tricky because the CD-ROM
> wouldn't boot and the DISK set failed with a "CRC error" (indepentend
> of the disks i used and the BIOS settings).
>
> So i made a DOS-Bootdisk with loadlin on it to boot the stuff in the
> SUSECDROM1\boot\loader (or similar) folder.
> Then i had to insert my second hd into my other computer to make a
> swap partition. And reinstall it in the old computer.
> Now i could install SuSE and everything seemed to work...
> ...until the first reboot.
> The kernel said: Cannot mount root fs on 03:01 (wich is a reiserfs on
> /dev/hda1).
> The reiser module seems to be part of the initrd so this cannot be the
> problem and the major and minor number also seems to be correct
> according to ls -l /dev/hda1. Neither GRUB nore LILO seem to work.

Well, this is the error message you typically get if the root file
system is not supported by the kernel. If there would be a problem with
accessing the root device itself (like missing IDE support), you would
get a different error message.

> Right now, i have to use my dos-bootdisk, boot the installation system
> from the cd-rom and have to chose "Boot installed system". After the
> HD check, i can boot from /dev/hda1 without any problems.

> Is there a way to find out all kernel parameters the were used for the
> last system boot so i can find out the difference between both ways of
> booting? Maybe some kind of boot log?

Try dmesg | grep command. Mine looks like this:

Kernel command line: BOOT_IMAGE=Linux ro root=307 quiet hdc=ide-scsi
hdd=ide-scsi max_scsi_luns=1

However, if your system cannot mount the root file system, it also
cannot write any log files. Maybe you should double-check your boot
loader configuration to see if the initrd is actually used. If anything
else fails, try to recompile the Kernel and build reiserfs support into
it.

best regards
        Andreas Janssen 

-- 
Andreas Janssen
andreas.janssen@bigfoot.com
PGP-Key-ID: 0xDC801674
Registered Linux User #267976

Relevant Pages