Pool gone after power outage

Hello,

could maybe someone guide me on how to proceed :slight_smile:
after power outage the pool with my APPS became offline.
it was installed on the same ssd physical disc as the boot-pool (truenas system).
but all it had inside was wireguard app for remote connections.

i had these alerts:

Failed to configure kubernetes cluster for Applications: Missing “APPS/ix-applications/k3s, APPS/ix-applications/releases” dataset(s) required for starting kubernetes.

Device: /dev/sda [SAT], 2 Currently unreadable (pending) sectors.

Failed to configure kubernetes cluster for Applications: Missing “APPS/ix-applications/releases, APPS/ix-applications/k3s” dataset(s) required for starting kubernetes.

in the tests the disk itself seems to be ok.
when i list the pools in the shell its not there anymore and i cannot import it.
is there a way to somehow restore the pool ?
should i just delete the pool and then create a new one to store wireguard ?
or is there a more rational place to put this one specific app?

Thanks in advance

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error

1 Extended offline Completed without error 00% 18624 -

2 Extended offline Completed without error 00% 18610 -

3 Short offline Completed without error 00% 18610 -

4 Short offline Completed without error 00% 18602 -

=== START OF INFORMATION SECTION ===
Model Family: Intel 53x and Pro 1500/2500 Series SSDs
Device Model: INTEL SSDSC2BW120A4
Serial Number: PHDA4350046A1207GN
LU WWN Device Id: 5 5cd2e4 04ba32b86
Firmware Version: DC32
User Capacity: 120,034,123,776 bytes [120 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
TRIM Command: Available, deterministic
Device is: In smartctl database 7.3/5319
ATA Version is: ACS-2 (minor revision not indicated)
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Wed May 28 14:04:00 2025 EEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x02) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 2930) seconds.
Offline data collection
capabilities: (0x7f) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Abort Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 48) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x0025) SCT Status supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
5 Reallocated_Sector_Ct 0x0032 100 100 000 Old_age Always - 0
9 Power_On_Hours_and_Msec 0x0032 100 100 000 Old_age Always - 18627h+14m+49.100s
12 Power_Cycle_Count 0x0032 098 098 000 Old_age Always - 2581
170 Available_Reservd_Space 0x0033 100 100 010 Pre-fail Always - 0
171 Program_Fail_Count 0x0032 100 100 000 Old_age Always - 0
172 Erase_Fail_Count 0x0032 100 100 000 Old_age Always - 0
174 Unexpect_Power_Loss_Ct 0x0032 100 100 000 Old_age Always - 58
183 SATA_Downshift_Count 0x0032 100 100 000 Old_age Always - 0
184 End-to-End_Error 0x0033 100 100 090 Pre-fail Always - 0
187 Uncorrectable_Error_Cnt 0x0032 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0032 028 039 000 Old_age Always - 28 (Min/Max 16/39)
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 58
199 UDMA_CRC_Error_Count 0x0032 100 100 000 Old_age Always - 0
225 Host_Writes_32MiB 0x0032 100 100 000 Old_age Always - 716789
226 Workld_Media_Wear_Indic 0x0032 100 100 000 Old_age Always - 65535
227 Workld_Host_Reads_Perc 0x0032 100 100 000 Old_age Always - 59
228 Workload_Minutes 0x0032 100 100 000 Old_age Always - 65535
232 Available_Reservd_Space 0x0033 100 100 010 Pre-fail Always - 0
233 Media_Wearout_Indicator 0x0032 070 070 000 Old_age Always - 0
241 Host_Writes_32MiB 0x0032 100 100 000 Old_age Always - 716789
242 Host_Reads_32MiB 0x0032 100 100 000 Old_age Always - 1061095
249 NAND_Writes_1GiB 0x0032 100 100 000 Old_age Always - 97894

What version of TrueNAS are you running?

Had you rebooted the system prior to this and did it work correctly?

You realize this is a completely unsupported configuration (putting anything on the boot device in addition to the OS) and may not work. TrueNAS is an appliance and needs to be treated as such if you expect it to just work and updates / upgrades to just work.

Having said that, have you tried manually importing that additional zpool?

Presumably you followed some user written guide to accomplish this wholly unsupported setup?
If so, perhaps you could try asking whomever wrote that guide for assistance.

It should be on the data pool and not on the boot drive. Truenas is not going to look for it or anything else on the boot drive and this is by design according to IX systems…

If you set up the app fresh, then Truenas should setup the necessary IX stuff properly on the selected data pool.