Scale GNU/Linux 22.12.3.1 suddenly cannot boot

[The_Saver]

Hello everyone,

Suddenly my TrueNAS Scale 22.12.3.1 cannot boot. Well, unless I unplug all my 24 HDDs which are on the same pool.
Then it can boot. But what use is my server if I cannot access my disks?

I have seen two different errors:

Code:

Booting ´TrueNAS Scale GNU/Linux 22.12.3.1'
double free at 0xb6c53540
Aborted. Press any key to exit.

where the 0x-address changes slightly, and also:

Code:

Booting ´TrueNAS Scale GNU/Linux 22.12.3.1'
alloc magic is broken at 0xb136f40: 0
Aborted. Press any key to exit.

I tried to upgrade to 22.12.3.2, but I am unfortunately receiving the same error.

Now that I am booted into 22.12.3.2 and have plugged all my 24 disks in (looks the same in 22.12.3.1), I am wondering whether or not I can import my pool?

My pool is called "storage". I am afraid to click "Add Disks" in case all my data gets deleted. Is this very safe to try?

When I try to use zpool commands I cannot see my pool (because it is not imported automatically when I plug in the disks after it has booted?)

I have tried to search online, but so far I cannot find a solution that is specific enough to this problem, and I am also afraid to try different "random" things before asking here as my data is at stake. One thing that pops up, though, is grub used for bootloader which could be the culprit? I don't know anything about grub.


Thank you so much for reading - please let me know what I can try to debug. And hopefully other people with the same issue in the future can read this thread to solve the issue :)

 

[The_Saver]

Is it safe to add my existing pool as shown in the picture in the middle? I am afraid to lose data.


Do you guys have an idea of a command I can try to run or something? I'd greatly appreciate it.

 

[The_Saver]

Am I the only one who has experienced this issue?

 

[danb35]

I am afraid to click "Add Disks" in case all my data gets deleted. Is this very safe to try?

No, it is not safe to try, and yes, it will erase all your data as it says. You don't want to add your disks to a pool; you want to import a pool--which you should be able to do through the GUI.

 

[The_Saver]

No, it is not safe to try, and yes, it will erase all your data as it says. You don't want to add your disks to a pool; you want to import a pool--which you should be able to do through the GUI.

Thank you

In my GUI I cannot import the pool:

It doesn't show up as an option.

But, all my disks show up with my correct pool name (storage). But it says that it is exported. I don't know why it is exported as it is not something that I have done. Maybe it happened because I booted my TrueNAS Scale without the disks attached, and then reattached them after booting, in order to avoid the errors I showed above.

What is a safe approach to "unexport" my pool and use my server normally again?

 

[danb35]

What happens if you run zpool import storage from the shell? If that does complete without error, try zpool export pool and try importing from the GUI again.

 

[The_Saver]

What happens if you run zpool import storage from the shell? If that does complete without error, try zpool export pool and try importing from the GUI again.

Thank you, it worked with zpool import storage

Because it was in the middle of replacing a bad disk it now automatically resumed the operation, which is perfect!:

I think it might be best to wait a few hours?

I think I will try to reboot the server normally after it has finished.
Then, if everything isn't back to normal, I will try what you said with zpool import storage and then zpool export pool and then try to import with the GUI.

 

[danb35]

Yes, I'd let it finish resilvering before you do anything else.

 

[The_Saver]

After the resilvering finished I rebooted and everything was back to normal as if nothing happened! Thank you!