Re: Cannot mount reiser fs using patched potato kernel
You should check for the version of reiserfs that you are using. IF you have
created your file systems on a more recent version older versions might have
some problems recognizing it.
On Thursday 29 November 2001 07:06 am, Dougie Nisbet wrote:
> I have an Supemicro 370DDE machine with 4 40GB hardrives.
> The Chipset on the mobo is the Apollo Pro 266.
> I have applied the Reiser patch to the 2.2.19pre17 kernel.
> The options have appeared for Reiser in make xconfig, and they're selected.
> The kernel has re-compiled fine.
>
> I also have Mandrake 8 installed. Mandrake sees my reiser filesystems ok,
> and they were in fact created using Mandrake.
>
> When I try mounting a reiser file system using potato, I get the following:
> >>> tbird2:~# mount -t reiserfs /dev/hda10 /spare
> >>> mount: wrong fs type, bad option, bad superblock on /dev/hda10,
> >>> or too many mounted file systems
>
> I wondered if there was some subtle difference between the way Mandrake
> made reiser file systems and the reiserfsprogs-3.x.0j utils that I
> installed on potato.
> So I deleted the parition, and used mkreiserfs under potato.
> The partition is created with no errors, and I reboot. reiserfsck thinks
> it's fine too. But I cannot mount the file system.
>
> Thanks to nate for giving me a few things to check. Such as ensuring that
the partition is type 83:
> >>> tbird2:~# fdisk -l /dev/hda
> >>>
> >>> Disk /dev/hda: 255 heads, 63 sectors, 5005 cylinders
> >>> Units = cylinders of 16065 * 512 bytes
> >>>
> >>> Device Boot Start End Blocks Id System
> >>> /dev/hda1 * 1 781 6273351 b Win95 FAT32
> >>> /dev/hda2 782 5005 33929280 85 Linux extended
> >>> /dev/hda5 782 817 289138+ 82 Linux swap
> >>> /dev/hda6 818 1425 4883728+ 83 Linux
> >>> /dev/hda7 1426 2130 5662881 83 Linux
> >>> /dev/hda8 2131 3194 8546548+ 83 Linux
> >>> /dev/hda9 3195 4292 8819653+ 83 Linux
> >>> /dev/hda10 4293 5005 5727141 83 Linux
>
> The kernel has reiser support:
> >>> tbird2:/proc# cat filesystems
> >>> ext2
> >>> reiserfs
> >>> umsdos
> >>> msdos
> >>> vfat
> >>> nodev proc
> >>> nodev nfs
> >>> nodev smbfs
> >>> iso9660
> >>> nodev autofs
> >>> nodev devpts
>
> There are some error messages in the syslog, which suggest all is not well;
along the lines of:
> >>>Nov 29 11:04:30 tbird2 kernel: reiserfs_read_super: can't find a
> >>> reiserfs filesystem on dev 16:41. Nov 29 11:04:30 tbird2 kernel:
> >>> reiserfs_read_super: try to find super block in old location Nov 29
> >>> 11:04:30 tbird2 kernel: reiserfs_read_super: can't find a reiserfs
> >>> filesystem on dev 16:41.
>
> I've run out of ideas. Any suggestions welcome.
>
> Dougie
Reply to: