Solved PCI bus error
-
@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.
-
-
Cloud computing is the future
-
@JaredBusch I'm assuming you already found this, but if not.
From Marcus
Boot into the RHEL4 rescue environment
chroot /mnt/sysimage
Edit /etc/modprobe.conf and change the scsi_hostadapter entries to look like this:alias scsi_hostadapter mptbase
alias scsi_hostadapter1 mptscsi
alias scsi_hostadapter2 mptfc
alias scsi_hostadapter3 mptspi
alias scsi_hostadapter4 mptsas
alias scsi_hostadapter5 mptscsihcd /boot
move the current initrd images to another folder or rename them to .old
run mkinitrd (example: mkinitrd -v -f initrd-2.6.9.-11.EL.img 2.6.9.-11.EL)
Repeat the above step for each kernel (in case you ever decide to boot into them later)
Exit the chroot environment
Try booting the VM -
@DustinB3403 if I did, I did not read far enough down.
Now I just need a way to get to rhel4 recovery mode.
-
@Pete-S said in PCI bus error:
@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.
It was not a Xeon, but I did try a physical restore also. With the same result.
