서비스체인 panic 에러가 납니다

안녕하세요.

현재 테스트용으로 서비스체인 단독으로 cn1대 돌리고 있습니다.

1.9.1 버전이며 주말에 인프라 이슈로 서버 재부팅된 후 데몬 실행 시 아래와 같은 panic 에러가 납니다.

INFO[03/06,11:16:47 +09] [51] Commit new mining work                    number=67889644 hash=af98f9…f68c7f txs=0 elapsed=748.476µs  commitTime=59.901µs finalizeTime=668.429µs
INFO[03/06,11:16:47 +09] [25] received a quorum of the messages and change state to prepared  msgType=1 prepareMsgNum=1 commitMsgNum=0 valSet=1
INFO[03/06,11:16:47 +09] [24] Committed                                 number=67889644 hash=456054…9b39f5 address=0x97A61E43EfBC9dC5b3082DC7ee2074B4a5872A48
INFO[03/06,11:16:47 +09] [51] Successfully sealed new block             number=67889644 hash=456054…9b39f5
ERROR[03/06,11:16:47 +09] [5] unknown ancestor (writeBlockWithStateParallel)  num=67889644 hash=456054…9b39f5 parentHash=520585…830ce6
ERROR[03/06,11:16:47 +09] [51] Failed writing block to chain             err="unknown ancestor"
WARN[03/06,11:16:57 +09] [25] [RC] timeoutEvent Sent!                   set by=startNewRound sequence=67889644 round=0 proposer=0x97A61E43EfBC9dC5b3082DC7ee2074B4a5872A48 preprepare is nil?=false len(prepares)=1 len(commits)=1
WARN[03/06,11:16:57 +09] [25] [RC] Prepares:                            messages="\n\t0x97A61E43EfBC9dC5b3082DC7ee2074B4a5872A48\n"
WARN[03/06,11:16:57 +09] [25] [RC] Commits:                             messages="\n\t0x97A61E43EfBC9dC5b3082DC7ee2074B4a5872A48\n"
WARN[03/06,11:16:57 +09] [25] [RC] Prepare messages received before catchUpRound  address=0x97A61E43EfBC9dC5b3082DC7ee2074B4a5872A48 state=Committed len(prepares)=1 messages="\n\t0x97A61E43EfBC9dC5b3082DC7ee2074B4a5872A48\n"
WARN[03/06,11:16:57 +09] [25] [RC] Commit messages received before catchUpRound  address=0x97A61E43EfBC9dC5b3082DC7ee2074B4a5872A48 state=Committed len(commits)=1 messages="\n\t0x97A61E43EfBC9dC5b3082DC7ee2074B4a5872A48\n"
WARN[03/06,11:16:57 +09] [25] [RC] Catch up round                       address=0x97A61E43EfBC9dC5b3082DC7ee2074B4a5872A48 old_round=0 old_seq=67889644 old_proposer=0x97A61E43EfBC9dC5b3082DC7ee2074B4a5872A48 new_round=1 new_seq=67889644 new_proposer=0x97A61E43EfBC9dC5b3082DC7ee2074B4a5872A48
WARN[03/06,11:16:57 +09] [25] [RC] Prepare messages received before startNewRound  address=0x97A61E43EfBC9dC5b3082DC7ee2074B4a5872A48 state=Committed from=0x97A61E43EfBC9dC5b3082DC7ee2074B4a5872A48 round=1 len(prepares)=0 messages="\n"
WARN[03/06,11:16:57 +09] [25] [RC] Commit messages received before startNewRound  address=0x97A61E43EfBC9dC5b3082DC7ee2074B4a5872A48 state=Committed from=0x97A61E43EfBC9dC5b3082DC7ee2074B4a5872A48 round=1 len(commits)=0 messages="\n"
WARN[03/06,11:16:57 +09] [25] [RC] Received 2f+1 Round Change Messages. Starting new round  address=0x97A61E43EfBC9dC5b3082DC7ee2074B4a5872A48 state=Committed from=0x97A61E43EfBC9dC5b3082DC7ee2074B4a5872A48 currentRound=1 newRound=1
WARN[03/06,11:16:57 +09] [25] Received preprepare message of the hash locked proposal and change state to prepared  address=0x97A61E43EfBC9dC5b3082DC7ee2074B4a5872A48 from=0x97A61E43EfBC9dC5b3082DC7ee2074B4a5872A48 state="Accept request"
INFO[03/06,11:16:57 +09] [24] Committed                                 number=67889644 hash=456054…9b39f5 address=0x97A61E43EfBC9dC5b3082DC7ee2074B4a5872A48
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x54c220]

goroutine 1282 [running]:
math/big.(*Int).Add(0xc002dc8560, 0xc002f43f88, 0x0, 0x93b25974cf15d913)
	/usr/local/go/src/math/big/int.go:118 +0x40
github.com/klaytn/klaytn/node/cn.(*ProtocolManager).BroadcastBlock(0xc000219760, 0xc0004584d0)
	/ext-go/1/src/github.com/klaytn/klaytn/node/cn/handler.go:1283 +0x219
created by github.com/klaytn/klaytn/datasync/fetcher.(*Fetcher).insertWork
	/ext-go/1/src/github.com/klaytn/klaytn/datasync/fetcher/fetcher.go:705 +0xc85

@Aidan 내용 확인 좀 부탁드립니다.

안녕하세요, 궁금한게 있어 몇개 여쭤보겠습니다.

인프라 이슈로 서버가 재부팅 되었다는 말씀은 kscnd stop 을 사용해서 종료한 것이 아닌 비정상종료를 하셨다는 말씀이실까요??

혹시 kscnd.conf의 additional에 --start-block-num 으로 일정 블록 이전으로 돌아가서 재시작 한다던지, 체인백업을 해놓은 것이 있어 복구를 해보셨다던지 등 추가적으로 조치하신 사항들이 있으실까요?