2020年1月20日 星期一

Proxmox 啟動後,出現 LXC CT 啟動錯誤的解決方式

重開 proxmox 之後,出現以下訊息



用 systemctl status pve-container@102.service service 查
root@pve1:~# systemctl status pve-container@102.service
● pve-container@102.service - PVE LXC Container: 102
   Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2020-01-20 17:00:51 CST; 1min 27s ago
     Docs: man:lxc-start
           man:lxc
           man:pct
  Process: 3100 ExecStart=/usr/bin/lxc-start -n 102 (code=exited, status=1/FAILURE)

Jan 20 17:00:51 pve1 systemd[1]: Starting PVE LXC Container: 102...
Jan 20 17:00:51 pve1 lxc-start[3100]: lxc-start: 102: lxccontainer.c: wait_on_daemonized_start: 865 No such file or directory - Failed to receive the container state
Jan 20 17:00:51 pve1 lxc-start[3100]: lxc-start: 102: tools/lxc_start.c: main: 329 The container failed to start
Jan 20 17:00:51 pve1 lxc-start[3100]: lxc-start: 102: tools/lxc_start.c: main: 332 To get more details, run the container in foreground mode
Jan 20 17:00:51 pve1 lxc-start[3100]: lxc-start: 102: tools/lxc_start.c: main: 335 Additional information can be obtained by setting the --logfile and --logpriority options
Jan 20 17:00:51 pve1 systemd[1]: pve-container@102.service: Control process exited, code=exited, status=1/FAILURE
Jan 20 17:00:51 pve1 systemd[1]: pve-container@102.service: Failed with result 'exit-code'.
Jan 20 17:00:51 pve1 systemd[1]: Failed to start PVE LXC Container: 102.
Dec 3 15:57:40 sword systemd[1]: Starting PVE LXC Container: 102...
Dec 3 15:57:40 sword lxc-start[15552]: lxc-start: 102: lxccontainer.c: wait_on_daemonized_start: 865 No such file or directory - Failed to receive the container state
Dec 3 15:57:40 sword lxc-start[15552]: lxc-start: 102: tools/lxc_start.c: main: 329 The container failed to start
Dec 3 15:57:40 sword lxc-start[15552]: lxc-start: 102: tools/lxc_start.c: main: 332 To get more details, run the container in foreground mode
Dec 3 15:57:40 sword lxc-start[15552]: lxc-start: 102: tools/lxc_start.c: main: 335 Additional information can be obtained by setting the --logfile and --logpriority options
Dec 3 15:57:40 sword systemd[1]: pve-container@107.service: Control process exited, code=exited, status=1/FAILURE
Dec 3 15:57:40 sword systemd[1]: pve-container@107.service: Failed with result 'exit-code'.
Dec 3 15:57:40 sword systemd[1]: Failed to start PVE LXC Container: 102.
Dec 3 15:57:40 sword pvedaemon[15550]: command 'systemctl start pve-container@102' failed: exit code 1
Dec 3 15:57:40 sword kernel: [ 3234.588046] lxc-start[15562]: segfault at 50 ip 00007f7e8a656f8b sp 00007ffe43ae6f00 error 4 in liblxc.so.1.6.0[7f7e8a5fd000+8a000]
Dec 3 15:57:40 sword kernel: [ 3234.588073] Code: 9b c0 ff ff 4d 85 ff 0f 85 82 02 00 00 66 90 48 8b 73 50 48 8b bb f8 00 00 00 e8 8>0 78 fa ff 4c 8b 74 24 10 48 89 de 4c 89 f7 <41> ff 56 50 4c 89 f7 48 89 de 41 ff 56 58 48 8b 83 f8 00 00 00 8b
Dec 3 15:57:40 sword pvedaemon[1585]:  end task UPID:sword:00003CBE:0004EF8D:5DE6DA54:vzstart:107:kronvold@pam: comman>d 'systemctl start pve-container@107' failed: exit code 1

開機後 root zfs 正常啟動 但 ssd 的 zfs 沒有 mount 手動 zfs mount -a 就 okay

原因是
zpool.cache 髒了,zpool table 沒有建立。

解決方法
zpool set cachefile=/etc/zfs/zpool.cache <pool name>
例如:
zpool set cachefile=/etc/zfs/zpool.cache ssdpool1

沒有留言:

張貼留言