Hi all,

 

I'm having a bit of trouble after a power cut 

 

Unfortunately my UPS failed and the power got cut to my unRAID server as well. The server wasn't actually doing anything significant at the time, just idling, as it were. However after rebooting i discovered that when i tried to open iTunes on my computer (the library is on an unRAID share) all my shares became unavailable. The GUI is still accessible and when looking at the 'main' page, everything seems to be alright, but when checking my syslog these lines are just being repeated over and over, until i reboot the system...

 

May 12 19:52:10 unRAID emhttp: get_filesystem_status: statfs: /mnt/user/iTunes Transport endpoint is not connected (Other emhttp)
May 12 19:52:13 unRAID emhttp: get_filesystem_status: statfs: /mnt/user/Files and Programs Transport endpoint is not connected (Other emhttp)
May 12 19:52:13 unRAID emhttp: get_filesystem_status: statfs: /mnt/user/Media Transport endpoint is not connected (Other emhttp)
May 12 19:52:13 unRAID emhttp: get_filesystem_status: statfs: /mnt/user/Minecraft Transport endpoint is not connected (Other emhttp)
May 12 19:52:13 unRAID emhttp: get_filesystem_status: statfs: /mnt/user/PLEX Transport endpoint is not connected (Other emhttp)
May 12 19:52:13 unRAID emhttp: get_filesystem_status: statfs: /mnt/user/Usenet Transport endpoint is not connected (Other emhttp)
May 12 19:52:13 unRAID emhttp: get_filesystem_status: statfs: /mnt/user/iTunes Transport endpoint is not connected (Other emhttp)
May 12 19:52:13 unRAID emhttp: get_filesystem_status: statfs: /mnt/user/Files and Programs Transport endpoint is not connected (Other emhttp)
May 12 19:52:13 unRAID emhttp: get_filesystem_status: statfs: /mnt/user/Media Transport endpoint is not connected (Other emhttp)
May 12 19:52:13 unRAID emhttp: get_filesystem_status: statfs: /mnt/user/Minecraft Transport endpoint is not connected (Other emhttp)
May 12 19:52:13 unRAID emhttp: get_filesystem_status: statfs: /mnt/user/PLEX Transport endpoint is not connected (Other emhttp)
May 12 19:52:13 unRAID emhttp: get_filesystem_status: statfs: /mnt/user/Usenet Transport endpoint is not connected (Other emhttp)
May 12 19:52:13 unRAID emhttp: get_filesystem_status: statfs: /mnt/user/iTunes Transport endpoint is not connected (Other emhttp)

 

Each line refers to a different one of ,my 6 shares... 'Files and Programs', 'Media', 'Minecraft', 'PLEX', 'Usenet', 'iTunes'.

I have read this thread http://216.119.154.106/forum/index.php?topic=22971.0, and even tried Joe L's recommendation on page 5 about putting

ulimit -n 20000;/usr/local/sbin/emhttp &

into the go script. But no change.

 

Admittedly this doesn't match my symptoms, my GUI is still accessible and i still have 50% of RAM unused.

 

I also managed to trigger the fault by trying to copy a 10gig folder of MP3's on to the server, it got to about 3% and then the shares crashed and the same thing happened in the syslog.

 

Any tips on what to do will be very appreciated,

 

Rich

 

Additional I'm adding a second copy of my syslog, this one's after a reboot, but before the shares crash. I'm posting it because i think theres stuff in there now, that wasnt there before the power cut/system crash. Theres a lot of 'Other emhttp' when i look at it via unmenu... might just be me being paranoid though?

 

syslog was too big to upload, so heres the link for it https://dl.dropboxusercontent.com/u/26618776/syslog.txt

 

Second syslog... before share crash https://dl.dropboxusercontent.com/u/26618776/syslog2.txt

The key line is:

May 12 19:50:37 unRAID kernel: shfs[28040]: segfault at 3c539 ip b741cf9a sp b5b11ee4 error 4 in libc-2.11.1.so[b73aa000+15c000]

May 12 19:50:38 unRAID emhttp: get_filesystem_status: statfs: /mnt/user/Files and Programs Transport endpoint is not connected

May 12 19:50:38 unRAID emhttp: get_filesystem_status: statfs: /mnt/user/Media Transport endpoint is not connected

 

The user-share file system crashed. 

Please report this to [email protected]

Point him to this thread.

 

Joe L.

Thank you, i'll send him an email.

Just bumping the thread 

Revert to stock system for testing. See my sig.

Already tried that... same error in syslog

Does anyone know what the error in the syslig refers to? Is reinstalling the unRAID os likely to solve the problem?

 

Thank you,

 

Rich

Is reinstalling the unRAID os likely to solve the problem?

Assuming you actually did follow dgaschk's advice, reverting to a stock configuration and rebooting IS reinstalling unraid. Unraid is installed fresh to RAM on every boot, with the only modifications being done with the various files and locations called out in dgaschk's revert to stock signature. Have you also followed the check file systems part of his signature?

No I haven't, I'll do that next.

 

If its not the OS then, could a share have become corrupted and be causing this? The fault is triggered when accessing a share.

If its not the OS then, could a share have become corrupted and be causing this? The fault is triggered when accessing a share.

And that is EXACTLY why he requested you check the file-systems for corruption as described in the wiki.  The shared file-system should be able to handle any values returned from the underlying reiserfs file-system, but who knows what it returns if corrupted.  If you check the file-systems, and they are sane, then the fault IS in the unRAID shared-file-system code.

Well, I've checked the file systems and it came up ok.

I've reformatted my usb drive and put a fresh copy of unRAID on (instead of just using a fresh go script) and same problem.

 

Is it likely to be the shares then and if so, is there a way to diagnose / fix them? 

Attach a new syslog.

As suspected, a single corrupted share. I spent about 5 hours copying data, so i could delete the, then empty, share and continued with each share until the fault stopped.

 

Eventually got to the right one.