I had a fairly catastrophic failure on my system and I've been trying to recover from it. Ended up that there is just something off about my old usb stick. I've fdisk/reformatted/reinstalled/you name it and I can't get anything to work properly.

 

I've been scraping through syslog and samba logs and I'm getting nothing even remotely useful. The only clue I've had so far is that /mnt/user and /mnt/user0 (which as I understand it is the cache drive) are mounted r/o. I get as much from the cli.

 

I don't even know where to start with trying to fix that. When I go to create a user share, either it looks like it created it and in reality created nothing, or it will pop up and tell me "Share X has been deleted". I started that with my old share names. I saw a permissions thing fly through a syslog so I ran a fix permissions. Tried again, no errors, no share. Tried again, nothing. The screen would refresh clearing all the input boxes and never create a share. I have tried the same with completely new names. I get the same thing, first time it clears the input boxes, it even puts the file in place in /boot/config/shares. The second time around, it says the share was deleted and nothing.

 

At this point, I can get to my individual drives, I'm tempted to just spin up a second system as my unraid system and slowly migrate my data over.

Post up your syslog.

 

http://lime-technology.com/wiki/index.php/Troubleshooting#Capturing_your_syslog

There you are, syslog

syslog.txt

Disk 5 has some corruption and has been mounted as read-only to prevent further corruption.

 

 

Apr 30 20:06:36 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 34203 does not match to the expected one 1
Apr 30 20:06:36 Tower kernel: REISERFS error (device md5): vs-5150 search_by_key: invalid format found in block 177275. Fsck?
Apr 30 20:06:36 Tower kernel: REISERFS (device md5): Remounting filesystem read-only

 

You should run reiserfsck as per this:

 

https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems

 

I also noticed that the system started a parity check as soon as it loaded.  Either you did an unclean shutdown (just pressed the power switch), or your flash drive may also be corrupted (didn't notice in the logs).  It wouldn't hurt to put it into your desktop and run chkdsk on it.

To clear up a misconception in the OP, /mnt/user is the user shares including any files still on cache, and /mnt/user0 is the user shares not including any files still on cache.

 

Don't see the usual FAT line in the syslog for a corrupt flash, but there is this

Apr 30 20:05:15 Tower logger: Installing system plugins
Apr 30 20:05:15 Tower logger: installing plugin: webGui-latest
Apr 30 20:05:15 Tower logger: 
Apr 30 20:05:15 Tower logger: Warning: simplexml_load_file(): /boot/plugins/webGui-latest.plg:1: parser error : Document is empty in /usr/local/sbin/installplg on line 13
Apr 30 20:05:15 Tower logger: 
Apr 30 20:05:15 Tower logger: Warning: simplexml_load_file():  in /usr/local/sbin/installplg on line 13
Apr 30 20:05:15 Tower logger: 
Apr 30 20:05:15 Tower logger: Warning: simplexml_load_file(): ^ in /usr/local/sbin/installplg on line 13
Apr 30 20:05:15 Tower logger: 
Apr 30 20:05:15 Tower logger: Warning: simplexml_load_file(): /boot/plugins/webGui-latest.plg:1: parser error : Start tag expected, '<' not found in /usr/local/sbin/installplg on line 13
Apr 30 20:05:15 Tower logger: 
Apr 30 20:05:15 Tower logger: Warning: simplexml_load_file():  in /usr/local/sbin/installplg on line 13
Apr 30 20:05:15 Tower logger: 
Apr 30 20:05:15 Tower logger: Warning: simplexml_load_file(): ^ in /usr/local/sbin/installplg on line 13
Apr 30 20:05:15 Tower logger:  xml parse error

Which usually means a corrupt flash has prevented a plugin from being written.

 

Just to make sure, you don't have a drive redballed instead of just corrupt do you?