Bob Cadenza

Why doesn't python output show up in logs? To do a test, I made a simple python program that just prints a number out every 5 seconds. But when I run in userscripts, nothing is printed out. What is going on?

Thanks @SimonF, A couple of questions, my looks a little different, as I don't have Serial: option. And I should put the main disk id, and not the partition right? Why is it asking for Disk Size?

I have a drive that I don't have as part of array, and is not on its own controller, so can't just pass that through, and also is not the boot drive, so just want it to show up as a secondary drive. How should I do this? Thanks,

Ok so I have learned some. Firstly using du -sh inside /var/lib/docker the btrfs stuff doesn't get calculated correctly, so I have found that docker system df --format 'There are \t {{.TotalCount}} \t {{.Type}} \t taking up ......{{.Size}}' shows the best account of the space used. In my case I had a large amount of build cache, so after deleting the build cache, I was able to clear a lot of space.

Yes I read the link, but what I read was you basically delete the img, and then reinstall the apps, which is what I don't want to do as I have some custom docker images that I don't want to have to rebuild. Regardless, would like to know what is taking the space anyway, as I don't want to deal with this again in the future. Should I rebuild to use standard directory, or xfs?

I would rather not have to delete all my images, and start again.

So I am getting docker size warnings, so looking to clean stuff up, but can't find what could be taking up space. I do see that stuff in /var/lib/docker/btrfs/subvolumes is 90% of space, but when I look at sizes of volumes, images, and containers I don't see anything this big. I also used https://github.com/SpaceinvaderOne/Unraid_check_docker_script/blob/main/Unraid_check_docker_script.sh but again didn't see anything. I did see reference to old (5+ year) old bugs in btrfs that had stale, duplicated data, but am not sure if that is still relevant. What can I do to see what to clean up?

I have a NVME drive being passed through unraid as a VM to an ubuntu VM. I am currently getting random errors such as errors below. Does this actually indicate an error, or is this a setting or such? Also posted the smartctl below. [Jul17 16:11] print_req_error: 14 callbacks suppressed [ +0.000003] blk_update_request: critical medium error, dev nvme0n1, sector 2597372384 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ +0.074604] blk_update_request: critical medium error, dev nvme0n1, sector 2597372384 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ +0.074383] blk_update_request: critical medium error, dev nvme0n1, sector 2597372384 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ +0.068966] blk_update_request: critical medium error, dev nvme0n1, sector 2597375536 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ +0.074432] blk_update_request: critical medium error, dev nvme0n1, sector 2597375536 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ +0.074535] blk_update_request: critical medium error, dev nvme0n1, sector 2597375536 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ +0.074392] blk_update_request: critical medium error, dev nvme0n1, sector 2597375536 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ +0.021549] blk_update_request: critical medium error, dev nvme0n1, sector 2597376104 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ +0.074414] blk_update_request: critical medium error, dev nvme0n1, sector 2597376104 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ +0.074332] blk_update_request: critical medium error, dev nvme0n1, sector 2597376104 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ +4.419550] print_req_error: 59 callbacks suppressed [ +0.000009] blk_update_request: critical medium error, dev nvme0n1, sector 2597375536 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ +0.074354] blk_update_request: critical medium error, dev nvme0n1, sector 2597375536 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ +0.074440] blk_update_request: critical medium error, dev nvme0n1, sector 2597375536 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ +0.074299] blk_update_request: critical medium error, dev nvme0n1, sector 2597376104 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ +0.074701] blk_update_request: critical medium error, dev nvme0n1, sector 2597376104 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ +0.074286] blk_update_request: critical medium error, dev nvme0n1, sector 2597376104 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ +0.074340] blk_update_request: critical medium error, dev nvme0n1, sector 2597376816 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ +0.075307] blk_update_request: critical medium error, dev nvme0n1, sector 2597376816 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ +0.074317] blk_update_request: critical medium error, dev nvme0n1, sector 2597376816 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ +0.074543] blk_update_request: critical medium error, dev nvme0n1, sector 2597378592 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 === START OF INFORMATION SECTION === Model Number: SPCC M.2 PCIe SSD Serial Number: 230155785140024 Firmware Version: VB421D65 PCI Vendor/Subsystem ID: 0x10ec IEEE OUI Identifier: 0x00e04c Controller ID: 1 NVMe Version: 1.3 Number of Namespaces: 1 Namespace 1 Size/Capacity: 2,048,408,248,320 [2.04 TB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64: 500e04 c91e050719 Local Time is: Sat Jul 22 08:17:04 2023 EDT Firmware Updates (0x02): 1 Slot Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test Optional NVM Commands (0x0014): DS_Mngmt Sav/Sel_Feat Log Page Attributes (0x02): Cmd_Eff_Lg Maximum Data Transfer Size: 32 Pages Warning Comp. Temp. Threshold: 100 Celsius Critical Comp. Temp. Threshold: 110 Celsius Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 8.00W - - 0 0 0 0 230000 50000 1 + 4.00W - - 1 1 1 1 4000 50000 2 + 3.00W - - 2 2 2 2 4000 250000 3 - 0.50W - - 3 3 3 3 4000 8000 4 - 0.0090W - - 4 4 4 4 8000 30000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 0 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature: 43 Celsius Available Spare: 100% Available Spare Threshold: 32% Percentage Used: 0% Data Units Read: 40,869,455 [20.9 TB] Data Units Written: 55,079,426 [28.2 TB] Host Read Commands: 873,033,683 Host Write Commands: 288,842,365 Controller Busy Time: 0 Power Cycles: 2 Power On Hours: 745 Unsafe Shutdowns: 1 Media and Data Integrity Errors: 952 Error Information Log Entries: 8,627 Warning Comp. Temperature Time: 0 Critical Comp. Temperature Time: 0 Error Information (NVMe Log 0x01, 8 of 8 entries) No Errors Logged

I want to run VM's, but also want to run a docker container I have running on port 53. How can make it so VM doesn't start up dnsmasq when enableing unraid VMs?

Thanks htpc-diagnostics-20221214-0855.zip

Hello, A Disk has gone offline this morning, and I rebooted it, did a SMART test, which it passed, and brought it back online, when it failed again. Can anyone tell me if it is the disk or something else? Note I haven't had any errors or other issues before today. Disk is a 5y/o Western Digital 3TB WD Blue

I am new to KVM, so not sure what I am doing. But I got an OVA that I need to use, so I got the vmdk out, and converted it to a cow2 file. Then I created a VM in unraid and set this cow2 as the manual partition, but when I try booting it I just get UEFI shell, and not sure how to get it to boot using drive. Any ideas? <domain type='kvm' id='3'> <name>MyVM</name> <uuid>dc203763-aaec-4881-56dc-a1f5b26ba58e</uuid> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="linux.png" os="linux"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-7.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/dc203763-aaec-4881-56dc-a1f5b26ba58e_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='1' threads='2'/> <cache mode='passthrough'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/user/domains/blockchain/Ethereum.qcow2' index='1'/> <backingStore/> <target dev='hdc' bus='sata'/> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <interface type='bridge'> <mac address='52:54:00:f3:73:05'/> <source bridge='br0'/> <target dev='vnet2'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/4'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/4'> <source path='/dev/pts/4'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-3-Ethereum/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <audio id='1' type='none'/> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>

When you change git config, it only changes it in the OS which is in RAM. Not sure how to have this kept between reboots. Was thinking of using a git container and using that instead of using built in git.

Same here, I handle docker container updates separately, so would like to have option to this plugin to skip these checks.

Does this docker app out of the box allow me to see network traffic on per container basis?