berta123

Yes I have plenty of connections. In fact all the drives are in the server right now as I do a pre-clear on the new drives to test them. Is there a particular command I would use to copy over to the new drives? Would I be able to change from xfs to ZFS for the array drives in the process? Also does this work if I need to reduce the total number of drives?

It’s fine for it to be offline.

Hello everyone! I decided to build out a remote backup server for my unraid instance. I currently have dual parity with 12 data disks. My plan is to take all my existing drives and move them to a simple QNAP device and then use all new SAS drives in the array. The new drives are larger than the old in aggregate but there are less drives (replacing 12tb drives with 18tb) So my question is how can I most efficiently migrate data from the old drives to the new and remove the old drives from the array? Keeping Parity throughout the process is nice, but not a strict requirement. I seem to have found 2 ways online, replacing drives 2 at a time and rebuild parity, or transfer data off the old drives and zero them out. Is there a 3rd way given the large number of disks? Which of these would be faster?

Yes that certainly is a possibility, but as evidenced by this forum this appears to be something that can happen and I’m not sure I quite understand why parity is no help in this situation. Could I have not just popped out the “unformatted” disk and replaced it with a new disk and had it rebuild the “failed” (unformatted) drive?

Ok I’m going to reformat. Maybe as a single disk ZFS with 6.12! Can you give any ideas of what to do to protect against this in the future (besides a full backup which I already do to stuff that is not replaceable)

Not really, but the disk is fairly new and 90% of data on the server is entirely replaceable (backups etc) so perhaps the best path is to just wipe the disk and start over? I assume the double parity doesn’t help in this case?

Updated diagnostics attached. The disk also has a new error message: "Unmountable: Wrong or No Filesystem" beta-diagnostics-20230617-0944.zip

Do I need to be in a certain mode (maintenance etc)? From when the array is started: Disk /dev/sdn: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors Disk model: ST8000NM017B-2TJ Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: F8C062CD-3423-4A8F-BAEE-836784168F0B Device Start End Sectors Size Type /dev/sdn1 64 15628053134 15628053071 7.3T Linux filesystem

Attached below. Thanks for taking a look @JorgeB beta-diagnostics-20230616-1604.zip

Hi all, Noticing this error after a power outage. I say noticing because I've been really busy for the last few weeks since I added this drive and it may have been there the whole time. Or maybe it's new. Honestly not sure. At any rate my last added and newest drive in the array is saying Unmountable: unsupported or no file system even when booted into maintenance mode. I'd love some help on next steps? I started to run xfs_repair but then I noticed the drive is set to auto for a file system so I wasn't even sure that was right. Diags attached. Thanks! beta-diagnostics-20230615-2105.zip

I recently migrated my unraid system over to new hardware (Intel i9-13900k from old threadripper). I am trying to get WSL2 running in a windows VM and it seems every time I enable Virtual Machine Platform the VM refuses to boot and goes to Startup Repair. Frustratingly it won't give me the safe boot option or allow me to restore from a restore point so to troubleshoot my only option is to continually reinstall the OS. I've tried Q35 and i440fx. I have kvm-intel.nested=1 in my syslinux config. I'm at a total loss. Any ideas? Here is my config: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='8'> <name>matt-ws-vm</name> <uuid>59d27f82-1b9f-b464-d414-569246da5e34</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>16</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='5'/> <vcpupin vcpu='6' cpuset='6'/> <vcpupin vcpu='7' cpuset='7'/> <vcpupin vcpu='8' cpuset='8'/> <vcpupin vcpu='9' cpuset='9'/> <vcpupin vcpu='10' cpuset='10'/> <vcpupin vcpu='11' cpuset='11'/> <vcpupin vcpu='12' cpuset='12'/> <vcpupin vcpu='13' cpuset='13'/> <vcpupin vcpu='14' cpuset='14'/> <vcpupin vcpu='15' cpuset='15'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-7.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/59d27f82-1b9f-b464-d414-569246da5e34_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='8' threads='2'/> <cache mode='passthrough'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <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='raw' cache='writeback'/> <source file='/mnt/user/domains/matt-ws-vm/vdisk1.img' index='3'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Win11_22H2_English_x64v1.iso' index='2'/> <backingStore/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <alias name='ide0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.225-2.iso' index='1'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </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'/> </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='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:73:2b:d0'/> <source bridge='br0'/> <target dev='vnet7'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' 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='/var/lib/libvirt/qemu/channel/target/domain-8-matt-ws-vm/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> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> <alias name='tpm0'/> </tpm> <graphics type='vnc' port='5901' autoport='yes' websocket='5701' 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='0x02' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>

For others who find this, switching to virtio from virtio-net AND uninstalling the driver from windows and re-installing it seemed to get the speeds up. I now get 4-6 Gb/s which is still much less than the 32 Gb/s I get from a Linux VM, but I suppose that is just the Windows tax?

I tried virtio and got similar results. I’m surprised it’s so slow. I saw this post from a long time ago that seems to suggest it is possible to get 15gbps VM to host but only on 6.8.3? Any ideas what could have changed in newer versions? I’m running a threadripper cpu so I doubt cpu performance is the bottleneck.

Yep! That’s what I meant by proxmox host. The proxmox host is a separate machine on the network and sees the expected speeds.

Bumping this back up