Skip to contentSkip to conversation

Can't mount an ext3 partition - why?

DISCUSSION Igor Krasnoselski 3 participants 3 messages Jun 17, 2003 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

Igor Krasnoselski

author
#1 lore raw

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" ?

Signature · 3 lines
Best regards,
 Igor                            mailto:[email protected]
                                 mailto:[email protected]
#2 lore raw
Quoted 3 lines · Igor Krasnoselski

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" ?

And CONFIG_DEVFS_MOUNT=y , right? Install devfsd, or modify fstab, or use the devfs=nomount boot parameter.

Geller Sandor <[email protected]>

#3 lore raw
In reply to Igor Krasnoselski

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

--Brian

Quoted 29 lines · 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" ?

Signature · 2 lines
OpenGFS -- http://opengfs.sourceforge.net
Home -- http://www.brianandsara.net