No hard disk found! Error Installing Proxmox

S

shf

New Member
Apr 15, 2025
4
0
1
Hello,

We are trying to install Proxmox 8.3 or 8.4, and it said, "No hard disk found! - The installer could not find the supported hard drive."

We are using Dell R620 server, the point is that, we have installed ESXi host in this server previously and after that we installed Proxmox 8.3 without any issues. But due to some reason we need to remove it and install another OS. I am now trying to install Proxmox 8.3 or 8.4 again - but it is stuck at No hard disk found! even after destroying the RAID. Sometimes it passes the initial steps but stuck at 'cleaning up the root disk' during the installation. It is happening with Proxmox 8.3 or 8.4 only - as I installed Proxmox 7.4 without any issues in the same server with same configuration.

The specs of the server (Dell R620) is given below

4 hard drives on RAID10, making up 1675 GB
BIOS Version: 2.5.2
RAID Controller: PERC H310 Mini
RAID Firmware Version: 20.13.3-0001
iDRAC Setting: 1.65.65.04
iDRAC Firmware: 2.21.21 (build 12)
BIOS Mode Set to 'BIOS'

Please suggest the solution as we are completely frustrated installing Proxmox again and again but there is no way!
 
Ctrl+Alt+F2 details attached
 

Attachments

  • ctrlaltf2 details.jpeg
    ctrlaltf2 details.jpeg
    102.9 KB · Views: 27
Getting an error again after recreating RAID and initialize it completely, installation stuck at 'Creating lvs', error: Unable to partition /dev/sdb
 

Attachments

  • unable to partition dev-sdb.jpeg
    unable to partition dev-sdb.jpeg
    128.7 KB · Views: 15
i have similar issue, proxmox can't detect the VD, any one that can recommend a solution.
 
boot the installer in debug mode, and then after the install has failed, retrieve "dmesg" and "lsblk" output and the installer log files from /tmp and attach them here..
 
  • Like
Reactions: news
@fabian sorry for the delay, please see below. just to add, i was able to install proxmox on this same box but after installation and doing some initial setup i encounter hang, specially when configuring the addition disk space. so i would restart the installation.

this is the content of the /tmp forlder after installation, attached is the dmesg output

TIA

root@pve2itsm:/tmp#

root@pve2itsm:/tmp# pwd
/tmp
root@pve2itsm:/tmp# ls -lt
total 8
drwx------ 3 root root 4096 May 27 09:45 systemd-private-a2bf8e3f8b5e4d56989d5e97a51e62d4-chrony.service-fPH2B4
drwx------ 3 root root 4096 May 27 09:45 systemd-private-a2bf8e3f8b5e4d56989d5e97a51e62d4-systemd-logind.service-Xwlyt2
root@pve2itsm:/tmp# cd systemd-private-a2bf8e3f8b5e4d56989d5e97a51e62d4-chrony.service-fPH2B4
root@pve2itsm:/tmp/systemd-private-a2bf8e3f8b5e4d56989d5e97a51e62d4-chrony.service-fPH2B4# ls -lt
total 4
drwxrwxrwt 2 root root 4096 May 27 09:45 tmp
root@pve2itsm:/tmp/systemd-private-a2bf8e3f8b5e4d56989d5e97a51e62d4-chrony.service-fPH2B4# cd tmp/
root@pve2itsm:/tmp/systemd-private-a2bf8e3f8b5e4d56989d5e97a51e62d4-chrony.service-fPH2B4/tmp# ls -lt
total 0
root@pve2itsm:/tmp/systemd-private-a2bf8e3f8b5e4d56989d5e97a51e62d4-chrony.service-fPH2B4/tmp#
root@pve2itsm:/tmp/systemd-private-a2bf8e3f8b5e4d56989d5e97a51e62d4-chrony.service-fPH2B4/tmp#
root@pve2itsm:/tmp/systemd-private-a2bf8e3f8b5e4d56989d5e97a51e62d4-chrony.service-fPH2B4/tmp#
root@pve2itsm:/tmp/systemd-private-a2bf8e3f8b5e4d56989d5e97a51e62d4-chrony.service-fPH2B4/tmp# cd ../../systemd-private-a2bf8e3f8b5e4d56989d5e97a51e62d4-systemd-logind.service-Xwlyt2/
root@pve2itsm:/tmp/systemd-private-a2bf8e3f8b5e4d56989d5e97a51e62d4-systemd-logind.service-Xwlyt2# ls -lt
total 4
drwxrwxrwt 2 root root 4096 May 27 09:45 tmp
root@pve2itsm:/tmp/systemd-private-a2bf8e3f8b5e4d56989d5e97a51e62d4-systemd-logind.service-Xwlyt2# cd tmp/
root@pve2itsm:/tmp/systemd-private-a2bf8e3f8b5e4d56989d5e97a51e62d4-systemd-logind.service-Xwlyt2/tmp# ls -lt
total 0
root@pve2itsm:/tmp/systemd-private-a2bf8e3f8b5e4d56989d5e97a51e62d4-systemd-logind.service-Xwlyt2/tmp#
 

Attachments

I meant "dmesg" and "lsblk" and the installer log files in /tmp from the installer - if you start it in debug mode, you get dropped into a shell at various points, including after the (failed) installation before rebooting..
 
You must log in or register to reply here.
Top Bottom