rancher2使用docker安装后自带了一个k3s，应该是用来管理rancher服务器。我用rancher建了个K8S集群，最近服务器异常，rancher一直重启，提示自带的K3s加载etcd失败，请问怎么恢复这个自带K3s自带的etcd的snapshot，因为docker一直在重启，也没法进入rancher那个容器执行k3s的命令。谢谢
{“level”:“info”,“ts”:“2025-01-06T00:40:09.51376Z”,“caller”:“etcdserver/server.go:509”,“msg”:“recovered v2 store from snapshot”,“snapshot-index”:9060928,“snapshot-size”:“16 kB”}
{“level”:“warn”,“ts”:“2025-01-06T00:40:09.517286Z”,“caller”:“snap/db.go:88”,“msg”:“failed to find [SNAPSHOT-INDEX].snap.db”,“snapshot-index”:9060928,“snapshot-file-path”:“/var/lib/rancher/k3s/server/db/etcd-tmp/member/snap/00000000008a4240.snap.db”,“error”:“snap: snapshot file doesn’t exist”}
{“level”:“panic”,“ts”:“2025-01-06T00:40:09.517761Z”,“caller”:“etcdserver/server.go:516”,“msg”:“failed to recover v3 backend from snapshot”,“error”:“failed to find database snapshot file (snap: snapshot file doesn’t exist)”,“stacktrace”:“go.etcd.io/etcd/server/v3/etcdserver.NewServer\n\t/go/pkg/mod/github.com/k3s-io/etcd/server/v3@v3.5.9-k3s1/etcdserver/server.go:516\ngo.etcd.io/etcd/server/v3/embed.StartEtcd\n\t/go/pkg/mod/github.com/k3s-io/etcd/server/v3@v3.5.9-k3s1/embed/etcd.go:246\ngithub.com/k3s-io/k3s/pkg/daemons/executor.(*Embedded).ETCD\n\t/go/src/github.com/k3s-io/k3s/pkg/daemons/executor/etcd.go:30\ngithub.com/k3s-io/k3s/pkg/etcd.(*ETCD).StartEmbeddedTemporary\n\t/go/src/github.com/k3s-io/k3s/pkg/etcd/etcd.go:895\ngithub.com/k3s-io/k3s/pkg/cluster.(*Cluster).reconcileEtcd\n\t/go/src/github.com/k3s-io/k3s/pkg/cluster/bootstrap.go:509\ngithub.com/k3s-io/k3s/pkg/cluster.(*Cluster).Bootstrap\n\t/go/src/github.com/k3s-io/k3s/pkg/cluster/bootstrap.go:63\ngithub.com/k3s-io/k3s/pkg/daemons/control.prepare\n\t/go/src/github.com/k3s-io/k3s/pkg/daemons/control/server.go:277\ngithub.com/k3s-io/k3s/pkg/daemons/control.Server\n\t/go/src/github.com/k3s-io/k3s/pkg/daemons/control/server.go:34\ngithub.com/k3s-io/k3s/pkg/server.StartServer\n\t/go/src/github.com/k3s-io/k3s/pkg/server/server.go:56\ngithub.com/k3s-io/k3s/pkg/cli/server.run\n\t/go/src/github.com/k3s-io/k3s/pkg/cli/server/server.go:496\ngithub.com/k3s-io/k3s/pkg/cli/server.Run\n\t/go/src/github.com/k3s-io/k3s/pkg/cli/server/server.go:41\ngithub.com/urfave/cli.HandleAction\n\t/go/pkg/mod/github.com/urfave/cli@v1.22.14/app.go:524\ngithub.com/urfave/cli.Command.Run\n\t/go/pkg/mod/github.com/urfave/cli@v1.22.14/command.go:175\ngithub.com/urfave/cli.(*App).Run\n\t/go/pkg/mod/github.com/urfave/cli@v1.22.14/app.go:277\nmain.main\n\t/go/src/github.com/k3s-io/k3s/cmd/server/main.go:81\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250”}
panic: failed to recover v3 backend from snapshot