NAS reboot caused No Pools Found

Hello, this is my first time posting and I’m in need of some significant help… Been really difficult trying different solutions to my issue.

My NAS PC randomly rebooted while I was copying files over and when it started up again, the pool was gone.

I have two hard drives that were mirrored in the pools and while truenas is able to detect them, I am unable to see my storage pool “ProtoNAS”. The only pool that seems to be visible is “boot-pool”

I’ve tried a few different solutions that seemed similar to mine around the forums and web to no avail.
Hoping to get some directions on what I can do to recover the data as it’s quite sentimental

Not sure if any of these details would help identify what went wrong and how to go about the recovery.

Motherboard CMOS battery died, clocks reset recently
Used the upgrade pool button (NAS seemed to be working after the upgrade as well)
Reading and copying files to my android tablet was fine about 30mins before the nas rebooted
Nas rebooted when I was on my windows PC copying files to Adobe media encoder.

I can add some specific outputs and details once I get home.

Boot-pool is on a different drive.

In total I had 2 hard drives of 12TB in mirror
And a single 256gb SSD

When you get home please run the following commands and post the output of each command here inside a separate </> box:

  • lsblk -bo NAME,MODEL,ROTA,PTTYPE,TYPE,START,SIZE,PARTTYPENAME,PARTUUID
  • sudo zpool status -v
  • sudo zpool import
  • sudo zpool import ProtoNAS
2 Likes

While I know it is important to recover your data and @Protopia will get you there, it is also important to know why your computer randomly rebooted. Do you know what caused the reboot? If you do not, here is a question followed by some advice.

Question:

  1. Do you have your computer on a Uninterruptable Power Supply (UPS)? If not, get one if your data is valuable to you.

  2. How old is this computer you are using? A CMOS battery takes many many years to die.

  3. What is the Make/Model of the hard drives? Need to be sure they are not SMR drives which is not compatible with ZFS during heavy write operations.

Advice:

  1. Run Memtest86 (or Memtest86+) for 3 complete passes of the complete test series. This will give you a good foundation that your RAM and the CPU interface is good and stable.
  2. Next run a CPU stress test for at least 15 minutes, longer is better (1 hour) and some people do it for a solid week (mission critical).
  3. Never “Upgrade” the pool unless there is a new feature you need. It makes rolling back to the previous version impossible, which is really a good thing to be able to do when trouble hits. If you really want to upgrade, wait 2+ months.
1 Like

Thanks for the response!

I didn’t lose power, so I’m not sure why the PC randomly rebooted.

And no, it was not on a UPS. Though I do understand their use case and intend to get one.

The computer is quite old. I threw this Nas together using some older PC parts.

FX6300
970a g46
12gb ddr3 ram

The two harddrives are Seagate 12TB enterprise capacity drives. I can pull the exact model when I get home.

In terms of running memtest and CPU stress test. That would require me to dual boot into a different OS than TrueNAS scale correct?

And yea… I now realize “if it ain’t broke, don’t upgrade”

Hopeful and grateful for the support
Thansk

When you get home, don’t forget to try the first three commands in @Protopia’s post above.

This will require you logging into an SSH session or using the “Shell”.

1 Like

Please do also try the 4th command too. I am not expecting it to work but I am hoping that it will give us an error message that will help.

No, but you would need to boot into something like “The Ultimate Boot CD” which has a number of testing program, Memtest and CPU stress tests are there. You can use something like Rufus to create a bootable USB Flash Drive.

Your NAS would not be usable during these tests.

Just got home and booted up the NAS to run the commands in shell on the webgui

lsblk: unknown column: START,SIZE,PARTTYPENAME,PARTUUID

however: lsblk

root@truenas[~]# lsblk
NAME     MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda        8:0    0  10.9T  0 disk  
├─sda1     8:1    0     2G  0 part  
└─sda2     8:2    0  10.9T  0 part  
sdb        8:16   0  10.9T  0 disk  
├─sdb1     8:17   0     2G  0 part  
└─sdb2     8:18   0  10.9T  0 part  
sdc        8:32   0 119.2G  0 disk  
├─sdc1     8:33   0   260M  0 part  
├─sdc2     8:34   0   103G  0 part  
└─sdc3     8:35   0    16G  0 part  
  └─sdc3 253:0    0    16G  0 crypt [SWAP]
  pool: boot-pool
 state: ONLINE
status: Some supported and requested features are not enabled on the pool.
        The pool can still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
        the pool may no longer be accessible by software that does not support
        the features. See zpool-features(7) for details.
  scan: scrub repaired 0B in 00:00:11 with 0 errors on Tue Feb 18 03:45:13 2025
config:

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

errors: No known data errors
no pools available to import
cannot import 'ProtoNAS': no such pool available

in the Storage dashboard tab
“ProtoNAS” pool exists - but it’s offline

there are 2 unassigned disks and the add to pool option is available to select and add them to the existing pool where i can choose ProtoNAS
however due to the warning that says it will wipe the drives i have not progressed with this

What is the actual command you typed?

i copied it from Protopia’s snippet

  • lsblk -bo NAME,MODEL,ROTA,PTTYPE,TYPE,START,SIZE,PARTTYPENAME,PARTUUID

It works for me (on Arch Linux), and I don’t see why it wouldn’t work on Debian (SCALE).

There might have been a character (a false comma) that throws off the Shell?

What does this output?

lsblk --list-columns

not sure, doesnt seem to be working either

root@truenas[~]# lsblk --list-columns
lsblk: unrecognized option '--list-columns'
Try 'lsblk --help' for more information.

maybe a typo with START / STATE

is this useful?

root@truenas[~]# lsblk -bo NAME,MODEL,ROTA,PTTYPE,TYPE,STATE,SIZE,PARTTYPENAME,PARTUUID
NAME     MODEL              ROTA PTTYPE TYPE  STATE             SIZE PARTTYPENAME PARTUUID
sda      ST12000NM0127         1 gpt    disk  running 12000138625024              
├─sda1                         1 gpt    part              2147483648 FreeBSD swap df4aa63d-6a5d-11ef-85b2-d43d7e5548d5
└─sda2                         1 gpt    part          11997991055360 FreeBSD ZFS  df6b7731-6a5d-11ef-85b2-d43d7e5548d5
sdb      ST12000NM0127         1 gpt    disk  running 12000138625024              
├─sdb1                         1 gpt    part              2147483648 FreeBSD swap df35bcb5-6a5d-11ef-85b2-d43d7e5548d5
└─sdb2                         1 gpt    part          11997991055360 FreeBSD ZFS  df5a79cd-6a5d-11ef-85b2-d43d7e5548d5
sdc      Patriot_P220_128GB    0 gpt    disk  running   128035676160              
├─sdc1                         0 gpt    part               272629760 EFI System   0829b924-698d-11ef-b0df-d43d7e5548d5
├─sdc2                         0 gpt    part            110578630656 FreeBSD ZFS  0831d37b-698d-11ef-b0df-d43d7e5548d5
└─sdc3                         0 gpt    part             17179869184 FreeBSD swap 082e6b9a-698d-11ef-b0df-d43d7e5548d5
  └─sdc3                       0        crypt running    17179869184              
1 Like
lsblk --version

I might have to create another VM just for SCALE at this point.

There must have been a nonprintable character/space somewhere in the command.

i just wasnt able to find the output column “start” when i did --help

Now this, just to confirm:

zpool import -d /dev/disk/by-partuuid

zpool import -d /dev/disk/by-partuuid
returns:

root@truenas[~]# zpool import -d /dev/disk/by-partuuid
no pools available to import