FreeNAS savecore: error reading last dump header

[Scampicfx]

Hey guys,

in order to get familiar with FreeNAS I was playing around with volume manager. Meanwhile, I was logged in via IPMI.

For testing purpose, I created one volume and added vdev consisting of 3 disks, raidz1, using volume manager.
Afterwards, I extended this volume by adding another vdev consisting of 3 disks, raidz1.

I noticed some errors while being logged in via IPMI. What do they mean?



Via IPMI, i noticed this error two times in total:
freenas savecore: error reading last dump header at offset 17179865088 in /dev/dumpdev: Invalid argument

I'm wondering what's the meaning of this error?

 

[Ericloewe]

What version is that?

 

[Scampicfx]

Hey,

it's the newest version:

FreeNAS-9.10.2-U3
It's running on Intel Xeon E5 1650v4, 32 GByte ECC RDIMM. I did a fresh install in order to have a clean system for testing purpose.

A few hours ago I updated the Avago SAS HBA to firmware P13. After firmware update, my testing-zpool wasn't listed anymore in freenas, so I decided to create a new zpool. However, when trying to arrange all disks to a new zpool / vdev, I noticed the error "freenas error: unable to gpt format the disk "da0/1/2/3/4/5/"" appearing in FreeNAS WebGUI.
I did some searching and noticed that some people in this case recommend to plug the hard disks to windows machines in order to delete the volume. However, I don't have any windows machine which is capable of running SAS drives.

So, I unplugged all hard drives, reinstalled FreeNAS. After installation I opened FreeNAS WebGUI and started installing the hot-swap hard drives, one after the other. I created 3 vdevs each consisting of 2 disks in mirror-mode.
Afterwards, I detached this volume, I wiped all disks and started recreating a new zpool consisting of 1x 3 disk vdev raidz1... And then I continued adding the second vdev raidz1, consisting of 3 disks, too. However, at this point I noticed the error shown above in the screenshot.

I'm a bit wondering if this is some hardware conflict or any corrupted ram?

By the way: While I was closely monitoring IPMI during booting, I noticed the error "pmc: unknown intel cpu" appearing towards the end of bootup proccess... Is there something wrong with this system?

 

[Dice]

Is there something wrong with this system?

Does it respond well to CPU and RAM stresstest?

 

[Scampicfx]

Hey,

I did some test (memtest86) and everything is fine so far.

The point I'm wondering about is, what this error means?
freenas savecore: error reading last dump header at offset 17179865088 in /dev/dumpdev: Invalid argument

I'm using disks with 4k native sectors. Is this error related to the sectors of the hard drives?
What does offset mean?
And why does the error pmc: unknown intel cpu appear during boot up?

 

[Scampicfx]

Hey,

I did some further testing...

I deleted my striped RAIDZ1 and noticed following messages during detaching the volumes:

May 22 18:50:59 freenas savecore: /dev/dumpdev/: No such file or directory
May 22 18:51:02 freenas savecore: /dev/dumpdev/: No such file or directory

Afterwards, I wiped all disks, selected the option to "mark them as new" and created a new RAIDZ2 using 6 disks.

Following message appeared:

May 22 18:53:45 freenas savecore: error reading last dump header at offset 17179865088 in /dev/dumpdev: Invalid argument

GEOM_ELI: Device da0p1.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI: Crypto: hardware
GEOM_ELI: Device da1p1.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI: Crpto: hardware
GEOM_ELI: Device da2p1.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI: Crpto: hardware
GEOM_ELI: Device da3p1.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI: Crpto: hardware
GEOM_ELI: Device da4p1.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI: Crpto: hardware
GEOM_ELI: Device da5p1.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI: Crpto: hardware

The raidz2 itself looks fully functional. But this error makes me worried. What does this error mean?