Green Dragon

Thank you very much!

So, the 'Xeon E3-1200 v3/4th Gen Core' is the correct video processor for the i7?

Thanks for the reply! Here is the output you requested: root@Battarang:~# lspci -Dmm | grep -E 'Display|VGA' 0000:00:02.0 "VGA compatible controller" "Intel Corporation" "Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller" -r06 -p00 "ASUSTeK Computer Inc." "Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller" root@Battarang:~# cat /tmp/gpujson Time = Sat, 12 Aug 2023 05:47:10 -0700 root@Battarang:~# cat /boot/config/plugins/gpustat/gpustat.cfg VENDOR="" GPUID="" TEMPFORMAT="C" DISPCLOCKS="1" DISPENCDEC="1" DISPPCIUTIL="1" DISPTEMP="1" DISPFAN="1" DISPPWRDRAW="1" DISPPWRSTATE="1" DISPTHROTTLE="1" DISPSESSIONS="1" UIREFRESH="1" UIREFRESHINT="1000" DISPMEMUTIL="1" DISP3DRENDER="1" DISPBLITTER="1" DISPVIDEO="1" DISPVIDENH="1" DISPINTERRUPT="1" DISPEVENT="1" DISPVERTEX="1" DISPTEXTURE="1" DISPSHADEREXP="1" DISPSEQUENCER="1" DISPSHADERINTER="1" DISPSCANCON="1" DISPPRIMASSEM="1" DISPDEPTHBLK="1" DISPCOLORBLK="1" DISPGFXTRANS="1" root@Battarang:~# timeout -k .500 .600 intel_gpu_top -Jo - -d pci:slot=0000:00:02.0 { "period": { "duration": 0.035772, "unit": "ms" }, "frequency": { "requested": 0.000000, "actual": 0.000000, "unit": "MHz" }, "interrupts": { "count": 0.000000, "unit": "irq/s" }, "rc6": { "value": 97.967684, "unit": "%" }, "power": { "GPU": 0.000000, "Package": 0.000000, "unit": "W" }, "imc-bandwidth": { "reads": 61.424176, "writes": 23.887180, "unit": "MiB/s" }, "engines": { "Render/3D/0": { "busy": 0.000000, "sema": 0.000000, "wait": 0.000000, "unit": "%" }, "Blitter/0": { "busy": 0.000000, "sema": 0.000000, "wait": 0.000000, "unit": "%" }, "Video/0": { "busy": 0.000000, "sema": 0.000000, "wait": 0.000000, "unit": "%" }, "VideoEnhance/0": { "busy": 0.000000, "sema": 0.000000, "wait": 0.000000, "unit": "%" } } }root@Battarang:~#

Hita! PROBLEM: GPU Statistics is displaying stats from an old gpu DETAILS: I recently changed motherboards. I went from an Intel Xeon to an Intel i7 4790. I only just installed gpu top and gpu statistics. When i select 'Unit ID for Dashboard(Multiple):' dropdown it lists '00:02.0: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller - 0000:00:02.0' which of course was the old gpu prior to replacement. Running intel_gpu_top from the console reports the following: Thoughts?

shutdown unraid server, pulled the drive, reinstalled from backup, restarted, VIOLA! this is the second time this flash drive has lost its mind (and GUID). the guid normally looks something like this: 53209-234590-672075320707808932 when it fails it looks like this: 53209-234590-000000000000000000 <idk>....

I have been running a 6.11.5 server for some time now without much issue. Well, it seems my flash drive is now either corrupted or 'offline'. (missing key file??) I logged in today to see this: So, I logged in to Connect to download the backup and pro.key. After downloading both I now see that the drive is BLACKLISTED: Flash config shows a clearly invalid GUID: So, I have just a few key questions for clarification: 1. Can I just install the same 6.11.5 OS on a new USB drive, boot without the backup config or pro.key, 'transfer' the license to new drive from the console' then shutdown and copy the (backup) /config to the new drive then boot to UnRaid and my good config? I guess what im asking here is, is there any danger of corrupting my unraid server by booting to a basic (demo) usb flash drive and looking around before transferring then copying my good configs to the new drive? 2. How the heck does this just 'happen'? I did not transfer my license (didnt even remove the bad one) so why did my bad usb drive get automagically blacklisted? What usb flash drive is my license now assigned to? 3. How would YOU recover from this? Thanks!

In rutorrent, I have ratio group actions set to continue seeding regardless of the ratio (I never want them to stop seeding). I do have a ratio group action configured to change the channel to 'delete ok' once the configured seed TIME is met (as you would expect, different per tracker). I do this so that when the time comes for me to manually remove torrents I'll know which have met the trackers seed requirements and can be deleted. Nonetheless, once a seeded torrent exceeds a 1:1 upload ratio its marked as finished and seeding stops. I must then go in and manually start them. As configured, the channel does change to 'delete ok' once the configured seed TIME is reached so I know that the ratio rules are otherwise working. In all cases, if the ratio has not yet reached 1:1 then the torrent continues to seed. I may have narrowed this down to the watchdog script restarting and re-initializing plugins when the VPN IP address expires or otherwise no longer works (network failure?). I think that somewhere in this process any torrents with greater that 1:1 ratio are changed to 'finished' status. I have tried enabling the default ratio group in rtorrent.rc but this does not help. Anyone else having a similar experience? EDIT: SOLVED! After weeks of researching and testing this (and no response here) I seem to have found the reason for the problem! The watchdog script restarts rtorrent whenever there is a problem with the vpn (as indicated above). Part of this restart reinitializes the plugins with the following line in rtorrent.rc and /home/nobody/initplugins.sh: execute = {/bin/bash,-c,/usr/bin/sleep 10s && /usr/bin/php /usr/share/webapps/rutorrent/php/initplugins.php $WEBUI_USER &} This 'reset' appears to have the effect of causing any torrents with a ratio of 1:1 or better to stop seeding regardless of configuration. The remarks in the files indicate that it is there so that the plugins 'rss' and 'scheduler' will work properly. I do not use these plugins so I disabled them and commented out the line in both files. So far (48 hours) I have not seen a problem and my initial problem is GONE! This is a great docker and i sincerely hope this saves someone else the frustration I experienced. gd

Awesome! Could it be as simple as me needing to bind the 'Serial bus controller: Intel Corporation Comet Lake' to iommu for my 2003 server qemu issue referenced above?

Attempts have been made. Unfortunately, as you can see from this thread, I am unable to get it to successfully install. As it stands today I do not have it successfully installed.

Here ya go... Enjoy! gothamcity-diagnostics-20221127-1426.zip

I am running VMBackup. No other VM related plugins though. Is this typical behavior for a plugin such as VMBackup to cause a connect/disconnect which generates a libvert I/O error every ten minutes? Is this a reportable bug? VMBackup? Libvert? UnRaid?

Seems reasonable. Believe me when I say that I wish this software would run on a newer OS. Where can I find older versions of the tools?

Also found that If I stop all VMs, disable VMs, then enable VMs the libvirt service fails to start. A complete reboot of UnRaid is required to get VMs working again.

Hiya! After upgrading to 6.11.5 I am seeing the following errors in the libvirt log, about every 10 minutes: 2022-11-21 02:38:20.190+0000: 13082: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error 2022-11-21 02:48:23.307+0000: 13082: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error 2022-11-21 02:58:26.536+0000: 13082: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error 2022-11-21 03:08:29.686+0000: 13082: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error 2022-11-21 03:18:32.955+0000: 13082: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error Thoughts?

Hiya! I am attempting to run Emilien-Lamberts script to restore an ubuntu VM. I have several good backups to choose from. The problem is that my dumb@$$ used spaces in the name so the script is not creating the restore directory properly nor does it appear to find the backup files: ################################################# Make sure the informations is correct this script does not check errors. Please check this before continuing. 1) On the dashboard, delete your VM if it still exists ('Remove VM & Disks)' 2) Make sure all VMs are shut down' 3) Make sure your VMs Manager is turned ON before launching this operation. (settings => VM Manager => Enable VMs: Yes) ################################################# Enter path of virtual machine backup folder, for eg: /mnt/user/John-Doe/my_backup_folder ... Path without the last / like this: /mnt/user/PATH_BACKUP_FOLDER Path of backup folder: /mnt/user/backups/vms/Ubuntu\ (bbs\ website) ################################################# Enter name of virtual machine, like: Ubuntu Name of vm folder: Ubuntu (bbs website) ################################################# Enter date of backup, for eg: 20220124_0200_Ubuntu (bbs website).xml 20220124_0200_vdisk1.img or .zst ... Date like this: 20220124_0200 Date of backup: 20221120_0630 ################################################# Checking information : Your backup path is: /mnt/user/backups/vms/Ubuntu (bbs website) Your vm name is: Ubuntu (bbs website) Your backup date is: 20221120_0630 Are You Sure? [Y/n] y Creation VM folder in domains directory mkdir /mnt/user/domains/Ubuntu (bbs website) mkdir: cannot create directory ‘/mnt/user/domains/Ubuntu’: File exists mkdir: cannot create directory ‘(bbs’: File exists mkdir: cannot create directory ‘website)’: File exists !!! Backup file not found !!! root@GothamCity:/mnt/user/backups/Unraid-VM-Backup-Plugin-Restoration-Script# Any thoughts on how can I get past this? Thanks!

Hiya! I am having a problem with an ubuntu vm pausing after about 10 or 15 minutes. Here are some particulars: three vms currently running (1 win2k3 sp2, 1 ubuntu v22.04.1, 1 ubuntu v22.04.1) only one of the ubuntu vms are pausing domain share is on an xfs 1TB ssd with 832GB free all vdisks are confirmed to be on the 1TB ssd the pausing vm has a 20GB disc with 13GB allocated (the other two vms have 50GB discs) Thoughts?

Well, I disabled my serial adapter, reset the default windows COM port to 1 and tried to install the qemu guest agent. Same error, 'A program run as part of the setup did not finish as expected'... Realized I didn't have SP2 installed so I did that. No joy... Still getting the error.

Same error after installing the serial driver. It should be noted that I changed the default COM port to 12. This vm hosts a bulletin board system (bbs) so the default COM port is remapped in order that the netserial adapter (IP to COM) can operate over COM ports 3 and 4. I'll disable the driver, reset the COM port and see if this works.

virtio-win-0.1.225-2.iso

Well, unfortunately thats a bust. Im getting a fatal error trying to install the msi. 'A program run as part of the setup did not finish as expected'... <sigh>...

Aaaah, Thanks! So, for a windows server 2003 vm I need to install a qemu client from within the vm desktop?

Where are the following scripts located? 'disklocation.sh, fix.common.problems.sh, logrotate, user.script.start.daily.sh' Can they be edited?

Hiya! I'm configuring vm backups using the vm backup plugin and I want to enable snapshots. When I do I find the following recommendation: "IMPORTANT: It is highly recommended that you install the qemu guest agent on your VMs before using snapshots to ensure the integrity of your backups." As Im unfamiliar with vm backups I have no idea what this is suggesting. I looked in the configuration for the vm and see nothing related to qemu and the only installable community app i find is qemubackup which does not clearly indicate that its what I'm looking for. Any assistance, education, or clarification would be greatly appreciated!

Hiya! I created a new Windows Server 2003 VM to run my bbs on. The default iso creates a serial port (com1). This causes problems with my port translator. Can I disable this in the configuration so that the port never shows up in device manager? Thanks!

Hiya! After connecting this usb drive to a vm I am able to access it from within the vm. However, when I shut the vm down i see a greyed out reboot button after the drive. Why and what is this, please? Thanks!