VDEVS Not Assigned after hard shutdown

[Carsonix]

Hello,

TrueNAS Linux Scale

After a hard shutdown this happened.

On the command line…

sda is my boot drive.

I can see disk hdb and hdc
I can see TrueNAS in /mnt (my pool name) in mirror mode

…but when I run…

zpool import -f -F -R /mnt TrueNAS

…it outputs…

Cannot import ‘TrueNAS’: No such pool available

This screenshot is what I’m seeing in the Web GUI.

I’m a TrueNAS newb, I’ve searched the internet and seen a few posts with the same problem, but the fixes don’t work. Anyone know how to fix this?

Thanks!

[chuck32]

Can you post the output of zpool status?

Also please list your hardware.

[Carsonix]

zpool status

pool: boot-pool
state: ONLINE
scan: scrub repaired 0B 00:00:07 with 0 errors on Thu Apr 25 03:45:09 2024
config:
            NAME           STATE          READ  WRITE  CKSUM
            boot-pool       ONLINE        0     0      0
               sda3         ONLINE        0     0      0

errors: No known data errors

1 x ADATA SSD 256GB
2 x WD BLUE 2 TB HDD (only a few months old) (My TrueNAS pool that’s not working)

Running on an old Acer Aspire AX3470-EB20P

[chuck32]

What does zpool import yield without any arguments?

We had a similar issue a few days ago, unfortunately OP didn’t report back if it worked. It’s weird that the pool is shown in the GUI.

Do you see the disks under Storage / Disks?

Edit: if the disks show up as members of an exported pool you should try exporting and importing the pool again.
Here’s the mentioned thread.

@Protopia suggested exporting the pool in the GUI and then try Importing it again in their last response. I feel this would be the next logical step.

[Protopia]

@chuck32

@Protopia suggested exporting the pool in the GUI and then try Importing it again.

LOL. Whilst I have a lot of background in Servers and massive storage systems (EMC), I do not consider myself to be either a ZFS or TrueNAS (or Linux) expert. So, whilst it is lovely to be referenced as if I am an expert, please get some corroborating advice first.

[chuck32]

@Protopia

So, whilst it is lovely to be referenced as if I am an expert, please get some corroborating advice first.

I was referencing this thread (should have linked it)

Import/add previously used TrueNAS disk (zfs_member)

If it doesn’t work with the GUI, you probably need a reboot, then see what the status is - and if necessary export it again from the GUI and switch to trying to get it working from the command line - because from the CLI you have a lot more options to deal with recovery situations. Assuming you can get it imported and functioning correctly from the CLI, you can then export it from the CLI and import it again through the GUI and you should be good to go.

I think in this case exporting and importing it is worth a try, depending on whether the disks show that they belong to an exported pool.

Edit: edited my original answer.

[Carsonix]

admin@truenas[~]$ sudo zpool import
no pools available to import

During bootup there is a strange message about SATA ports. But it goes by to quickly…

failed to identify INIT_DEV_PARAMS on ATA3

If I install these drives on another trueNAS system will they be imported?

This computer is ancient, originally running WIndows 7.

I don’t know if its the computer or the drives.

TrueNAS isn’t even showing sdb

I’m new to TrueNAS, this is my first time using it.

[Protopia]

I think you need to go into BIOS and check that the disks are recognised by the BIOS.

You may also want to check all the BIOS settings and ensure they are optimised for Linux and to enable EUFI if your BIOS supports it. Then (if you have no data on your system yet) reinstall and see if things are any better.

If it still doesn’t work, please post full details of your NAS hardware.

[Carsonix]

Good idea.

1 was viewable in the BIOS but listed as 0 GB
The other was not visible.

Plugged them into a different motherboard, same thing.

Only bought them a few months ago. WD Blue 2TB HDD.

Looks like the drives got roasted. The boot drive SSD was fine. Reinstalled TrueNAS and it wouldn’t detect the HDDs.

Thanks for the help everyone.

[PZ0013]

Hi

I have a similiar problem in that after a hard shutdown (looks like it was a power surge), the disk that was running the pool got fried. (Disk was no longer detected in BIOS and also not detected when plugged into another computer).

That disk was running the Apps pool and I’m guessing I need to reinstall all the apps to restore everything.

Would like to ask for some advice as to how I should do this. I’m a dabbler at best with TrueNAS. The Apps pool was running a Home Assistant VM, Plex, qBittorrent, Prowlarr, Tailscale, and NextCloud.

1. I have the existing App pool that was running from the fried disk (now no longer attached to the system), and another replacement disk.

I thought the straightforward way might be to just add the unassigned replacement disk to the App pool but then I get errors ‘Name not added’ and ‘At least 1 VDEV is required’ despite specifying the values.

Should I just delete the pool and start again? Is there anything worthwhile salvaging from the existing pool?

2. Alot of the apps above were installed from TrueCharts, which I understand is no longer supported in TrueNAS Scale now. The installation instructions I was following previously seem to tend to favour TrueCharts for ease of installation(?). Would the TrueNAS versions (if they exist) be practical to install?

Thanks

[Protopia]

Firstly, if the single disk that was the pool is toast, then the pool itself is toast. You might as well delete it and recreate it on a new drive. After that…

1. Since your apps pool was not redundant, once you have your new disk configured as a new pool you will need to restore the data from the replication backups you took to your main pool. This will restore the entire pool, including the apps themselves and any ixVolumes (internal data) that these apps had created, toether with any other datasets you may have created on the apps pool. Any application data held in Host Paths (i.e. datasets on a different pool) accessed by apps will (of course) still exist on these other pool(s).

If you do not have a backup, then…

2. Start by creating a replication backup from the new apps-pool to a backup dataset on your main (HDD?) pool.

3. You will need to reinstall all apps from scratch. There is some talk of someone having created a replica snapshot of the TrueCharts catalogue which allows you to reinstall TrueCharts apps, but I haven’t seen any detailed instructions. If you cannot find these then you will either have to use TrueNAS Charts equivalents where they exist or roll your own using Docker apps.

4. Any other (apps?) data on your apps pool will have been lost. Hopefully this will only be e.g. Plex/Jellybean style metadata which can be redownloaded off the internet.

P.S. There is nothing wrong with the TrueNAS Charts apps. Some of us who saw the writing on the wall used TrueNAS Charts in preference and limited our use of TrueCharts as much as possible.