Error "kdb_enter +0x3b: movq"

[KarolKo]

Hi Everyone,

I found a couple of threads about users experiencing the Error "kdb_enter +0x3b: movq" during install, but I am getting this error while FreeNAS is booting and trying to import the POOL.

How did I get there? I wanted to access (READ) some data on my FreeNAS and while browsing, it became inaccessible. It has rebooted and when I connected a screen, I saw this error.

I tried the single user mode and zpool import command and it reports ONLINE.

I have done an clean install of FreeNAS and then tried to import the pool and it became inaccessible again.

My setup
I have a small test setup of FreeNAS just to temporarily backup some data. Its a quite small PC and it only has 4GB of ram with an SDD drive for system install and 1 single 2TB drive for the data. I only had the 2TB drive half full with the data. So, yes I have read the 8GB minimum and who knows, perhaps its down to this and case is closed.

What I also tried is to create an VirtualBox virtual machine with 8GB RAM and import the POOL from the UI, yet the result is again the same error.

I am using FreeNAS 11.2-U3 but tried also with an older version of 11.2.

The error I am getting when booting normally:

Then booted single user mode and tried:

set vfs.zfs.recover=1
set vfs.zfs.debug=1
boot -s

zpool import -nF

 

[Chris Moore]

It appears to be a hardware problem. Please review the link below:

Forum Guidelines
https://www.ixsystems.com/community/threads/forum-guidelines.45124/

 

[KarolKo]

Thanks,

for completeness then:
Supermicro X7SPA-H EMBEDDED Intel® Atom™ D510
2x 2GB VS2GSDS667D2
1x 2TB ST2000DL003-9VT166 (POOL)
1X 30 GB Samsung SSD (boot)

 

[HoneyBadger]

Do you get a result when trying to import with the -F flag?

 

[KarolKo]

The result is identical with the first screenshot. I get the kdb_enter +0x3b: movq error and end up in some sort of db> console.

I get the same result whether I attach the HDD and I try to import the pool on the actual PC or to a virtual machine on another PC with 8GB ram.

 

[HoneyBadger]

The result is identical with the first screenshot. I get the kdb_enter +0x3b: movq error and end up in some sort of db> console.

I get the same result whether I attach the HDD and I try to import the pool on the actual PC or to a virtual machine on another PC with 8GB ram.

You might need to try a different OS entirely (with ZFS support of course) since it looks like it's panicking on import.

 

[KarolKo]

You might need to try a different OS entirely (with ZFS support of course) since it looks like it's panicking on import.

Thanks for the tip. I installed 19.04 Ubuntu and tried to import the POOL:

 

[KarolKo]

In the meanwhile I also scanned the entire HDD for read errors and there are ZERO unreadable sectors on it.