jbat66

This question doesn't fit this thread. I would suggest you start a new thread, so the right people may see it.

This is minor, but I have many scripts that do copying and the such and I used figlet to make the output and status large on the screen. Would it be possible to add figlet back in? It is not a utility per se' but is useful in scripts for larger output, and was in the old nerd plug in.

Others have chimed in with the correct answer, in that the docker image file has to go somewhere, and the VM data also has to go somewhere if you enable it. I would recommend not doing VM's in UNRAID while under proxmox, you caaaaan, but why? Secondly I recommend just having one large disk, since you don't want to use Unraid's Raiding while virtulized, it does take a large performance hit. Your server that you are running proxmox on should have a raid of some sort, if not you can do it in unraid, but I wouldn't. If you don't have raid on your underlying server, then you could pass the drives through, but that is not how I'm using it. I just want the one click docker management that unraid gives me, and in some cases the file sharing.

OK, so changing to Intel NIC, did not work. I upgraded to 6.12 RC6 - thinking the updated Kernel would help - that did not work. I'm really out of ideas. I couldn't download a diag this time, because with 6.12 RC6, I couldn't get the console screen to come up. Heck even a command to restart networking form command line would be helpful, as I could setup a cron job to restart it when it can not longer ping the gateway. I have one that will reboot the server when it can't ping the gateway but that is hard on the system, because half the time I have to rebuild a drive.

As a matter of fact, I just installed in Intel NIC 2 min ago, and I'm waiting for reboot. We will see how long it stays up. Thanks for the info.

No, I didn't. After reading it, I was able to get it installed. First one I ever had to pre-install. lol

This has been driving me crazy. I purchased two different TP-Link NIC's and still have the problem. I thought maybe it was the internal NIC. Looks like it is just a problem in the Unraid code. Maybe it is the fact the on board NIC and the two I purchased are running RealTech chipsets. The funny thing is that Unraid worked great for years on this server with the internal NIC. I was away for a few months, and when I got back to the server it started having the problem. So it wasn't because of an update, unless it was a plugin update that caused it. Frustrating. Every time I pull diag, I get the same lines in syslog.

Just a note, I tried to install SwingMusic and got the following error: docker: Error response from daemon: pull access denied for swingmusic, repository does not exist or may require 'docker login': denied: requested access to the resource is denied. Looking in the Unraid app code, I see: https://registry.hub.docker.com/_/swingmusic , and when I go to it, I get a 404 error.

This is a wierd one. I was away from the server for several weeks and when I came back the server was running, but no gui, or any network access. I rebooted from console, and all was good for about a day and then no network. the server was fine, just no network. I was running 6.x something and figured I would upgrade to latest version so upgraded to 6.11.5. Same thing, the server would run fine for a day or so and then no network. I then figured I would replace my NIC, but no more slots, so I plugged in a USB3 Ethernet dongle, and moved ETH0 over to the dongle. Everything stayed running for over a week. I then thought I would try the internal NIC again and set it up as ETH0, but left the USB3 dongle plugged in, and added another IP so I can get to the GUI if the NIC/networking quit. Yep that night, networking quit, for both. I had to again reboot from console. While I can continue to run on the USB dongle, I would rather figure out if there is a setting or something to fix the network from quitting when using the internal NIC. Thoughts on what could be the cause? In each case I start seeing these lines in the syslog, when the Network quits: ### [PREVIOUS LINE REPEATED 2 TIMES] ### May 17 02:08:31 Thor kernel: net_ratelimit: 9 callbacks suppressed May 17 02:08:31 Thor kernel: r8169 0000:08:00.0 eth0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 17 02:08:31 Thor kernel: r8169 0000:08:00.0 eth0: rtl_ephyar_cond == 1 (loop: 100, delay: 10). ### [PREVIOUS LINE REPEATED 5 TIMES] ### May 17 02:08:31 Thor kernel: r8169 0000:08:00.0 eth0: rtl_eriar_cond == 1 (loop: 100, delay: 100). ### [PREVIOUS LINE REPEATED 2 TIMES] ### May 17 02:10:10 Thor kernel: net_ratelimit: 9 callbacks suppressed May 17 02:10:10 Thor kernel: r8169 0000:08:00.0 eth0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 17 02:10:10 Thor kernel: r8169 0000:08:00.0 eth0: rtl_ephyar_cond == 1 (loop: 100, delay: 10). thor-diagnostics-20230517-0652.zip

Thank you, I will give that a try.

Been a reliable system up until a few days ago. Then started getting XFS metadata I/O errors and on other occasions md disk read errors per the console. I do a reboot, Get a warning message that several disks had read errors, but all are OK now, and parity check started. After 16 hours of check, it comes back good. and then stays running for a few days, until the next time. Generaly when this happens, no one is useing the shares, nor the dockers (of course they are still running in the background). While I have VM's they are not running. Upgraded to 6.9.2 a month or two ago, never had a problem on the previous version of unraid. 6.8.x I have purchased a replacement drive, thinking it was disk2, but every time it 'seems' to be several disks with read errors. Unraid version: 6.9.2 ASUSTeK COMPUTER INC. PRIME B450M-A, Version Rev X.0x American Megatrends Inc., Version 1201 BIOS dated: Thu 25 Apr 2019 12:00:00 AM MDT Mem: 16 Gig DDR4 CPU: AMD Ryzen 3 2200G with Radeon Vega Graphics @ 3850 MHz thor-diagnostics-20220201-1851.zip

Make sure you are running syncthing with the correct UMASK/PUID/PGID, and make sure that the folder in the share has the correct permissions. While this may not work for your setup, I'm using UMASK 000, PUID 99, PGID 100. Another thing you can look at is. binhex-urbackup. It just works! It is like your own Crashplan, but free. You can do file level backups, limit what you want backed up, and can even do image level backups.

Yes mine is working Great. Make sure your underlying permissions are correct on the files as well as the dockers. My dockers are running as UMASK:000, PUID:99, PGID:100. I hope that helps.

Yes you can setup the sync links the way you want. You can say Computer B is the fast computer. then setup sync from A <-> B, C <-> B, you don't setup A <-> C, that way it all goes through B.

I thought I would try a force update this morning and it fixed it... Then I came here to let you know, and looks like you pushed the fix. Thanks so much, Have a great day!!!

Thanks for supporting syncthing. Looks like the latest update broke something I have two different unraid servers and syncthing broke when I updated them on both servers. I tried pulling latest and no luck. The logs show: today at 10:55 PM 2021-04-06 22:55:27,064 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23178730679744 for <Subprocess at 23178730781904 with name syncthing in state STARTING> (stdout)> today at 10:55 PM 2021-04-06 22:55:27,064 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 23178730448352 for <Subprocess at 23178730781904 with name syncthing in state STARTING> (stderr)> today at 10:55 PM 2021-04-06 22:55:27,064 INFO exited: syncthing (exit status 1; not expected) today at 10:55 PM 2021-04-06 22:55:27,064 DEBG received SIGCHLD indicating a child quit today at 10:55 PM 2021-04-06 22:55:28,065 INFO gave up: syncthing entered FATAL state, too many start retries too quickly Just curious if you have any ideas. I did look around the interwebs but didn't find anyone having this issue.

So in the docker under setting poller, you get poller, performance, log. librenms, has vm appliances, so I got one of those stood up and everything is working, but look at the menu difference, and you have setting to enable the poller. I'm not sure what is up with the docker version.

I have libreNMS docker installed, and have a mysql container installed, and libreNMS comes up like it should, talks to the DB just fine. I can add a device, but it doesn't ever poll the device. I can manually poll the device via command line in the container, but there doesn't seem to be any cron or anything that runs the poller. I have been reading up that there has been some changes in the docker, and looks like it may need a side car container called dispatcher for polling. I'm just curious does anyone have libreNMS running with the latest container and polling working? Thank you

I was wanting to see if I "could" run a VM inside of unraid, while unraid was running as a VM under Proxmox. There is no need in doing this as it is better to run your VM's under the hypervisor that is talking directly to your hardware, in this case it is Proxmox. I could not get VM's in unraid to work with out passing all the CPU functions (such as virtualization) down to unraid. While you can run an emulated CPU, the reason for doing that is to be able to migrate a running VM between dissimilar hosts. Since you can't migrate unraid you might as well pass all the CPU features onto unraid. IMHO.

It is passing all the CPU features to the VM, it is not locking the VM to the CPU. When not set as "host" it emulates a CPU. When you do pass all the CPU features to the VM, you can not migrate the VM to another host while the VM is running. Since Unraid is locked to that host because of the physical USB key, it doesn't matter that you can not migrate the VM. If this was VMware, think of it as disabling EVC (Enhanced vMotion Compatibility) processor support. EVC is a way to emulate a particular generation of CPU. You can have several hosts all running different generations of intel CPU's and if you have all the hosts/vm's emulate the lowest common CPU, then you can live motion your VM's from one host to another.

October 2020 [GUIDE] Installing UnRaid (ver. 6.83) on ProxMox (ver. 6.2-4) Background; I have been using UnRaid for close to a year, and have just started using ProxMox a few weeks ago. However I have been using other virtualization technologies and hypervisors for years, Hyperconverge (Cisco HyperFlex, Nutanix) and Hypervisors (VMWare, Hyper-V, VirtualBox, etc) for years. I wanted to virtualize UnRaid on ProxMox, but found complicated older forum posts, and thought there should be a better way. I experimented and hope I found an easy way to set this up. I just wanted to share to the community. 1. Download the Unraid Server OS and make a USB key. Take notes USB 2.0 is generally better than USB 3.0/3.1 for USB drives used for Unraid. Note, Unraid does not install to a drive, it will only and always boot from the USB drive/key. It installs into memory on each boot, and runs from there.(https://unraid.net/download) 2. Make sure to boot the unraid OS on your server without proxmox running, in other words, you can have proxmox installed, but boot from the key once to make sure it is going to work with your hardware. I went through three USB drives, even two of the same type, before I found one that would work! If you have DHCP set up on your network, you should get a DHCP IP address that you recognize from your network. In my case my network is 10.0.0.x. If you get an IP that starts with 169.254, then this generaly means the usb drive is bad, you will probably see some comments above about not finding files. You can also login to unraid via console and try deleting /boot/config/network.cfg and rebooting to see if that fixes it. More than likely it is an incompatible USB drive. 3. Reboot back into ProxMox 4. Make a VM with the following settings Memory; UnRaid likes memory, so make sure you give it enough. Processors; Make sure you go to the bottom of the list of processors and pick the "host" type. This passes through your hosts processor. This will limit you on migrating your UnRaid VM to another host, but you can't do that anyway, since it is linked to your USB drive. BIOS; Use SeaBIOS Display; use the default if you wish. I love SPICE, so that is what I use. If you use spice you have to have the viewer installed on your workstation. Machine; Default i440fx SCSI Controller; VirtIO SCSI I tried the others, but this works fine. CD/DVD Drive; ProxMox will not boot a USB drive in a VM, however you can boot an ISO, and there is an ISO that will boot a USB drive... See where I'm going there? Make your life easy and download plopkexex (https://www.plop.at/en/plopkexec/download.html) extract it and then upload plopkexec64.iso to your ISO share. Then mount that ISO in your VM. Tada no config, and it just works. Hard Disk; Make a hard disk or disks for your VM. I really don't recommend that you make several virtual disks and set them up inside of Unraid and make a array, just make one and go with that. You can always make a larger one later and copy your files across to the larger one inside of unraid at a later time if you want to go larger or smaller. Lastly, you can pass through direct hard drives, and other direct USB drives, if you want Unraid to control them directly, then you can setup an array just like you normally would. However if you are doing that, you might as well delete proxmox and set your server up with unraid, as unraid will do VM's and Docker locally. Network Device; use e1000. I had problems getting any other virtual NIC to work other than the e1000. You may end up getting no IP for your IP address on UnRaid, or the 169.254 type address. You can also login to unraid via console and try deleting /boot/config/network.cfg and rebooting to see if that fixes it. USB Device; You must pass through the USB Device that your Unraid is installed on, if you do it this way, and not the other way of copying your USB contents to a virtual drive, your unraid experience will be the same as if you have it running on a non-virtualized server. What I mean is that changes will get copied back to the USB drive like they should. 5. Boot your VM In summary, there are a few gotchas, getting correct NIC type, getting a USB stick to boot, and the big one, getting a good install on a USB that will boot correctly on your hardware. I have tested a VM in Unraid (I'm NOT going to run any in Unraid under Proxmox, but it does work, and I have tested several dockers. All work as expected.

Is there any update on this? does it get looked at? commented on? Not sure if I need to do something further.

Good idea!. I submitted it here:

This idea comes from @forusim in the thread I started (see below) (quote) On the GUI would it be possible to draw the part of I/O wait different? Work I/O wait 70% ||||||||||| | | | | | | | | | | | | | | | | | | | | | | I find it useful to know, if drives are locking the system or the cpu is really doing stuff. (end quote)

UB just uses rsync to copy/move files, now while rsync "can" send files over a network connection, you would have to specify that in the command line. I don't see any reason why your NIC would have traffic because of an UB move. sniff the traffic and see what kind of traffic it is.