我最近购买了一台二手 Dell T710，我安装了 Debian Stretch 9.6 和 proxmox 软件包。
我打算运行一些虚拟机。我使用 LVM 安装并让安装程序完成其任务。
我正在使用 4 500GB SATA 运行硬件 10 raid，并通过 UEFI 2.1 引导 500GB 备用。
我注意到，当我打开 proxmox 网页时，该卷上没有可用空间可供我使用，或者至少我是这样解释主页上的图形的。
因此，我开始缩小主分区，该分区占用了 pv 上的剩余空间，并且无法缩小分区来仅为 proxmox 创建一个新分区，或者在我可以配置的同一组中创建一个新卷proxmox 访问。
我目前正在从服务器上运行的 systemrescuecd 会话进行剪切和粘贴。有简单的方法吗？
我一直在这里阅读：
和这里：
我确实遵循了另一个链接，该链接向我展示了如何在一个命令中执行文件系统和卷收缩......
我不记得链接，但我认为命令是lvresize -r -L lVPath PVPath.我提供了一些希望相关的系统信息：
% lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
home gladiator-vg -wi-a----- 50.00g
root gladiator-vg -wi-a----- 27.94g
swap_1 gladiator-vg -wi-a----- 31.98g
home不是 中的最后一卷VG。我正在读到这可能需要一些更复杂的操作。
% lvdisplay
--- Logical volume ---
LV Path /dev/gladiator-vg/root
LV Name root
VG Name gladiator-vg
LV UUID txWegy-ROvW-TMSG-0y4i-sCey-JHDQ-YpKRmL
LV Write Access read/write
LV Creation host, time gladiator, 2018-11-21 00:45:44 +0000
LV Status available
# open 0
LV Size 27.94 GiB
Current LE 7152
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0
--- Logical volume ---
LV Path /dev/gladiator-vg/swap_1
LV Name swap_1
VG Name gladiator-vg
LV UUID eifh70-cPbQ-Nh7l-UYUG-OHq2-Swkh-942xCe
LV Write Access read/write
LV Creation host, time gladiator, 2018-11-21 00:45:44 +0000
LV Status available
# open 0
LV Size 31.98 GiB
Current LE 8187
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1
--- Logical volume ---
LV Path /dev/gladiator-vg/home
LV Name home
VG Name gladiator-vg
LV UUID Ze23Gj-OGmr-buUx-SHES-hpP1-9Jjp-cENrqj
LV Write Access read/write
LV Creation host, time gladiator, 2018-11-21 00:45:44 +0000
LV Status available
# open 0
LV Size 50.00 GiB
Current LE 12800
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:2
% lvscan
ACTIVE '/dev/gladiator-vg/root' [27.94 GiB] inherit
ACTIVE '/dev/gladiator-vg/swap_1' [31.98 GiB] inherit
ACTIVE '/dev/gladiator-vg/home' [50.00 GiB] inherit
% pvdisplay
--- Physical volume ---
PV Name /dev/sda3
VG Name gladiator-vg
PV Size 929.76 GiB / not usable 2.00 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 238018
Free PE 209879
Allocated PE 28139
PV UUID VjY4Hv-BfxI-plZ2-5A17-SCcC-pCYm-g9xGZ5
% pvscan
PV /dev/sda3 VG gladiator-vg lvm2 [929.76 GiB / 819.84 GiB free]
Total: 1 [929.76 GiB] / in use: 1 [929.76 GiB] / in no VG: 0 [0 ]
% fdisk -l
Disk /dev/loop0: 405.6 MiB, 425336832 bytes, 830736 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/sda: 930.5 GiB, 999116767232 bytes, 1951399936 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 056405C6-7818-4837-92CB-E47732521E90
Device Start End Sectors Size Type
/dev/sda1 2048 1050623 1048576 512M EFI System
/dev/sda2 1050624 1550335 499712 244M Linux filesystem
/dev/sda3 1550336 1951397887 1949847552 929.8G Linux LVM
Disk /dev/sdb: 7.5 GiB, 8053063680 bytes, 15728640 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00007a66
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 1 15728639 15728639 7.5G c W95 FAT32 (LBA)
Disk /dev/mapper/gladiator--vg-root: 28 GiB, 29997662208 bytes, 58589184 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/gladiator--vg-swap_1: 32 GiB, 34338766848 bytes, 67067904 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/gladiator--vg-home: 50 GiB, 53687091200 bytes, 104857600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
更新：
我能够成功缩小分区，创建卷组。 Proxmox 认为这些卷不可用。
我想我需要配置 proxmox 以使用pv我创建的或删除新的pv，并尝试重新配置/重新安装 proxmox 以设置它需要的卷。有什么建议么？
xxxx@xxxxxx:~# pvscan
PV /dev/sda3 VG xxxxxx-vg lvm2 [929.76 GiB / 619.64 GiB free]
Total: 1 [929.76 GiB] / in use: 1 [929.76 GiB] / in no VG: 0 [0 ]
root@gladiator:~# systemctl status pveproxy
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2018-12-22 19:39:22 EST; 1h 30min ago
Process: 2696 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
Main PID: 2754 (pveproxy)
Tasks: 3 (limit: 4915)
Memory: 122.7M
CPU: 1min 50.387s
CGroup: /system.slice/pveproxy.service
├─2754 pveproxy
├─8411 pveproxy worker
└─8412 pveproxy worker
lsblk --ascii
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 930.5G 0 disk
|-sda1 8:1 0 512M 0 part /boot/efi
|-sda2 8:2 0 244M 0 part /boot
`-sda3 8:3 0 929.8G 0 part
|-gladiator--vg-root 253:0 0 28G 0 lvm /
|-gladiator--vg-swap_1 253:1 0 32G 0 lvm [SWAP]
|-gladiator--vg-home 253:2 0 50G 0 lvm /home
|-gladiator--vg-thinlv_tmeta 253:3 0 100M 0 lvm
| `-gladiator--vg-thinlv 253:5 0 200G 0 lvm /thinlv
`-gladiator--vg-thinlv_tdata 253:4 0 200G 0 lvm
`-gladiator--vg-thinlv 253:5 0 200G 0 lvm /thinlv
sr0 11:0 1 1024M 0 rom
# systemctl status pveproxy
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2018-12-22 19:39:22 EST; 1h 54min ago
Process: 2696 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
Main PID: 2754 (pveproxy)
Tasks: 4 (limit: 4915)
Memory: 126.5M
CPU: 2min 22.812s
CGroup: /system.slice/pveproxy.service
├─2754 pveproxy
├─9922 pveproxy worker
├─9923 pveproxy worker
└─9924 pveproxy worker
Dec 22 21:33:55 gladiator pveproxy[9920]: worker exit
Dec 22 21:33:55 gladiator pveproxy[2754]: worker 9920 finished
Dec 22 21:33:55 gladiator pveproxy[2754]: starting 1 worker(s)
Dec 22 21:33:55 gladiator pveproxy[2754]: worker 9923 started
Dec 22 21:33:55 gladiator pveproxy[9923]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1647.
Dec 22 21:33:55 gladiator pveproxy[9921]: worker exit
Dec 22 21:33:55 gladiator pveproxy[2754]: worker 9921 finished
Dec 22 21:33:55 gladiator pveproxy[2754]: starting 1 worker(s)
Dec 22 21:33:55 gladiator pveproxy[2754]: worker 9924 started
Dec 22 21:33:55 gladiator pveproxy[9924]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1647.
~# ls -lR /etc/pve
/etc/pve:
total 8
drwxr-xr-x 2 root root 4096 Dec 21 23:34 local
-rw-r--r-- 1 root root 192 Dec 20 21:09 storage.cfg
/etc/pve/local:
total 0
storage.cfg我事后重新添加了。但是，我的所有证书文件都消失了，并且我被拒绝尝试重新创建它们。
此外，我试图添加另一个lv以安装在/var/lib/vz.我相信这阻碍了我的启动。
我fstab从systemrescuecd环境中进行编辑并注释掉了有问题的行。
所以请让我知道我还能提供什么修复。
我并不着急，我只是想弄清楚这个问题并学习 proxmox。
我添加了一个薄卷：
# lvdisplay
--- Logical volume ---
LV Path /dev/gladiator-vg/root
LV Name root
VG Name gladiator-vg
LV UUID txWegy-ROvW-TMSG-0y4i-sCey-JHDQ-YpKRmL
LV Write Access read/write
LV Creation host, time gladiator, 559220-11-12 16:29:28 -0500
LV Status available
# open 1
LV Size 27.94 GiB
Current LE 7152
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0
--- Logical volume ---
LV Path /dev/gladiator-vg/swap_1
LV Name swap_1
VG Name gladiator-vg
LV UUID eifh70-cPbQ-Nh7l-UYUG-OHq2-Swkh-942xCe
LV Write Access read/write
LV Creation host, time gladiator, 559220-11-12 16:29:28 -0500
LV Status available
# open 2
LV Size 31.98 GiB
Current LE 8187
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1
--- Logical volume ---
LV Path /dev/gladiator-vg/home
LV Name home
VG Name gladiator-vg
LV UUID Ze23Gj-OGmr-buUx-SHES-hpP1-9Jjp-cENrqj
LV Write Access read/write
LV Creation host, time gladiator, 559220-11-12 16:29:28 -0500
LV Status available
# open 1
LV Size 50.00 GiB
Current LE 12800
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:2
--- Logical volume ---
LV Name thinlv
VG Name gladiator-vg
LV UUID XzlKYn-xyrk-w8dG-QNrG-kcml-fVpW-BTYJ4s
LV Write Access read/write
LV Creation host, time sysresccd, 559220-12-12 17:54:03 -0500
LV Pool metadata thinlv_tmeta
LV Pool data thinlv_tdata
LV Status available
# open 1
LV Size 200.00 GiB
Allocated pool data 0.00%
Allocated metadata 0.43%
Current LE 51200
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:5
我尝试添加另一个lv以提供更多空间/var/lib/vz。就在那时，我相信系统在日志中出现了依赖错误。
所以我删除了它并忘记编辑fstab。上面指出，我在意识到问题后启动了它。
所以系统启动时，只是没有 Proxmox :(
# systemctl list-units --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● pve-cluster.service loaded failed failed The Proxmox VE cluster filesystem
● pve-daily-update.service loaded failed failed Daily PVE download activities
● pve-firewall.service loaded failed failed Proxmox VE firewall
● pve-guests.service loaded failed failed PVE guests
● pve-ha-crm.service loaded failed failed PVE Cluster Ressource Manager Daemon
● pve-ha-lrm.service loaded failed failed PVE Local HA Ressource Manager Daemon
● pvesr.service loaded failed failed Proxmox VE replication runner
● pvestatd.service loaded failed failed PVE Status Daemon
● virtualbox.service loaded failed failed LSB: VirtualBox Linux kernel module
# journalctl -xe
Dec 23 16:31:00 gladiator systemd[1]: pvesr.service: Main process exited, code=exited, status=111/n/a
Dec 23 16:31:00 gladiator systemd[1]: Failed to start Proxmox VE replication runner.
-- Subject: Unit pvesr.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit pvesr.service has failed.
--
-- The result is failed.
Dec 23 16:31:00 gladiator systemd[1]: pvesr.service: Unit entered failed state.
Dec 23 16:31:00 gladiator systemd[1]: pvesr.service: Failed with result 'exit-code'.
Dec 23 16:31:01 gladiator cron[2314]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
Dec 23 16:31:05 gladiator pveproxy[6281]: worker exit
Dec 23 16:31:05 gladiator pveproxy[2735]: worker 6281 finished
Dec 23 16:31:05 gladiator pveproxy[2735]: starting 1 worker(s)
Dec 23 16:31:05 gladiator pveproxy[2735]: worker 6295 started
Dec 23 16:31:05 gladiator pveproxy[6295]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/sh
Dec 23 16:31:05 gladiator pveproxy[6283]: worker exit
Dec 23 16:31:05 gladiator pveproxy[6282]: worker exit
Dec 23 16:31:05 gladiator pveproxy[2735]: worker 6282 finished
Dec 23 16:31:05 gladiator pveproxy[2735]: worker 6283 finished
Dec 23 16:31:05 gladiator pveproxy[2735]: starting 1 worker(s)
Dec 23 16:31:05 gladiator pveproxy[2735]: worker 6297 started
Dec 23 16:31:05 gladiator pveproxy[6297]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/sh
Dec 23 16:31:10 gladiator pveproxy[6295]: worker exit
Dec 23 16:31:10 gladiator pveproxy[2735]: worker 6295 finished
Dec 23 16:31:10 gladiator pveproxy[2735]: starting 2 worker(s)
Dec 23 16:31:10 gladiator pveproxy[2735]: worker 6300 started
Dec 23 16:31:10 gladiator pveproxy[2735]: worker 6301 started
Dec 23 16:31:10 gladiator pveproxy[6300]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/sh
Dec 23 16:31:10 gladiator pveproxy[6297]: worker exit
Dec 23 16:31:10 gladiator pveproxy[6301]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/sh
Dec 23 16:31:10 gladiator pveproxy[2735]: worker 6297 finished
Dec 23 16:31:10 gladiator pveproxy[2735]: starting 1 worker(s)
Dec 23 16:31:10 gladiator pveproxy[2735]: worker 6302 started
Dec 23 16:31:10 gladiator pveproxy[6302]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/sh
Dec 23 16:31:15 gladiator pveproxy[6300]: worker exit
Dec 23 16:31:15 gladiator pveproxy[6301]: worker exit
Dec 23 16:31:15 gladiator pveproxy[2735]: worker 6300 finished
Dec 23 16:31:15 gladiator pveproxy[2735]: starting 1 worker(s)
Dec 23 16:31:15 gladiator pveproxy[2735]: worker 6303 started
Dec 23 16:31:15 gladiator pveproxy[2735]: worker 6301 finished
Dec 23 16:31:15 gladiator pveproxy[2735]: starting 1 worker(s)
Dec 23 16:31:15 gladiator pveproxy[2735]: worker 6304 started
Dec 23 16:31:15 gladiator pveproxy[6303]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/sh
Dec 23 16:31:15 gladiator pveproxy[6302]: worker exit
Dec 23 16:31:15 gladiator pveproxy[6304]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/sh
Dec 23 16:31:15 gladiator pveproxy[2735]: worker 6302 finished
Dec 23 16:31:15 gladiator pveproxy[2735]: starting 1 worker(s)
Dec 23 16:31:15 gladiator pveproxy[2735]: worker 6305 started
Dec 23 16:31:15 gladiator pveproxy[6305]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/sh
Dec 23 16:31:20 gladiator pveproxy[6303]: worker exit
Dec 23 16:31:20 gladiator pveproxy[6304]: worker exit
Dec 23 16:31:20 gladiator pveproxy[2735]: worker 6303 finished
Dec 23 16:31:20 gladiator pveproxy[2735]: starting 1 worker(s)
Dec 23 16:31:20 gladiator pveproxy[2735]: worker 6306 started
Dec 23 16:31:20 gladiator pveproxy[2735]: worker 6304 finished
Dec 23 16:31:20 gladiator pveproxy[2735]: starting 1 worker(s)
Dec 23 16:31:20 gladiator pveproxy[2735]: worker 6307 started
Dec 23 16:31:20 gladiator pveproxy[6306]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/sh
Dec 23 16:31:20 gladiator pveproxy[6305]: worker exit
Dec 23 16:31:20 gladiator pveproxy[6307]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/sh
Dec 23 16:31:20 gladiator pveproxy[2735]: worker 6305 finished
Dec 23 16:31:20 gladiator pveproxy[2735]: starting 1 worker(s)
Dec 23 16:31:20 gladiator pveproxy[2735]: worker 6308 started
Dec 23 16:31:20 gladiator pveproxy[6308]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/sh
Dec 23 16:31:25 gladiator pveproxy[6306]: worker exit
Dec 23 16:31:25 gladiator pveproxy[6307]: worker exit
Dec 23 16:31:25 gladiator pveproxy[2735]: worker 6306 finished
Dec 23 16:31:25 gladiator pveproxy[2735]: starting 1 worker(s)
Dec 23 16:31:25 gladiator pveproxy[2735]: worker 6309 started
Dec 23 16:31:25 gladiator pveproxy[2735]: worker 6307 finished
Dec 23 16:31:25 gladiator pveproxy[2735]: starting 1 worker(s)
Dec 23 16:31:25 gladiator pveproxy[2735]: worker 6310 started
Dec 23 16:31:25 gladiator pveproxy[6309]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/sh
Dec 23 16:31:25 gladiator pveproxy[6308]: worker exit
Dec 23 16:31:25 gladiator pveproxy[6310]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/sh
Dec 23 16:31:25 gladiator pveproxy[2735]: worker 6308 finished
Dec 23 16:31:25 gladiator pveproxy[2735]: starting 1 worker(s)
Dec 23 16:31:25 gladiator pveproxy[2735]: worker 6311 started
Dec 23 16:31:25 gladiator pveproxy[6311]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/sh
Dec 23 16:31:30 gladiator pveproxy[6309]: worker exit
Dec 23 16:31:30 gladiator pveproxy[6310]: worker exit
Dec 23 16:31:30 gladiator pveproxy[2735]: worker 6309 finished
Dec 23 16:31:30 gladiator pveproxy[2735]: starting 1 worker(s)
Dec 23 16:31:30 gladiator pveproxy[2735]: worker 6312 started
Dec 23 16:31:30 gladiator pveproxy[2735]: worker 6310 finished
Dec 23 16:31:30 gladiator pveproxy[2735]: starting 1 worker(s)
Dec 23 16:31:30 gladiator pveproxy[2735]: worker 6313 started
Dec 23 16:31:30 gladiator pveproxy[6312]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/sh
Dec 23 16:31:30 gladiator pveproxy[6311]: worker exit
Dec 23 16:31:30 gladiator pveproxy[6313]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/sh
Dec 23 16:31:30 gladiator pveproxy[2735]: worker 6311 finished
Dec 23 16:31:30 gladiator pveproxy[2735]: starting 1 worker(s)
Dec 23 16:31:30 gladiator pveproxy[2735]: worker 6314 started
Dec 23 16:31:30 gladiator pveproxy[6314]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/sh
lines 1167-1189/1189 (END)
Dec 23 16:31:25 gladiator pveproxy[2735]: worker 6310 started
Dec 23 16:31:25 gladiator pveproxy[6309]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APISe
Dec 23 16:31:25 gladiator pveproxy[6308]: worker exit
Dec 23 16:31:25 gladiator pveproxy[6310]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APISe
Dec 23 16:31:25 gladiator pveproxy[2735]: worker 6308 finished
Dec 23 16:31:25 gladiator pveproxy[2735]: starting 1 worker(s)
Dec 23 16:31:25 gladiator pveproxy[2735]: worker 6311 started
Dec 23 16:31:25 gladiator pveproxy[6311]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APISe
Dec 23 16:31:30 gladiator pveproxy[6309]: worker exit
Dec 23 16:31:30 gladiator pveproxy[6310]: worker exit
Dec 23 16:31:30 gladiator pveproxy[2735]: worker 6309 finished
Dec 23 16:31:30 gladiator pveproxy[2735]: starting 1 worker(s)
Dec 23 16:31:30 gladiator pveproxy[2735]: worker 6312 started
Dec 23 16:31:30 gladiator pveproxy[2735]: worker 6310 finished
Dec 23 16:31:30 gladiator pveproxy[2735]: starting 1 worker(s)
Dec 23 16:31:30 gladiator pveproxy[2735]: worker 6313 started
Dec 23 16:31:30 gladiator pveproxy[6312]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APISe
Dec 23 16:31:30 gladiator pveproxy[6311]: worker exit
Dec 23 16:31:30 gladiator pveproxy[6313]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APISe
Dec 23 16:31:30 gladiator pveproxy[2735]: worker 6311 finished
Dec 23 16:31:30 gladiator pveproxy[2735]: starting 1 worker(s)
Dec 23 16:31:30 gladiator pveproxy[2735]: worker 6314 started
Dec 23 16:31:30 gladiator pveproxy[6314]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APISe
答案1
Proxmox 应该能够看到名为 的卷组 (VG) gladiator-vg。 （我发现 Proxmox 自动检测到 VG 并要求我命名它。）如果没有，请添加此块以/etc/pve/storage.cfg声明 Proxmox 内部应通过任意标签了解您的 VG datastore。
lvm: datastore
vgname gladiator-vg
content images,rootdir
shared 0
您无法从 Proxmox 内在此 VG 上创建任意逻辑卷 (LV)，但没有什么可以阻止您从主机命令行执行此操作。不过，您可以做的是使用从此 VG 获取的虚拟磁盘创建 VM。
现在，假设您还想使用 Thin LV，您会发现需要更多的幕后调整。创建 500 GB 的存储块用作精简分配池
lvcreate --size 500G --thin gladiator-vg/thinlv
并将下一个块添加到storage.cfg文件中。它thin使用名为 的 LV声明了一个名为 的精简池thinlv。
lvmthin: thin
thinpool thinlv
vgname gladiator-vg
content rootdir,images
Proxmox 非常擅长快速捕捉变化storage.cfg。您当然不需要重新启动服务器。
