Solved 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.
-
@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.
-
@JaredBusch said in PCI bus error:
@DustinB3403 if I did, I did not read far enough down.
Now I just need a way to get to rhel4 recovery mode.
This may help http://ftp.redhat.com/pub/redhat/linux/enterprise/4/en/RHAPS2/i386/isos/
-
@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 1CCB came back with this.
-
New servers arrived today.
My office is warmer now.
-
Awesome mounting solution
-
What OS will you be installing?
-
@hobbit666 said in PCI bus error:
What OS will you be installing?
Proxmox or raw KVM on Fedora if Proxmox gets too annoying.
-
@JaredBusch said in PCI bus error:
Awesome mounting solution
Servers off the floor?
Servers Not lying in liquid
Servers Have Power
Mounting apparatus made of
something other than cardboardLooks good to me!
-
@JaredBusch said in PCI bus error:
@hobbit666 said in PCI bus error:
What OS will you be installing?
Proxmox or raw KVM on Fedora if Proxmox gets too annoying.
Annoying in what way?
-
@dafyre said in PCI bus error:
Servers off the floor?
Servers Not lying in liquid
Servers Have Power
Mounting apparatus made of
something other than cardboardServer rack made of metal and capable of being grounded
-
@DustinB3403 said in PCI bus error:
@JaredBusch said in PCI bus error:
@hobbit666 said in PCI bus error:
What OS will you be installing?
Proxmox or raw KVM on Fedora if Proxmox gets too annoying.
Annoying in what way?
Like only being able to do some things if ZFS is used.
-
@JaredBusch said in PCI bus error:
@DustinB3403 said in PCI bus error:
@JaredBusch said in PCI bus error:
@hobbit666 said in PCI bus error:
What OS will you be installing?
Proxmox or raw KVM on Fedora if Proxmox gets too annoying.
Annoying in what way?
Like only being able to do some things if ZFS is used.
Gotcha
