Issues with importing TrueNAS pool after disk passthrough on Proxmox

TrueNAS General
, , ,
1

Good evening, I’m trying to import the pools associated with my HDDs that were in my TrueNAS Core VM hosted on my Proxmox server. I did a disk passthrough of all my HDDs that I used to use in my old TrueNAS Scale, which was hosted on a desktop.

However, when I try to use Import Existing Pool, the pool dropdown is empty. When I go to the disks section, the attached disks are still listed.

I tried to repeat the disk passthrough steps again, but I got the same result. Then, I tried to do an HBA passthrough by adding the PCI Device, and I got the message “No IOMMU detected, please activate it. See Documentation for further information.” After further research, I found that my ASUS P8Z68-M PRO motherboard only supports VT-x and not VT-d. Getting a new motherboard is not an option.

Now, I’m facing two options here, and I’m looking for your help:

  1. Am I missing anything with the disk passthrough configuration?
  2. If I need to recreate the pools, is there an option where I can access the content of the disks to copy them out to avoid losing everything?
2

if you type zpool import in the shell, what do you see?

3

root@truenas[~]# zpool import
pool: ST6000DM003-2CY186
id: 7078325671507864147
state: UNAVAIL
status: The pool was last accessed by another system.
action: The pool cannot be imported due to damaged devices or data.
see:
config:

    ST6000DM003-2CY186  UNAVAIL  unsupported feature(s)
      vtbd1p2           ONLINE

pool: HUH728080ALE601
id: 12999178226493712428
state: UNAVAIL
status: The pool was last accessed by another system.
action: The pool cannot be imported due to damaged devices or data.
see:
config:

    HUH728080ALE601  UNAVAIL  unsupported feature(s)
      vtbd4p2        ONLINE

pool: BINARIES
id: 17124278433026681159
state: UNAVAIL
status: The pool was last accessed by another system.
action: The pool cannot be imported due to damaged devices or data.
see:
config:

    BINARIES    UNAVAIL  unsupported feature(s)
      vtbd3p2   ONLINE

pool: ST8000DM004-2U9188
id: 6974209251100144465
state: UNAVAIL
status: The pool was last accessed by another system.
action: The pool cannot be imported due to damaged devices or data.
see:
config:

    ST8000DM004-2U9188  UNAVAIL  unsupported feature(s)
      vtbd5p2           ONLINE

pool: VIRTUALIZATION
id: 2228135571006298343
state: UNAVAIL
status: The pool was last accessed by another system.
action: The pool cannot be imported due to damaged devices or data.
see:
config:

    VIRTUALIZATION  UNAVAIL  unsupported feature(s)
      vtbd2p2       ONLINE

pool: HUA723030ALA640
id: 12106392342997030624
state: UNAVAIL
status: The pool was last accessed by another system.
action: The pool cannot be imported due to damaged devices or data.
see:
config:

    HUA723030ALA640  UNAVAIL  unsupported feature(s)
      vtbd6p2        ONLINE
4

I hope I am wrong, but I suspect that the way proxmox does a disc passthrough is not the same as a “real” hardware passthrough.
As you say your motherboard does not support vt-d.

I suspect its still a virtual disc. And ZFS really doesnt like virtual discs for data pools.

Can you recreate your exact old setup? With the drives exactly on the same sata ports ?

Again I hope i am wrong and there is some CLI-fu to import your pool.

5

So, you are trying to mount pools created with TrueNAS scale on a virtualized instance of TrueNAS core?

Also, it appears that you have a pool per disk. Is this correct?

Also, I believe you probably forgot to export the pools before decommissioning the other system, but this is not really a problem

6

So, you are trying to mount pools created with TrueNAS scale on a virtualized instance of TrueNAS core?

Yes

Also, it appears that you have a pool per disk. Is this correct?

Yes

Also, I believe you probably forgot to export the pools before decommissioning the other system, but this is not really a problem

Yes

7

Only if I delete proxmox and reinstall TrueNAS Scale on the same machine.

8

Which version of CORE are you trying to use?

It appears it doesn’t support the features that are in use/enabled on the pool.

Use Scale instead.

Having a single disk per pool… is well… strange. As you have no drive failure resiliency, and without setting copies=2, no bitrot protection either.

Normally, if you had a bunch of 8TB drives for example you’d combine them together using raidz1 or raidz2 in a pool.

1 Like
9

Which version of CORE are you trying to use?

TrueNAS-13.0-U6.1

Having a single disk per pool… is well… strange. As you have no drive failure resiliency, and without setting copies=2, no bitrot protection either.

I was just doing tests to learn about how to use TrueNAS

10

I think TrueNAS Core 13.3 Beta may support the pool features used by Scale.

11

Thank you @Stux, now I’m able to access my storage again!

1 Like