Espressomatic

Running 7.0.0-beta.1 here - going to post into the bug forum. Not sure when this first came up, but IMO, it's critical. Summary: This is precisely what doesn't work - you can take a working OVMF VM's vdisk file, recreate the VM with the same settings, without install media, point it to the vidsk, and it'll no longer work. Details I have the same problem when trying to use a pre-existing qcow2 file, such as the pre-installed Fedora Server qcow2 file from their site. I can exit to the bootloader, make changes, save, and continue, but still get dumped back to the UEFI shell. The boot disk is already selected as the first boot option. It doesn't matter how I select the existing qcow2 file, I can never get it to boot so long as OVMF bios is selected. When selecting SeaBIOS, it boots right up. If I use ISO install media when creating the VM, there are no problems using OVMF and the iso boots fine with boot priority 2. When done installing, the resulting qcow2 file I created while setting up (boot priority 1), boots without issue. Likewise to reports above, if I remove the VM (but keep the qcow), and then create the VM again with the same settings, manually specifying that same qcow file, without install media, it will no longer boot. Here's the XML from two VMs. One still working, and the other I just broke with the steps above. Working one is Fedora, broken one is Debian. XML looks pretty much identical other than ids and "disconnected" on the non-working for guest agent connection. Fedora working <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='13'> <name>Fedora</name> <uuid>ae05b20a-155b-71d3-a0f9-3f7bc1292789</uuid> <metadata> <vmtemplate xmlns="unraid" name="Fedora" icon="fedora.png" os="fedora" webui="" storage="default"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>1</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-8.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/ae05b20a-155b-71d3-a0f9-3f7bc1292789_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='1'/> <cache mode='passthrough'/> </cpu> <clock offset='utc'> <timer name='hpet' present='no'/> <timer name='hypervclock' present='no'/> <timer name='pit' tickpolicy='delay'/> <timer name='rtc' tickpolicy='catchup'/> </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/vm_hosts/Fedora/vdisk1.qcow2' index='1'/> <backingStore/> <target dev='hdc' bus='virtio'/> <serial>vdisk1</serial> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <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> <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='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'/> </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> <interface type='bridge'> <mac address='52:54:00:f3:61:90'/> <source bridge='br0'/> <target dev='vnet12'/> <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/1'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/run/libvirt/qemu/channel/13-Fedora/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <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='5901' autoport='yes' websocket='5701' listen='0.0.0.0' sharePolicy='ignore'> <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> <watchdog model='itco' action='reset'> <alias name='watchdog0'/> </watchdog> <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> Debian not working after recreating and pointing to existing qcow2 file <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='15'> <name>Debian</name> <uuid>9512924f-3e97-3821-9dc0-9a17cb6ebc48</uuid> <metadata> <vmtemplate xmlns="unraid" name="Debian" icon="debian.png" os="debian" webui="" storage="default"/> </metadata> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>1</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-8.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/9512924f-3e97-3821-9dc0-9a17cb6ebc48_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='1'/> <cache mode='passthrough'/> </cpu> <clock offset='utc'> <timer name='hpet' present='no'/> <timer name='hypervclock' present='no'/> <timer name='pit' tickpolicy='delay'/> <timer name='rtc' tickpolicy='catchup'/> </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/vm_hosts/Debian/vdisk1.qcow2' index='1'/> <backingStore/> <target dev='hdc' bus='virtio'/> <serial>vdisk1</serial> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <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> <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='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'/> </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> <interface type='bridge'> <mac address='52:54:00:c3:bc:1c'/> <source bridge='br0'/> <target dev='vnet14'/> <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/2'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/2'> <source path='/dev/pts/2'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/run/libvirt/qemu/channel/15-Debian/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <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='5902' autoport='yes' websocket='5702' listen='0.0.0.0' sharePolicy='ignore'> <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> <watchdog model='itco' action='reset'> <alias name='watchdog0'/> </watchdog> <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>

I've also successfully ran the image I made in 6.12 while running 7, but I didn't have success making a new image when I tried. It was just some quick testing but I was hitting a wall and haven't gone back to try again.

Has anyone verified success doing a brand new Macinabox install while running Unraid 7.0.0-beta1?

System Temp has a small bug in it which causes the plugin startup script to delete sensors-detect on Unraid 7 betas. # Remove sensors-detect script (Unraid 6.7 and earlier) source /etc/unraid-version version=${version:2:2} if [[ $((${version/./}*1)) -lt 8 ]]; then rm -f /usr/sbin/sensors-detect fi As the above only checks the minor version number, it's evaluating 0 as less than 8 and deleting the script. And once the script is deleted, the plugin can't find any sensors, identify, nor load their drivers .

ipmitool not working in Unraid 7.0.0-beta.1 Same error as has been seen in the past with NerdPack before NerdTools took over: can't open libcrypto.so.1 root@TVHD:# ipmitool ipmitool: error while loading shared libraries: libcrypto.so.1: cannot open shared object file: No such file or directory If anyone has any advice how to get this going in the meantime, manually I'd love to hear about it (sourcing elsewhere, re-building on this machine, etc.) Unfortunately the info I've found from a few years back didn't work out (downloading txz from different repo, etc.)

I've been running on a Pro license since sometime in 2018 and after a lot of research and experimentation, I'm likely going to spin up two more systems with Unraid. One will probably start on Basic, the other on Unleashed and next year, they should jump to Lifetime - just for the hell of it, as I won't be using more than 6 disks on either of these systems. The Lifetime price makes Unraid the cheapest solution around IMO. Looking at products like TrueNAS, Rocknas, Proxmox and others, which most people like to call "FREE," it's a no-brainer once you know more than the bare minimum about deploying and maintaining each system. So while coupons are great, they're not a big deal long-term. For starters, Unraid isn't going to shorten your lifespan nor make you lose your hair like the others. You'll also sleep better.

I set up a machine on its own VLAN blocked from everything else, with port 22 wide open to the wild. Username root and password password. The filesystem has over 100,000 folders, 6-10 deep, every folder has between 1 and 5 GOATSE photos. And that's all.

Hopefully the new >2TB NVMe and SSD options I pick will be quieter than the testers I have in the system now. Not in including the fans, this system of all solid state and non-moving parts is noisier than most of my spinning HDDs. High-pitched SSD activity whine is pretty annoying.

Exactly. I've already upgraded to 7.0 on my production NAS system earlier in the week, and this new system is starting with it as I move every non-NAS service from the first system. I had to free up over 50TB of space on the first system to start playing with ZFS and identical drives, but it'll end up being a nice way to stress-test my new fiber to the home connection when I get to reclaiming that data.

Looks like Unraid, without UD plugin expressly installed, does the same thing. I created a single drive pool, added the 1TB SSD, set it to use ZFS and after starting the array and then formatting, it's also MBR. When I did all the disk setup and ZFS pool creation from shell, making sure its GPT, exporting, then bringing that drive into Unraid, it ends up showing "unknown" for partition table format - but it seems to work. Going to put this out of my mind for now as I still need to buy some permanent storage for this system and will try to make sure each disk is simply over 2TB. This box is going to be solid-state pools only, as it's dedicated to nothing but VM hosting - not a general NAS with exported shares.

Setting up a new system... Is it not possible, via the webUI, to specify partition table format when setting up disks? It looks like UD always uses MBR on drives under 2TB? Any way to set up the disks I'm using at the moment for testing, 1TB SSD and 500GB NVME, as GPT? Setting disks ahead of time, like on a Mac using Disk Utility or on Linux/Unraid using gdisk doesn't seem to help because UD destroys the GPT and creates a new MBR when formatting. And using gdisk to change the table format in place doesn't seem to work on disks formatted with UD.

This is an old thread, but I see room for two changes that would alleviate the lack of "love" and provide more information for anyone going through this. 1. Allow creating a pool without shutting down the array - I can't fathom why we need to shut down current array drives and shares (and basically the entirety of Unraid) to make a new pool using completely new disks. 2. After creating a pool, generate a pop-up informing the user that it needs to be formatted to show up as a usable filesystem - offer the ability to start or skip the format in that pop-up. There's no amount of hand-holding that will prevent unintended data loss in every circumstance. IMO, the above would do a much better job than what we have now for that and to make the whole thing more informative and much more intuitive.

OK, that's good to know, as I don't want to have to do a major data shuffle again later in the year. - EDIT: I decided to jump right onto v7 beta1 to set this up. This time around I used a great unix/linux compression utility (rm) that can take any amount of data and squeeze it down to 0 bytes.

Is the current state of ZFS at a stable and future-proof point where I can create a RAIDZ2 vdev (alone in a pool) out of 6 (same capacity) drives - and then when 7 (and later) are released, be able to take advantage of the hybrid solid-state cache feature(s) without having to destroy or remake the vdev and pool? How about later when OpenZFS 2.3 is integrated with the ability to expand vdevs? I know current vdevs on TrueNAS for example are OK, I just want to make sure Unraid's will also be good to go.

Floorp which is based on Firefox for Desktop. Safari for Mobile. I'd use Safari for desktop if uBlock Origin were available. I keep Chrome installed only for sanity-checking problem websites. Google for example is screwing with Firefox on Youtube. It's going to be interesting to see how many enthusiasts drop Chrome when the switch over to their more restrictive extension system which is going to prevent uBlock Origin from deploying.

There's a plugin that allows automatic control based on drive spin-up and chron for scheduling. This would be an ideal feature to add to that plugin.

This is the only option I've been searching for in an "auto turbo" plugin. Anything else out there that might be able to do this?

"in a share" is the problem. Make multiple different shares and set access restrictions on the ones you don't want to expose to certain people, or flat-out don't export the ones you want hidden.

Here's a suggestion (which I intend to try myself): Spin up a Debian/Ubuntu VM, let it access Unraid's share folders, set up SAMBA and export shares from within that VM. Looks like there was a much simpler alternative. I just had to share an unassigned device to realize full speed testing on Samba. 117MB/s up or down without issue, multiple times over.