So quick back story, I have two servers both same specs
-Threadripper 5995wx
-Asus sage wrx80e mobo
-256gb ddr4 ram
-2x nvidia A6000
-2x AJA Kona cards
-1x 25gb nic card
-1x sync card
I’ve been struggling with getting proxmox 8.1 installed on these things. I’ve followed multiple trouble shooting threads from this forum.
https://forum.proxmox.com/threads/proxmox-ve-7-4-cannot-be-installed.125677/
https://forum.proxmox.com/threads/proxmox-ve-7-4-cannot-be-installed.125677/post-549781
I’ve even tried installing directly on top of Debian which didn’t work because I ran into the same issue with that, I could not get it to install. I have made a windows 10 install work fine. The thing that really gets me is, I got through instillation on one of the machines once but had to wipe because I messed up on gpu pass through and after spending a couple days trying to find my fuck up I couldn’t.
Anyways the first large hang up I come across is the loading initial ramdisk on the installer getting stuck I’ve been messing around with different settings for weeks and haven’t had any luck. I know I’m not being very specific but unfortunately I’ve done so much I really can’t remember what I have and haven’t done.
I’ve tried booting in legacy mode, Urdu mode, my last attempt as of yesterday was just trying to boot into a live OS that works on two other computers no problem but I end up hanging up here
(Sorry for copy and paste instead of picture, file size was too big)
1609928) whel-hed 8000:23:00.0: init 0000:25:00.0 fail
1.690095] xhci_hed 0000:28:90.1: init 9000:28:00.1 fail,
- 16
1.690199) xhci_hed 0000:28:00.3: init
9900:28:00.3 fail,
-16
ad volume group
"pve" using metadata type 1vm2
- 16
agical volume (s)
in volume group "pve"' now active
napper/pve-root:
recovering journal
napper/pve-root:
clean, 53013/6291456 files, 2737719/25165824 blocks
7.720817] system [1]: Failed to find module autofs4'
PP! Starting of proc-sys-fs-binfmt-misc.automount cable File Formats File
ND1
Timed out waiting for device dev-disk-byx2duuid-FA10\x2d6B53.device
Dependency failed for boot-efi. mount
/boot/eti.
ND]
Dependency failed for local-fs.target
Local File Systems
AD. Dependency failed for systemd-fsck@dev-disk-byix2d..ce-File System Che
EDI
Failed to start pvefw-logger.service - Proxmox VE firewali logger.
EDI
Failed to start systemd-binfmt.service
- Set Up Additional Binary Forma
ED
Failed to mount run-rpc_pipefs.mount - RPC Pipe File System.
END] Dependency failed for rpc_pipefs.target
END]
Dependency failed for rpe-gssd.service
- RPC security service for NFS c
are in emergency mode. em logs,
After
logging
type
"journalctl
-xb"* to view
"systemct1 reboot' to reboot,
"exit"
Dot into default mode root password for maintenance
press Control-D
continue):
I’m relatively new to Linux so I might be missing something simple but I’m honestly stumped at this point…
-Threadripper 5995wx
-Asus sage wrx80e mobo
-256gb ddr4 ram
-2x nvidia A6000
-2x AJA Kona cards
-1x 25gb nic card
-1x sync card
I’ve been struggling with getting proxmox 8.1 installed on these things. I’ve followed multiple trouble shooting threads from this forum.
https://forum.proxmox.com/threads/proxmox-ve-7-4-cannot-be-installed.125677/
https://forum.proxmox.com/threads/proxmox-ve-7-4-cannot-be-installed.125677/post-549781
I’ve even tried installing directly on top of Debian which didn’t work because I ran into the same issue with that, I could not get it to install. I have made a windows 10 install work fine. The thing that really gets me is, I got through instillation on one of the machines once but had to wipe because I messed up on gpu pass through and after spending a couple days trying to find my fuck up I couldn’t.
Anyways the first large hang up I come across is the loading initial ramdisk on the installer getting stuck I’ve been messing around with different settings for weeks and haven’t had any luck. I know I’m not being very specific but unfortunately I’ve done so much I really can’t remember what I have and haven’t done.
I’ve tried booting in legacy mode, Urdu mode, my last attempt as of yesterday was just trying to boot into a live OS that works on two other computers no problem but I end up hanging up here
(Sorry for copy and paste instead of picture, file size was too big)
1609928) whel-hed 8000:23:00.0: init 0000:25:00.0 fail
1.690095] xhci_hed 0000:28:90.1: init 9000:28:00.1 fail,
- 16
1.690199) xhci_hed 0000:28:00.3: init
9900:28:00.3 fail,
-16
ad volume group
"pve" using metadata type 1vm2
- 16
agical volume (s)
in volume group "pve"' now active
napper/pve-root:
recovering journal
napper/pve-root:
clean, 53013/6291456 files, 2737719/25165824 blocks
7.720817] system [1]: Failed to find module autofs4'
PP! Starting of proc-sys-fs-binfmt-misc.automount cable File Formats File
ND1
Timed out waiting for device dev-disk-byx2duuid-FA10\x2d6B53.device
Dependency failed for boot-efi. mount
/boot/eti.
ND]
Dependency failed for local-fs.target
Local File Systems
AD. Dependency failed for systemd-fsck@dev-disk-byix2d..ce-File System Che
EDI
Failed to start pvefw-logger.service - Proxmox VE firewali logger.
EDI
Failed to start systemd-binfmt.service
- Set Up Additional Binary Forma
ED
Failed to mount run-rpc_pipefs.mount - RPC Pipe File System.
END] Dependency failed for rpc_pipefs.target
END]
Dependency failed for rpe-gssd.service
- RPC security service for NFS c
are in emergency mode. em logs,
After
logging
type
"journalctl
-xb"* to view
"systemct1 reboot' to reboot,
"exit"
Dot into default mode root password for maintenance
press Control-D
continue):
I’m relatively new to Linux so I might be missing something simple but I’m honestly stumped at this point…
Last edited: