Magiverous

That's weird, because according to the status dots it is. Does it just THINK it is?

Cool, as long as unraid will spin them down when idle I'm fine with that 🙂 Thanks so much for the assist.

The green dots are present when spun up on the 'Main' page but I also noticed that in the settings for the 'turbowrite' plugin they count as spun down towards the 'Data Drives Spun Down: (as of last poll)'. I'm just worried that if unraid thinks that they are already spun down, it won't spin them down normally in line with my settings.

Ah ok. ANy idea on the whole unraid thinking that the drives are spun down bit? I assume because it thinks they already are, it's never going to spin them down in the normal course of events? Cheers again for the help.

Dont know if it will include any drive data, but here is the zip diagnostic for good measure... tower-diagnostics-20200910-1454.zip

Thanks for the reply. That may be an issue, it won't let me run any smart diagnostics as it thinks the drive is spun down. Can I get anything else useful for you from anywhere else in unraid?

Hi I recently installed some SAS drives in my server and I have 2 minor issues I was hoping someone might be able to help with. Firstly, none of the drives are showing any temperature info on the dashboard Secondly, none of the drives show as 'spun up' despite them being active and in some cases transferring data. The smart section greys out the boxes and says they need to be spun up to run tests and turbowrite treats them as spun down when selecting write mode. Other than that they work absolutely fine. Anyone have any ideas? Cheers.

Huh, I've changed over most of it and you're very right - several minor and none critical errors (especially in Krusader) have literally vanished JUST by switching that over. Why is this not more visible info? Thanks man 🙂 🙂

Ahh, it is. That's great news. I'll get on that today. Once more, thanks for the help 🙂

Ugh, can I just update that in the configs, or is this a reinstall ALL dockers job? As a relative newbie to unraid I'm not sure how that information has escaped me for the last 6 months. I've not seen that mentioned in ANY of the tutorials i've watched for my various dockers. Better to find out now rather than another 6 months down the line with a heap more stuff running i guess

I see, thank you so much for the assistance. Is it primarily openvpn I should be putting directly on the cache or is the same true of most dockers? Wouldn't want to be hitting issues with other more critical stuff down the line. In this case I've just been unable to connect out of the local network for a few days, if some of my other stuff goes down it would be much much more bothersome Thanks again, I really appreciate the help.

The error in the log indicates that /usr/local/openvpn_as/scripts/openvpnas is missing. My docker settings have the config pointing to /mnt/user/appdata/openvpn-as/ (which is stored on the cache drive as per share settings). The /mnt/user/appdata/openvpn-as/ folder has no 'scripts' directory either.

What I'm not understanding is why it's pointing to a folder that doesn't and from what I can tell, has never existed. I've never changed any default settings when setting up the container in the past. Unless they've changed the default settings within the container I just don't understand.

Hi guys, I'm having a weird issue after the most recent update. Having just gotten around to updating, I can no longer get openVPN to start correctly. Please see the image below for a snap of the log file - seems a directory has gone awry... *edit* looks like others have had the same issue, is there a confirmed solution yet? If I have to set it all up AGAIN I think I'm just done with this container. Every other update it seems like I have to reconfigure from scratch...

Ahh, thank you. Any idea why the other share was inheriting the settings from the VM share after I deleted it? Was just curious more than anything in case I'm messing with the shares again in future 🙂