mrpainnogain

okay somehow it managed to work again after i removed the other NVME which considered to be "broken" . now i remember that the cache with series 2L028LXX used to be labeled "nvme0n1" and somehow it changed to nvme1n1 after the 2nd nvme was added. and that may be causing the issue with the array. all good for now, but i am still figuring out how to do the BTRFS with the other cache.

okay i did start the array , but it says Unmountable: Unsupported or no file system. asas-diagnostics-20240204-2034.zip

i did unassigned all devices , start array , then stop it again . and i am about to mount the cache , and it says the FS is auto . is it safe to start the array again ? the FS was BTRFS previously. do i have to change the file system type to BTRFS manually?

somehow i still got the same warning after changing it to raid1 via the terminal command with sudo nano ...... i also did reboot the system asas-diagnostics-20240204-1959.zip

do i need to do this via terminal? i got the permission denied , when trying to access that as a root

ok currently i am trying to start the array with only the first cache ( the cache that i have been using far before i added another cache) and i am having this " cache - too many missing/wrong devices" . how do i resolve this? asas-diagnostics-20240204-1938.zip

Ok, also do i need to re-direct the vm vdisk directory and other things for the vm? Or i can just hit play button after

So after i disable docker and vm, i can move the file from my cache to array? And after formatting the cache i can move the file back and use the vm and docker without additional settings?

Hey i am having similar issues with raid 1 config, how do you manage to move the data from the cache to array and move it back again? Since i am planning to re-format the nvme disks

Okay , i will try that later. In the mean time, will it be possible if i just unmount the problem device? And just run the pool with the healthy device. Because the last time i did this, i got the “too many missing disks” error when trying to start the array.

are you saying my first cache is failing? or the cache 2 ? is doing BTRFS scrub necessary in this case? just a friendly reminder, i did try different m2 slots with the previous NVME that i thought was broken, but i did not move the NVME on the first cache at all.

i have already done that couple hours ago, the cache came back online. re-mounted to the pool. but the issue happened again

do you mean i need to stop the array and assign cache 1 with nvme0n1 and cache 2 with nvme1n1 and start the array again? will i get "wrong" cache notifications? the 2L082xxx is my first cache from the beginning regarding to the missing device, may be it was the first NVME that i thought was broken, but i was pretty sure that i unmount that NVME and also formatted it. i also took it off from the motherboard.

Hi guys for the last several days my system has been flooded with BTRFS error. i used to have one cache on my unraid pool and one day i decided to add another one as BTRFS so that the i expected the cache to mirror the other one. everything seemed to be running perfectly for couple of weeks until one day i noticed that the temperature on the new cache was showed as "*" . Then i went to check the log and it was flooded with BTRFS error. first i just unmount the disk and re-formatted it , put it back on the pool. but the error seemed to be happening again. i tried to put it on the other NVME slots on the motherboard but it didn't fix the issue. i also tried other NVME stick , but the issue was still there. The other thing i noticed was that every time it happens , the second cache always got crashed since i couldn't see the identity or capabilities details whenever i clicked on that cache icon. Also after i stopped the array , the other cache always went missing until i rebooted the system. I need some guidance here, since i am very new to unraid. thanks here's attached my recent diagnostic. example of the recent logs: Feb 3 00:49:25 ASAS kernel: BTRFS error (device nvme1n1p1): bdev /dev/nvme0n1p1 errs: wr 11126892, rd 1855, flush 30442, corrupt 0, gen 0 Feb 3 00:49:25 ASAS kernel: BTRFS warning (device nvme1n1p1): lost page write due to IO error on /dev/nvme0n1p1 (-5) asas-diagnostics-20240203-0109.zip

Hi there, Seems like i am having similar issues with my CPU cooler. Suddenly when i rebooted my Unraid Server, my Kraken Z63 is not detected anymore. But strangely, the device is detected at the other VM's. and also the XML files of my VM <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='4'> <name>Windows 10</name> <uuid>577c3725-44e6-7800-26d6-11cd892c09f9</uuid> <description>GAMESSSSSS</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>12582912</memory> <currentMemory unit='KiB'>12582912</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='10'/> <vcpupin vcpu='2' cpuset='1'/> <vcpupin vcpu='3' cpuset='11'/> <vcpupin vcpu='4' cpuset='2'/> <vcpupin vcpu='5' cpuset='12'/> <vcpupin vcpu='6' cpuset='3'/> <vcpupin vcpu='7' cpuset='13'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-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/577c3725-44e6-7800-26d6-11cd892c09f9_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <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'/> </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/cache/Windows 10/vdisk1.img' index='4'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/disk3/Windows 10/vdisk2.img' index='3'/> <backingStore/> <target dev='hdd' bus='virtio'/> <alias name='virtio-disk3'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Win10_20H2_v2_English_x64.iso' index='2'/> <backingStore/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <alias name='sata0-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.190-1.iso' index='1'/> <backingStore/> <target dev='hdb' bus='sata'/> <readonly/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <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='0x8'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xd'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0xe'/> <alias name='pci.7'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/> </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='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:4f:e8:36'/> <source bridge='br0'/> <target dev='vnet1'/> <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='/var/lib/libvirt/qemu/channel/target/domain-4-Windows 10/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> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0414'/> <product id='0xa010'/> <address bus='1' device='5'/> </source> <alias name='hostdev2'/> <address type='usb' bus='0' port='3'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc07d'/> <address bus='1' device='6'/> </source> <alias name='hostdev3'/> <address type='usb' bus='0' port='4'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x048d'/> <product id='0x5702'/> <address bus='1' device='11'/> </source> <alias name='hostdev4'/> <address type='usb' bus='0' port='5'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x04a9'/> <product id='0x1746'/> <address bus='1' device='9'/> </source> <alias name='hostdev5'/> <address type='usb' bus='0' port='6'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x04b8'/> <product id='0x0046'/> <address bus='1' device='8'/> </source> <alias name='hostdev6'/> <address type='usb' bus='0' port='2.1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0bda'/> <product id='0x8771'/> <address bus='1' device='3'/> </source> <alias name='hostdev7'/> <address type='usb' bus='0' port='2.2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1532'/> <product id='0x0227'/> <address bus='1' device='7'/> </source> <alias name='hostdev8'/> <address type='usb' bus='0' port='2.3'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1e71'/> <product id='0x3008'/> <address bus='1' device='12'/> </source> <alias name='hostdev9'/> <address type='usb' bus='0' port='2.4'/> </hostdev> <hub type='usb'> <alias name='hub0'/> <address type='usb' bus='0' port='2'/> </hub> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> Which bus number should i change ? cheers