Cannot Install Proxmox on T610 Poweredge with H700 PERC card

Brodesps

New Member
May 30, 2026
6
1
3
Melbourne, Australia
Hi all,
Having trouble with installing Proxmox on a RAID-0 VD via my perc card (h700), every time I try and get started with the Install media, it keeps I/O erroring at the 3% Creating LVs screen. I need to install via the PERC as I can't use onboard SATA and the raid controller at the same time.
I have tried two different USBs, all ports on my T610, with no luck. I am on the latest firmware for my machine (6.6.0 BIOS) and downloaded a fresh Proxmox ISO 9.2-1 last night (29th May).
If anyone can help, very appreciated.

// DELL POWEREDGE T610
 
Last edited:
Welcome, @Brodesps
As a test, I would try to install some other Linux distribution - to check whether the issue is PVE related or rather a general one.
 
Are they Dell drives that are backing the PERC? IDRAC (even iDRAC6) should give you some idea if things are OK as Onslow suggested. Seems like there might be other problems with the HW.
 
There are multiple documented issues with modern Kernels (>6.2) with LSI based controllers on older (pre Haswell) platforms, stemming from bios mapping issues- older kernels were much more foregiving. You can try to shoehorn their firmware into memory by playing around with kernel cmd line (eg, pci=realloc, pci=realloc=off, pci=nommconf, etc) but when I ran into this issue I spent entirely too much time trying to "fix" it without success.

The answer from my perspective is if you MUST continue using such old hardware, stick to PVE7 (early versions of pve8 work too, but you would need to be judicious about pinning the old kernel.) yes its unsupported but it will work flawlessly.
 
yes its unsupported but it will work flawlessly.
"unsupported" is not just a random tag. It is an active risk. And this is true also for my homelab.

Did you notice there were NINE PVE-kernel releases (in "no-subscription") alone during this crazy May 2026? Guess how many you get for Version 7...

Obviously you're fine with that. Obviously I am not. You may know how to handle that special case. When you recommend that to a "New Member", without knowing anything about the knowledge-level of @Brodesps and the intended use case (commercial?) I need to mention the above and recommend: no, do not do that!
 
Last edited:
lets put things in perspective.

OP wants to run pve on a 15 year old server. it is clearly NOT for production use. what, exactly, do you suppose any such "risk" actually entails?! regardless of the NUMBER of kernels released since, NONE of them open up features relevant to ops use case, and many security fixed were backported. Not all and no further, but considering the use case I doubt thats an actual concern.
 
  • Like
Reactions: Brodesps
You and I do have a fundamental different point of view and we give different recommendations. I believe that is ok. Let the user decide :-)
 
You and I do have a fundamental different point of view and we give different recommendations. I believe that is ok. Let the user decide
Thats an observable fact :) but when you say
unsupported" is not just a random tag. It is an active risk.
I need to mention the above and recommend: no, do not do that!
It is explicitly a different message; I believe you come from a genuine place and want to help people- please expound on WHAT you feel is the risk is here. I think that would settle both your point and mine.
 
Hi all,
Having trouble with installing Proxmox on a RAID-0 VD via my perc card (h700), every time I try and get started with the Install media, it keeps I/O erroring at the 3% Creating LVs screen. I need to install via the PERC as I can't use onboard SATA and the raid controller at the same time.
I have tried two different USBs, all ports on my T610, with no luck. I am on the latest firmware for my machine (6.6.0 BIOS) and downloaded a fresh Proxmox ISO 9.2-1 last night (29th May).
If anyone can help, very appreciated.
I'm not sure this will help at all, but I had ALL kinds of trouble trying to set up a Dell R720. I ended up purchasing an SSD and a CD style mounting bracket, then removing the CD rom and putting the SSD in that slot, using the CD rom connection, to create a bootable drive, THEN I had to get into the BIOS of the H710 (in my case, not H700) and as I recall (sorry, it's been a long time) and I THINK I had to change them over to IT mode. Wish I could remember more, but I did spend days/weeks on this now and then before I got it. It's been running ProxMox now for many months just great!
 
  • Like
Reactions: Brodesps
Welcome, @Brodesps
As a test, I would try to install some other Linux distribution - to check whether the issue is PVE related or rather a general one.
Hi Onslow, thanks for getting back to me. I can confirm for the time being that Windows Server 2012 works (seeing how file sharing is working as of today), will try to install Fedora or Linux Mint as a test now. (8 minutes until USB creation finished)
 
Last edited:
Are they Dell drives that are backing the PERC? IDRAC (even iDRAC6) should give you some idea if things are OK as Onslow suggested. Seems like there might be other problems with the HW.
fyi DELL POWEREDGE T610
The drives are not all DELL firmware enabled, I have one of four drives that are DELL and the rest are WD Red Nasware drives. They were all able to be wiped with zeros by shredOS before being decommissioned. I currently have my DELL fw drive working as a storage pool via Win Server 2012 as a test. Haven't tried the other 3 drives in raid-5 thru win server 2012 yet.
The boot drive (WD green 240gb ssd) seems to run fine as long as the OS is bios along with use of PERC.
I can't see RAID/PERC settings in my iDRAC, the administrator of the server that passed it along thought that was strange and said "it must not be connected to the system", despite the system itself being able to boot to the PERC.
 
Last edited:
There are multiple documented issues with modern Kernels (>6.2) with LSI based controllers on older (pre Haswell) platforms, stemming from bios mapping issues- older kernels were much more foregiving. You can try to shoehorn their firmware into memory by playing around with kernel cmd line (eg, pci=realloc, pci=realloc=off, pci=nommconf, etc) but when I ran into this issue I spent entirely too much time trying to "fix" it without success.

The answer from my perspective is if you MUST continue using such old hardware, stick to PVE7 (early versions of pve8 work too, but you would need to be judicious about pinning the old kernel.) yes its unsupported but it will work flawlessly.
I'll do more research for this, and if I must use a older version then such must be done. This server isn't seeing the light of day anyway (staying connected to a local network with no outside passthrough).
 
"unsupported" is not just a random tag. It is an active risk. And this is true also for my homelab.

Did you notice there were NINE PVE-kernel releases (in "no-subscription") alone during this crazy May 2026? Guess how many you get for Version 7...

Obviously you're fine with that. Obviously I am not. You may know how to handle that special case. When you recommend that to a "New Member", without knowing anything about the knowledge-level of @Brodesps and the intended use case (commercial?) I need to mention the above and recommend: no, do not do that!
This server (DELL POWEREDGE T610) came from my high school, the leaving administrator passed it on to me as a testing platform to enhance my exposure and to get my foot through the door into IT administration. I spent two weeks learning from him before he left of Friday arvo. It's never going to see the light of day (completely locked into an local internet situation, no outside connectivity).
If an older version is needed to be used, then it can be a good experience to see what differences there are and how to solve future issues. That's what makes a good IT manager.
 
Last edited:
  • Like
Reactions: UdoB
Welcome, @Brodesps
As a test, I would try to install some other Linux distribution - to check whether the issue is PVE related or rather a general one.
@Onslow Update on your message, It seems that it doesn't want to install Linux Mint, error code 127: ubi-console-setup failed, cannot install.
Trying Fedora now.
UPDATE:
Linux Mint - Does not Work
Fedora - Installs perfectly on RAID Virtual Drive
Proxmox - Somehow works if I install on a drive from another machine?
Will try to install proxmox 9.2 again.
 
Last edited: