[6.4.1] User Shares Completely Missing

[lishpy]

Hi all,

 

Running 6.4.1, last weekend the power went out at my house and my UPS shut down the server after about an hour (a clean shutdown). I powered it back on earlier this week, but didn't have a chance to look at it today. I started the array just now (since I have autostart disabled) and all of my user shares are missing. I can access the individual disks, but SMB folders are all gone. Did I miss something here with upgrading in the past releases? I'd appreciate any assistance here. I've attached my diagnostics.

 

Thanks!

 

tower-diagnostics-20180309-1235.zip

[Warrentheo]

The syslog is just an endless stream of:

Mar  9 04:40:02 Tower emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Pro.key (-3)
Mar  9 04:40:02 Tower emhttpd: error: get_filesystem_status, 6460: Operation not supported (95): getxattr: /mnt/user/CommunityApplicationsAppdataBackup
Mar  9 04:40:03 Tower emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Pro.key (-3)
Mar  9 04:40:03 Tower emhttpd: error: get_filesystem_status, 6460: Operation not supported (95): getxattr: /mnt/user/CommunityApplicationsAppdataBackup
Mar  9 04:40:04 Tower emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Pro.key (-3)
Mar  9 04:40:04 Tower emhttpd: error: get_filesystem_status, 6460: Operation not supported (95): getxattr: /mnt/user/CommunityApplicationsAppdataBackup

To my untrained eyes, this would seem to indicate an issue with your "._Pro.key" file...

 

Edit: perhaps re-inject your unraid key from your purchase email?

[lishpy]

7 minutes ago, Warrentheo said:

The syslog is just an endless stream of:

Mar  9 04:40:02 Tower emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Pro.key (-3)
Mar  9 04:40:02 Tower emhttpd: error: get_filesystem_status, 6460: Operation not supported (95): getxattr: /mnt/user/CommunityApplicationsAppdataBackup
Mar  9 04:40:03 Tower emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Pro.key (-3)
Mar  9 04:40:03 Tower emhttpd: error: get_filesystem_status, 6460: Operation not supported (95): getxattr: /mnt/user/CommunityApplicationsAppdataBackup
Mar  9 04:40:04 Tower emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Pro.key (-3)
Mar  9 04:40:04 Tower emhttpd: error: get_filesystem_status, 6460: Operation not supported (95): getxattr: /mnt/user/CommunityApplicationsAppdataBackup

To my untrained eyes, this would seem to indicate an issue with your "._Pro.key" file...

 

That's odd, the webUI is showing the system as unRAID Pro. I just confirmed as well, the Pro.key file is located under /flash/config. There isn't anything named ._Pro.key.

[JorgeB]

Power down, run chkdsk on you flash drive, power back on and if still issues grab and post new diags right after boot/array start.

[trurl]

59 minutes ago, lishpy said:

my UPS shut down the server after about an hour

Not apparently related to your issue but this is much too long to run on battery. If you drain the UPS what happens if you get another outage before it has time to recharge?

[lishpy]

54 minutes ago, trurl said:

Not apparently related to your issue but this is much too long to run on battery. If you drain the UPS what happens if you get another outage before it has time to recharge?

The server is not set to power back on post utility coming back on so that's a non issue. I'd rather have the server running on battery if I'm using it then shut down after 10 minutes expecting it to go back out again. It's rare that the power goes out and I need the server online immediately anyway.

[JonathanM]

8 hours ago, lishpy said:

my UPS shut down the server after about an hour

Recharge time not withstanding, if you drain sealed lead acid batteries down that far, they will lose capacity and wear out much faster than if they were only discharged a little ways each time. Plan on replacing batteries much more often than you otherwise would have to.