LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 12-06-2013, 12:50 AM   #1
hedron
Member
 
Registered: Jul 2009
Location: NYC
Distribution: Slackware, Bluewhite
Posts: 225

Rep: Reputation: 23
fuse control filesystem already available


I just compiled kernel 3.12.3 and it keeps giving me the above error. It then interrupts the boot process and says that an error occurred during the root filesystem check and I should do an fsck. This was just after the USB devices were scanned by the kernel.

I already tried booting with the install disc and running fsck.ext4. So, I don't think it's that. I believe that I have something set incorrectly in make menuconfig. Tomorrow, I'm going to try disabling fuse altogether.

I'm just thinking that maybe someone here has a better idea. Well, better than google, since google has no clue on the issue.
 
Old 12-06-2013, 05:04 AM   #2
ReaperX7
Senior Member
 
Registered: Jul 2011
Location: California
Distribution: LFS-7.6, Slackware 14.1, FreeBSD 10.1
Posts: 3,849
Blog Entries: 15

Rep: Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189
Certain packages that use various parts of the kernel often must be rebuilt against a new kernel and fuse isn't exempt from this if you change major kernel revisions.

You may have to chroot back in and rebuild fuse's module.
 
Old 12-06-2013, 07:32 PM   #3
hedron
Member
 
Registered: Jul 2009
Location: NYC
Distribution: Slackware, Bluewhite
Posts: 225

Original Poster
Rep: Reputation: 23
Hmm.. I did removepkg fuse-blah-blah and now the boot sequence halts at the same time right after the USB except it doesn't mention anything about fuse. I don't know what fuse is and I don't think I'll even use it.

The error message now reads:

Testing root filesystem status read-only filesytem
checking root filesystem
fsck.ext4 exec format error

**an error occurred during the root filesystem check. **
** you will now be given a chance to log into the ***
** system single user blah blah ... ***

...or so...

Quote:
Originally Posted by ReaperX7
You may have to chroot back in and rebuild fuse's module.
Are you telling me there's no way to do this without jumping through hoops? I'm not really sure what you mean. I don't know how to cross compile. It's hard enough deciphering whether or not I need CRC functions or not or why I am being forced to select some of them. There isn't whole lot of explanation in regards to some of the more cryptic kernel options. I generally go by the rule that if I don't know what it is, then I don't need it. But that usually leads me into perplexing errors like this one.
 
Old 12-06-2013, 11:41 PM   #4
ReaperX7
Senior Member
 
Registered: Jul 2011
Location: California
Distribution: LFS-7.6, Slackware 14.1, FreeBSD 10.1
Posts: 3,849
Blog Entries: 15

Rep: Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189Reputation: 1189
When you built the kernel did you go off a Slackware kernel config schematic?
 
Old 12-07-2013, 01:06 AM   #5
hedron
Member
 
Registered: Jul 2009
Location: NYC
Distribution: Slackware, Bluewhite
Posts: 225

Original Poster
Rep: Reputation: 23
I started with the default huge smp kernel config and removed a ton of stuff I thought wasn't needed. Basically, I'd come across an option and if it was a device I knew wasn't part of my set up I'd disable it. If it was an option I'd generally do what my intuition told me to do superseded by what the help file told me to do. I know that's not entirely scientific, but lacking a thorough guide to hold my hand it's the only way I can do it.

I briefly searched for a minimal config file. I'll into it in more detail tomorrow.
 
Old 12-07-2013, 02:15 AM   #6
gnashley
Amigo developer
 
Registered: Dec 2003
Location: Germany
Distribution: Slackware
Posts: 4,775

Rep: Reputation: 481Reputation: 481Reputation: 481Reputation: 481Reputation: 481
I'd sooner use the config file for the generic kernel as a starting point. For most setups, all you need to add is support for your root '/' filesystem as a hard-linked option. Then, just leave the rest alone -as modules.
 
Old 12-07-2013, 05:18 AM   #7
turtleli
Member
 
Registered: Aug 2012
Location: UK
Posts: 162

Rep: Reputation: Disabled
Quote:
Originally Posted by hedron View Post
I don't know what fuse is and I don't think I'll even use it.
Fuse is for userspace filesystems i.e. ntfs-3g. It is not your source of problems.

Quote:
Originally Posted by hedron View Post
fsck.ext4 exec format error
This looks like the source of the problem. Can you check if CONFIG_BINFMT_SCRIPT is enabled in your kernel configuration (Executable file formats / Emulations -> Kernel support for scripts starting with #!)? fsck.ext4 is a script called by fsck which cannot run if support is disabled.

Is there a reason you need to compile a newer kernel?

Quote:
Originally Posted by ReaperX7 View Post
Certain packages that use various parts of the kernel often must be rebuilt against a new kernel and fuse isn't exempt from this if you change major kernel revisions.
I don't think this is true except for packages which have external kernel modules. Do you have examples otherwise?
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: User Data Encryption with FUSE-based EncFS filesystem LXer Syndicated Linux News 0 02-01-2013 06:21 PM
[SOLVED] FUSE filesystem SETATTR function not implemented smeezekitty Programming 2 11-18-2009 01:52 PM
Fuse filesystem instead of NTFS? DirkDiggler Linux - General 4 06-02-2007 08:05 PM
encrypted filesystem without loopback device and fuse - possible? nilsglow Linux - Security 3 02-17-2006 09:07 AM
shared filesystem crap: shfs, sshfs, lufs, fuse whansard Linux - Networking 1 06-26-2005 08:58 PM


All times are GMT -5. The time now is 08:15 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration