Import of pool fails with "failed to reclaim memory" errors

DurkaDurkaDurka

Dabbler
Joined
May 16, 2020
Messages
19
I have a RAIDZ-1 with 5 drives that has worked flawlessly for years. No de-dupe, no encryption. I was running the most recent version of TrueNAS core, though I did not update my pool with the latest ZFS. I went on a trip and came back to a halted system (possible power outage). Upon reboot, I found errors when it went to mount the pool that state "jid 0, uid 0, was killed, failed to reclaim memory." It will do this over and over and will not allow access to the GUI or command line.

I'm running an Avago HBA in IT mode (not RAID) on an old AMD APU setup, 8 GB RAM single DDR3 DIMM. I ran memory tests using memtestx86 to ensure no RAM issues. I suspected possible USB drive corruption or maybe a shortage of swap based on its size (16 GB), so I took it out, installed a left over 80 GB SSD with a fresh install. This came up properly, but as soon as I did the import via the GUI, the entire system hangs. A reboot shows the same behavior as the last installation now that it is trying to import - "failed to reclaim memory" errors on import. I will say that while on the trip, I was not paying attention to usage, so I'm fairly certain disk usage was over 95% or possibly higher. I attached images of the boot process during import. I've even tried doing a control-C during the import. If necessary, I can reinstall the OS so it doesn't know of the imported pool. Maybe I can do the import manually to see what's going on.

I'd very much like access to my data (at least readonly). Most of it I can replace, but some stuff my wife put on there, I don't have a copy of. What options do I have?
 

Attachments

  • IMG_3867.jpg
    IMG_3867.jpg
    286.6 KB · Views: 192
  • IMG_3868.jpg
    IMG_3868.jpg
    603.6 KB · Views: 200
  • IMG_3869.jpg
    IMG_3869.jpg
    662.7 KB · Views: 190

DurkaDurkaDurka

Dabbler
Joined
May 16, 2020
Messages
19
Just to get a little further along, I reinstalled the OS and enabled SSH :

root@truenas[/etc/ssh]# zpool import
pool: MONSTER
id: 4231639146976791286
state: ONLINE
status: Some supported features are not enabled on the pool.
(Note that they may be intentionally disabled if the
'compatibility' property is set.)
action: The pool can be imported using its name or numeric identifier, though
some features will not be available without an explicit 'zpool upgrade'.
config:

MONSTER ONLINE
raidz1-0 ONLINE
gptid/cfd16e8b-07c5-11ed-880a-6805cab9bb6a ONLINE
gptid/9ecdd683-98ad-11ea-9124-708bcda44581 ONLINE
da0p2 ONLINE
gptid/de8b4660-48de-11ec-a735-6805cab9bb6a ONLINE
gptid/9f8dc016-98ad-11ea-9124-708bcda44581 ONLINE

Note, the name "da0p2" came about some time ago when I replaced a failing drive. Not sure why it didn't get re-named like the others, but it worked properly. Please let me know how I can proceed to possibly repair of ZFS pool or try to temporarily mount it. I do have a backup of my TrueNAS configuration from prior to all of this.
 

DurkaDurkaDurka

Dabbler
Joined
May 16, 2020
Messages
19
So I ended up trying FreeNAS 11 instead of TrueNAS Core and was able to import the pool. Unfortunately, it was 100% full and disallowed removal of files. What I've done is mount it at the command line and am in the process of copying critical files off via SFTP. I'll recreate the pool fresh once done.

Hopefully someone else in the future running into this problem can try what I tried with success. I'll probably end up just staying on this revision of the OS for stability.
 
Last edited:
Top