Daryl Williams

Thanks again for your help.

Thanks. Worked it out. I somehow must have run it on my 2tb drive at some point. This was showing as the boot device. I've unassigned it and run the onboarding wizard and it's giving me all the options. Thanks again

/dev/nvme0n1p1: LABEL="zfs_cache" UUID="13032507992519089239" UUID_SUB="5333955551239897464" BLOCK_SIZE="4096" TYPE="zfs_member" /dev/nvme2n1p1: UUID="3c263600-df91-48d4-83f9-6cdac5359cf3" UUID_SUB="cd7f0384-5c4c-4a11-8e8f-5c65a67e6cbc" BLOCK_SIZE="4096" TYPE="btrfs" /dev/nvme5n1p1: LABEL="zfs_cache" UUID="13032507992519089239" UUID_SUB="3451360335556235392" BLOCK_SIZE="4096" TYPE="zfs_member" /dev/sde1: UUID="48e73b97-a226-49c0-81b8-87ee5ce2ccaf" BLOCK_SIZE="512" TYPE="xfs" /dev/nvme1n1p1: LABEL="zfs_cache" UUID="13032507992519089239" UUID_SUB="4102454655082185234" BLOCK_SIZE="4096" TYPE="zfs_member" /dev/sdh4: UUID="437930af-9bd3-41e4-b524-fdfa175c5691" UUID_SUB="c0815c22-ace4-4c17-892c-25c4d4f595bf" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="5c7bc212-5123-4337-b7fb-51fdb20aeb50" /dev/sdh2: LABEL_FATBOOT="EFI" LABEL="EFI" UUID="4D27-19D8" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="32392bc5-1239-4721-8298-f9a0430ff491" /dev/sdo1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="272C-EBE2" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="0a848e3f-01" /dev/loop1: BLOCK_SIZE="131072" TYPE="squashfs" /dev/loop0: BLOCK_SIZE="131072" TYPE="squashfs" /dev/sdf1: UUID="7c7bec4e-1820-40db-a1e2-8e56a9d129c5" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="6cbf4976-009e-4825-9e83-cc991b7edbcf" /dev/sdd1: UUID="87dd318d-af1f-423d-addf-8fd965aeb7e9" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="7e2cd86c-1882-4b0d-b060-3018c879d526" /dev/sdm1: UUID="401d73c1-73ec-4c57-a1d7-85d59883f0d2" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="dae2a088-b217-45fd-80a0-7cd65f6b8161" /dev/sdb1: UUID="07e839b4-419d-4df3-aac2-6f9e9a1aa30b" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="07bed044-d4ce-4440-8651-46d31f8698b3" /dev/sdk1: UUID="ed14d29e-efd1-4581-b2f6-bb16622a7d5a" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="3502bedc-f8c9-44b0-95c0-0c4c1508e67a" /dev/sdi1: UUID="56f52da6-2c6d-4f59-bbcc-4cc008241dac" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="acb0b525-8a74-49a4-a127-a61d138f2543" /dev/sdg1: UUID="f29ed138-e002-4d3b-8ab1-53dfdc4697cb" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="f8be1a26-1426-48de-836c-8780b76a431e" /dev/sdc1: UUID="82eabfbb-cd10-461b-9aa1-f12f4468d2dd" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="747b3ba4-a110-4b80-9731-bd9d74837fd8" /dev/sdl1: UUID="7fb806e1-a73d-4cfc-91e8-d5c35fb8e395" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="bf8b1825-74eb-4b19-9691-7e017621292f" /dev/sdj1: UUID="22bb480e-42e8-4559-b318-c7db85165f17" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="2ca18e07-4505-4170-af26-7a890fb34819" /dev/sda1: PARTUUID="84f27b8b-a42f-41bb-ae23-4283adf4ff61" /dev/sdh3: PARTLABEL="Unraid Boot Partition" PARTUUID="48587c76-f1c7-4022-ba41-62b5fdfcf397" /dev/sdh1: PARTLABEL="BIOS Boot Partition" PARTUUID="8c52e5dc-4f3a-4a0b-bafb-6a3dff41b945"

Correct. The original boot device is unassigned, as are the 2 Optane drives. The onboard loads, it shows the configuration page for server name, etc, then the plugins and finally the summary with confirm and apply, but no boot options.

Sorry. The screenshot is a little misleading. I started the array after trying the onboarding wizard, as I need to retrieve some files. The array was stopped when I tried.

I've run the command on the boot disk. Which is now showing as unmountable. Do I need to do anything after this, as it's still not allowing reconfiguration in the onboarding process. Am I being stupid?

I've booted from the flash and the drives are as below. I have the two new drives. But when I run through the onboarding process it just shows my existing setup and ask me to confirm and apply but doesn't give me an option to create a new pool. What am I doing wrong? I'm also getting a license mismatch after booting with flash. I assume this is correct because I'm assuming it's due to swapping boot devices?

So just change the boot order in the BIOS to start up from the flash drive again then try again? Do I need to do anything with the licensing? Or will it just read it from the existing TPM licensing?

Hi, I've recently upgraded to 7.3.0-beta.1 and have run the process to boot from an internal drive. This worked as planned. I've now got hold of a couple of Intel Optane 16GB drives, which I want to use in mirror to run the Unraid OS. I've run the onboarding wizard again, but don't get the option to select any drives for a new configuration. Am I doing something wrong? Both the drives can be seen in unassigned disk devices. Any advice would be appreciated.

I replaced I a disk in my array. Parity sync went fine but after rebooting server one disk is no longer included in the array and the other which I've tried to add in which said was missing, now says it wrong. Any troubleshooting help would really be appreciated. djw-unraid-diagnostics-20260216-1731.zip

I've now managed to dump the vbios on a Windows PC using GPU Z. Sonoma boots and I can VNC to it when while the it is using the WX 2100 as the primary GPU, but it's not visible from within the VM. Any ideas?

I've built a Sonoma VM and am trying to passthrough my AMD WX 2100 gpu. I've followed the instructions from SpaceInvaderOne but cannot seem to get it to work. The VM boots up and is accessible using virtual GPU, and will also boots when I add the physicals devices, and can connect via RealVNC. Unfortunately, the GPU is not listed in the VM and I'm restricted to a lower resolution. The bindings are as follows. lspci -k | grep -A 2 "09:00" 09:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Lexa XT [Radeon PRO WX 2100] Subsystem: Dell Device 0b0c Kernel driver in use: vfio-pci -- 09:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X] Subsystem: Dell Device aae0 Kernel driver in use: vfio-pci Is it right that the audio device is listed as RX 550.... which strangely was my old gpu which is no longer in the sytem I'm running Unraid 7.2 I get the following output. Script location: /tmp/user.scripts/tmpScripts/Dump vBios/script Note that closing this window will abort the execution of this script You have selected this device to dump the vbios from 09:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Lexa XT [Radeon PRO WX 2100] This does look like a valid GPU to me. Continuing ......... Checking if location to put vbios file exists Vbios folder already exists I will try and dump the vbios without disconnecting and reconnecting the GPU This normally only works if the GPU is NOT the Primary or the only GPU I will check the vbios at the end. If it seems wrong I will then retry after disconnecting the GPU Defining temp vm with gpu attached Domain 'dumpvbios' defined from /tmp/dumpvbios.xml Starting the temp vm to allow dump Domain 'dumpvbios' started Waiting for a few seconds ..... Stopping the temp vm Domain 'dumpvbios' destroyed Removing the temp vm Domain 'dumpvbios' has been undefined Okay dumping vbios file named WX2100.rom to the location /mnt/user/isos/vbios/ cat: rom: Input/output error Um.... somethings gone wrong and I couldn't dump the vbios for some reason Sometimes when this happens all we need to do to fix this is 'stub' or 'bind to the vfio' the gpu and reboot the server This can be done in Unraid 6.8.3 with the use of the vfio config plugin or if you are on Unraid 6.9 or above it can be done directly from the gui in Tools/System Devices .....So please do this and run the script again Any help would be greatly appreciated. Please let me know if you need any further information. Thanks.

Sorry to be a pain. I've gone through the whole process again and the RaidZ cache is now there and is showing data in it. When I enable docker and VM I get the following. Appdata and System shares appear to be pointing to the right location. Maybe I'm missing something very simple? I've attached fresh diagnostics. Thanks in advance. djw-unraid-diagnostics-20230808-1943.zip

Great. Thanks for your help.

That's great. It's back. It's showing the file btrfs 🤔 I guess to run as ZFS, I will need to go through the process of moving to array, then reformatting to RaidZ and then move back?

Just want to check I'm doing this right. Do I click this?

Hi All, I decided to upgraded my cache to a ZFS pool. Migrated data from appdate, domain and system to array using mover. Configured new pool and migrated all back with no problems. Dockers started etc. The problem I have now is that after a reboot, all data has now gone and I'm getting the error UNMOUNTABLE: UNSUPPORTED OR NO FILE SYSTEM ZFS. I'm now at a loss of what to do. Is the data recoverable? djw-unraid-diagnostics-20230808-1339.zip

Thanks guys. All sorted.

Thanks for the info. The rootshare is setup to /mnt/user0. This was automatically done using the built in rootshare creator. I seem remember that I used SpaceInvaders instructions on how to manually create a rootshare, which I did to /mnt/user. Is there a way of amending the path of the rootshare via the automatic process to point to /mnt/user or to create a new rootshare to this location?

Through a rootshare, and then dowloads is pinned. Files are not showing. If I browse to the location manually from Start>Run, the files are there immediately.

Whenever I download something to my downloads share on Unraid, the files don't seem to show in the Windows SMB until the mover is run. The files are visible in the Unraid file explorer. Caching is set to Yes on the share. I'm sure the files used to be visible all the time and this has only happened since upgrading to version 6.12 of Unraid. Can anybody confirm that this is by design or am I losing my mind. Any suggestions to something that I may have missed? Mover schedule is set to an hour but most times I need the files immediately and don't want to have to manually invoke the mover. Thanks in advance.

I've recently moved my Unraid system from AMD to Intel. Since the move, I've not been able to start my Windows 10 VM. It's stuck in a loop, not being able to boot into Windows and going into auto repair. I've built myself a new physical Windows machine and have been able to mount two .img files to recover data from them, but I'm unable to mount the primary .qcow2 disk. so I can recover the rest of my files. Can anybody help me on how to do this, either from Windows or Linux if necessary. I'm normally a Windows user so step by step would be great if in Linux. Thanks in advance

I found that other people have reported this problem. It appears to be something to do with the HDMI port which doesn't passthrough. I swapped to using display port and it passed through straight away. It's strange as the 2 other GPU cards passthrough via HDMI but the GTX1660ti does not. Cable and port are fine as Unraid boots on the card as it's the primary GPU in BIOS. On 10/9/2019 at 7:47 AM, stvwndr219 said: SOLVED: The issue appears to be with using an HDMI cable on the VM. I got my DisplayPort to HDMI cable out and converted one of the DisplayPort slots on the 1080 Ti to HDMI on my monitor and we are good to go. I do wonder if passing through HDMI audio from the GPU means you can't use the HDMI output due to the HDMI audio being on the same IOMMU group as the GPU. Not sure, but it works now.

I've bound the devices again for the device. It shows this in the vfio log. I've noticed at boot it doesn't get to the login prompt when binding these devices. Is this normal? It still doesn't passthrough. I've attached the latest diagnostics. djw-unraid-diagnostics-20220215-1406.zip

djw-unraid-diagnostics-20220212-2058.zip