저는 최근에 중고 Dell T710을 구입했고 Debian Stretch 9.6과 proxmox 패키지를 설치했습니다.
일부 가상 머신을 실행할 계획입니다. 저는 LVM을 사용하여 설치했고 설치 프로그램이 그 작업을 수행하도록 했습니다.
UEFI 2.1을 통해 4개의 500GB SATA와 500GB의 예비 부팅이 포함된 하드웨어 10 RAID를 실행하고 있습니다.
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는 이러한 볼륨을 사용할 수 없는 것으로 간주합니다.
pv내가 만든 것을 사용하도록 proxmox를 구성하거나 새 것을 삭제 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.cfgProxmox가 임의의 태그를 통해 VG에 대해 내부적으로 알아야 함을 선언합니다 datastore.
lvm: datastore
vgname gladiator-vg
content images,rootdir
shared 0
Proxmox 내에서는 이 VG에 임의의 논리 볼륨(LV)을 생성할 수 없지만 호스트 명령줄에서 이 작업을 수행하는 데 방해가 되는 것은 없습니다. 하지만 할 수 있는 일은 이 VG에서 얻은 가상 디스크를 사용하여 VM을 만드는 것입니다.
이제 Thin LV도 사용한다고 가정하면 좀 더 뒤에서 조정이 필요하다는 것을 알게 될 것입니다. 씬 할당 풀로 사용할 500GB 스토리지 블록 생성
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. 서버를 다시 시작할 필요는 없습니다.
