vanstinator

To be totally fair it's also beta hardware. So I get the requirement. At any rate I cloned the repo and manually built the image I needed for now. I'll hop back over when it ships to stable

It would be nice to have an option to run EA controller versions. I picked up a new wifi 6 AP to play around with from the store but it requires 5.14 which doesn't seem to be released as stable yet so at the moment completely stuck. Current plan is to fork the image myself for the time being.

I love being able to add arbitrary disks as needed. I'd love to see the ability to securely remotely access my server without having to configure something like wireguard. I think it would help with less tech savvy users.

I've done the same. Created 3 disks. #1 clover.qcow2 (from the zip file in the video), #2 mojave.img (created myself) #3 vdisk3. The system boots to clover just fine. But there's not an install option for the OS. Just a row of clover options. If anyone else has run into this and has any suggestions that I can try I'd really appreciate it! My XML is as follows: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Mojave</name> <uuid>0ef26eff-b13d-925f-ed4c-db47768e784e</uuid> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="linux.png" os="linux"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='4'/> <vcpupin vcpu='2' cpuset='1'/> <vcpupin vcpu='3' cpuset='5'/> <vcpupin vcpu='4' cpuset='2'/> <vcpupin vcpu='5' cpuset='6'/> <vcpupin vcpu='6' cpuset='3'/> <vcpupin vcpu='7' cpuset='7'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/0ef26eff-b13d-925f-ed4c-db47768e784e_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='4' threads='2'/> </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/Mojave/clover.qcow2'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Mojave/mojave.img'/> <target dev='hdd' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Mojave/vdisk3.img'/> <target dev='hde' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='4'/> </disk> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <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'/> <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'/> <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'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <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'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:df:22:62'/> <source bridge='br0'/> <model type='vmxnet3'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-usb'/> <qemu:arg value='-device'/> <qemu:arg value='usb-mouse,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=somekey'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,vendor=GenuineIntel,kvm=on,+invtsc,+avx,+avx2,+aes,+xsave,+xsaveopt,+ssse3,+sse4_2,+popcnt,vmware-cpuid-freq=on,'/> </qemu:commandline> </domain>

Yes please!

Updated from 6.5.3. Stuck at the screen below. No idea how to get diagnostics via the command line. EDIT: Apparently I too had `dynamix.plg` installed. Removed it, rebooted, and was good to go.

I upgraded from 6.2.4 to 6.3.1 and I've got a call trace in my log when I start now. I turned off docker and disabled all my plugins and I'm still seeing it. I've attached a diagnostics dump of the clean boot. gallifrey-diagnostics-20170217-1044.zip

Try the support section of the forum. You're not going to get help here as this is a release thread and as such is meant to discuss release related topics only.

An additional parity bit will not help with this. Thanks for the reply!

Any chance you'll look in to using the dual parity setup to do some sort of verification and healing of file corruption?

I would do this, but I have a question about if the parity drives have to be the same size, or if I can take this as an opportunity to expand the size of my parity? This was talked about enough last year in regards to which algorithm they were going to use that I can assure you this is quite likely not going to let you do that. It's going to be a literal 2nd parity disk such that you can survive 2 drive failures, not likely to be something that you can use to pool 2 smaller drives.

Well I decided to preclear my 2nd parity drive and now it's sitting in my server just waiting for 6.2. I was convinced we'd get it in January and the drive has been sitting ready to go since then. Now we're almost out of February

New Release! *frantically clicks the announcement link.* Oh... never mind :'(

I get really excited when the latest post in this section is a release, and then I realize someone else commented on this thread...

Can someone ELI5 what Enable Copy-On-Write: in the add-share screen does? I saw it get added to 6.X and I only partially understood what was going on. I for the life of me can't find those patch notes to read over it again. I'm adding a new share, first since this feature was added, and I'm not sure what to set it to...

He'll soon learn BRiT I probably will

It was announced some months ago that 6.2 would feature dual parity and more recently it was said in one of the announcements (ok hinted) that it was in a closed beta. We'll see it soon enough and now that the holidays are done I'd guess sooner rather than later.

So I'm transitioning from smidions version of this container. I installed this one, but the default configuration folder doesn't popular with anything. What should my file structure look like? EDIT: Operator error. Was trying to bind to port 80 when the webui was already there. *facepalm

I'll let this thread sit a few more weeks and if I don't get a bite on the CM590 we'll talk!

These things are notoriously hard to find these days, but I love how simple and plain they are. If you're looking to sell I'm willing to buy if the price is right.

So this is old, but wondering if there was any traction on this? I'm actually looking for just a solution. While I love the unraid SMART if I could add those drives to a dashboard like HDSentinel that would be awesome.

See I'm happy with my Plus license and the 12 disks. I'll never need more than that. I'd rather it either get bolted to that license, or be a reasonable cost upgrade if it goes the route of paid. I'd like to use it without getting a full blown Pro license. I must admit one thing at the beginning of this post. It has been forty years since I took a one semester course in Data theory in Grad School back at Ohio State. And I have forgotten more that I can remember from that course. But once, you get beyond detecting and correcting one error, the mathematics of the problem become much more complex. I would imagine that the cost of upgrading the hardware to be able to implement a double correcting scheme may well outweigh the cost upgrading to a Pro license. There will the cost of at least one more hard drive and perhaps a CPU upgrade required in many servers to deliver satisfactory performance. If you want some conformation of the issues involved, just Google for terms like error detection and correction. Take at look at the math behind these schemes. While there may be a simple and cheap answer to how to implement a 'dual parity' scheme (and I hope there is), I suspect that this feature will involve much more than most of us can visualize at this point. Agreed. That being said I'm more liking the prospect of having that extra layer of redundancy. While my important data that is on my box is backed up my media isn't as at this point it's just not feasible. I could "live without it" in the event of a serious failure. But if I have the option of making that set of data more redundant to reduce (not eliminate obviously) the chances of data loss due to more than one of my drives deciding to bite the dirt before I can rebuild I like the thought of having a higher disk failure tolerance. As far as cost goes I'm already planning on the extra drive, sata card, and enclosure I'm going to need as I've filled my current box. A 50 dollar or whatever upgrade to Pro makes that just a bit harder. A smaller fee to just get that feature would be doable, and obviously including it in Plus and Pro would be nice but I get why that might not happen at the Plus level. As far as error correcting and whatnot that'd be nice but I have no plans on upgrading silicon right now and I can get by without it.

See I'm happy with my Plus license and the 12 disks. I'll never need more than that. I'd rather it either get bolted to that license, or be a reasonable cost upgrade if it goes the route of paid. I'd like to use it without getting a full blown Pro license.

even if we don't get official vanilla support for it though with the community we've got someone will probably be able to come up with a plugin solution.

Dual Parity! *starts looking for a sata card