More than one matching pool, select pool, HOW?

[neofusion]

Apologies, I didn't see your post. I compared the page you linked and it probably would've worked also, since it explains how to list IDs and how to import a pool by ID. This was totally what I was looking for, but somehow I completely missed your submission.

It's fine, in the end you found a solution.
I was just curious to know if it applied to the TN implementation of zfs or not. :)

 

[cameronlanders]

If I insert a former TrueNAS SSD into the tower and try to boot, TrueNAS gets confused as to which disk to use for it's boot-pool. That's quite expected. It tells me I have to manually tell it which drive to use, also fine. It doesn't tell me how to do that tho. I can't find any documentation on this. How do I tell this thing what to use as boot-pool?

View attachment 57226

I have struggled with this. Here's the easy fix:
1. Use the command, "zpool import" with no arguments to see the list of disks marked as 'boot-pool'. One of these will be the one you actually intend as your boot pool disk. Note the numeric ID (mine is 19 digits in length).
2. Duplicate the failing zpool command, only substiture your ID instead of 'boot-pool', like so:
/sbin/zpool import -N -f 0123456789012345678
where: 0123456789012345678 is your actual ID from the output of previous zpool import.
3. type "exit" and you're done. From there it should import the correct zpool ID.

Cheers,
-=Cameron

 

[cameronlanders]

I have struggled with this. Here's the easy fix:
1. Use the command, "zpool import" with no arguments to see the list of disks marked as 'boot-pool'. One of these will be the one you actually intend as your boot pool disk. Note the numeric ID (mine is 19 digits in length).
2. Duplicate the failing zpool command, only substiture your ID instead of 'boot-pool', like so:
/sbin/zpool import -N -f 0123456789012345678
where: 0123456789012345678 is your actual ID from the output of previous zpool import.
3. type "exit" and you're done. From there it should import the correct zpool ID.

Cheers,
-=Cameron

Many thanks to jgreco for editing the above. Well done.

Some additional nuance and detail to add here in case it helps anyone:
Once you have completed the above steps, that gets you past the issue for that boot session, but don't just reboot - if you do that, you'll experience the same problem and have to go through the above steps over again.

Instead, once you have executed a successful zpool import command using the ID as described above, and after you type 'exit", the 0-9 menu appears so you can configure your network settings, etc.

Once you see the 0-9 menu, you can then access TrueNas from the web UI. Do that!

From the Web UI, click 'Storage', and then click 'Disks'. You should see the offending disk in the list that you identified earlier.

Click the down arrow on the far right of that disk's entry in the list to expand the details section. When the details section for that disk expands down, you will see a button at the bottom right with a little trash can icon that says, "Wipe". Use that button to wipe the disk.

I had to to wipe the disk in order to remove the extraneous 'boot-pool' marker from one of my drives (which was not the intended boot drive). From then on, I was able to boot right into the 0-9 menu no problem because that eliminated the conflict.

Note that the 'boot-pool' marker is not the same as a disk or partition label - some of the developers may be able to explain how that marker is implemented, and whether there may be some other way to remove it if you don't want to wipe your disk. (My drive had no data yet anyway so I didn't care).

Bottom line: if you leave the 'boot-pool' marker on more than one drive, you will continue to have this issue on every boot until you resolve it.

Cheers,
-=Cameron

 

[AlphaAjaxPapa]

Necroposting here because I had this problem, and this thread helped me.

Here's my scenario in case others find themselves in a similar place.

1. Purchase a random server without doing much research. :chef's kiss:
2. Install an NVME drive on a daughtercard because NVME is faster.
3. Install TrueNAS Scale on NVME.
4. Learn the server can't support booting from NVME.
5. Big sad.
6. Remove daughtercard and NVME.
7. Install TrueNAS Scale via traditional means on an available disk.
8. Get everything working.
9. Decided to put NVME back in because what else would I do with it?
10. Reboot to error.
11. Bigger sad, much confusion, made promises to deities I won't be keeping.
12. Find this post.

From there it went like this.

1. Attempted the method posted by @cameronlanders.
2. Couldn't get the pool number I needed because even when I tried "zpool import | less" I could not scroll back up far enough to see it.
3. Fell back to creating a live Linux USB.
   1. Used Unetbootin.
   2. Picked the Mint Distro because that's the only one I know, and even then it's pretty touch-and-go.
   3. Use Gparted to because it has a GUI and it made me feel good.
   4. Formatted to Fat32 because it's a safe bet.
4. Rebooted system.
5. And there was much rejoicing.
6. Adopted the NVME into TrueNAS Scale.
   1. Stern warnings of only having one disk duly noted.
7. Went to bed.

So yeah, definitely a learning experience, but in the end it's all worked out. I just need another NVME now so I can erase the shame of a single-drive pool.