Some time ago I posted this: 

 

 

I had the issue twice at that time (6.6.1) and not once since.  I'm now on 6.6.6 and the same issue happened yesterday.  It was within a couple of hours of unRAID losing power (power went out and it wasn't possible to cleanly shutdown unRAID before my UPS ran out of juice).  The NAS was performing backups at the time so I didn't get a chance to gather logs or diagnostics before I had to get things going again.  Rebooting always fixes this.

 

Is anyone aware if this is still a known issue?  Complete details in the attached post (as complete as I could make them, at the time).

 

Please post the diagnostics: Tools -> Diagnostics

2 minutes ago, johnnie.black said:

Please post the diagnostics: Tools -> Diagnostics

Before I do, is the diagnostics dump still useful if unRAID has been rebooted already?

 

Looking at what it generates, it seems very ... detailed.  Can it be anonymised at all?  I have share names that match my clients and would like to protect their privacy.

Just now, digitalformula said:

Before I do, is the diagnostics dump still useful if unRAID has been rebooted already? 

Not unless it happens again.

 

Just now, digitalformula said:

Looking at what it generates, it seems very ... detailed.  Can it be anonymised at all?

There's an anonymize option when generating the diags.

Just now, johnnie.black said:

Not unless it happens again.

 

There's an anonymize option when generating the diags.

Right, so I'll generate it and hold onto the diagnostics in case it happens and then post both that and a later one.

 

Thanks for pointing out the anonymise option - I didn't notice the explanation down there.  Nice to see that as a feature.

4 hours ago, digitalformula said:

it wasn't possible to cleanly shutdown unRAID before my UPS ran out of juice)

Your server should be configured to shutdown after a very short time on UPS. 

1 minute ago, trurl said:

Your server should be configured to shutdown after a very short time on UPS. 

While I agree in principal, it isn't. However, since you mentioned it, this UPS is primarily for another device on the network and only has a single USB connection that is plugged into that device.

1 minute ago, digitalformula said:

While I agree in principal, it isn't. However, since you mentioned it, this UPS is primarily for another device on the network and only has a single USB connection that is plugged into that device.

Your server is more important. What is that other device? You can configure APCUPSD to get the UPS status over the network from another computer running APCUPSD. I have my PC on the same UPS as my server with the USB connection to my server and the PC instance of APCUPSD getting the UPS status from the server instance of APCUPSD.

Just now, trurl said:

Your server is more important. What is that other device? You can configure APCUPSD to get the UPS status over the network from another computer running APCUPSD. I have my PC on the same UPS as my server with the USB connection to my server and the PC instance of APCUPSD getting the UPS status from the server instance of APCUPSD.

Actually it isn't. Not sure why you'd make that assumption. But again, since you asked, it's a development and compilation node. unRAID/NAS is for local backups so doesn't affect "daily" work if offline (and yes the backups are also sent off-site). That node going offline is more damaging to the environment here than unRAID going offline during the day. This time, the backup was a manual one that I considered important enough to want unRAID back ASAP.

 

Sure, "reversing" the USB connection to do what you've done might allow something different but it's not something I've looked into, yet (but probably will now).