A month ago, I upgraded from 24.10.1 to 24.10.2 and when I rebooted my FreeNAS, it couldn’t find the boot device. I’m attaching a screenshot of what shows up. It doesn’t matter if I try going into 24.10.2 or 25.4.
It may not identify the root cause, but I would simply save the config file and do a clean install.
So a couple of questions.
Boot pool status is DEGRADED: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected…
2025-01-21 12:44:38 (America/Chicago)
Does this mean I should probably replace one (or both) of the NVMe drives that are in the FreeNAS mini? I’m assuming that’s where the boot/system is located, but I’m not 100% and am not sure how to find out exactly.
I’m familiar with Linux in general but this is my first time dealing with a dedicated NAS setup. I had used Amahi Home Server in the past, but it’s an entirely different animal.
Have a great night. 
Patrick.
Go to System > General Settings > Manage Configuration and select Download File.
Save this somewhere safe.
You can use this file to reestablsh all of your settings etc upon a fresh install. There should be no need to disconnect any storage as long as you are confident in installing the OS on the correct HDD.
Once you have saved the configuration file you need to promptly replace the boot pool disk as it is degraded and failing. This (after your config file is saved) should be your first priority. I would also make sure you have a proper back up of your files just in case.
Thank you. One more question. The boot disk is a 16 GB SSD, and I have two 119.4 GB SSD’s that aren’t being used (the two NVMe drives). Could I just use one of those instead? If so, I’m assuming I would have to remove the current boot drive.
Have a great night.
Patrick.
You can. Just make sure you have a copy of the config file and your data is backed up somewhere else.
I can’t stress this enough to the OP → BE CAREFUL when you select what drive(s) to install the TrueNAS OS to. You only want to select the specific SSD/NVMe you want the OS to be on as it destroys all data on the selected devices.
Good luck!
I’m going to add this just for clarification purposes (and to see if the “boot drive” is really failing or if that error was a one-off.
truenas_admin@truenas[~]$ sudo smartctl -x /dev/sdh
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.6.44-production+truenas] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org=== START OF INFORMATION SECTION ===
Device Model: 16GB SATA Flash Drive
Serial Number: (removed for the posting)
LU WWN Device Id: 5 dc663a 657a00100
Firmware Version: SFDK002A
User Capacity: 16,013,942,784 bytes [16.0 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
TRIM Command: Available
Device is: Not in smartctl database 7.3/5706
ATA Version is: ACS-2 T13/2015-D revision 3
SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sun May 11 13:51:38 2025 CDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM feature is: Disabled
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Unavailable
ATA Security is: Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: Enabled=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSEDGeneral 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: ( 32) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No 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: ( 1) minutes.
SCT capabilities: (0x0039) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.SMART Attributes Data Structure revision number: 0
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
9 Power_On_Hours -O–C- 100 100 000 - 43064
12 Power_Cycle_Count -O–C- 100 100 000 - 132
163 Unknown_Attribute ------ 100 100 001 - 2421
164 Unknown_Attribute ------ 100 100 001 - 442
166 Unknown_Attribute ------ 100 100 010 - 0
167 Unknown_Attribute -O—K 100 100 000 - 0
168 Unknown_Attribute -O–C- 100 100 000 - 0
175 Program_Fail_Count_Chip PO–C- 100 100 010 - 0
192 Power-Off_Retract_Count -O–C- 100 100 000 - 91
194 Temperature_Celsius -O—K 060 060 030 - 40 (Min/Max 30/60)
241 Total_LBAs_Written -O–CK 100 100 000 - 5170891732
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warningGeneral Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
Address Access R/W Size Description
0x00 GPL,SL R/O 1 Log Directory
0x01 SL R/O 1 Summary SMART error log
0x02 SL R/O 51 Comprehensive SMART error log
0x03 GPL R/O 64 Ext. Comprehensive SMART error log
0x04 GPL,SL R/O 8 Device Statistics log
0x06 SL R/O 1 SMART self-test log
0x07 GPL R/O 1 Extended self-test log
0x09 SL R/W 1 Selective self-test log
0x10 GPL R/O 1 NCQ Command Error log
0x11 GPL R/O 1 SATA Phy Event Counters log
0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xe0 GPL,SL R/W 1 SCT Command/Status
0xe1 GPL,SL R/W 1 SCT Data TransferSMART Extended Comprehensive Error Log Version: 1 (64 sectors)
Device Error Count: 1
CR = Command Register
FEATR = Features Register
COUNT = Count (was: Sector Count) Register
LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
LH = LBA High (was: Cylinder High) Register ] LBA
LM = LBA Mid (was: Cylinder Low) Register ] Register
LL = LBA Low (was: Sector Number) Register ]
DV = Device (was: Device/Head) Register
DC = Device Control Register
ER = Error register
ST = Status register
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It “wraps” after 49.710 days.Error 1 [0] occurred at disk power-on lifetime: 40429 hours (1684 days + 13 hours)
When the command that caused the error occurred, the device was active or idle.After command completion occurred, registers were:
ER – ST COUNT LBA_48 LH LM LL DV DC
– – – == – == == == – – – – –
00 – 50 00 20 00 00 00 49 a9 c8 40 08 at LBA = 0x0049a9c8 = 4827592Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
– == – == – == == == – – – – – --------------- --------------------
61 00 c8 00 20 00 00 00 49 a9 c8 40 08 39d+23:26:01.695 WRITE FPDMA QUEUED
61 00 c8 00 20 00 00 00 49 a9 c8 40 08 39d+23:26:01.632 WRITE FPDMA QUEUED
61 00 08 00 38 00 00 00 49 a9 b8 40 08 39d+23:26:01.600 WRITE FPDMA QUEUED
61 00 20 00 18 00 00 00 43 84 40 40 08 39d+23:26:01.567 WRITE FPDMA QUEUED
61 00 10 00 30 00 00 01 a8 87 70 40 08 39d+23:26:01.535 WRITE FPDMA QUEUEDSMART Extended Self-test Log Version: 1 (1 sectors)
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error1 Extended offline Completed without error 00% 43048 -
2 Short offline Completed without error 00% 39394 -
3 Short offline Completed without error 00% 34395 -
4 Short offline Completed without error 00% 34394 -
5 Short offline Completed without error 00% 34393 -
6 Short offline Completed without error 00% 34392 -
7 Short offline Completed without error 00% 34391 -
8 Short offline Completed without error 00% 34390 -
9 Short offline Completed without error 00% 34389 -
#10 Short offline Completed without error 00% 34388 -
#11 Short offline Completed without error 00% 34387 -
#12 Short offline Completed without error 00% 34386 -
#13 Short offline Completed without error 00% 34385 -
#14 Short offline Completed without error 00% 34384 -
#15 Short offline Completed without error 00% 34383 -
#16 Short offline Completed without error 00% 34382 -
#17 Short offline Completed without error 00% 34381 -
#18 Short offline Completed without error 00% 34380 -
#19 Short offline Completed without error 00% 34379 -SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.SCT Status Version: 3
SCT Version (vendor specific): 1 (0x0001)
Device State: Active (0)
Current Temperature: 0 Celsius
Power Cycle Min/Max Temperature: --/ 0 Celsius
Lifetime Min/Max Temperature: --/ 0 CelsiusSCT Temperature History Version: 2
Temperature Sampling Period: 1 minute
Temperature Logging Interval: 1 minute
Min/Max recommended Temperature: -127/127 Celsius
Min/Max Temperature Limit: -127/127 Celsius
Temperature History Size (Index): 478 (20)Index Estimated Time Temperature Celsius
21 2025-05-11 05:54 40 *********************
… …(239 skipped). … *********************
261 2025-05-11 09:54 40 *********************
262 2025-05-11 09:55 ? -
263 2025-05-11 09:56 40 *********************
… …(118 skipped). … *********************
382 2025-05-11 11:55 40 *********************
383 2025-05-11 11:56 ? -
384 2025-05-11 11:57 40 *********************
… …(113 skipped). … *********************
20 2025-05-11 13:51 40 *********************SCT Error Recovery Control:
Read: 70 (7.0 seconds)
Write: 70 (7.0 seconds)Device Statistics (GP Log 0x04)
Page Offset Size Value Flags Description
0x01 ===== = = === == General Statistics (rev 2) ==
0x01 0x008 4 132 — Lifetime Power-On Resets
0x01 0x018 6 5170827972 — Logical Sectors Written
0x01 0x020 6 68037338 — Number of Write Commands
0x01 0x028 6 10135136603 — Logical Sectors Read
0x01 0x030 6 550769085 — Number of Read Commands
0x01 0x038 6 155030400000 — Date and Time TimeStamp
0x07 ===== = = === == Solid State Device Statistics (rev 1) ==
0x07 0x008 1 0 N-- Percentage Used Endurance Indicator
|||_ C monitored condition met
||__ D supports DSN
|___ N normalized valuePending Defects log (GP Log 0x0c) not supported
SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x0001 2 0 Command failed due to ICRC error
0x0002 2 0 R_ERR response for data FIS
0x0003 2 0 R_ERR response for device-to-host data FIS
0x0009 4 3 Transition from drive PhyRdy to drive PhyNRdy
0x000a 4 2 Device-to-host register FISes sent due to a COMRESET
0x000f 2 0 R_ERR response for host-to-device data FIS, CRC
All of the S.M.A.R.T. tests seem to pass, and it seems like that was a one-time error. It very well could have been something that I did at the time, or a power outage at the exact wrong time.
I’m off to flash a USB thumb drive, so I can reinstall. And then look for a drive caddy for the 2.5" drive at the top of the unit (it didn’t come with one, so I want to add one in).
Have a great day.
Patrick.
I usually physically remove all storage drives during a reinstall to avoid any such mistakes.
It is a couple clicks to reimport all your pools after you did the basic initial install.
