Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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.
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?
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.
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.
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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.