Magiverous
-
Posts
21 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Magiverous
-
-
1 minute ago, JorgeB said:
Like mentioned it's normal on the SMART page, no idea where the plugin get its info from, best to ask on the appropriate support thread.
Cool, as long as unraid will spin them down when idle I'm fine with that 🙂
Thanks so much for the assist.
-
1 minute ago, JorgeB said:
Do you mean in the main page or SMART test page? It's normal on the SMART test page, on the main page I believe it should show correctly, but note that by default stats are only update every 30 minutes, that can be changed on disk settings.
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.
-
2 minutes ago, JorgeB said:
GUI SMART tests don't work on SAS drives, you can still run them manually.
The lack of temperature issue is a smartctl problem/bug, it should be fixed on an upcoming release.
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.
-
11 minutes ago, JorgeB said:
Probably a controller with custom SMART data, but we can't say for sure without the diagnostics.
Dont know if it will include any drive data, but here is the zip diagnostic for good measure...
-
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.
-
10 hours ago, aptalca said:
If your appdata share is already set to cache only (recommended way), it's just a matter of editing the container settings and changing it from /mnt/user to /mnt/cache and it will use the same exact folders, so no reinstalling or anything.
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 🙂 🙂
-
3 hours ago, aptalca said:
If your appdata share is already set to cache only (recommended way), it's just a matter of editing the container settings and changing it from /mnt/user to /mnt/cache and it will use the same exact folders, so no reinstalling or anything.
Ahh, it is. That's great news. I'll get on that today.
Once more, thanks for the help 🙂
-
Just now, aptalca said:
We recommend all config folders to be put on /mnt/cache
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
-
4 minutes ago, aptalca said:
/usr/local/openvpn_as symlinks to /config. You don't have those subfolders because openvpn installation failed (likely due to fuse filesystem).
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.
-
1 minute ago, aptalca said:
What folder are you talking about?
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.
-
34 minutes ago, 15goudreau said:
It could be just the default location for the /config as explained up. I am going to re-set up instead of using appdata and put in directly onto the cache drive and see if it happens again when an update hits. I agree this is obnoxious and none of my other containers suffer this issue so I have to think it's an openvpn-as issue completely.
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...
-
8 hours ago, Squid said:
You have VMs enabled, and the domain dir in VM Settings is set to the domains share. Disable the VM service and problem solved. And it's probably also recreating the ISOs share at every reboot also
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 🙂
-
On 1/4/2020 at 4:32 PM, jonathanm said:
Recreate the issue, then download the diagnostics zip file and attach the entire file to your next post in this thread. Don't edit your current post, it won't show up as new and we won't know you added anything. Since the issue happens after a reboot, you probably need to collect a zip file from right before you reboot, and a new zip file after the share shows back up.
Anyone still looking at this? Tis still happening ever reboot 😞
-
1 hour ago, jonathanm said:
Recreate the issue, then download the diagnostics zip file and attach the entire file to your next post in this thread. Don't edit your current post, it won't show up as new and we won't know you added anything. Since the issue happens after a reboot, you probably need to collect a zip file from right before you reboot, and a new zip file after the share shows back up.
Ok, here you go. I've got 3 logs. One is pre reboot with everything the way it should be in terms of shares. The second is post reboot after the share reappears. The third is after changing the SMB status on the media share and it inheriting the deleted shares comment and cache settings. I hope that helps.
tower-diagnostics-20200104-1708 prereboot.zip tower-diagnostics-20200104-1807 postreboot.zip tower-diagnostics-20200104-1811 postsharechange.zip
-
Good morning all
I'm having an odd issue with my shares.
I was doing some spring cleaning, removed a few shares I didn't need anymore.
What I've found is every time I reboot the server, one of the removed shares (domains) is showing back up again. I delete it and all seems well until I make a change to another existing share - for example, I switched my 'media' share from private SMB to public and it seemed to inherit the cache setting and the comment from the deleted share.
It's happened a couple of times now, and if needed I can post a log if you direct me as to which one you need to see 🙂
Thanks for any help.
*edit* typo
*edit 2* added images and logs
-
My favourite thing is the ease of initial setup and overwhelming compatibility with my old ass hardware.
I'd love to see more than one unraid login.
Thanks for the giveaway 🙂
Issues With SAS Drives
in General Support
Posted
That's weird, because according to the status dots it is. Does it just THINK it is?