Hey,

I am getting the following error in the scroll screen during bootup:

Failed to create /dev/fuse: Permission denied
Fusermount: fuse device not found, try 'mod probe' first
FUSE mount point creation failed
Unmounting /dev/hda1

Hda1 is my ntfs Windows partition. I upated my kerenel (thanks to Okie) because I was recieving this message before. It was my understanding it would go away after updating the kernel... it didn't. I put in the command 'mount -a' and here is what 'mount' has to say:
/dev/hda1 on /mnt/windows type fuseblk (rw,nosuid,nodev,noatime,allow_other,default_permissions,blksize=4096)

All is well with the world and I can read/write to the NTFS partition. Why wount it mount at startup? I have the most recent version of Fuse as far as I know.

Thanks,

Brandon

is it in your fstab? (/etc/fstab)
if not, add it.

you could allso try to set the mount command in /etc/bash.rc or /etc/profile, but i'm not sure of those.

if these won't work, could you post the output?

The Windows partition is in my fstab, which is why it attempts to mount during the bootup. Those messages come up during the initialization screen.

Any other ideas?

Regards,

Brandon

Check whether /dev/fuse actually exists. If not, as root:

mknod /dev/fuse -m 0660 c 10 229

Whether it existed or you just created it, you also need to do this:

chown root.fuse /dev/fuse

Thanks Jay, I'll do that as soon as I get home. If you don't mind, could you please give me a layman explanation as to what those commands mean? I believe the mknod is something along the lines of making a node? The chown command I'm not familiar with.

Thanks for your help,

Brandon

Jay,

I performed the commands you gave and it doesn't seem as though they're sticking. It creates the character device with mknod. I had some trouble with 'chown root.fuse /dev/fuse'. It kept telling me that root was an invalid user. Ater trying different ways of entering it, I came up with 'chown root /dev/fuse' That was accepted. I rebooted and came up with the same error as stated in the first post. So, I went to my /dev folder and the fuse character device was gone! I'm assumimg this is why I got the error message again. Please advise on what to try next

Thanks,

Brandon

Hmm, it's been a while since I used these commands so I may just possibly have slipped in a typo. Could you do it over, using

chown root:fuse

this time - notice the colon.

What these commands do is this:
mknod makes an interface to your hardware; if you look in the /dev directory, you will find plenty of files to allow your operating system to interact with the hardware. /dev/cdrom and /dev/sda are obvious, I think; then there is also, for example, /dev/dsp, which is an interface to sound devices. These nodes also tell the operating system which drivers to use (that is the 10 229 part in your case, "major" and "minor" respectively as they are known, i.e. which category of driver and which specific subtype of that category).
The chown part changes the owner of the /dev/fuse file; /it needs to be owned by user root and group fuse - which is why we use root:fuse. Which makes me wonder: is there actually a fuse group on your system? Check the output of

groups

If you don't see any "fuse" in there, that could be the root of this whole issue.

Jay,

You've hit the nail in the head. There is no fuse group. At first I had kernel 2.6.18, and I installed the ntfs-3g driver (along with libfuse, a dependency). It said that I would need to upgrade the kernel to 2.6.20n and I did. Is it possible that the libfuse got lost during the upgrade or are the two completely unrelated? Just so you know, the groups present are: root, bin, daemon, sys, adm, disk, wheel. So, the next question is, how do we make a fuse group? I'll research and see if I can find anything. Any more help is much appreciated.

Regrads,

Branon

Hey,

After looking it up, it appears that I will download fuse from fuse.sourcedorge.net and install it. After that, I'll perform the commands previously mentioned. I'll post the results. If there is anything to add, please do.

Thanks,

Brandon

"how do we make a fuse group?" -- addgroupor groupadd. If the man pages aren't enough, feel free to ask ...

Nothing more to add for now. And yes, I imagine that the problem is a consequence of the kernel upgrade; anything that is closely related to the kernel needs to be upgraded as well.

Thank you guys, I'm still in the early infancy stages with Linux. All your help is much appreciated. I'll perform these tasks when I get home. Just to confirm, by installing fuse, will this automatically create fuse group? If it doesn't, I'll add the group with the command told to me by Archtoad. Then, I'll create the character device for fuse. Wish me luck.

Thanks,

Brandon

Yes, it should. But before you install any new packages, I suggest that you simply try adding the fuse group manually. It that helps, you won't even need to install anything anymore. As you can mount the ntfs partition from the command line, your fuse appears to be fine - it's probably on the absence of a fuse group that is preventing the system from mounting the partition automatically.

Hey,

So, I tried adding adding the group 'fuse' with the '/usr/sbin/groupadd fuse' command. Everything went Ok. I proceeded to do the mknod and chown commands, went off without a hitch. I rebooted and recieved the same error. Also, in the beginning, before it gets to the fuse portion, it says 'mounting local filesystems: failed'. I don't know if that's an indication of anything other than what it says, but I'm telling you. Now, I don't know if this tells you anything, when I enter the 'groups' command, fuse does not pop up. Only the aforementioned ones do. When try to add the group again, it says it exists. I'm just not sure where it exists. Now, I tried installing fuse from source, rebooted and same error. Tried redoing all of the previous commands, rebooted and still the same problem. Even after doinf the mknod comand, the character device disappears still! Hopefully you guys aren't out of ideas yet. Please advise further.

Thanks,

Brandon.

That is probably because you are using the groups command as either a regular user or as root. Plain "groups" only show the groups that your user or root belongs to. If you added root to the fuse group, however, it should show up if your run "groups" as root. If you want to see whether fuse exists, you need to run the groups command for user fuse:

groups fuse

As a graphical equivalent of this command, you can simply have a peep at /etc/group - the file that lists all existing groups on your system.

You can also try this to avoid the groups issue altogether:

mknod --mode=0660 /dev/fuse c 10 229
chown root.root /dev/fuse
depmod
/sbin/ldconfig