[SOLVED] PROXMOX INSTALL | error: unknown filesystem.

Seby_Plays

New Member
Jan 2, 2020
8
0
1
22
Guten Abend,
Ich habe mir am Gestrigen Morgen drei mal einen ProxMox install USB-Stick erstellt.
Doch bei jedem mal, wenn ich in den installer booten möchte, werde ich in den GRUB RESCUE-Mode versetzt
und mir folgendes angezeigt :

00 |------------------------------GRUB-RESCUE------------------------------|
01 | error: unknown filesystem. ----------------------------------------|
02 | error: unknown filesystem. ----------------------------------------|
03 | error: unknown filesystem. ----------------------------------------|
04 | error: unknown filesystem. ----------------------------------------|
05 | error: unknown filesystem. ----------------------------------------|
06 | error: unknown filesystem. ----------------------------------------|
07 | error: unknown filesystem. ----------------------------------------|
08 | error: unknown filesystem. ----------------------------------------|
09 | error: unknown filesystem. ----------------------------------------|
10 | Entering rescue mode... ---------------------------------------------|
11 | grub rescue> ------------------------------------------------------------|
12 |---------------------------------------------------------------------------------|

Ich freu mich auf antworten.
MfG
 

Seby_Plays

New Member
Jan 2, 2020
8
0
1
22
Hi,

kaputter USB Stick?
Probier mal Proxmox über Debian zu installieren.
https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster


Abend!
Danke für die antwort.
Ich habe die Debian Installation ausprobiert, leider kam das raus:

---------------------------------------------------------------------------------------
Errors were encountered while processing:
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@debian:~#
---------------------------------------------------------------------------------------
 

wolfgang

Proxmox Staff Member
Oct 1, 2014
6,496
496
103
Bitte schau mal ob in den Logs ein hinweis ist.

journalctl -u pve-manager
journalctl -xe
 

Seby_Plays

New Member
Jan 2, 2020
8
0
1
22
root@debian:~# journalctl -xe
Jan 03 20:55:11 debian pveproxy[421]: worker exit
Jan 03 20:55:11 debian pveproxy[424]: worker exit
Jan 03 20:55:11 debian pveproxy[1333]: worker 421 finished
Jan 03 20:55:11 debian pveproxy[1333]: worker 424 finished
Jan 03 20:55:11 debian pveproxy[1333]: starting 2 worker(s)
Jan 03 20:55:11 debian pveproxy[1333]: worker 429 started
Jan 03 20:55:11 debian pveproxy[1333]: worker 430 started
Jan 03 20:55:11 debian pveproxy[429]: /etc/pve/local/pve-ssl.key: failed to load
Jan 03 20:55:11 debian pveproxy[430]: /etc/pve/local/pve-ssl.key: failed to load
Jan 03 20:55:15 debian pveproxy[427]: worker exit
Jan 03 20:55:15 debian pveproxy[1333]: worker 427 finished
Jan 03 20:55:15 debian pveproxy[1333]: starting 1 worker(s)
Jan 03 20:55:15 debian pveproxy[1333]: worker 432 started
Jan 03 20:55:15 debian pveproxy[432]: /etc/pve/local/pve-ssl.key: failed to load
Jan 03 20:55:16 debian pveproxy[429]: worker exit
Jan 03 20:55:16 debian pveproxy[430]: worker exit
Jan 03 20:55:16 debian pveproxy[1333]: worker 429 finished
Jan 03 20:55:16 debian pveproxy[1333]: worker 430 finished
Jan 03 20:55:16 debian pveproxy[1333]: starting 2 worker(s)
Jan 03 20:55:16 debian pveproxy[1333]: worker 434 started
Jan 03 20:55:16 debian pveproxy[1333]: worker 435 started
Jan 03 20:55:16 debian pveproxy[434]: /etc/pve/local/pve-ssl.key: failed to load
Jan 03 20:55:16 debian pveproxy[435]: /etc/pve/local/pve-ssl.key: failed to load
lines 1135-1157/1157 (END)
Jan 03 20:55:11 debian pveproxy[421]: worker exit
Jan 03 20:55:11 debian pveproxy[424]: worker exit
Jan 03 20:55:11 debian pveproxy[1333]: worker 421 finished
Jan 03 20:55:11 debian pveproxy[1333]: worker 424 finished
Jan 03 20:55:11 debian pveproxy[1333]: starting 2 worker(s)
Jan 03 20:55:11 debian pveproxy[1333]: worker 429 started
Jan 03 20:55:11 debian pveproxy[1333]: worker 430 started
Jan 03 20:55:11 debian pveproxy[429]: /etc/pve/local/pve-ssl.key: failed to load local private
Jan 03 20:55:11 debian pveproxy[430]: /etc/pve/local/pve-ssl.key: failed to load local private
Jan 03 20:55:15 debian pveproxy[427]: worker exit
Jan 03 20:55:15 debian pveproxy[1333]: worker 427 finished
Jan 03 20:55:15 debian pveproxy[1333]: starting 1 worker(s)
Jan 03 20:55:15 debian pveproxy[1333]: worker 432 started
Jan 03 20:55:15 debian pveproxy[432]: /etc/pve/local/pve-ssl.key: failed to load local private
Jan 03 20:55:16 debian pveproxy[429]: worker exit
Jan 03 20:55:16 debian pveproxy[430]: worker exit
Jan 03 20:55:16 debian pveproxy[1333]: worker 429 finished
Jan 03 20:55:16 debian pveproxy[1333]: worker 430 finished
Jan 03 20:55:16 debian pveproxy[1333]: starting 2 worker(s)
Jan 03 20:55:16 debian pveproxy[1333]: worker 434 started
Jan 03 20:55:16 debian pveproxy[1333]: worker 435 started
Jan 03 20:55:16 debian pveproxy[434]: /etc/pve/local/pve-ssl.key: failed to load local private
Jan 03 20:55:16 debian pveproxy[435]: /etc/pve/local/pve-ssl.key: failed to load local private
lines 1135-1157/1157 (END)
Jan 03 20:55:11 debian pveproxy[421]: worker exit
Jan 03 20:55:11 debian pveproxy[424]: worker exit
Jan 03 20:55:11 debian pveproxy[1333]: worker 421 finished
Jan 03 20:55:11 debian pveproxy[1333]: worker 424 finished
Jan 03 20:55:11 debian pveproxy[1333]: starting 2 worker(s)
Jan 03 20:55:11 debian pveproxy[1333]: worker 429 started
Jan 03 20:55:11 debian pveproxy[1333]: worker 430 started
Jan 03 20:55:11 debian pveproxy[429]: /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 1699.
Jan 03 20:55:11 debian pveproxy[430]: /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 1699.
Jan 03 20:55:15 debian pveproxy[427]: worker exit
Jan 03 20:55:15 debian pveproxy[1333]: worker 427 finished
Jan 03 20:55:15 debian pveproxy[1333]: starting 1 worker(s)
Jan 03 20:55:15 debian pveproxy[1333]: worker 432 started
Jan 03 20:55:15 debian pveproxy[432]: /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 1699.
Jan 03 20:55:16 debian pveproxy[429]: worker exit
Jan 03 20:55:16 debian pveproxy[430]: worker exit
Jan 03 20:55:16 debian pveproxy[1333]: worker 429 finished
Jan 03 20:55:16 debian pveproxy[1333]: worker 430 finished
Jan 03 20:55:16 debian pveproxy[1333]: starting 2 worker(s)
Jan 03 20:55:16 debian pveproxy[1333]: worker 434 started
Jan 03 20:55:16 debian pveproxy[1333]: worker 435 started
Jan 03 20:55:16 debian pveproxy[434]: /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 1699.
Jan 03 20:55:16 debian pveproxy[435]: /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 1699.
 

Seby_Plays

New Member
Jan 2, 2020
8
0
1
22
Bitte schau mal ob in den Logs ein hinweis ist.

journalctl -u pve-manager
journalctl -xe


Ich kann mein zertifikat auch nicht updaten bzw. ein neues zertifikat generieren mit "pvecm updatecerts"

Da nur folgendes dabei entspringt :

------------------------------------------------------------------
root@debian:~# pvecm updatecerts
ipcc_send_rec[1] failed: Connection refused
ipcc_send_rec[2] failed: Connection refused
ipcc_send_rec[3] failed: Connection refused
Unable to load access control list: Connection refused
root@debian:~#
------------------------------------------------------------------
 

Seby_Plays

New Member
Jan 2, 2020
8
0
1
22
Zudem, kann ich wegen diesem error auch keine anderen sachen mehr installieren!
Immer der selbe fehler mit den prozessen!!!
 

wolfgang

Proxmox Staff Member
Oct 1, 2014
6,496
496
103
Die Logs geben nichts her der Zertifikats Fehler ist zu erwarten da das pmxcfs nicht richtig installiert ist.
schick mir bitte den gesamten Output von

Code:
apt-get install -f
apt-get install -V proxmox-ve pve-manager
 

Seby_Plays

New Member
Jan 2, 2020
8
0
1
22
Wie gesagt, ich kann wegen diesem bug nichts installieren!


root@debian:/home/default# apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libgnutls-dane0 libunbound8
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up pve-manager (6.1-5) ...
Job for pvestatd.service failed because the control process exited with error code.
See "systemctl status pvestatd.service" and "journalctl -xe" for details.
dpkg: error processing package pve-manager (--configure):
installed pve-manager package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on pve-manager; however:
Package pve-manager is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@debian:/home/default# apt-get install -V proxmox-ve pve-manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
proxmox-ve is already the newest version (6.1-2).
pve-manager is already the newest version (6.1-5).
pve-manager set to manually installed.
The following packages were automatically installed and are no longer required:
libgnutls-dane0 (3.6.7-4)
libunbound8 (1.9.0-2+deb10u1)
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up pve-manager (6.1-5) ...
Job for pvestatd.service failed because the control process exited with error code.
See "systemctl status pvestatd.service" and "journalctl -xe" for details.
dpkg: error processing package pve-manager (--configure):
installed pve-manager package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on pve-manager; however:
Package pve-manager is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@debian:/home/default#
 

oguz

Proxmox Staff Member
Staff member
Nov 19, 2018
5,192
672
118

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!