southloven

Your question helped me see what I was missing. I went back in and Used the code to get a key. Thank you.

I just purchased an new key for a secondary server I want to run for a while as I trouble shoot my new hardware. however it looks like the activation process has changed since 6.9.2. If there a way for me to activate the old version? My gui is asking for a url the the Key file, not the Key Activation Code.

Ive been having so many problems, I figured I would load from almost scratch. This is a new setup, just attached the old array. When I create a share user, I don't see the shares listed to give the user permissions to. Is there something I need to do to get unraid to see my shares here. Or am I remembering incorrectly and there is another way? ozunraid-diagnostics-20240129-1543.zip

it was in the 20% range as i remember. had an estimated finish of 53 to 350ish days. It had been running for a about a day. woke up this morning to 3 day estimated finish. I don't have history for this configuration (new hardware build). I had a rebuild of the Parity drive (replaced for larger drive) run for 3 days estimated completion with the gui/ssh not responding after 36 hours (dockers still where ) so. . I let it run for 4 days and did a hard shut down. I was doing a check to feel more comfortable about the rebuild. Could the slow drives mean anything? (not a hardware guy) thanks for the insite on the loads.txt file.

My Parity check seems to be taking a extended amount of time. Reading others similar issues but dont see where in the diagonstics to see writed\s to the dives. Attached is the info I have see recommended be gathered. ozunraid-diagnostics-20240121-2134.zip

Anyone who reads this, I tried to shut down the array based off reading another post so I could check settings with the array off. it hung trying to unmount the user share. Did another hard shutdown, and it came back up with all my user shares and the system folder.

GUI and SSH became non responsive during a parity drive replacement, but my dockers where still running. I let it run until past when the parity rebuild would be completed and did a hard reboot. Came back up, I stopped the array and I added my new drives and the parity. Start the Array and start checking things and notice Docker isn't running. determined the /mnt/user/system/ folder where it says my docker.img file was at does not exist. I go look at shares, and a lot of my user shares are missing. I also cant find the system folder. I don't see why. I haven't found a solution in the forums. ozunraid-diagnostics-20240118-0920.zip

Adding to this, I realized I had fallen behind on unraid updates, and it looks like it may have been that that is causing my issue. I found where JorgeB is recommending switching to ipvlan, but I also noticed after I uploaded this that there was a related fix common issues that sent me to https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces with fix options that appied to me (Ubiquity user) in the 6.12.4 update.

I recently built a new server, but its become unresponsive a number of times over the last week. First time was a day after I got it up and running. It ran a week fine, then over the last 36 hours it has become unresponsive 4 times. Ive looked at the logs and don't see anything to me that looks like the cause. Things I think might be of note. I moved my unraid install from my old server, it was running fine prior I see the signs of a failed disk, but I know I have a WD RED that was DOA still in the server. Ive been trying to get preclear done on the others before RMA. There are two hard reboots in the syslog file. 1st time I think is on Jan 6 23:42:50, but there wasn't much of a gap, and I am way out of my comfort zone with these logs. The 2nd time was Jan 7 09:22:02. Fairly confidant on that because of the gap of logs. Any help would be appreciated, ozunraid-diagnostics-20240107-1011.zip syslog-192.168.21.90.log

I can update that, but I wouldn't think I was trying to write a 500gb file.

Appdata is the one that I have issues on. Docker containers start having issues and from what I see it writes erroring. When I free up space, I stop having issues.

ozunraid-diagnostics-20240102-1359.zip

Ive looked and cant find anyone with a similar issue. Maybe my googlefu is broken today. A couple of years ago, I ran into a situation that my 500GB cache drive would allow writes when it got to 240GB full or so. I thought it was a drive issue, but was given a 1tb drive that I upgraded to. Yesterday because of migrating to new hardware with a Parity check running, and non clearing some cache only data I ran into a similar issue at 399gb on my 1tb drive. everything Ive read has me thinking I should have been able to use the rest of the drive. Is there a setting I am overlooking?

I just got a 2nd mount up and running and it hit me I May have a problem with restarts. If docker containers have to be started after the mounts are established how to you make sure both mounts have completed before starting the dockers? Has any one addressed? or is this not a problem?

Ive been having issues of the last few weeks and recently rebuilt my installation following @tidusjar advice and moved the databases over to a MariaDB docker instance. Just wanted to give a thank you for the assistance.

Installed from Community Applications but ended up needing to change the backup locations. Drop down would not let me start over, and I figured I would reset the settings to default and see if that allowed me. Nope. Then I tried uninstalling it, and reinstalling it. The installer thinks it is still installed. Just Giving feed back as would if I were the developer. Look forward to trying it again when I am able to get it installed.

@cinereus I figured out a way to get my Array to shutdown with out having to manually run unmounts. After using lsof | grep /mnt/user/ To find out which mounts were hanging. I created a new User script that runs "At stopping of Array" using the mount points I found above. You may have to track down what mounts are giving you an issue. #!/bin/bash ####################### ### unmount Script #### ####################### #### Version 0.0.1 #### ####################### echo "$(date "+%d.%m.%Y %T") INFO: *** Starting rclone_unmount script ***" umount -l /mnt/user/mount_mergerfs/gdrive_vfs umount -l /mnt/user/mount_mergerfs/**RcloneRemoteName** umount -l /mnt/user/mount_rclone/gdrive_vfs umount -l /mnt/user/mount_rclone/**RcloneRemoteName** umount -l /mnt/user0/mount_rclone/cache/**RcloneRemoteName** umount -l /mnt/user/local/**RcloneRemoteName** echo "$(date "+%d.%m.%Y %T") INFO: *** Ending rclone_unmount script ***" exit Maybe this will help you, if you haven't found a solution. I also don't know if this is "safe" so if anyone who knows more than me could chime in, I would be grateful.

I'm here looking for the answers to the same questions it looks like @cinereus has.

24 hours with no issues... maybe it was a fluke.

So that fixed one part of my issue it looks like, but after coming back after a few hours, it looked like the docker was not connecting out. I did a ping on google.com and received a temporary domain name resolution failure notice. Any Ideas?

So I am having the exact same issue, Even getting the TLS errors at times. I am thinking Slickvpn may block us from connecting after a number of tries because I changed servers both times I ran into it and it went away. 2020-10-09 15:20:06,709 DEBG 'start-script' stdout output: Fri Oct 9 15:20:06 2020 library versions: OpenSSL 1.1.1g 21 Apr 2020, LZO 2.10 2020-10-09 15:20:11,709 DEBG 'start-script' stdout output: Fri Oct 9 15:20:11 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts 2020-10-09 15:20:11,709 DEBG 'start-script' stdout output: Fri Oct 9 15:20:11 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]192.171.19.130:443 Fri Oct 9 15:20:11 2020 UDP link local: (not bound) 2020-10-09 15:20:11,710 DEBG 'start-script' stdout output: Fri Oct 9 15:20:11 2020 UDP link remote: [AF_INET]192.171.19.130:443 2020-10-09 15:20:34,563 DEBG 'start-script' stdout output: Fri Oct 9 15:20:34 2020 [VPN] Peer Connection Initiated with [AF_INET]192.171.19.130:443 2020-10-09 15:20:35,803 DEBG 'start-script' stdout output: Fri Oct 9 15:20:35 2020 TUN/TAP device tun0 opened Fri Oct 9 15:20:35 2020 /usr/bin/ip link set dev tun0 up mtu 1500 2020-10-09 15:20:35,804 DEBG 'start-script' stdout output: Fri Oct 9 15:20:35 2020 /usr/bin/ip addr add dev tun0 local 10.10.8.10 peer 10.10.8.9 2020-10-09 15:20:35,805 DEBG 'start-script' stdout output: Fri Oct 9 15:20:35 2020 /root/openvpnup.sh tun0 1500 1557 10.10.8.10 10.10.8.9 init 2020-10-09 15:20:35,808 DEBG 'start-script' stdout output: [debug] Waiting for valid local and gateway IP addresses from tunnel... 2020-10-09 15:20:35,809 DEBG 'start-script' stdout output: Fri Oct 9 15:20:35 2020 Initialization Sequence Completed Are you using a core subscription? I am so just asking incase that may be related. I have figured out if I roll back to the below version, It works, but I think the VPN is disconnecting every 12-24 hours. Just pointed to a new slickvpn server, im hoping that helps. binhex/arch-delugevpn:2.0.4.dev38_g23a48dd01-2-06 Any thing major happen to change after 01-2-06? I have tried the later versions with new docker config folders and can't get them to connect either. Same end point in the logs.