[solved] Can't get usermounts to work on full slackware install

[Von Loghausen]

Hello all,

 

I'm trying to get a full slackware install to work, but so far it isn't very kind to me.

I followed the wiki, except that instead of Slackware 12.x, I used 13, since I read that unraid is partially based on 13.

So far I have unraid up and running from the harddisk, I can navigate the page just fine, and samba is purring happily.

 

However, when it comes to user shares, something goes wrong. I can define usershares, but it seems like Fuse isn't working. I can see the share in the network, however it only has 1.2 GB free space (same amount as / ) instead of the 1.5TB that the disk is offering.

 

I already added rc.fuse to rc.local, just to be sure it's loaded before emhttp, but no difference.

 

System specs;

 

cpu / mobo: Atom 330 Ion

mem: 2gb

bootdisk: OZC Onyx 2 32gb SSD (reserved first 20gb for cache )

datadisk:3x 1.5 TB Samsung ecogreen (though only 1 connected right now)

 

kernel config: http://pastebin.com/kiHdk3Wv

 

http://www.dumpert.nl/mediabase/foto/e0ec614f_2010_05_17_18.00.50.jpg

Group picture

[josetann]

Try this:

 

If you forget and enable User-Shares, then try to run fuse, it won't work (even after stopping and starting the array). If you accidentally did this, here's how to fix it. Stop the array, disable User-Shares. Remove the entire /mnt/user directory using the command rm -rf /mnt/user (note that if you copied anything to a User-Share when it was not working properly, this will completely delete it, you've been warned!). Start the array. Stop it again and enable User-Shares. Start it back up, and it should work. You will need to have fuse start up in your rc.local file before emhttp does.

[Von Loghausen]

Tried that, unfortunately it didn't work.

[BRiT]

First make sure you have all the libraries available for the user shares and emhttp:

 

ldd /usr/local/sbin/shfs

ldd /usr/local/sbin/emhttp

 

If either is missing a library, you might need to copy it over from the extracted bzroot 4.5.4 image.

 

As for fuse being started, it should be handled via the /etc/rc.d/rc.S script which should be invoked before any rc.local script is.

 

Also make sure that /boot/config is a symlink to /flash/config and that /flash is mounted by label in /etc/fstab.

 

/dev/disk/by-label/UNRAID /flash vfat rw,noatime,nodiratime,umask=0,shortname=mixed 0 0

 

[Von Loghausen]

Ah, it seems like I had the wrong libfuse.so linked, 2.7 instead of 2.8.1...

Rebooting now...

 

Aaaaand it works!

Sir BRiT... you are truly worthy of you hero subtitle

 

Now on to the daunting task of installing xbmc on top of unRAID...

[gswarriorfan]

oh man sounds like an awesome project you got going!  keep us posted!

[Von Loghausen]

I guess I've been spoiled by things like apt-get and yum, but after a whole night of downloading dependencies (and their dependencies, and Their dependencies) from slackbuilds.org I have compiled a version of XBMC with vdpau support.

Unfortunately it's complaining about a lack of openGL when it starts, even though I've installed the nvidia closed source driver. Still, I think this should be doable, and I'm sure that slowly I'll get there.

[Joe L.]

I guess I've been spoiled by things like apt-get and yum, but after a whole night of downloading dependencies (and their dependencies, and Their dependencies) from slackbuilds.org I have compiled a version of XBMC with vdpau support.

Unfortunately it's complaining about a lack of openGL when it starts, even though I've installed the nvidia closed source driver. Still, I think this should be doable, and I'm sure that slowly I'll get there.

I'm impressed...  It sounds like you are getting close.

[Von Loghausen]

And it's working!

 

As it turns out, the glxinfo in slack 13 is a dud, that's why xbmc is complaining. I followed the advice in this post and got it working.

 

Several days ago I contacted Pat about the issue. He said the development team was aware of the change. He did not say whether he would change anything with the next round of Current.

 

In my case, XBMC would not start because the software was trying to extract information from the traditional glxinfo command (specifically looking for GL support).

 

I extracted the glxinfo command from 12.2 (x/mesa-7.0.3 package), broke the newer sym link, and then installed the older glxinfo. XBMC then started with no complaints.

 

I'm still not there yet, as sound isn't working, and I also want to use a usb IR receiver I got from a mediacenter. The latter isn't as important though, since the remotes batteries are dead anyway.

[Von Loghausen]

Who would have thought that getting sound to work was so hard.

It turned out I needed a newer version of Alsa. However, getting that to compile was a PITA. I kept getting Unknown Symbol errors on modprobe.

Turns out that, contrary to what the alsa guide describes, you have to compile as many alsa modules from the kernel as possible instead of only soundcore.

With that done, the alsa 1.0.23 drivers were recognized by the kernel and voila: S/PDIF output.

Now... lessee if I can get that USB IR-receiver to work with lirc...