Problem mounting ReiserFS as root partition

Problem mounting ReiserFS as root partition

[Till Gerken]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

I encountered a very strange problem that I was not able to solve so far. I 
did not find anything similar on the web either.

I am not able to mount my ReiserFS partition as root partition with any kernel 
later than 2.4.20-pre11. When trying, I get

read_super_block: can't find a reiserfs filesystem on (dev 03:00, block 64, 
size 1024)

The same with block 8 and then a kernel panic.

I have tested this with 2.4.20 and 2.4.21 kernels, both compiled with exactly 
the same configuration as my current 2.4.20-pre11 kernel. Only the 
2.4.20-pre11 kernel is able to mount this partition as root partition.

I have booted from a Knoppix CD using a 2.4.20-xfs kernel and it was able to 
mount the partition. Unfortunately I could not test if it is able to mount it 
as root partition during boot.

reiserfsck does not report any problems, reiserfsck --rebuild-sb tells me that 
the super block is ok. I tested this with various versions of the tools up to 
3.6.6.

I would be grateful for any hints.

Till
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE+7G/pFwwirB11AGMRAvUhAJ9elrxZHfF7MACxTEocbPN8NBZ6ugCeKSgM
5lMNJkbNMgNF/cLM68iVVto=
=uSiR
-----END PGP SIGNATURE-----

Re: Problem mounting ReiserFS as root partition

[Oleg Drokin]

Hello!

On Sun, Jun 15, 2003 at 03:08:39PM +0200, Till Gerken wrote:

> I am not able to mount my ReiserFS partition as root partition with any kernel 
> later than 2.4.20-pre11. When trying, I get
> read_super_block: can't find a reiserfs filesystem on (dev 03:00, block 64, 
> size 1024)

Are you sure you want to mount /dev/hda as opposed to some partition on /dev/hda?
Please check that you are mounting correct thing (root= option in lilo.conf for example).

Bye,
    Oleg

Re: Problem mounting ReiserFS as root partition

[Till Gerken]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 16 June 2003 08:36, Oleg Drokin wrote:
> On Sun, Jun 15, 2003 at 03:08:39PM +0200, Till Gerken wrote:
> > I am not able to mount my ReiserFS partition as root partition with any
> > kernel later than 2.4.20-pre11. When trying, I get
> > read_super_block: can't find a reiserfs filesystem on (dev 03:00, block
> > 64, size 1024)
>
> Are you sure you want to mount /dev/hda as opposed to some partition on
> /dev/hda? Please check that you are mounting correct thing (root= option in
> lilo.conf for example).

I stumbled about the same. I want to mount /dev/hda1 as root.

till@wallace:~> cat /proc/partitions
major minor  #blocks  name

   3     0   80418240 hda
   3     1   80418239 hda1
   3    64   39088896 hdb
   3    65   18434556 hdb1
   3    66          1 hdb2
   3    69     514079 hdb5
   3    70   14852092 hdb6

The above indicates that it should try device 03:01, I guess. My grub line 
however is

kernel (hd0,0)/boot/vmlinuz-2.4.21 root=/dev/hda1,rw hdc=ide-scsi pci=biosirq 
idebus=66

The weird thing is that the above line works with a kernel up to 2.4.20-pre11, 
any later kernel with exact the same configuration will print the error 
quoted in my original mail.

Till
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE+7YsOFwwirB11AGMRAqeBAJ4muMPiYJha6nMGkL1xFdoRswG+mACfcnKR
uuSV1eA2piVXLM9JxmpL7FQ=
=EgLx
-----END PGP SIGNATURE-----

Re: Problem mounting ReiserFS as root partition

[Oleg Drokin]

Hello!

On Mon, Jun 16, 2003 at 11:16:52AM +0200, Till Gerken wrote:

> kernel (hd0,0)/boot/vmlinuz-2.4.21 root=/dev/hda1,rw hdc=ide-scsi pci=biosirq 
> idebus=66

I suggest you to replace the comma between "root=/dev/hda1" and "rw" with space.
 
Bye,
    Oleg

Re: Problem mounting ReiserFS as root partition

[Till Gerken]

On Monday 16 June 2003 11:21, Oleg Drokin wrote:
> On Mon, Jun 16, 2003 at 11:16:52AM +0200, Till Gerken wrote:
> > kernel (hd0,0)/boot/vmlinuz-2.4.21 root=/dev/hda1,rw hdc=ide-scsi
> > pci=biosirq idebus=66
>
> I suggest you to replace the comma between "root=/dev/hda1" and "rw" with
> space.

You are right, that did the trick. Since I have been using that configuration 
file for well over a year, I assumed it to be correct - especially since it 
worked as expected.

Thanks for the tip,

Till