Ruato
-
Posts
53 -
Joined
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Ruato
-
-
5 minutes ago, PeteAsking said:
New controller tag has been released and is tested for home use:
11notes/unifi:8.0.26-unraid
Is this now the new recommended tag for home usage?
-
On 9/21/2023 at 11:29 AM, itimpi said:
Just thought I would check whether the lack of new reports is good sign and means your issues are now resolved since the last release of the plugin, or is that you have simply not been in a position where a check is running so you would notice if there is still a problem.
Have been travelling (too much) and have not been able to test this. Very good that @dopeytree confirmed the fix. Great work @itimpi!
-
14 hours ago, itimpi said:
Going through a reboot sequence should not generate the notification spuriously so it is possible in your case the notification was genuine. The issue I have found relates to stopping and then restarting the array without going through a shutdown or reboot sequence.
I will test the this with the upcoming new version as soon as I get back home. I will stop the array before shutdown to guarantee clean shutdown.
-
14 minutes ago, itimpi said:
Thanks - I see what is the issue now and have reproduced it? That notification is erroneously being generated as you are stopping the array without doing a full shutdown or reboot as I am getting an event from Unraid I did not expect during the stopping sequence. All my recent testing concentrated on using the Stop or Reboot buttons to get a tidy shutdown or deliberately forcing an unclean shutdown. Can you confirm that you are getting the notifications while stopping the array?
I will issue an update shortly that will fix this issue.
Great that you found something. For me, the unnecessary notification came after updating my server to 6.12.4. That is,
1) Run the update to 6.12.4
2) Shutdown
3) Boot up the server
4) Start array manually
--> notification -
2 hours ago, itimpi said:
How are you sure? Lots of people get them without realizing it as it can happen when you press the Shutdown or Reboot button if a timeout kicks in or if for any reason or if Unraid cannot write to the flash drive during these sequences. About the only way to be certain you have not had one is to successfully Stop the array before attempting to Shutdown or Reboot.
At the moment I am waiting for someone on the latest release.to be able to give me some diagnostics (with the plugin ‘testing’ logging mode active) to confirm that there is still a problem with the Unclean shutdown detection. I have not managed to spuriously get one in my recent testing when actively trying various scenarios to force iit.
I have increased the shutdown timeouts a lot and they are 5-10 minutes. Additionally, I followed the latest shutdown from the monitor and it _seemed_ good and went fast. So, at least it wasn't the timeouts.
Is there a way to check from the system whether the latest shutdown was clean or not? And is it so that the plugin only checks the latest shutdown? That is, it is not checking if there was an unclean shutdown before that.
I am travelling this week so I cannot examine this more now. Hopefully, you get diagnostics before that from someone else.
-
15 hours ago, itimpi said:
If you are on the latest release of the plugin (2023.09.06) then there is a good chance it IS genuine but it would be nice to make sure. If you enable the 'testing' mode of logging in the plugin's settings and once this has happened post a copy of you system's diagnostics I can check whether it is genuine. It should also be present in the Unraid syslog but you have to find it there.
I did get one also and I know that I have not had an unclean shutdown. And I am on the latest release of this plugin.
-
Long-time satisfied Unraid user here. I am planning on migrating my two SSD brtfs cache pool to ZFS based on the excellent and informative videos by SpaceinvaderOne. In the videos, he explains how to setup appdata snapshots. However, I am wondering whether ZFS snapshots can be utilized also for docker.img, libvirt.img and vdisk images. That is, is it safe to take uncorrupted ZFS snapshots on them while VMs and docker containers are running?
-
17 minutes ago, itimpi said:
I thought I mentioned earlier that the plugin can currently think there has been an unclean shutdown when this not the case so generates that notification spuriously and it can be ignored. This is being worked on.
Sorry for the unnecessary question/post. I had missed your earlier post.
-
11 hours ago, itimpi said:
Deleting the progress file will not help. What seems to be confusing things is a parity.tuning.restart file in the plugins folder on the flash drive - that should only be present immediately after booting if a restart of an array operation is pending. Deleting this file should solve your immediate problem but it is not clear why it was there in the first place. You do have the restart option enabled but that file should only get created if an array operation was actually in progress when the system was last shutdown/rebooted - I assume this was not the case?
There is also a parity.tuning.scheduled file present which I would also expect to be removed after the parity check completes, but I do not see an entry in the parity.tuning.progress file that the completion was ever detected which probably also explains the parity.tuning.scheduled file still being there. I assume it DID finish?
i will see if i can recreate the issue, but if after deleting the parity.tuning.restart file it reappears i would love to know what lead up to that.
EDIT: I can confirm that I am getting some unexpected behaviour if a restart happens during the check so that gives me something to look at. The restart happens fine but the plugin then seems to get a bit confused about the state of things for tidying up as it should
I also get "extra" notifications. That is, I had an unclean shutdown (an issue with a VM). I resolved the situation but now I get the following notification every time I start the array after a reboot even though the shutdowns have been clean.
"Event: Parity Check Tuning
Subject: [XXX] Automatic unRaid Parity-Check will be started
Description: Unclean shutdown detected
Importance: warning"Additionally, it does not start a parity check, I just get the notification.
-
1 hour ago, binhex said:
you can use the built in functionality to set a password, simply edit the container and set the 'value' to your password for key 'VNC_PASSWORD'
Excellent, thank you! Will try this when I get home.
-
32 minutes ago, JonathanM said:
Best policy is to stop the container when it's not needed.
Start it when you want to use it, and stop it as soon as you are done.
Thank you! Yes, I have been doing this but I was just wondering whether there is more elegant solution.
-
Is there a way to password protect the access to this docker?
-
Long time Unraid user here. Thank you for your hard work for this new release!
ZFS is a major change and I am considering whether I should convert my individual array drives to ZFS or whether I should start utilizing ZFS pools. I am sure it would be greatly appreciated by many if part of the Unraid release notes or general documentation there were migrate instructions from XFS array disks to ZFS pool/pools or to individual ZFS formatted array disks. In addition, it would be great, if one could find pros and cons listed for different ZFS options and maybe also preconditions for ZFS usage (for example, RAM requirements). I am pretty sure that many Unraid users (that are not adept with ZFS) are considering what to do with ZFS.-
2
-
2
-
-
On 7/27/2020 at 11:41 AM, bonienl said:
The WG tunnel terminates internally to the system and bypasses the firewall (iptables) function.
Is this still the status? That is, no way to restrict the wireguard clients' access to Unraid server services / dockers via iptables?
Additionally, are you aware if there are any plans to enhance the Unraid wireguard firewall functionalities?Thank you!
-
Hi, I tried to search but could not find a solution. I have a Wireguard server running on my Unraid Server and I have setup several "Remote tunneled access" peers. How can I achieve the following:
- The remote peers need to connect to the Internet via my external network connection. This works currently.
- The remote peers need to be restricted only to a certain IP and a port in the Unraid server (one docker image running in my Unraid Server). That is, I do not want them to be able to access the rest of my LAN or the Unraid server services.
How can the above restriction be achieved? Is there a setting in Wireguard peer config to achieve this or could be done with some iptables magic in the Unraid server?
Thank you very much for any help!
-
34 minutes ago, tjb_altf4 said:
It's done on a per disk/pool basis on their individual settings page, which you can get to from main tab
Yes, I noticed and tried to delete the post but I was too slow.
Thank you!
-
On 12/23/2021 at 2:11 PM, dlandon said:
Normally sda is the Unraid flash drive. In your case the flash is sdb. Is there something on your flash drive causing this? Take your flash to a PC and see if there is something that might be the problem.
For me the Unraid flash is sdc. The two external USB hard drives connected via UD are sda and sdb. Is there a reason to worry or do something?
-
1 hour ago, bally12345 said:
Wanted to do a bit more recently and add vlan with different DNS for kids WiFi but by the looks of it I will need to buy a USG or UDM?
I already have 24 port netgear switch so don't want to spend extra.
Question is can I achieve this the way it is currently set up or do I need to buy extra hardware?
Possibly looking at EdgeRouter X or 4 sfp too.You shoud be able to achieve it by configuring your existing switch but you cannot do that using Unifi Controller. You need to do it via the means offered by your switch. EdgeRouter X cannot either be configured using Unifi Controller.
BR, R
-
1
-
-
On 11/29/2020 at 9:08 PM, binhex said:
by look of it:- /usr/local/bin/urbackupclientctl
as its installed to ram (keep in mind everything is in ram in unraid, other than cache, array disks and flash drive), so you will probably(i dont know yet), have to re-run the script i mentioned above, or perhaps just copy the urbackupclient that gets built and shove that on your flash drive and then copy that to /usr/local/bin/ and execute that as part of the go script - whateve the mechanism there is a bit of fiddling to be done but its def doable!.
Hi, did you already figure this out and made some solution that automatically starts the client whenever the server is restarted?
-
There are quite a lot of unhappy people regarding the firmware update: https://community.ui.com/releases/UAP-Firmware-4-3-24-11355/36d1d2c3-dc75-4f5d-88d9-fb8dda5169ab.
-
Great! This is exactly the thing I was missing with UrBackup. I already had setup a Win10 VM to backup Unraid directories.
A couple of questions:
- Where does it install the binaries?
- Is it automatically restarted whenever the server is restarted or did you do something to enable it?
-
I am planning to change from Binhex docker to this one in order to get the hardware transcoding with Intel Quick Sync.
Are Intel 9 series iGPUs already supported (I have i5-9600K)? Or should I wait for a new stable release of Unraid with a newer version of Linux kernel?
-
19 hours ago, Ruato said:
Hi,
When installing the docker it is recommended that the GitLab data directory is configured to be in the cache. How can I relocate the repositories to the array? That is, they will take a lot of storage and keeping them in the cache is not feasible. Thank you!
Found a solution:
- Add an additional path to the docker configuration.
- Edit the gitlab.rb confgiration.
- Specify the new location as the only repository location via the Gitlab web UI.
-
Hi,
When installing the docker it is recommended that the GitLab data directory is configured to be in the cache. How can I relocate the repositories to the array? That is, they will take a lot of storage and keeping them in the cache is not feasible. Thank you!
Thank you!
[Plugin] CA Fix Common Problems
in Plugin Support
Posted
I was earlier having this issue. Then it went away (maybe because I updated Unraid to 6.12.8) but Today it started to happen again. Has the root cause been found yet?