March 26Mar 26 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.
March 26Mar 26 Community Expert To change to a different boot drive/pool, you must boot from the flash drive, and also wipe the existing boot drive first.
March 26Mar 26 Author 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?
March 26Mar 26 Author 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?
March 27Mar 27 Community Expert 8 hours ago, Daryl Williams said: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.15 hours ago, JorgeB said:and also wipe the existing boot drive first.You need to wipe them before, you can use sgdisk -Z /dev/sdx (all data will be lost)
March 27Mar 27 Author 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?
March 27Mar 27 Community Expert Array must be stopped for onboarding wizard; also, the boot disk cannot be assigned to any pools.
March 27Mar 27 Author 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.
March 27Mar 27 Community Expert And the device is unassigned? I assume the onboard loads you just don't see the boot pool option?
March 27Mar 27 Author 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. Edited March 27Mar 27 by Daryl Williams
March 27Mar 27 Community Expert Solution 38 minutes ago, Daryl Williams said:but no boot options.That suggests it's still detecting an internal boot pool. Post the output fromblkid
March 27Mar 27 Author /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"
March 27Mar 27 Author 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
March 27Mar 27 Community Expert 18 minutes ago, Daryl Williams said:/dev/sdh3: PARTLABEL="Unraid Boot Partition"Yep, this was one the issue.
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.