niranjan94

Yes. that's what I ended up doing. Also finished copying over all the data successfully from the old disk3. As of now, looks like there was no data loss. Still a little concerned about what happened since I don't yet know what went wrong where. But anyway, thanks a ton for all your help @JorgeB in debugging this. 😄

So, I pre-cleared the new disk3 again (no errors in the pre-clear report), added it back to the array. Now it says data rebuild is in progress. But I still see Unmountable: wrong or no file system against disk3 while the rebuild is happening. I still also see Unmountable disk present: while the rebuild is happening. I don't remember this being the case during a disk replacement + rebuild. Is this expected ? wednesday-diagnostics-20250809-1003.zip

Yes. This was a weird behavior. Thankfully, I did not have any critical data on disk3 that I would be sad about loosing. Just some entertainment stuff. So, I'm gonna go ahead reformat the new disk3, add it to the array and copy over whatever data I can from the old disk three.

Unfortunately it failed too # xfs_repair -v /dev/sdb1 Phase 1 - find and verify superblock... couldn't verify primary superblock - not enough secondary superblocks with matching geometry !!! attempting to find secondary superblock... ......................................................................................................................................................................................................................................... ..................................................................................................................................................................................Sorry, could not find valid secondary superblock Exiting now.

# wipefs -a /dev/sdb /dev/sdb: 2 bytes were erased at offset 0x000001fe (dos): 55 aa /dev/sdb: calling ioctl to re-read partition table: Success # sgdisk -o -a 8 -n 1:32K:0 /dev/sdb Creating new GPT entries in memory. The operation has completed successfully.Then tried mounting with the UD plugin and the mount failed. Aug 7 22:43:01 WEDNESDAY unassigned.devices: Mounting partition 'sdb1' at mountpoint '/mnt/disks/WW675B6T'... Aug 7 22:43:01 WEDNESDAY unassigned.devices: Mount cmd: /sbin/mount -t 'xfs' -o rw,relatime '/dev/sdb1' '/mnt/disks/WW675B6T' Aug 7 22:43:01 WEDNESDAY kernel: XFS (sdb1): Mounting V5 Filesystem e28b8fc3-0300-49ce-be43-85460e8a8b4c Aug 7 22:43:01 WEDNESDAY kernel: XFS (sdb1): totally zeroed log Aug 7 22:43:01 WEDNESDAY kernel: XFS (sdb1): Corruption warning: Metadata has LSN (4:33) ahead of current LSN (1:0). Please unmount and run xfs_repair (>= v4.3) to resolve. Aug 7 22:43:01 WEDNESDAY kernel: XFS (sdb1): log mount/recovery failed: error -22 Aug 7 22:43:01 WEDNESDAY kernel: XFS (sdb1): log mount failed Aug 7 22:43:02 WEDNESDAY unassigned.devices: Mount of 'sdb1' failed: 'mount: /mnt/disks/WW675B6T: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error. dmesg(1) may have more information after failed mount system call.' Aug 7 22:43:02 WEDNESDAY unassigned.devices: Partition 'WW675B6T' cannot be mounted.

Filesystem check on the emulated disk resulted in the same error as before. bad primary superblock - bad magic number !!! attempting to find secondary superblock... Ran sgdisk -o -a 8 -n 1:32K:0 /dev/sdb and got this error. Should I run with -g? Found invalid GPT and valid MBR; converting MBR to GPT format in memory. *************************************************************** Non-GPT disk; not saving changes. Use -g to override.

I still have the old disk. I'm able to still read the data from it via an external linux machine. I rebooted and the disk still did not mount (same error: Unmountable: wrong or no file system) I unassigned disk3 and have started the array now. Unraid says device is missing(disabled), contents emulated for disk3. But when checking the shares, I see that data that was stored in disk3 missing (So the emulation isn't working as expected) Both current and old disk3 drives are still intact New diagnostics attached wednesday-diagnostics-20250807-1941.zip

# fdisk -l /dev/sdb Disk /dev/sdb: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: ST4000VN006-3CW1 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: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sdb1 1 4294967295 4294967295 2T 0 Empty Partition 1 does not start on physical sector boundary.

The disk size is 4TB. But seems to be showing a 2TB in this # fdisk -l /dev/sdb1 Disk /dev/sdb1: 2 TiB, 2199023255040 bytes, 4294967295 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 3584 bytes

No superblock was found after more than 2 hours. I have cancelled this now That has a similar output like xfs repair on md3p1 # xfs_repair -n /dev/sdb1 Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... warning: device is not properly aligned /dev/sdb1 .............................................................

This is what the xfs_repair is doing Phase 1 - find and verify superblock... couldn't verify primary superblock - not enough secondary superblocks with matching geometry !!! attempting to find secondary superblock... .............................................................. But there were no issues reported before. The array rebuilt successfully with the new disk and was running okay.

Configuration Version: 7.1.4 Parity ST4000VN008 - 4 TB (sde) Disk 1 ST4000VN006 - 4 TB (sdc) Disk 2 ST2000VN004 - 2 TB (sdf) Disk 3 ST4000VN006 - 4 TB (sdb) - NEW Timeline Old disk 3 (3TB) was seeing some read errors. Old drive. I was purchasing a replacement drive Unraid disabled disk 3 all of a sudden and started emulating it New disk 3 (4TB) arrived Stopped the array Removed old disk 3 & replaced it with new disk 3 (4TB) Ran pre-clear on the new disk 3 Started the array Unraid successfully rebuilt the new disk 3 (4TB) No data loss. All okay. Array is green. Parity check is green. All of a sudden today the new disk3 went into Unmountable: Unsupported or no file system state What I have done after Stopped the array and started it Stopped that array and started it in maintenance mode /sbin/xfs_repair -n /dev/md3p1 in progress. It has been running for a couple of hours now. Any help and guidance to solve this will be appreciated :) Diagnostics attached. wednesday-diagnostics-20250807-1528.zip

Specs Unraid Version: 6.12.13 CPU: AMD Ryzen 9 7950X Motherboard: MSI X670E CARBON RAM: 64 GB DDR5 (32 GB x 2) What I have done Ubuntu VM on Unraid with 8 CPU and 8704 mb of RAM (XML Attached) CPU Pinning & Isolation to ensure no other service is using those 8 CPUs (4 physical cores + 4 hyperthreaded cores) assigned to the VM Inside the VM, android emulator is started using https://github.com/google/android-emulator-container-scripts (It uses docker & KVM Nested Virtualization) What is happening Sometimes, when the emulator is running and is busy, all of Unraid just crashes (probably some sort of kernel panic?) and reboots. What have I checked Have enabled `Mirror syslog to flash` and checked the syslog for any indication of the crash reason. Syslog has nothing around the time of the crash. All okay before. All okay after. Connected a display to Unraid to monitor the logs and nothing came there when it crashed either as far as I can tell (it quickly went blank) Have increased the RAM/Memory on the VM in question and checked, doesn't seem to help. (Though I'd think if it was a resource constraint only the VM should have crashed and not the entire Unraid server) --- I have tried everything I can think of and currently at a loss for ideas. Any help would be appreciated Thank you in advance ... ubuntu-vm.xml

Hi @eight-year-petitioner2843 I was actually able to get this working without any custom BIOS by doing a full delete of all NVIDIA related things and installing them from scratch. Been running fine without any issues for the past couple of months !

I managed to get this working by doing the following in this order (But not exactly sure which of these was the final fix) Switched to Virtual display drivers Started the VM Scrubbed NVIDIA related drivers & software Disabled Hyper-V from within windows features. (Seems I had it enabled) Stopped the VM Changed from Virtual display drivers back to NVIDIA Started the VM Installed the NVIDIA drivers And voila! Started working like a charm ! My currently working VM config <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 11 - NVMe</name> <uuid>e5695dd6-49b8-42a3-b340-ed310de457e4</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>17301504</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>16</vcpu> <cputune> <vcpupin vcpu='0' cpuset='8'/> <vcpupin vcpu='1' cpuset='24'/> <vcpupin vcpu='2' cpuset='9'/> <vcpupin vcpu='3' cpuset='25'/> <vcpupin vcpu='4' cpuset='10'/> <vcpupin vcpu='5' cpuset='26'/> <vcpupin vcpu='6' cpuset='11'/> <vcpupin vcpu='7' cpuset='27'/> <vcpupin vcpu='8' cpuset='12'/> <vcpupin vcpu='9' cpuset='28'/> <vcpupin vcpu='10' cpuset='13'/> <vcpupin vcpu='11' cpuset='29'/> <vcpupin vcpu='12' cpuset='14'/> <vcpupin vcpu='13' cpuset='30'/> <vcpupin vcpu='14' cpuset='15'/> <vcpupin vcpu='15' cpuset='31'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-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/e5695dd6-49b8-42a3-b340-ed310de457e4_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'/> <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='qemu-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <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='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0xa'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0xb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' 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='pci' index='0' model='pcie-root'/> <interface type='bridge'> <mac address='12:12:00:db:cb:f8'/> <source bridge='br0'/> <model type='virtio-net'/> <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='3'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> </tpm> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x03' 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> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </source> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> </domain>