Hi all,

I'm new to this side of the tech world so forgive me if I miss anything obvious. I have my Unraid set up on an old Dell r210 II, Xeon E3-1240 @ 3.4Ghz, 16GB DDR3. It runs fine all day with all dockers working perfectly and its nice and fast to work with and use e.t.c. but every night it has some sort of error, Unraid continues to work but all the dockers become unresponsive and I can't access the drive remotely through my Windows PC any more. All i have to do is restart the server and all is well but then it just happens again the next night. Here is the error from the logs, i've posted the errors from 3 different nights and i notice they're all at the exact same time - its not related to how long the server has been running as it had different uptimes;

Nov  4 03:40:01 Tower kernel: shfs[23621]: segfault at 0 ip 0000000000403bd6 sp 000014b4ac5cf930 error 4 in shfs[403000+c000]
Nov  4 03:40:01 Tower kernel: Code: 89 7d f8 48 89 75 f0 eb 1d 48 8b 55 f0 48 8d 42 01 48 89 45 f0 48 8b 45 f8 48 8d 48 01 48 89 4d f8 0f b6 12 88 10 48 8b 45 f0 <0f> b6 00 84 c0 74 0b 48 8b 45 f0 0f b6 00 3c 2f 75 cd 48 8b 45 f8
  
  
  
Nov  5 03:40:01 Tower kernel: shfs[8739]: segfault at 0 ip 0000000000403bd6 sp 000014adc39b7930 error 4 in shfs[403000+c000]
Nov  5 03:40:01 Tower kernel: Code: 89 7d f8 48 89 75 f0 eb 1d 48 8b 55 f0 48 8d 42 01 48 89 45 f0 48 8b 45 f8 48 8d 48 01 48 89 4d f8 0f b6 12 88 10 48 8b 45 f0 <0f> b6 00 84 c0 74 0b 48 8b 45 f0 0f b6 00 3c 2f 75 cd 48 8b 45 f8

  

Nov  8 03:40:01 Tower kernel: shfs[23292]: segfault at 0 ip 0000000000403bd6 sp 0000146042515930 error 4 in shfs[403000+c000]
Nov  8 03:40:01 Tower kernel: Code: 89 7d f8 48 89 75 f0 eb 1d 48 8b 55 f0 48 8d 42 01 48 89 45 f0 48 8b 45 f8 48 8d 48 01 48 89 4d f8 0f b6 12 88 10 48 8b 45 f0 <0f> b6 00 84 c0 74 0b 48 8b 45 f0 0f b6 00 3c 2f 75 cd 48 8b 45 f8

Would anyone be able to advise me on what this could be and what I can do to fix it?

 

Many thanks,

Dan

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.

1 hour ago, trurl said:

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.

Hi please see attached and thank you for helping 

tower-diagnostics-20201108-1418.zip

When you reboot syslog resets, so nothing in those diagnostics about those errors.

 

When do you have mover scheduled?

 

It looks like cache isn't mounting for some reason. Have you formatted it?

 

Are you planning to add parity?

2 hours ago, trurl said:

When you reboot syslog resets, so nothing in those diagnostics about those errors.

 

When do you have mover scheduled?

 

It looks like cache isn't mounting for some reason. Have you formatted it?

 

Are you planning to add parity?

Interesting, i hadn't thought of that - I'm going to run it without a cache drive for tonight and see if that affects it.

 

The cache disk was formatted and it seemed to have been mounted. It is quite an old SSD though so could possibly have faults. I'm afraid I haven't looked at / seen any settings to do with Mover so i'm not sure. I'll google a guide for it 

Not planning to add parity at this stage, its mainly a media server and anything personal I also have backed up on Gdrive and a separate USB HDD.

 

If it fails again tonight I'll update with the diagnostics again, if it works fine I guess that points to something to do with the cache drive I can then work further on.

EDIT: I've found the mover stuff, and yes indeed it seemed to have been set to 03:40am... 

Edited November 9, 20205 yr by bigdan1190

All has been working ok for a few days now, it seems removing and re-adding the cache SSD from/to the array did the trick! Thanks very much.