Proxmox installation of package failed during install

A

Arctic

New Member
May 30, 2024
16
1
3
So I used to have Proxmox 6.4 installed on a server, and I think I might have set it up wrong so I tried to reinstall Proxmox. When I tried to install it again I keep getting an error, however it's not the same exact error every time. I get through the install wizard to set up Proxmox and it starts to install. It gets to about 50%-70% when it starts to install packages. Then at a random % it will say that it failed to install a package. I've gotten all different types of packages every time, ranging from "ceph-common_12.2.11+dfsg1-2.1+b1_amd64.deb", "libhtml-parser-perl_3.72-3+b3_amd64.deb", "gnupg-l10n_2.2.12-1+deb10u1_all.deb", libnl-route-3-200_3.4.0-1_amd64.deb", and many others. I've tried to remake the installation media on the same USB and different USBs and nothing has changed. I've also tried a different M.2 all together and it still gives the same type of error.

Any ideas on how to fix it?
 
Bad install media, or target disk possibly dying. Could also be bad RAM. Re-download the ISO from torrent and try burning it to micro- or full-size SD card, and run memtest86+ for at least 6 hours
 
Kingneutron said:
Bad install media, or target disk possibly dying. Could also be bad RAM. Re-download the ISO from torrent and try burning it to micro- or full-size SD card, and run memtest86+ for at least 6 hours
Click to expand...
I can't torrent in my organization. I know the disk isn't dying, tried multiple disks. Also tried multiple installation medias and it didn't change anything.
 
Try installing plain Debian on that server & test outcome. Something seems not right with your HW. Could you share the HW used - maybe this could shed some light on the issue.
 
gfngfn256 said:
Try installing plain Debian on that server & test outcome. Something seems not right with your HW. Could you share the HW used - maybe this could shed some light on the issue.
Click to expand...
I’m out for Christmas right now and won’t be back until 1/6 so it will be a minute as I don’t know the hardware off the top of my head. But once I get back I’ll look into it. I’ll also try to install Debian.
 
gfngfn256 said:
Did you wipe the server disk before trying to reinstall?
Click to expand...
No, I thought it does this during installation anyways so I left it. But I don’t think the disk is the issue as I have tried multiple different disks and the issue persists.
 
gfngfn256 said:
Try installing plain Debian on that server & test outcome. Something seems not right with your HW. Could you share the HW used - maybe this could shed some light on the issue.
Click to expand...
I just got back and was able to find out my hardware. This is my hardware:
Motherboard: Asrock Rack ROMED8-2T Server Motherboard AMD EPYC 7003 (with AMD 3D V-Cache Technology)/7002 series processors SP3 (LGA 4094) Dual 10GbE
CPU: AMD EPYC 48 CORE Processor 7642 2.3GHZ Base / 3.3GHZ MAX 256MB L3 Cache TDP 225W SP3 Socket (Rome) (2ND GEN) (100-000000074) (OEM Tray Processor)
RAM: 256GB 4x64GB DDR4-3200 PC4-25600 2Rx4 RDIMM ECC Registered Memory by NEMIX RAM
SSD: SAMSUNG 990 PRO SSD NVMe M.2 PCIe Gen4, M.2 2280 Internal Solid State Hard Drive, Seq. Read Speeds Up to 7,450 MB/s for High End Computing, Gaming, and Heavy Duty Workstations, MZ-V9P2T0B/AM
GPU x6: NVIDIA Tesla P40
Riser Cables (not sure if you need to know these but just in case): GLOTRENDS 600mm PCIe 3.0 X16 Riser Cable (0->180 Degree), Compatible with NVIDIA-RTX 2000/GTX1600 Series, AMD-RX6000/5000/500/400/Vega Series, etc.
 
I guess you are using the O/B G/C ASPEED AST2500 for install - but that should not be a problem AFAIK.

Try installing Debian.
 
Okay new update. I tried to reinstall Proxmox again to see if it would work and I get through the package installation part and almost got to the end and around 95% I get a new error. The code new error code is:
Code: 
command 'chroot /target dpkg --force-confold --configure -a' failed with exit code 1 at /usr/bin/proxinstall line 482.
Any ideas on how to what causes this?
 
gfngfn256 said:
I guess you are using the O/B G/C ASPEED AST2500 for install - but that should not be a problem AFAIK.

Try installing Debian.
Click to expand...
I tried to install Debian and it installed successfully. However, I did have to restart the install multiple times because it got hung up at different parts. I'm not sure if this is just a Debian thing or if this is an issue with my system.
 
Arctic said:
However, I did have to restart the install multiple times because it got hung up at different parts. I'm not sure if this is just a Debian thing or if this is an issue with my system.
Click to expand...
The install will reboot the machine; but I don't think that is a "Debian thing" to have to "restart the install" multiple times. Try stress testing that (working?) Debian install (all tests) for a few days - I'm pretty sure something is not right with your HW. In order the suspects are: RAM, Disk (could also be the controller or cooling), CPU (also cooling) & PSU.

Good luck.
 
  • Like
Reactions: Johannes S
So I tried to start to stress test in Debian and found out that my DNS wasn’t configured correctly even though the DNS settings were correct. Eventually I gave up and decided to install Windows to stress test it. I got though the installation and then after reboot it would boot, load, and then blue screen before loading in over and over and over. I’ve began to test hardware parts. Tomorrow I’m going to test RAM and PSU as we have had an issue with the PSU in the past.
 
Forgotten to mention cables & connections in my above post. They can sometimes also be the source of malfunctioning HW. So replacing, resetting, & reconnecting of all the parts can sometimes correct such failures.

One other thing, we neglected to give any attention to the NIC. Sometimes a bad NIC or a badly-connected one, can cause a complete system malfunction - maybe try reseating it, replacing it or changing its cables. May help.

In the end, it sometimes can also be the M/B. That is more difficult to replace.

Good luck.
 
So I tried to start to stress test in Debian and found out that my DNS wasn’t configured correctly even though the DNS settings were correct. Eventually I gave up and decided to install Windows to stress test it. I got though the installation and then after reboot it would boot, load, and then blue screen before loading in over and over and over. I’ve began to test hardware parts. Tomorrow I’m going to test RAM and PSU as we have had an issue with the
 
So I have tested the RAM and PSU. Both are good. I'm going to try and redo the thermal paste today but I think the CPU might be failing. For one loading into for example the Windows 10 installation takes about 2+ mins, usually it would take maybe 30 secs to a minute. Secondly when I had Proxmox installed and working there were multiple times a day where the node would become unresponsive and I would have to restart the server to fix it, but I just kind of ignored it as it wasn't a huge problem at the time. I'm going to try and find a test replacement CPU and I'll let you know how it goes.
 
  • Like
Reactions: gfngfn256
You must log in or register to reply here.
Top Bottom