Can't mount an ext3 partition - why?

Can't mount an ext3 partition - why?

[Igor Krasnoselski]

Hello all,

maybe it's so easy... but I stuck on it:

I have a 2.4.18-3 pre-compiled kernel coming with an RH7.3
distribution. Running a system under it I create an ext-3 partition on
a secondary HDD (/dev/hdc1). All was fine, but now I have to recompile
my kernel with some new modules, and new kernel can't mount this! It
mounts my /dev/hda partitions (/, /boot and swap) without any
question, but /dev/hdc1 makes it stuck! fsck says, it has something
wrong on it... But old kernel mounts hdc1 silently, and I have no reason
to run fsck (I think).

Please tell me what I miss in the kernel config? Here's related part
of it:

#
# File systems
#
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BFS_FS is not set
CONFIG_EXT3_FS=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_UMSDOS_FS=y
CONFIG_VFAT_FS=y
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
CONFIG_TMPFS=y
CONFIG_RAMFS=y
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
# CONFIG_JFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_NTFS_FS is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
CONFIG_DEVFS_FS=y
CONFIG_DEVFS_MOUNT=y
# CONFIG_DEVFS_DEBUG is not set
CONFIG_DEVPTS_FS=y
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_EXT2_FS=y
# CONFIG_SYSV_FS is not set
CONFIG_UDF_FS=y
# CONFIG_UDF_RW is not set
CONFIG_UFS_FS=y
# CONFIG_UFS_FS_WRITE is not set

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y                   *
CONFIG_SOLARIS_X86_PARTITION=y                *
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_LDM_PARTITION is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
CONFIG_SUN_PARTITION=y                        *
CONFIG_SMB_NLS=y
CONFIG_NLS=y

* is a result of my 'experiments' with different partition types...

PC is Intel Pentium II 233, hda is 4GB Fujitsy, hdc is 80GB Maxtor
(BIOS can't detect it, so in BIOS table I choose "none").

Any comments?

-- 
Best regards,
 Igor                            mailto:iek@tut.by

Re[2]: Can't mount an ext3 partition - why?

[Igor Krasnoselski]

Hello Herbert,

HP> what does an  fsck.ext3 -fpn  on the unmounted filesystem report?

I downloaded 2.4.21 sources, made "make oldconfig" and got a new
kernel with the same behavior :(

fsck.ext3 (e2fsck 1.27 8-Mar-2002)
run all 5 passes with no error reports under an old kernel, but under
new one it says:

fsck.ext3: No such file or directory while trying to open /dev/hdc1

The superblock could not be read....
etc.

I get further into this, and I find that I have no /dev/hdc1 (and
/dev/hdc, and /dev/hda too) at all! In place of them(?), I have

/dev/discs/~disc0/disc
/dev/discs/~disc0/part1
/dev/discs/~disc0/part2
/dev/discs/~disc0/part3
/dev/discs/~disc1/disc
/dev/discs/~disc1/part1

e2fsck gets them as previous /dev/hd+ args and reports no errors.
Is this a new feature since 2.4.18-3 kernel? Or maybe this all because
I add something strange to my config, like "/dev filesystem" ?

-- 
Best regards,
 Igor                            mailto:iek@tut.by
                                 mailto:u-com@mail.ru

Re: Can't mount an ext3 partition - why?

[Brian Jackson]

devfs will do that, use devfsd to add those legacy device nodes to /dev.

--Brian

On Tuesday 17 June 2003 09:24 am, Igor Krasnoselski wrote:
> Hello Herbert,
>
> HP> what does an  fsck.ext3 -fpn  on the unmounted filesystem report?
>
> I downloaded 2.4.21 sources, made "make oldconfig" and got a new
> kernel with the same behavior :(
>
> fsck.ext3 (e2fsck 1.27 8-Mar-2002)
> run all 5 passes with no error reports under an old kernel, but under
> new one it says:
>
> fsck.ext3: No such file or directory while trying to open /dev/hdc1
>
> The superblock could not be read....
> etc.
>
> I get further into this, and I find that I have no /dev/hdc1 (and
> /dev/hdc, and /dev/hda too) at all! In place of them(?), I have
>
> /dev/discs/~disc0/disc
> /dev/discs/~disc0/part1
> /dev/discs/~disc0/part2
> /dev/discs/~disc0/part3
> /dev/discs/~disc1/disc
> /dev/discs/~disc1/part1
>
> e2fsck gets them as previous /dev/hd+ args and reports no errors.
> Is this a new feature since 2.4.18-3 kernel? Or maybe this all because
> I add something strange to my config, like "/dev filesystem" ?

-- 
OpenGFS -- http://opengfs.sourceforge.net
Home -- http://www.brianandsara.net