I've spent the last 3 days scouring the forum looking for an answer to my problem. I upgraded from 4.7 to 5.0.11 to run the plex plug-in. I followed the instructions as per the wiki, did the permissions. Do I have to re add the shares or should they have been picked up with the upgrade? I can see the disks through finder as disk1/movies or disk2/photos.

They should have been picked-up. Any top level directory on a disk should appear as a user share.

 

Are the user shares still enabled? Did you try stopping and starting the array or rebooting?

 

 

The shares are enabled, I've made sure that all discs are listed in the "Included Disk(s)" section. It seems after every reboot the new shares I created(to see if I created new one if I could move the files to them) are deleted. The only one that is created and visible is the one made by sabnzbd.

When I do create new shares, when I go to add a file to the folder I get a error saying there isn't enough free space.

 

Here's the shares setting:

 

 

Name: Images

Comments:

Allocation method: High water

Min. free space:   86598754

Split level:   1

Included disk(s): disk1

Excluded disk(s): disk2, disk3, disk4, disk5

Share empty? No

 

 

 

 

The last person with this issue had a corrupt filesystem on his cache disk, but I would expect that any disk being corrupt could cause this. A syslog would help because it would show that either user or user0 failed to mount.

 

You can log onto the server and see if both /mnt/user and /mnt/user0 directories exist. Note that user0 will only exist if you have a cache disk.

 

You can also look-up the reiserfsck filesystem check procedure in the Wiki and follow that to test every data drive, including the cache drive.

 

Peter

 

Thanks Peter for the help!

 

Ran reiserfsck on all data drives,there were no corruption's found.

Checked the system log and I think (mainly because I have no idea what I'm looking for) the the user isn't mounting. I'll attach the syslog maybe someone can have a quick look to confirm.

If the user isn't mounting, how do I go about correcting it so user will mount on boot?

syslog-2011-11-11.txt

Do you have a cache drive?

 

If yes, try unassigning it and re-starting the array.

 

If not, then I still suspect some type of disk issue but I have no idea what. An email to Limetech might be a good idea.

 

The shutdown is strange with it saying user isn't mounted and that user isn't empty. Hmm, maybe something got written to the user directory somehow. Stop the array and log-on to the server. "cd /mnt/user" and "ls" and lets see what is there?

 

Peter

No cache drive.

 

did the "cd /mnt/user" then "ls"

 

this is what appeared after ls:

 

Downloads/ 

You must have an add-on that created that directory before the array was initialized. SABnzbd maybe?

 

Stop the add-on, "cd /mnt", "rm -r user" and then start the array and I'm betting it will work.

 

FYI, you should never have to create an existing user share if they are enabled. Any top level directory on a disk is automatically considered a user share.

 

You also need to figure out what add-on and delay it starting. If you start it via the go script then you can add a delay.

 

Peter

There are some odd repeating lines about "umount /user" in the syslog. Run check disk on the Flash in a PC. Disable all add-ons and restart.

If I erased the flash drive and started over. Would I lose any data on the drive? Would they still be accessible? Would taking the contents of the zip and over writing the files possibly help(not just bzroot and bzimage)? The only add-on I have running is SABNZD.

Erasing the flash drive would mostly be a waste of time because then you have to set everything back up again and then if you add SABnzbd again the same way you will again have the same problem. You just have to stop SABnzbd from creating that /mnt/user/Downloads directory.

 

Did you try stopping SABnzbd and then deleting the directory as I already suggested?

 

You could also delete your old SABnzbd install and try one of the new packages for the beta series.

 

Peter

 

 

I looked at the go script and there was another plug-in starting as well(sub-sonic), along with another command for SABnzb to start(perhaps from the original release of the plug-in that I inadvertently forgot to remove the command...more than likely). Deleted those two plus the new SABnzb and rebooted, now my shares are visible. I'll give the new packages for beta installs a go.

 

  Thanks for all your help Peter, greatly appreciated.

Good to hear. You can also change the title to included [solved] now.