I have setup a USB ext. 300GB HD as a media drive, and, long story short, can mount it manually, but during boot I receive an error, and it mounts, but with two faileds (I need to reboot, sorry, I don't know the exact faileds... the second and 5th (last) I'm pretty sure). I've basically tracked down the problem trying to manually mount like this...
$ sudo mount /dev/sda1 /media/media_drive -t ntfs-3g -r -o umask=0222
WARNING: Deficient FUSE kernel module detected. Some driver features are
not available (swap file on NTFS, boot from NTFS by LILO), and
unmount is not safe unless it's made sure the ntfs-3g process
naturally terminates after calling 'umount'. The safe FUSE kernel
driver is included in the official Linux kernels since version
2.6.20-rc1, or in the FUSE 2.6.0 or later software packages,
except the faulty FUSE version 2.6.2. Please see the next page
for more help: http://www.ntfs-3g.org/support.html#fuse26
I went to the hyperlink, found the problem (known bug/fix apperently), and got a conflict in output from what the site said I should see, as seen here...
[QUOTE]Please check the version of the installed kernel module in the following way. The versions must be at least the same as the below ones, and only the last numbers matter in the output:

grep fuse /var/log/messages # (or dmesg | grep fuse)
kernel: fuse init (API version 7.
kernel: fuse distribution version: 2.6.0

Moreover you should also see the fuseblk line if you run the below commands:

modprobe fuse
grep fuseblk /proc/filesystems
fuseblk
heres me running the original grep
$ sudo grep fuse /var/log/messages
Password:
Mar 11 13:47:41 localhost kernel: fuse init (API version 7.7)
Mar 11 13:47:41 localhost kernel: SELinux: initialized (dev fuse, type fuse), not configured for labeling
Mar 11 13:47:41 localhost kernel: audit(1173646061.328:6): avc: denied { mount } for pid=2568 comm="fusermount" name="/" dev=fuse ino=1 scontext=system_u:system_r:mount_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=filesystem
Mar 14 19:58:47 localhost kernel: SELinux: initialized (dev fuse, type fuse), not configured for labeling
I then tried this, and got a frozen terminal/console/not sure on all the lingo yet... lol. (Sorry that this is such an involved post. I just realized it's about about 3 questions in one <eek!>. I guess better than posting the same info all those times )
]$ sudo grep -r -s fuse d* /
Binary file /sbin/ldconfig matches
Binary file /sbin/lvm.static matches
Binary file /sbin/ipppd matches
Binary file /sbin/sln matches
Binary file /sbin/e2fsck matches
Binary file /sbin/dump matches
Binary file /sbin/restore.static matches
/sbin/mount.fuse:usage: ${PRGNAME} fusefs_type#[mountpath] mountpoint [FUSE options]
Binary file /sbin/rrestore matches
Binary file /sbin/lvm matches
Binary file /sbin/restore matches
Binary file /sbin/multipath.static matches
Binary file /sbin/vgscan matches
Binary file /sbin/nash matches
Binary file /sbin/mount.ntfs matches
Binary file /sbin/dump.static matches
Binary file /sbin/cryptsetup matches
Binary file /sbin/rdump.static matches
Binary file /sbin/udevd.static matches
Binary file /sbin/fsck.ext2 matches
Binary file /sbin/dhclient matches
Binary file /sbin/rmt matches
Binary file /sbin/mdadm.static matches
Binary file /sbin/mount.ntfs-3g matches
Binary file /sbin/kpartx.static matches
Binary file /sbin/rdump matches
Binary file /sbin/mdassemble.static matches
Binary file /sbin/insmod.static matches
Binary file /sbin/grub matches
Binary file /sbin/fsck.ext3 matches
Binary file /sbin/dmsetup.static matches
Binary file /sbin/dmraid.static matches
Binary file /sbin/vgchange matches
Binary file /sbin/fuser matches
Binary file /sbin/rrestore.static matches
Binary file /sbin/pvscan matches
Binary file /sbin/mount.ntfs-fuse matches
q
x
^[
exit
break
^B
You can see where I am in terms of newbiness based on all that Anways, my questions are :
1 - Why am I not showing the "fuse distribution..." but am showing "fuse int", albeit with a lower ver. number than needed (which I feel fully capable of following the directions on the site and fixing it, but NOT getting the same output has made me want to make sure I don't do further damage, and, honestelly, it's fun to know WHY something's fixed, versus just copying and pasting snippets) when I do the original grep etc.?
2 - Why did the second grep I did (my own idea... lil too confident already I think I've been proven, lol) freeze? (I've had that happen when using the console once before, and just X'd it and opened a new one, but in the vein of really wanting to know what's going on, and at least knowing where to begin my search in future, should this, or anything, happen again, I've left the window open, and want to know how to actually get out of this )
3 - How do I get out of this "freeze"/what caused/es it?

Thank you in advance,Elv1n06