Goldmaster Posted June 11, 2022 Share Posted June 11, 2022 (edited) Managed to solve this issue Turns out that its a problem with the wd m.2 drive I did email Western Digital for advice, and basically the issue stems from WD not testing hard drives in Linux. So after swapping app data round, reverting to docker img based rather than folder, I have pretty much sorted. Just need to reinstall programs, but that's about it. If anyone is looking at pass though hardware and find it suddenly doesn't work like this, then that might be a similar reason. I will leave the original post up below. Hi there, I had setup a working dual boot of windows 11 on unraid 6.9 and would work fine except for the ocational freeze up. I have a gt 710 gpu passed though, and used a m.2 drive for booting off. So I can boot in bere metal, like a normal pc or as a vm in unraid. After 6.10, the vm now doesnt boot, but just starts then pause, getting stuck at the tanocore logo and no windows loading icon. this is the xml settings <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 11 dual boot</name> <uuid>986c0163-34fc-a197-0b59-fc3497b10b59</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows11.png" os="windows10"/> </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='16'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='18'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='20'/> <vcpupin vcpu='6' cpuset='6'/> <vcpupin vcpu='7' cpuset='22'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-5.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/986c0163-34fc-a197-0b59-fc3497a10b58_VARS-pure-efi.fd</nvram> <boot dev='hd'/> </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='4' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </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> <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> <controller type='pci' index='0' model='pci-root'/> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:ce:87:e6'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' 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'/> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x2f' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/vbios/GeForce GT 710.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x2f' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x2d' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'/> </domain> When trying to boot, 2 times. this is what I get in the log window -rtc base=localtime \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 \ -netdev tap,fd=35,id=hostnet0 \ -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:ce:87:e6,bus=pci.0,addr=0x2 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0,index=0 \ -chardev socket,id=charchannel0,fd=33,server=on,wait=off \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=1 \ -audiodev '{"id":"audio1","driver":"none"}' \ -device 'vfio-pci,host=0000:2f:00.0,id=hostdev0,bus=pci.0,addr=0x4,romfile=/mnt/user/isos/vbios/GeForce GT 710.rom' \ -device vfio-pci,host=0000:2f:00.1,id=hostdev1,bus=pci.0,addr=0x5 \ -device vfio-pci,host=0000:2d:00.0,id=hostdev2,bus=pci.0,addr=0x6 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/0 (label charserial0) 2022-06-11T09:40:57.090130Z qemu-system-x86_64: vfio_err_notifier_handler(0000:2d:00.0) Unrecoverable error detected. Please collect any data possible and then kill the guest 2022-06-11T13:53:49.073923Z qemu-system-x86_64: terminating on signal 15 from pid 17120 (/usr/sbin/libvirtd) 2022-06-11 13:53:50.474+0000: shutting down, reason=destroyed 2022-06-11 13:55:36.093+0000: starting up libvirt version: 8.2.0, qemu version: 6.2.0, kernel: 5.15.43-Unraid, hostname: Hammerthread LC_ALL=C \ PATH=/bin:/sbin:/usr/bin:/usr/sbin \ HOME='/var/lib/libvirt/qemu/domain-2-Windows 11 dual boot' \ XDG_DATA_HOME='/var/lib/libvirt/qemu/domain-2-Windows 11 dual boot/.local/share' \ XDG_CACHE_HOME='/var/lib/libvirt/qemu/domain-2-Windows 11 dual boot/.cache' \ XDG_CONFIG_HOME='/var/lib/libvirt/qemu/domain-2-Windows 11 dual boot/.config' \ /usr/local/sbin/qemu \ -name 'guest=Windows 11 dual boot,debug-threads=on' \ -S \ -object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-2-Windows 11 dual boot/master-key.aes"}' \ -blockdev '{"driver":"file","filename":"/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}' \ -blockdev '{"driver":"file","filename":"/etc/libvirt/qemu/nvram/986c0163-34fc-a197-0b59-fc3497a10b58_VARS-pure-efi.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash1-format","read-only":false,"driver":"raw","file":"libvirt-pflash1-storage"}' \ -machine pc-i440fx-5.1,usb=off,dump-guest-core=off,mem-merge=off,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-format,memory-backend=pc.ram \ -accel kvm \ -cpu host,migratable=on,topoext=on,hv-time=on,hv-relaxed=on,hv-vapic=on,hv-spinlocks=0x1fff,hv-vendor-id=none,host-cache-info=on,l3-cache=off \ -m 8192 \ -object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":8589934592}' \ -overcommit mem-lock=off \ -smp 8,sockets=1,dies=1,cores=4,threads=2 \ -uuid 986c0163-34fc-a197-0b59-fc3497a10b58 \ -display none \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=36,server=on,wait=off \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 \ -netdev tap,fd=37,id=hostnet0 \ -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:ce:87:e6,bus=pci.0,addr=0x2 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0,index=0 \ -chardev socket,id=charchannel0,fd=35,server=on,wait=off \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=1 \ -audiodev '{"id":"audio1","driver":"none"}' \ -device 'vfio-pci,host=0000:2f:00.0,id=hostdev0,bus=pci.0,addr=0x4,romfile=/mnt/user/isos/vbios/GeForce GT 710.rom' \ -device vfio-pci,host=0000:2f:00.1,id=hostdev1,bus=pci.0,addr=0x5 \ -device vfio-pci,host=0000:2d:00.0,id=hostdev2,bus=pci.0,addr=0x6 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/0 (label charserial0) 2022-06-11T13:55:41.825439Z qemu-system-x86_64: vfio_err_notifier_handler(0000:2d:00.0) Unrecoverable error detected. Please collect any data possible and then kill the guest 2022-06-11T13:56:45.026047Z qemu-system-x86_64: terminating on signal 15 from pid 17120 (/usr/sbin/libvirtd) 2022-06-11 13:56:46.426+0000: shutting down, reason=destroyed -nodefaults \ -chardev socket,id=charmonitor,fd=36,server=on,wait=off \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 \ -netdev tap,fd=37,id=hostnet0 \ -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:ce:87:e6,bus=pci.0,addr=0x2 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0,index=0 \ -chardev socket,id=charchannel0,fd=35,server=on,wait=off \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=1 \ -audiodev '{"id":"audio1","driver":"none"}' \ -device 'vfio-pci,host=0000:2f:00.0,id=hostdev0,bus=pci.0,addr=0x4,romfile=/mnt/user/isos/vbios/GeForce GT 710.rom' \ -device vfio-pci,host=0000:2f:00.1,id=hostdev1,bus=pci.0,addr=0x5 \ -device vfio-pci,host=0000:2d:00.0,id=hostdev2,bus=pci.0,addr=0x6 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/0 (label charserial0) 2022-06-11T13:55:41.825439Z qemu-system-x86_64: vfio_err_notifier_handler(0000:2d:00.0) Unrecoverable error detected. Please collect any data possible and then kill the guest 2022-06-11T13:56:45.026047Z qemu-system-x86_64: terminating on signal 15 from pid 17120 (/usr/sbin/libvirtd) 2022-06-11 13:56:46.426+0000: shutting down, reason=destroyed 2022-06-11 14:05:05.485+0000: starting up libvirt version: 8.2.0, qemu version: 6.2.0, kernel: 5.15.43-Unraid, hostname: Hammerthread LC_ALL=C \ PATH=/bin:/sbin:/usr/bin:/usr/sbin \ HOME='/var/lib/libvirt/qemu/domain-3-Windows 11 dual boot' \ XDG_DATA_HOME='/var/lib/libvirt/qemu/domain-3-Windows 11 dual boot/.local/share' \ XDG_CACHE_HOME='/var/lib/libvirt/qemu/domain-3-Windows 11 dual boot/.cache' \ XDG_CONFIG_HOME='/var/lib/libvirt/qemu/domain-3-Windows 11 dual boot/.config' \ /usr/local/sbin/qemu \ -name 'guest=Windows 11 dual boot,debug-threads=on' \ -S \ -object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-3-Windows 11 dual boot/master-key.aes"}' \ -blockdev '{"driver":"file","filename":"/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}' \ -blockdev '{"driver":"file","filename":"/etc/libvirt/qemu/nvram/986c0163-34fc-a197-0b59-fc3497a10b58_VARS-pure-efi.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash1-format","read-only":false,"driver":"raw","file":"libvirt-pflash1-storage"}' \ -machine pc-i440fx-5.1,usb=off,dump-guest-core=off,mem-merge=off,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-format,memory-backend=pc.ram \ -accel kvm \ -cpu host,migratable=on,topoext=on,hv-time=on,hv-relaxed=on,hv-vapic=on,hv-spinlocks=0x1fff,hv-vendor-id=none,host-cache-info=on,l3-cache=off \ -m 8192 \ -object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":8589934592}' \ -overcommit mem-lock=off \ -smp 8,sockets=1,dies=1,cores=4,threads=2 \ -uuid 986c0163-34fc-a197-0b59-fc3497a10b58 \ -display none \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=36,server=on,wait=off \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 \ -netdev tap,fd=37,id=hostnet0 \ -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:ce:87:e6,bus=pci.0,addr=0x2 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0,index=0 \ -chardev socket,id=charchannel0,fd=35,server=on,wait=off \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=1 \ -audiodev '{"id":"audio1","driver":"none"}' \ -device 'vfio-pci,host=0000:2f:00.0,id=hostdev0,bus=pci.0,addr=0x4,romfile=/mnt/user/isos/vbios/GeForce GT 710.rom' \ -device vfio-pci,host=0000:2f:00.1,id=hostdev1,bus=pci.0,addr=0x5 \ -device vfio-pci,host=0000:2d:00.0,id=hostdev2,bus=pci.0,addr=0x6 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/24 (label charserial0) 2022-06-11T14:05:20.898479Z qemu-system-x86_64: vfio_err_notifier_handler(0000:2d:00.0) Unrecoverable error detected. Please collect any data possible and then kill the guest Any ideas why the exact vm that works fine on 6.9 now doesn't work on 6.10? My system specs are in my signature below. I will add that I have tried recreating the vm with what I know works and I still get the same issues. Looking at the log, it appears to be the m.2 drive. I Wonder if the latest version Isn't compatible with my m.2 or something? Thank you hammerthread-diagnostics-20221011-1309.zip Edited November 8, 2022 by Goldmaster Marking as solved for now Quote Link to comment
song Posted June 15, 2022 Share Posted June 15, 2022 (edited) I also have the same problem. In version 6.92, "Mac OS, Ubuntu and windows" can all work normally. After upgrading version 6.10, "Mac OS and Ubuntu" can normally drive the independent display. Only windows has an error. The graphics card can output pictures to the display, but the installation of the graphics card driver will send an error 43. I tried to rollback to version 6.92. Everything is normal. The independent display can be used normally Edited June 15, 2022 by song Quote Link to comment
JorgeB Posted June 17, 2022 Share Posted June 17, 2022 There are some known issues with V6.10.x, older Nvidia GPUs and pass-trough, VM might fail to boot or boot but give a code 43 error for the Nvidia driver, please try booting without the GPU (use VNC) just to check if the problem is the NVMe device or the GPU. Quote Link to comment
Goldmaster Posted July 24, 2022 Author Share Posted July 24, 2022 (edited) I did try vnc and that failed. I think it maybe that I have to reinstall windows 11 as I updated from windows 10 to 11. My motherboard does support windows 11 out of the box. Edited July 24, 2022 by Goldmaster Quote Link to comment
Goldmaster Posted July 31, 2022 Author Share Posted July 31, 2022 On 6/17/2022 at 12:57 PM, JorgeB said: There are some known issues with V6.10.x, older Nvidia GPUs and pass-trough, Where have you read this? Bit strange for a perfectly working gpu to have issues like this. its quite modern only 2016. Id more likely guess that latest hardware would have temporary issues if open source drivers are not available or been updated for support. Quote Link to comment
JorgeB Posted July 31, 2022 Share Posted July 31, 2022 9 minutes ago, Goldmaster said: Where have you read this? Nvidia 600 and 700 series models usually need an extra setting to work with v6.10.x, see below: https://forums.unraid.net/topic/124890-gtx650ti-code-43-with-windows-10/?do=findComment&comment=1139615 Quote Link to comment
Solution Goldmaster Posted October 9, 2022 Author Solution Share Posted October 9, 2022 On 6/17/2022 at 12:57 PM, JorgeB said: There are some known issues with V6.10.x, older Nvidia GPUs and pass-trough, VM might fail to boot or boot but give a code 43 error for the Nvidia driver, please try booting without the GPU (use VNC) just to check if the problem is the NVMe device or the GPU. I have tried 6.11 and I am still getting issues. its deafeningly the m.2 drive. I don't know why or how. Quote Link to comment
JorgeB Posted October 11, 2022 Share Posted October 11, 2022 Do you have a different m.2 device you could test with? Very difficult to help if it's a device specif issue. Quote Link to comment
Goldmaster Posted October 21, 2022 Author Share Posted October 21, 2022 Iam afraid not. it is the only m.2 drive I have, and the other is used for cache. I have tried Debian install and I still have the exact same error. I am on bios version 0701. Quote Link to comment
JorgeB Posted October 21, 2022 Share Posted October 21, 2022 You could swap them. Quote Link to comment
Goldmaster Posted October 21, 2022 Author Share Posted October 21, 2022 11 minutes ago, JorgeB said: You could swap them. Humm. Didn't think of that. Not sure how I would go about moving appdata, domains ect off the Samsung drive to the wd drive. There is space to do it. Quote Link to comment
trurl Posted October 21, 2022 Share Posted October 21, 2022 9 minutes ago, Goldmaster said: moving appdata, domains ect off the Samsung drive to the wd drive Midnight Commander is built-in, the disks are in /mnt Quote Link to comment
trurl Posted October 21, 2022 Share Posted October 21, 2022 https://wiki.unraid.net/Manual/Shares#Use_Cache_.28and_Mover_Behavior_with_User_Shares.29 Quote Link to comment
Goldmaster Posted October 21, 2022 Author Share Posted October 21, 2022 Thank you. So its a case of copy stuff off the samsung drive to the wd drive. but im not sure how this cache pool thing works, I take it is a case of set wd drive as cache, then stop vm and docker service and copy stuff from samsung drive to wd drive. Unassign Samsung drive from unraid. install windows or debian on the drive? Quote Link to comment
JorgeB Posted October 21, 2022 Share Posted October 21, 2022 Basically yes, copy the data, services must be stopped to copy, assign it as cache and leave the other unassigned. Quote Link to comment
Goldmaster Posted October 25, 2022 Author Share Posted October 25, 2022 Thank you. only issue is that some files have seamed to copy. Maybe duplicate but running mover doesn't move and replace. is there a way to say run say sudo mv -r /mnt/cache /mnt/disk1 or something like that? idearly in gui frendly way. Issue was that my server had gone to sleep, so hasn't been able to move everything in a whole go? Quote Link to comment
JorgeB Posted October 25, 2022 Share Posted October 25, 2022 Use Midnight Commander (mc on the console), you can select all files/folders to copy/move, use the Insert key IIRC. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.