Hard drive problems on root partition

atheist · 05-23-2004, 08:05 PM

I would appreciate some help regarding my root partition.
I've been rebooting a couple of times tonight, which is a thing I very rarely do, and noticed a boot message I'm not too happy with:

Code:

EXT3 FS on hda2, internal journal
mount: wrong fs type, bad option, bad superblock on tmpfs, or too many mounted file systems

Now. I'm not exactly sure what this means... And could use some help with that as well as how to correct this problem.
hda2 is an ext3 file system. Ex-ext2 file system which I changed to ext3 with the "tune2fs -j" command some months ago.
Any help or suggestion greatly appreciated.

mritch · 05-24-2004, 05:29 AM

the message tells about "tmpfs". this is shared memory to be used as a kind of auto-sizing ramdisk. if you have an entry
tmpfs /dev/shm(or /tmp) tmpfs defaults
in you /etc/fstab, you maybe havn't compiled it in you kernel. i asume your partition on hda2 works ok and >is< ext3?

whansard · 05-24-2004, 05:49 AM

yeah. that error isn't about your ext3.

atheist · 05-24-2004, 08:17 PM

Yeah. My partition is ext3 and is working well too. This message just kinda bothers me...
Anyways. Heres my fstab:

Code:

# /etc/fstab: static file system information.
#
# <file system>	<mount point>	<type>	<options>		<dump>	<pass>
/dev/hda2	/		ext3	errors=remount-ro	0	1
/dev/hda4	none		swap	sw			0	0
proc		/proc		proc	defaults		0	0
#/dev/fd0	/floppy		auto	user,noauto		0	0
/dev/hdc	/cdrom		iso9660	ro,user,noauto		0	0
/dev/hda1	/boot		ext3	defaults		0	2
/dev/hdb1	/files/anime2	ext3	defaults		2	1
/dev/hda3	/files/windows	vfat	defaults,umask=002,gid=100	2	1

Nothing about /dev/shm or /dev/tmp. Any ideas of what might be going wrong here?

mritch · 05-24-2004, 08:44 PM

can you send a partially copy of your dmesg? (mounting, little bit more than above) and your /etc/modules & .config file of your kernel. thx

atheist · 05-27-2004, 04:54 PM

Sorry about the late reply. I didn't notice it.

So heres the mounting related output of dmesg:

Code:

EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 136k freed
Adding 996020k swap on /dev/hda4.  Priority:-1 extents:1
EXT3 FS on hda2, internal journal
Real Time Clock Driver v1.12
NET: Registered protocol family 17
NTFS driver 2.1.6 [Flags: R/O MODULE].
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.

Heres /etc/modules:

Code:

apm
af_packet
pci-scan
sundance
nls_cp437
binfmt_aout
nls_cp861
nls_iso8859-1
ntfs

Uhm. And you really want the .config file of my kernel? That's long... 1085 lines to be exact. No problem though if you do. Just wanted to make sure before posting something so huge.
Thanks for trying to help. I hope you see this despite the late response.

mritch · 05-27-2004, 06:08 PM

did ya got rid of that message about tmpfs after mounting hda2? it's not in the dmesg you posted above anymore. i just wanted your modules & config to check if tmpfs is enabled since that was the cause of the errormessage in your 1st post.
your fstab doesn't contain a entry for the tmpfs so i wonder too where this message was comin' from.

atheist · 05-27-2004, 06:54 PM

Hmm, kinda looks like it... although it was there the last couple of times I rebooted due to some problems. Didn't really watch the latest reboot... but I didn't really do anything to fix that either.

Searching through my kernel configuration file for tmpfs I come accross this though:

Code:

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVPTS_FS_XATTR is not set
# CONFIG_TMPFS is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y

I guess I just need to enable tmpfs, right? I'll do that before the next time I reboot then.
Thanks for the help.

mritch · 05-27-2004, 07:13 PM

you don't really need tmpfs. it's kindof ramdrive which is quite handy to have mounted on /tmp for me (usually /dev/shm). it is autosizing and uses sharedmemory.
have a look at .../kernel-source/Documentation/filesystems/tmpfs.txt for some info.