Solved PCI bus error
-
@JaredBusch said in PCI bus error:
So the customer asked me to spec out a replacement server.
This is what I am thinking to recommend.
Dell PowerEdge R6515 – Chassis with 8x 2.5” drives AMD EPYC 7262 or 7302P 1x 16gb RDIMM 3200MT PERC H730P 3x 480GB SSD SATA Mix Use Hot plug Dual hot plug power supply Riser Config 1 1x16LP PCIe slot iDRAC 9 Express BOSS controller card with 2 M.2 240GB RAID 1Comments?
Yeah, I assume this is a low budget spec.
Pick the cheapest epyc rome unless you expect the server to handle lots more in the future. 7232P is the cheapest.
Also skip the BOSS card and pick 2x960GB read-intensive drives in RAID 1. Since you have the H730P RAID1 and it's cache, RAID1 should be more than fine.I mean comparing to the old machine you could also use the H330 card. You don't get the cache but the SSDs have cache and RAID1/10 doesn't require any parity calculations so the H330 will get the job done.
-
@Dashrender said in PCI bus error:
@JaredBusch said in PCI bus error:
So the customer asked me to spec out a replacement server.
This is what I am thinking to recommend.
Dell PowerEdge R6515 – Chassis with 8x 2.5” drives AMD EPYC 7262 or 7302P 1x 16gb RDIMM 3200MT PERC H730P 3x 480GB SSD SATA Mix Use Hot plug Dual hot plug power supply Riser Config 1 1x16LP PCIe slot iDRAC 9 Express BOSS controller card with 2 M.2 240GB RAID 1Comments?
Does iDRAC 9 Express allow remote access to the console?
I don't think so. You can only do power cycling with Express.
-
@Dashrender said in PCI bus error:
Does iDRAC 9 Express allow remote access to the console?
Forgot to change that. I just copy/pasted form the dell build screen.
-
@Pete-S said in PCI bus error:
Yeah, I assume this is a low budget spec.
Pick the cheapest epyc rome unless you expect the server to handle lots more in the future. 7232P is the cheapest.Budget is not an issue. But it does not need anything bigger.
The two specified, were the smallest two on Dell's website.
-
So restored the backup from 2012 onto a Proxmox VM on my laptop.
Damnit...
I know this backup set is good as I did it in 2012. At the time on VMWare 5. I have also restore to physical in 2015.
-
@JaredBusch do you routinely expect 8 year old backups to operate on today's hypervisors?
-
Pages 3 and 4 of this PDF list what iDrac offers for the different versions. Virtual Console is not included with iDrac Express
-
@DustinB3403 said in PCI bus error:
@JaredBusch do you routinely expect 8 year old backups to operate on today's hypervisors?
Routinely? No. I don't do that routinely. But yes, it should work.
The OS hasn't changed, and the backup I am restoring is the OS.
Data backups run nightly. -
@DustinB3403 said in PCI bus error:
Pages 3 and 4 of this PDF list what iDrac offers for the different versions. Virtual Console is not included with iDrac Express
I know. I would never buy without console. Just forgot to change the option.
-
@JaredBusch said in PCI bus error:
No. I don't do that routinely. But yes, it should work.
Well I ask, because you said this backup setup was made on VMWare 5 (assuming ESXi 5) which the drivers for that are incredibly out of date and likely has no workable path for the virtual hardware on the hypervisor you're trying on today.
It may make more sense (albeit more time) to try and restore this to ESXi 7, and take a new backup rather than relying on such an old rset, ensuring that you update drivers where-ever possible.
-
@JaredBusch Sorry, that was for @Pete-S who was uncertain.
-
@DustinB3403 said in PCI bus error:
Well I ask, because you said this backup setup was made on VMWare 5
I restored to that at the time as a test. I did not backup to that.
-
@JaredBusch said in PCI bus error:
@DustinB3403 said in PCI bus error:
Well I ask, because you said this backup setup was made on VMWare 5
I restored to that at the time as a test. I did not backup to that.
What did you backup from?
-
@DustinB3403 said in PCI bus error:
@JaredBusch said in PCI bus error:
@DustinB3403 said in PCI bus error:
Well I ask, because you said this backup setup was made on VMWare 5
I restored to that at the time as a test. I did not backup to that.
What did you backup from?
The physical server. You shut it down and boot to a CD/USB with their specific DR process.
-
Tried to make a new one today. Just because.
That did not work out so well
-
@JaredBusch said in PCI bus error:
@Pete-S said in PCI bus error:
Yeah, I assume this is a low budget spec.
Pick the cheapest epyc rome unless you expect the server to handle lots more in the future. 7232P is the cheapest.Budget is not an issue. But it does not need anything bigger.
The two specified, were the smallest two on Dell's website.Then you have another dell.com than I have.
Not a big difference however.
-
@Pete-S said in PCI bus error:
@JaredBusch said in PCI bus error:
@Pete-S said in PCI bus error:
Yeah, I assume this is a low budget spec.
Pick the cheapest epyc rome unless you expect the server to handle lots more in the future. 7232P is the cheapest.Budget is not an issue. But it does not need anything bigger.
The two specified, were the smallest two on Dell's website.Then you have another dell.com than I have.
Not a big difference however.
Might be because of the form factor. I didn’t look hard at options.
-
so this... any ideas how to go forward? Google and I are not getting along good enough to find an answer apparently.
-
@JaredBusch said in PCI bus error:
so this... any ideas how to go forward? Google and I are not getting along good enough to find an answer apparently.
I often see kernel panic when trying to put an an old image on a new virtualization platform or moving images from one virtual to another virtual platform. I don't know if it's because they remove driver support for old hardware when they compile the kernel or what.
I get around it by using virtualbox instead which seems to have infinitely better support for legacy systems. But my use case has often been to spin up an old image backup and see how it works or look for something. Not run it like it is in a production environment.
-
@Pete-S said in PCI bus error:
@JaredBusch said in PCI bus error:
so this... any ideas how to go forward? Google and I are not getting along good enough to find an answer apparently.
I often see kernel panic when trying to put an an old image on a new virtualization platform or moving images from one virtual to another virtual platform. I don't know if it's because they remove driver support for old hardware when they compile the kernel or what.
I get around it by using virtualbox instead which seems to have infinitely better support for legacy systems. But my use case has often been to spin up an old image backup and see how it works or look for something. Not run it like it is in a production environment.
Another option is to find old server hardware from the same era and just run it there. And then throw it all away when you're done with whatever it is you are doing. It just have to be really worth the trouble of dealing with old stuff and usually it's not, but there are always exceptions.
