Network Shares Dropping Randomly

[NotYetRated]

Hello, brand new to unRaid, so sorry for any basic missing info or ignorance here.

 

I have installed UnRAID 6.1rc6, with the following hardware and setup:

 

e3-1245V3

ASROCK 226ws mobo

32GB RAM

Drives Currently:

Array:

3TB

2TB

 

Cache:

240 Intel SSD

 

Unassigned:

4TB (will be parity)

250GB old HDD, want to use to downloads/scrap

 

I got things set up, created some folder shares for my tv/movies/other files, and set the SMB share settings to allow access to all for now. I have begun transferring 4TB of data(I have 12 total to move over), and every 500GB or so, the shares drop out and my windows 10 rig sending the files gets "file interruption". When that happens, I notice, from any box, I cannot access my unRaid shares. On the unRaid webUI, the "shares" tab appears blank. My only option is to spin down the array, restart unRaid, and the proceed with the transfers. This is time consuming and concerning.

 

I am unsure how to provide any logs for such an error. If anyone can chime in with suggestions/assistance, I would appreciate it.

[RobJ]

Please see Need help? Read me first!, and attach a Diagnostics zip.  Thank you!

[NotYetRated]

Please see Need help? Read me first!, and attach a Diagnostics zip.  Thank you!

 

 

So sorry, I had not noticed that post. Long day a good excuse? haha.  report attached, this is from immediately following a total crash of unRaid. Had to power button off/on the box. Have resumed transferring, will attach another report if the shares drop out again. (this is the first time i had a total crash).

 

Additional info:

 

Currently no plugins

2 dockers but not running. Plex Media Server and SABnzbD by Needo.

1 VM, also not running during these transfers.

bigbang-diagnostics-20150826-1449.zip

[NotYetRated]

After about 100 gigs of transfers, the shares dropped again. Report attached.

 

EDIT: Noticed, on the "main" tab, Array devices, cache and boot devices all showed, but Unassigned Devices was not even listed.

bigbang-diagnostics-20150826-1557.zip

[NotYetRated]

Another crash, happening more often. My files transfers have moved from larger media files, in to a large amount of small image files(blue iris captures). Since this, it has been happening more frequently.

 

Data attached.

bigbang-diagnostics-20150826-1722.zip

[crcobb]

Looking at your log file you are getting a SEGFAULT.  After the fault in shfs you lose access to all your mounted disks.  I am not an expert in solving this type of issue so maybe someone else can point you in the correct direction.  You might want to start with running a memory test.

 

Aug 26 16:49:13 BigBang kernel: php[3123]: segfault at 100030 ip 000000000056e80b sp 00007ffc8374f840 error 4 in php[400000+36c000]
Aug 26 17:02:16 BigBang kernel: kvm: already loaded the other module
Aug 26 17:13:54 BigBang kernel: mdcmd (12): spindown 1
Aug 26 17:22:19 BigBang kernel: shfs[1836]: segfault at 6778 ip 00002b2f61c65687 sp 00002b2f6273e8a0 error 4 in libc-2.17.so[2b2f61b6f000+1bf000]
Aug 26 17:22:46 BigBang emhttp: get_filesystem_status: statfs: /mnt/user/VMs Transport endpoint is not connected

[NotYetRated]

Looking at your log file you are getting a SEGFAULT.  After the fault in shfs you lose access to all your mounted disks.  I am not an expert in solving this type of issue so maybe someone else can point you in the correct direction.  You might want to start with running a memory test.

 

Aug 26 16:49:13 BigBang kernel: php[3123]: segfault at 100030 ip 000000000056e80b sp 00007ffc8374f840 error 4 in php[400000+36c000]
Aug 26 17:02:16 BigBang kernel: kvm: already loaded the other module
Aug 26 17:13:54 BigBang kernel: mdcmd (12): spindown 1
Aug 26 17:22:19 BigBang kernel: shfs[1836]: segfault at 6778 ip 00002b2f61c65687 sp 00002b2f6273e8a0 error 4 in libc-2.17.so[2b2f61b6f000+1bf000]
Aug 26 17:22:46 BigBang emhttp: get_filesystem_status: statfs: /mnt/user/VMs Transport endpoint is not connected

 

Nice catch, this didn't jump out at me while I was trying to divulge the log files.

 

Interestingly enough, once I managed to get the data off of the 2 drives involved in the specific transfers giving me this issue, I have not had it again, and I have since been through 2 other hard drives dumping about 5TB of data. Problem free.

 

I've got the 2 originals I was transferring from and plan to do a HDD check on them, though I cant see how the drives I am transferring from(on a different box) would cause unRaid to drop its shares.