tomjrob

The Tower is primarily used as a media server and file storage. The emby docker is used daily. Have streamed movies, TV Shows, etc. since the upgrade. In addition I have used a number of other dockers including Sonaar, Crashplan Pro backup (daily), Diskspeed, and others with no issues or errors in the logs. Have also booted and upgraded a Windows 10 VM. As I was away for Christmas, I also was able to access the Tower (all shares) and via VPM Manager (Wireguard) with no issues. Hope this helps. PS I did backup the flash drive and create a diagnostics report prior to the upgrade as this is a best practice, Didn't need them thankfully.

Upgraded from 6.12.4 to 6.12.6 with no issues. Tower has been running for 10 days with no problems.

JorgeB, Thank you for your help. I have enabled syslog server to a cache preferred share on the tower and it appears to be working as I see a new file syslog there. This problem is intermittant so it may take a while to catch the issue. I will post to this link when it happens.

I have been losing access to the unraid web interface. It has happened multiple times over the last few months. When it happens, I can still log into the server console with command line, however cannot ssh into the server. I have only been able to resolve by rebooting. I am attaching system diagnostics which I ran from the command line before rebooting, so I hope this will provide some insight. I would appreciate any help in determining what is happening here. Thanks to the community in advance. tower-diagnostics-20221012-1157.zip

Recently, I have been losing access to the unraid web interface. It has happened a few times over the last month or so. When it happens, I can still log into the server console with command line, however cannot ssh into the server. I have only been able to resolve by rebooting. I am attaching system diagnostics which I ran from the command line before rebooting, so I hope this will provide some insight. I would appreciate any help in determining what is happening here. Thanks to the community in advance. tower-diagnostics-20220423-0853.zip

Upgraded from 6.8.3 to 6.9.2 a few days ago. Upgrade went smoothly and all Dockers and VM's are running great. Only issue was the cache prefer setting not working on a share with a space. renamed shared to remove space and all working. Thanks to the entire team for the great work. Next step is to try multiple cache pools.

I have a very similar configuration setup for my wife. Windows 10 Desktop KVM on Unraid Using a Raspberry Pi 3 running an older free version of WTware. Link to the product is here. https://winterminal.com/index.html#raspberry This has been running flawlessly for a few years now. Haven't had to do anything to it since it was setup. When the rpi is turned on, it goes immediately to Sign In screen. She enters her thin client password, and the desktop loads. Enter password for desktop, and proceed. Sound, mouse, keyboard all work fine. Her "Monitor" is a cheap TV with HDMI input from the rpi. Setup was a long time ago but as I recall fairly simple. Download the software onto a windows machine, create a bootable wtware image on sd card, insert card in rpi and boot. There is some settup parameters to enter for ipaddress of the KVM, display size, etc., but not too difficult. Unfortunately, wtware started charging for newer versions of the software awhile back. I did find a link on their support site which contains a link to the last free version. The link was provided by their support folks, so they do not seem to have an issue providing the older version if people do not want newer features. Link here. https://forum.wtware.com/viewtopic.php?t=48400 One potential issue though is my wife does not watch movies, etc. using plex on her machine, so I cannot comment on the performance in that scenario. However, I have played youtube videos and seemed to work fine, provided the net is ok. In any case, hope this helps. You could try the free version and see how it works out. Good luck.

Could Use Some Guidance, I have installed and set up the Bazaar docker and have been able to get it working with my series (TV Shows) without any issues. This is a great addon and I appreciate the work done on this. Very helpful. I am having a problem with movies though. I am getting the message about the path being invalid, and I can see why it is happening. It appears as though Bazaar assumes that each movie will always be in it's own folder. However, mine are not. Example below: Actual Path: /mnt/Movies/Features/South Pacific 1958 Bluray-1080p.mkv Example of Bazaar Invalid path message shows path: /movies/Features/South Pacific (1958)/South Pacific 1958 Bluray-1080p.mkv When I created the Folder "South Pacific (1958)" and put the movie file there, the app worked great. My question is do I need to put each movie in a separate folder to get this working (not ideal solution because I would need to reconfigure hundreds of files) or is there a setting I am missing that would allow Bazaar to find the file if it is not in it's own folder. I have tried a number of different settings and searched the forums, but haven't found an answer yet. Thanks in advance to the members that assist here.

I found the issue to be a user script that was creating symlinks for virt manager persistent snapshots. It was referencing disk locations that were no longer valid after I reintroduced the ssd back into the array. It was set to run at array startup, and the script restarts the libvirt service. However, it was not completing due to the incorrect disk locations. Stopped the script and libvirt starts every time. Moved the specified locations back to original re-ran the script and all is ok. Sorry for the fire drill, and thanks for the assistance in identifying the root cause.

I rebooted the array in safe mode. I ran diagnostics prior to starting the array. That is file -1305.zip I then started the array and started the libvirt service with VM Manager. This time it started and the VM's showed up in the dashboard. Ran diags again. That is file -1307.zip I guess there is a plugin or something causing the problem. I hope this helps to identify the issue. I really appreciate the help. tower-diagnostics-20200314-1307.zip tower-diagnostics-20200314-1305.zip

Rebooted 2x. Does not fix the problem. I also noticed that the system gets hung trying to unmount disks whn rebooting. Have to force reboot, which obviously causes unclean shutdown. Any other ideas? Thanks in advance.

Hoping someone can help here so that I do not lose all of my VM machines. Used mover to empty cache ssd to check it with Crucial windows program. Looked like it was empty. Checked it in windows machine. All ok. Put it back into Unraid and used mover to add docker and kvm (libvirt files) back onto the cache. Restarted Docker & recovered all containers. But now libvirt service fails to start. Libvirt Log 2020-03-14 14:01:57.797+0000: 23130: info : libvirt version: 5.10.0 2020-03-14 14:01:57.797+0000: 23130: info : hostname: TOWER 2020-03-14 14:01:57.797+0000: 23130: error : qemuStateInitialize:837 : unable to set ownership of '/var/lib/libvirt/qemu/save' to 0:100: No such file or directory 2020-03-14 14:01:57.797+0000: 23130: error : virStateInitialize:668 : Initialization of QEMU state driver failed: unable to set ownership of '/var/lib/libvirt/qemu/save' to 0:100: No such file or directory 2020-03-14 14:01:57.797+0000: 23130: error : daemonRunStateInit:839 : Driver state initialization failed Diagnostics attached. tower-diagnostics-20200314-1020.zip

Upgraded from 6.8.1. to 6.8.3 today. No issues. All Dockers & VM's working. Kudos to the team.

Upgraded today. All is good. Thanks for the efforts here.

Just took a look at this thread and did a compare to the xml I have for my Windows 10 VM's. One difference I see is that I am using a different (older) version of the virtio iso. (virtio-win-0.1.141-1.iso) vs (virtio-win-0.1.171-1.iso). I have 2 Windows 10 VM's running, and the latest one was created a couple of weeks ago with 0.1.141-1.iso without issue. Maybe try a different version than virtio-win-0.1.171-1.iso. I only mention this because the error says to insure that the drivers are on the media. Good luck.

(Solved): BTRFS Cache Pool Errors The ADATA ssd "worked" when connected to the LSI LSI 9211-8i controller, but did not work and kept dropping offline when connected to the AsRock 970 Extreme4 motherboard SATA controller. However, I noticed that even though it worked when connected to the LSI card, it was running very slow and also very hot (124 degrees F). So, I decided to take johnnie.black's advice and exchange it with a samsung 860 EVO ssd. Much better performance and runs much cooler (75 degrees F). As always, thanks for the great advice here. Hope this helps someone else avoid issues with ssd's in a btrfs pool down the road.

Thank you for the quick response. As you suggested, I moved the Adata device to a different port (cable). The new connection is also on a different controller. Now connected to LSI card instead of motherboard sata port. Reintroduced it into the Cache, and the rebalance completed without error. The Adata has been running fine for a few hours in this configuration. I will monitor for awhile and report back as solved if there are no other errors. I am suspecting now that the new Adata SSD has an incompatibility with the port on the motherboard, because as mentioned in the initial post that port & cable had a 256GB SSD (Crucial) running for months on that port/cable without issue until I replaced the Crucial with the Adata. I also appreciate the link to the command to check the cache pool for errors. It showed many write errors prior to moving the the Adata ssd to the LSI card. Completely clean after the swap & rebalance. Thanks again for the help.

Could use some help here with Cache Pool errors. I apologize for the long post, but I believe that I should try and provide as much info as I can if I am going to ask anyone for help here. So, long story, but here goes. Array had been running fine for months with the initial configuration of the cache pool. Initial Cache pool prior to any issues: Cache - 256GB SSD Cache2 - 256GB SSD Cache3 - 512GB SSD Goal: Remove both 256 GB SSD's and replace with a new ADATA 512GB SSD. End up with (2) 512GB SSD's in Raid 1 pool. Used the procedures outlined here to reconfigure the cache pool. Made sure to do one step at a time and let rebalance complete before next step. https://forums.unraid.net/topic/46802-faq-for-unraid-v6/ Step 1: Replaced 1st 256GB with new 512GB SSD. Rebalance completed without error. Step 2: Removed Cache2 SSD. Rebalance completed without error. Step 3: Unassigned Cache2 slot. All ok so far. Final Cache pool: All steps completed and array working fine. Cache - New ADATA 512GB SSD Cache2 - Original 512GB SSDD Everything seemed to be great at this point. Array ran fine for about 24 hours. The problem: At some point, I noticed that the new ADATA SSD was not showing temperature on the main page, as though it was "spun down". Checked logs and logs were full of BTRFS errors on the new SSD. I assumed the new drive went bad. Steps taken so far to isolate. Ran BTRFS scrub on cache (No errors) Put array in maintenance mode and ran BTRFS filesystem check (No errors). Stopped array and replaced ADATA SSD in 1st cache slot with a 2TB spinning drive connected to a completely different controller and brought array back online. Rebalance showed many BTRFS errors on new spinning drive. I began to suspect that the new ADATA SSD drive may not be the problem. Stopped array, removed ADATA drive and attached it to Windows machine. Used Partition magic to wipe it and did a complete surface test. No errors! At this point I removed the spinning drive in 1st cache slot from the array and brought it back online with only Cache2 drive. Array showed "missing drive" in 1st cache slot as expected, but came online and did a rebalance. Rebalance completed without any errors with nothing in 1st cache slot. So I stopped array and powered down. I put the ADATA SSD back into the array. (Note that the slot I inserted this drive into is in the same slot as original cache2 256GB ssd in a hot swap chassis, so it is using the same slot and cable as the original cache 2 ssd, which ran fine for months.) Powered back up and assigned the ADATA ssd again to 1st Cache spot, and started the array. Immediately started getting many BTRFS errors trying to do the rebalance. This is where I sit. Rebalance is continuing even though there are many errors. I am attaching diagnostics taken at the time of the initial errors found before any troubleshooting steps were taken, as well as a screen shot of the current syslog showing the errors currently happening while trying to rebalance the cache. I am baffled as I do not believe the ADATA ssd is defective, do not believe it is a slot/cable issue, but cannot understand why I can't introduce a drive into 1st cache slot and rebalance the data. The cache appears to be fine as long as there is only one drive as part of the pool. Any help is appreciated. tower-diagnostics-20191204-0353.zip tower-syslog-20191204-0954.zip

Just finished setting up and testing WireGuard. Very easy, and all is working great. Can access unRaid Gui, unRaid shares, and all servers on the LAN from a remote laptop in a different state. Great performance. Very impressed so far. Thanks to the entire team. Next step to try is ipad client access.

Upgraded from 6.7.2 Last night. So far, all is good. Dockers, VM's all running. No errors in System Log. Thanks for all of the work to get this released. Great Work!

OK

Update: Just checked Docker Container Size again before trying your suggested changes, and it appears that all is OK now. binhex-nzbget 738 MB 13.8 MB 7.51 kB The only thing I did was change the port mapping & change it back to create the run command, so not sure but it appears that corrected the issue. I can now reduce docker image size. Thanks for the help.

Thanks for the help. I will try your suggestions and get back.

Run Command Attached

Squid, Thanks for the quick response. I have tried to see what is misconfigured, but do not see it. I have compared this container mappings to my sabnzb container, which appears to be mapped correctly, and cannot identify the problem. I am attaching the paths page of the container. Can you identify which setting is incorrect? Thanks in advance.