Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hey, I've been having a problem recently with an error I am getting in Slackware at boot time about a filesystem error...I'm never able to fully catch what it says (I'm not sure where the log would be located...tried looking some but no luck). All I know is its hda6 (/var) and says something about setskip. Any ideas?
I'm actually rather curious as to where the error log is kept so I can fully see what it says...not sure where it is though. I have noticed in my fstab that it runs fsck for each filesystem...I could turn em off but it does concern me.
Found syslog and messages...nothing about kern.log though. Here's a snippet of my syslog log that may/may not help...it really doesn't give much any more details than that.
Quote:
Mar 16 00:05:51 linux kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Mar 16 00:05:52 linux kernel: shpchp: shpc_init : shpc_cap_offset == 0
Mar 16 00:05:52 linux insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Mar 16 00:05:52 linux insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
I don't know if you all can decipher it or not. I know at bootup it tells me what filesystem/mountpoint and everything.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.