fuse: device not found, try 'modprobe fuse' first

cairn · 2017-04-09 14:25:00

As of a few months ago, whenever I try to mount an encrypted drive in VeraCrypt, I get this error: "fuse: device not found, try 'modprobe fuse' first"

1. "sudo modprobe fuse" gives:
modprobe: ERROR: could not insert 'fuse': Unknown symbol in module, or unknown parameter (see dmesg)

2. dmesg gives:
fuse: Unknown symbol setattr_prepare (err 0)

I've searched the forums and the only possibly relevant thing I see is a suggestion to update to the most recent kernel (the one in jessie backports). Unfortunately, this presents its own problems for me. I used apt-get to install the latest kernel (successfully), but I cannot boot it; it does not show up in grub, and I can't figure out how to update grub, probably because I have grub on a separate, usb partition (I'll be damned if I can remember why I thought that would be a good idea).

So, I'm hoping someone can either give me an easy way to fix the fuse problem, or else explain how to update grub when it's installed on an external, usb partition.

Thanks a lot.

Last edited by cairn (2017-04-09 14:25:53)

damo · 2017-04-09 14:39:32

Ref grub, can you boot at all? If so, run 'sudo update-grub' from the partition where you installed the new kernel - it should now appear (probably under the "Advanced" section in the grub menu) when you reboot. If you can now start that then run

sudo grub-install /dev/[wherever] && sudo update-grub

Head_on_a_Stick · 2017-04-09 14:56:03

I going to hazard a guess that your installed kernel (and hence modules) does not match your running kernel.

You should follow damo's fine advice

A backported kernel should not be needed and should probably not be used.

cairn · 2017-04-09 14:57:23

I tried the following:

#Installing the new kernel
sudo tee -a /etc/apt/sources.list <<< "deb http://httpredir.debian.org/debian jessie-backports main"

sudo apt update && sudo apt install linux-image-amd64/jessie-backports

#This output the following [I'd done the install once before, which is why it says nothing new was installed]:
linux-image-amd64 is already the newest version.
Selected version '4.9+79~bpo8+1' (Debian Backports:jessie-backports [amd64]) for 'linux-image-amd64'
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

#Updating grub
sudo update-grub

#This output the following:
Generating grub configuration file ...
Found background image: .background_cache.png
Found linux image: /boot/vmlinuz-3.16.0-4-amd64
Found initrd image: /boot/initrd.img-3.16.0-4-amd64
done

To me, this reads like grub has not been updated. And, indeed, the new kernel does not appear in grub at reboot, whether under advanced, or anywhere else.

EDIT:
damo, when you say to run

sudo grub-install /dev/[wherever] && sudo update-grub

I don't understand what this is supposed to do. Are you suggesting that I install grub onto my main partition (where root is installed) vs the external partition it is currently on? [apologies if this is a really stupid question]

Last edited by cairn (2017-04-09 15:02:01)

damo · 2017-04-09 15:10:06

^ Install grub to wherever you have decided you want it. The usual place is '/dev/sda', but you imply that you have it in a more exotic location.

PS Please use [ code ] tags for terminal output - it makes it much easier to read

Head_on_a_Stick · 2017-04-09 15:14:36

cairn wrote:

when you say to run
sudo grub-install /dev/[wherever] && sudo update-grub
I don't understand what this is supposed to do. Are you suggesting that I install grub onto my main partition (where root is installed) vs the external partition it is currently on?

Good question

You should install the GRUB bootloader the the MBR of your main drive, this is probably /dev/sda but we should check:

lsblk

Note that a partition number should *not* be used in the `grub-install` command.

Alternatively, you could add a menu entry for BunsenLabs to your USB stick's /etc/grub.d/40_custom that would always boot the correct kernel; read this post for details:

https://forums.bunsenlabs.org/viewtopic … 324#p47324

cairn · 2017-04-09 16:01:27

for some reason, when I ran:

sudo grub-install /dev/sdd && sudo update-grub

I got:

Installing for i386-pc platform.
Installation finished. No error reported.
Generating grub configuration file ...
Found background image: .background_cache.png
Found linux image: /boot/vmlinuz-3.16.0-4-amd64
Found initrd image: /boot/initrd.img-3.16.0-4-amd64
done

I don't know why the i386 platform was used, and I don't know why the old kernel was used.

Any ideas?

Head_on_a_Stick · 2017-04-09 21:07:41

cairn wrote:

why the i386 platform was used

That message indicates that a non-UEFI bootloader has been installed, I have no idea why GRUB calls it that

why the old kernel was used

Can we see the output of:

ls /boot
apt search "linux-image-*" | grep installed

ohnonot · 2017-04-10 06:27:31

there's never any real work for me to do here, because certain power users seem to living in the forums...
but i'll just chime in and confirm that fuse always forces me to reboot after a kernel upgrade, so right the track you are on.

#1 2017-04-09 14:25:00

fuse: device not found, try 'modprobe fuse' first

#2 2017-04-09 14:39:32

Re: fuse: device not found, try 'modprobe fuse' first

#3 2017-04-09 14:56:03

Re: fuse: device not found, try 'modprobe fuse' first

#4 2017-04-09 14:57:23

Re: fuse: device not found, try 'modprobe fuse' first

#5 2017-04-09 15:10:06

Re: fuse: device not found, try 'modprobe fuse' first

#6 2017-04-09 15:14:36

Re: fuse: device not found, try 'modprobe fuse' first

#7 2017-04-09 16:01:27

Re: fuse: device not found, try 'modprobe fuse' first

#8 2017-04-09 21:07:41

Re: fuse: device not found, try 'modprobe fuse' first

#9 2017-04-10 06:27:31

Re: fuse: device not found, try 'modprobe fuse' first

Board footer