Rebuilt but previous disks remain configured

I lost a boot disk so had to rebuild TN. When doing so, existing disks were not cleared. I know I can save and re-import the config but the boot disk changed which I imagine means I cannot use that backup.

If that’s the case, then I need to clear the old pool config so I can re-create that but so far, have not found a way that works.

A fresh installation should be able to import the data pool.
From there, you would have to recreate users as they were and reconfigure the shares.
But it may be possible to grab a copy of the previous configuration from the previous system datset and load it to restore the settings. So where was your system dataset? On the boot pool or on the data pool?

I don’t know why you’d assume that; this is exactly the scenario for which that capability is designed.

But otherwise, as Etorix says, just go ahead and import the pool.

I’m not assuming anything which is why I’m asking in the forums :).

As I mentioned, the boot disk changed so the backup configuration would not match the new setup. The old boot device was an nvme card but now it’s a separate ssd. Would I have to edit the backup file or something else?

Neither.

Ok, it won’t take much to test. I’ll do it now and see what happens and report back.

This is the result;
There were two nvme cards before the rebuild but both of those are gone, they were removed.
The shared configuration is there however but is not usable since the pool is not restored.

The only option seems to be to disconnect the old storage so that I can rebuild it from scratch.



1 Like

When you “rebuilt TN”, do you mean that you reinstalled TrueNAS? If so, did you per chance select all your 1TB drives during the install process? If so, you (unintenionally?) overwrote them, essentially destroying the old data pool. Normally you only select the specific devices you want to install the OS on, your 60GB may have been a better pick.

The tn02pool now likely shows as OFFLINE because the drives it was made up of are now part of your boot-pool instead. As part of the boot-pool they will be unavailable for anything else.

When re-installing TrueNAS, I installed onto one dedicated 64GB disk.
The storage disks were not touched.
Yes, I do see it shows boot-ppol but I’m not sure where that’s coming from since my previous install also used a small dedicated disk.

I don’t have any need for the old data on the storage, it’s the other configurations that I’d like to save, users, shares, etc.

I went ahead and disconnected the existing storage but still do not have access to the disks. Really not sure why they do show boot-pool

by any chance, does this has to do with selecting all the drives listed by putting * while TrueNAS installation?

Not sure what you’re asking sorry. While installing, I only selected the 64GB disk I installed for the OS. I did not select any of the 1TB SSD drives.

What’s the output of zpool status and zpool import at the shell? (sudo spool status and sudo zpool import if the former fail)

1 Like

I’ll share the commands but a reboot seemed to clear things up and now the disks are available again. However, two of them show they have problems.

root@truenas[~]# zpool status
  pool: boot-pool
 state: ONLINE
config:

        NAME        STATE     READ WRITE CKSUM
        boot-pool   ONLINE       0     0     0
          da7p2     ONLINE       0     0     0

errors: No known data errors

root@truenas[~]# zpool import
   pool: boot-pool
     id: 3936460655995097429
  state: DEGRADED
status: One or more devices contains corrupted data.
 action: The pool can be imported despite missing or damaged devices.  The
        fault tolerance of the pool may be compromised if imported.
   see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-4J
 config:

        boot-pool                DEGRADED
          mirror-0               DEGRADED
            da0p2                FAULTED  corrupted data
            da1p2                ONLINE
            da2p2                ONLINE
            da3p2                ONLINE
            da4p2                ONLINE
            da5p2                ONLINE
            da6p2                ONLINE
            3784024614667465404  FAULTED  corrupted data

   pool: boot-pool
     id: 15847089340067648294
  state: ONLINE
 action: The pool can be imported using its name or numeric identifier.
 config:

        boot-pool   ONLINE
          da0p2     ONLINE

   pool: boot-pool
     id: 14453227794243169978
  state: ONLINE
 action: The pool can be imported using its name or numeric identifier.
 config:

        boot-pool   ONLINE
          ada0p2    ONLINE

root@truenas[~]# zpool status
  pool: boot-pool
 state: ONLINE
config:

        NAME        STATE     READ WRITE CKSUM
        boot-pool   ONLINE       0     0     0
          da7p2     ONLINE       0     0     0

errors: No known data errors

:astonished:
Do I see an eight-way mirror? Well, a scrub should put it in back in order…

1 Like

I don’t know what the configuration was before it was rebuilt.

TrueNAS is actively using boot-pool for system services, including logging (/var/db/system/syslog-*), so the system won’t allow you to export or destroy the pool.

I’m also seeing multiple boot-pool IDs, which indicates leftover ZFS metadata across multiple disks. But since the OS is running on ada0 (64GB SSD), I should be able to safely remove these other pools.

However, it seems that da7 is somehow being used by the OS, it’s always busy so I cannot clear it. I didn’t install or check anything to use da7 when re-installing.

Seems I need to re-install again. Not sure why da7 is in use.

We don’t know either, and I have no idea what you mean by “rebuilt” and what exactly you have done…
First make sure you have a known good copy of your data, and check what you have here.

I did say I re-installed so ‘rebuilt’ TrueNAS.
I’ve also shared all that I’ve done. Nothing else so far, it’s a new install.

I don’t care about the data, this was one of several redundant backup devices. No data was lost.

I think I have to rebuild/re-install again.

I was able to remove partition details from the disks that were not working then I re-installed to be safe and all works now. Took a while because TrueNAS for some reason keeps locking the disks even though there is no pool created yet.