NAS reboot caused No Pools Found

TrueNAS General
,
61

That’s what confuses me too.

When it comes to SED encryption, I always thought it was “all or nothing”. Not that it would magically leave the partition table in the plain, and somehow intelligently only encrypt the rest of the data.

Clearly each drive has a “freebsd swap” partition and a “freebsd zfs” partition, which is readable with standard tools.

62

Well, you are assuming everything is working correctly. it’s entirely possible that it could be a buggy feature, that in addition to performing uncommanded encryption it does so sloppily and only end up encrypting partial contents.

63

SATA mode on my motherboard has 4 settings
Disable
IDE MODE
RAID MODE
AHCI MODE

64

What is it currently set to? (Don’t change anything.)

65

It’s currently IDE

66

The system time was also incorrect

67

IDE? That is odd. I would suspect it would default to AHCI, unless you changed it?

Do you remember ever changing it when you first setup your server?

68

I dont recall

I dont recall changing the SATA mode - it’s possible that it’s a remnant from when this PC was not a NAS? and was just an old PC being used with windows and some light games, however during that time, it wasnt with any of these harddrives

69

It’s quite possible that it defaults to IDE mode (being an old motherboard, as you say), though you had set it to AHCI for use with TrueNAS.

Your CMOS battery died and all your BIOS settings were reset to factory, including SATA mode.

This might have nothing do to with the issue you’re facing.

2 Likes
70

" * Modern features:

AHCI supports features like hot-swapping (adding or removing drives while the computer is running) which is not possible with IDE."

just googled so maybe this is related to the shut off and then being unable to be read

71

Did you try to do a shutdown, physical unplug, and then hold the power button for 5 seconds to fully discharge?

72

i did the full shutdown and held power and unplugged, then booted into bios - still sitting in bios right now

73

It’s actually the other way around. Shutdown → unplug → hold power button for 5 seconds → plug it back in → power on

Without changing anything, you can boot into TrueNAS to see if the full discharge makes the drives “behave” again. (Refer to the above about the correct order.)

74

yea this is what i did, sorry for the confusion

i will boot into truenas to see if anything changes.
I changed the system time to be accurate.

1 Like
75

should i disgard changes and just boot?

76

If you’re in the BIOS screen, you can just shutdown from the power button. (It will either instantly shut off or require you to hold the button for a few seconds. Depends on the system.)

Then when the system is powered off, you can unplug it from the wall and continue from there. Hold the power button for 5 seconds to let it fully discharge. Then plug it back in and power on.

77

booted up - disks are still in the same situation

78

Then you’re left with:

  1. Change SATA mode to “AHCI” and reboot. This is likely the simplest solution and the cause of your problem. Other variables seem to suggest so. (I’m just unsure if there’s a caveat that @HoneyBadger might know about, where doing so can actually risk irreversible changes on the drives.) :warning:
  2. Wait to see if @HoneyBadger notices anything about the sedutils output. I didn’t see anything unusual to suggest you were using encryption.
  3. Something else.

My gut is telling me that you might have set it to AHCI, then it reset to IDE, and that’s why you’re facing this issue.

79

I will try this and report the status,

80

Are you sure? I am not 100% certain this is entirely safe, and the friendly badger who does care is probably asleep.

EDIT: I just really hope you never set it to “RAID” before.