Hy,
I have setup a FreeNas server with an HP Proliant MicroServer gen7 two years ago. It has been running find until recently.
The server was rebooting multiple time by day. On reboot I have a message :
Sadly, this message doesn't seem to lead to specific problem.
As I was in need of another backup server I've built another FreeNAS server around an HP Proliant MicroServer gen8 this time. And I bought ECC Ram for both server which wasn't the case for the gen 7 before.
I was able to copy via ZFS all content from the gen7 to the gen8 with no problem.
Then I put my gen7 server back in service. I restart the Time Machine process of an host I had to backup. First nothing happen for 12 hours but it started to crash again and again after.
So my questions are :
- is my zsh volume corrupted ? is it possible only a dataset might be corrupted ?
- how can I assert that my hardware is not broken ?
I have setup a FreeNas server with an HP Proliant MicroServer gen7 two years ago. It has been running find until recently.
The server was rebooting multiple time by day. On reboot I have a message :
Code:
savecore: reboot after panic: solaris assert: 0 == bpobj_open(&bpo, dl->dl_os, obj) (0x0 == 0x11), file: /freenas-9.10-releng/_BE/os/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dsl_deadlist.c, line: 427
Sadly, this message doesn't seem to lead to specific problem.
As I was in need of another backup server I've built another FreeNAS server around an HP Proliant MicroServer gen8 this time. And I bought ECC Ram for both server which wasn't the case for the gen 7 before.
I was able to copy via ZFS all content from the gen7 to the gen8 with no problem.
Then I put my gen7 server back in service. I restart the Time Machine process of an host I had to backup. First nothing happen for 12 hours but it started to crash again and again after.
So my questions are :
- is my zsh volume corrupted ? is it possible only a dataset might be corrupted ?
- how can I assert that my hardware is not broken ?