Rollback an upgrade? Hardware not supported...

General support questions including new installations
pYr8
Posts: 13
Joined: 2011/12/27 15:24:47
Location: Texas

Rollback an upgrade? Hardware not supported...

Post by pYr8 » 2011/12/27 17:36:28

Hello All-

First time here. I've searched all over but not found a solid resolution to my problem. I think I've created a fairly unique mess.

The question: Can I roll back from CentOS 4 to CentOS 3.9?

The story:
I am looking to rollback an upgrade I'm in the middle of. I am working remotely, upgrading has been rpm/yum based. It's been a solid little samba server for 8 years but Windows 7 workstations are coming and I needed newer samba. In hindsight, I should have looked at a strait samba upgrade.

The machine has an old CERC ATA100 controller in it and I neglected to research that before attempting the upgrade to CentOS 4 (2.6.9-103.EL kernel). I had upgraded from RH9 to CentOS 3.9 successfully and was taking the next step.

I haven't rebooted because I first found no bootloader with dd if=/dev/sda bs=512 count=1 2>&1 method.

I had to remove the 2.4 kernel from the rpm db to get the 2.6 installed but all files are still there. I have overwritten the existing redhat-release with the centos-release rpm as well.

I'm feeling rather stupid as this is their production PDC and there is no BDC. I hope there is light at the end of the tunnel...

Thanks
Karl

User avatar
TrevorH
Forum Moderator
Posts: 29932
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Rollback an upgrade? Hardware not supported...

Post by TrevorH » 2011/12/27 18:53:37

I'm not sure what the point of a CentOS 3 -> 4 upgrade is at this point! CentOS 4 has about 3 months of life left before it hits the scrapheap. If you intend to upgrade then CentOS 5 or 6 would be a better bet. I'm not even sure what a CERC controller is but it sounds like some nasty FakeRAID controller so you might want to look at replacing it or doing a parallel install on a different machine and migrating any data you require to it.

I am pretty sure that the Samba that comes with CentOS 4 does not support Windows 7 clients - you need the non-standard samba3x-* packages in CentOS 5 for that or the ordinary version from CentOS 6.

pYr8
Posts: 13
Joined: 2011/12/27 15:24:47
Location: Texas

Re: Rollback an upgrade? Hardware not supported...

Post by pYr8 » 2011/12/27 19:03:53

[quote]
TrevorH wrote:
I'm not sure what the point of a CentOS 3 -> 4 upgrade is at this point! CentOS 4 has about 3 months of life left before it hits the scrapheap. If you intend to upgrade then CentOS 5 or 6 would be a better bet. I'm not even sure what a CERC controller is but it sounds like some nasty FakeRAID controller so you might want to look at replacing it or doing a parallel install on a different machine and migrating any data you require to it.

I am pretty sure that the Samba that comes with CentOS 4 does not support Windows 7 clients - you need the non-standard samba3x-* packages in CentOS 5 for that or the ordinary version from CentOS 6.[/quote]

I was taking baby steps on the upgrade, was planning on finishing on 5 or 6...
That controller is an old LSI board, real raid but real outdated.
Right now I'm just looking to roll back & get things fairly stable until I get a new machine ordered for them.
Any thought on the downgrade?

pYr8
Posts: 13
Joined: 2011/12/27 15:24:47
Location: Texas

Re: Rollback an upgrade? Hardware not supported...

Post by pYr8 » 2011/12/27 20:34:56

What if I were to go through the CentOS 3 process again, with removing the 2.6.9 kernel from the rpm db? I'm really just looking for a short term fix until I get new hardware in place. Right now if it were to go down due to power outage or similar they'd be dead in the water....

Thanks for any ideas that may come up.
Karl

User avatar
TrevorH
Forum Moderator
Posts: 29932
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Rollback an upgrade? Hardware not supported...

Post by TrevorH » 2011/12/28 00:50:26

[quote]
I had to remove the 2.4 kernel from the rpm db to get the 2.6 installed but all files are still there.
[/quote]

Doesn't this mean that you have the two files referred to in /boot/grub/grub.conf stilll in place and ready to be used at reboot? As long as you also have the /lib/modules/`uname -r` directory in place then you shouldn't have a problem rebooting at least to the kernel itself. The old initrd file should contain all the drivers from /lib/modules/`uname -r` that are required to initialise all the bits of hardware that are fundamental to the boot process. Of course the problem is that you only have one chance at this so you need to make sure it's right.

Can you post the output from

[code]
/sbin/lspci -nn
[/code]

and I'll have a check and see if I can work out if there is support for that controller in newer versions.

pYr8
Posts: 13
Joined: 2011/12/27 15:24:47
Location: Texas

Re: Rollback an upgrade? Hardware not supported...

Post by pYr8 » 2011/12/28 16:37:43

Hi Trevor-

The box was using LILO for RH9 & C3 and the edits are easy enough there. I like GRUB but don't think changing is in the picture while mounted...
I do have all the kernel files, I did a rpm -ql to create a list for those.
In rechecking my notes I also had to remove syslinux & mkbootdisk from the rpm db but retained the files and have lists for those as well.
One thing that concerned me was not having any bootloader referenced when I checked with dd.
There are still 2.4 kernel files & links in /boot as well:
config-2.4.21-63.EL
initrd-2.4.21-63.EL.img
module-info -> module-info-2.4.20-31.9 ( from hr9... still referenced ??? )
System.map -> System.map-2.4.21-63.EL
System.map-2.4.21-63.EL
vmlinux-2.4.21-63.EL
vmlinuz -> vmlinuz-2.4.20-31.9
vmlinuz-2.4.21-63.EL

The 2.4 kernel is only referenced in /boot as:
config-2.6.9-103.EL
symvers-2.6.9-103.EL.gz
System.map-2.6.9-103.EL
vmlinuz-2.6.9-103.EL

Here's the lspci output, 02:01.0 is the controller
02:01.0 "RAID bus controller" "American Megatrends Inc." "MegaRAID" -r02 "Dell" "PowerEdge Cost Effective RAID Controller ATA100/4Ch"

00:00.0 Class 0600: 8086:2578 (rev 02)
00:01.0 Class 0604: 8086:2579 (rev 02)
00:1d.0 Class 0c03: 8086:24d2 (rev 02)
00:1d.1 Class 0c03: 8086:24d4 (rev 02)
00:1d.2 Class 0c03: 8086:24d7 (rev 02)
00:1d.3 Class 0c03: 8086:24de (rev 02)
00:1d.7 Class 0c03: 8086:24dd (rev 02)
00:1e.0 Class 0604: 8086:244e (rev c2)
00:1f.0 Class 0601: 8086:24d0 (rev 02)
00:1f.1 Class 0101: 8086:24db (rev 02)
00:1f.2 Class 0101: 8086:24d1 (rev 02)
00:1f.3 Class 0c05: 8086:24d3 (rev 02)
00:1f.5 Class 0401: 8086:24d5 (rev 02)
02:00.0 Class 0300: 1002:4752 (rev 27)
02:01.0 Class 0104: 101e:1960 (rev 02)
02:0c.0 Class 0200: 8086:100e (rev 02)

Thanks much, back's up against the wall on this one :-o
Karl

pschaff
Retired Moderator
Posts: 18276
Joined: 2006/12/13 20:15:34
Location: Tidewater, Virginia, North America
Contact:

Rollback an upgrade? Hardware not supported...

Post by pschaff » 2011/12/28 16:56:35

That controller is supported by CentOS-6:[code]
$ grep -i 101e /lib/modules/*/modules.alias | grep -i 1960
/lib/modules/2.6.32-131.12.1.el6.x86_64/modules.alias:alias pci:v0000101Ed00001960sv*sd*bc*sc*i* megaraid_mbox
/lib/modules/2.6.32-131.17.1.el6.x86_64/modules.alias:alias pci:v0000101Ed00001960sv*sd*bc*sc*i* megaraid_mbox
/lib/modules/2.6.32-131.21.1.el6.x86_64/modules.alias:alias pci:v0000101Ed00001960sv*sd*bc*sc*i* megaraid_mbox
[/code]

Do note that upgrades across major versions are [b]never[/b] supported by either CentOS or [url=http://wiki.centos.org/FAQ/General?highlight=%28TUV%29#head-d29a2b7e61ffc544973098f9dd49fe4663efba50]TUV[/url]. A backup and fresh install is the only supported and recommend path to a stable and reliable system. Trying to upgrade from a 2.4 kernel and much older glibc from 3.x to 4.x to 5.x to 6.x is not likely to be other than an exercise if frustration.

pYr8
Posts: 13
Joined: 2011/12/27 15:24:47
Location: Texas

Re: Rollback an upgrade? Hardware not supported...

Post by pYr8 » 2011/12/28 17:47:20

[quote]
pschaff wrote:
That controller is supported by CentOS-6:[code]
$ grep -i 101e /lib/modules/*/modules.alias | grep -i 1960
/lib/modules/2.6.32-131.12.1.el6.x86_64/modules.alias:alias pci:v0000101Ed00001960sv*sd*bc*sc*i* megaraid_mbox
/lib/modules/2.6.32-131.17.1.el6.x86_64/modules.alias:alias pci:v0000101Ed00001960sv*sd*bc*sc*i* megaraid_mbox
/lib/modules/2.6.32-131.21.1.el6.x86_64/modules.alias:alias pci:v0000101Ed00001960sv*sd*bc*sc*i* megaraid_mbox
[/code]

Do note that upgrades across major versions are [b]never[/b] supported by either CentOS or [url=http://wiki.centos.org/FAQ/General?highlight=%28TUV%29#head-d29a2b7e61ffc544973098f9dd49fe4663efba50]TUV[/url]. A backup and fresh install is the only supported and recommend path to a stable and reliable system. Trying to upgrade from a 2.4 kernel and much older glibc from 3.x to 4.x to 5.x to 6.x is not likely to be other than an exercise if frustration.[/quote]

Indeed, at this point I'm looking to go no further. It's an exercise in futility!!
A rollback to 3 would be great until I get a new server delivered to the client and pull off a swap over a weekend with some remote hands...

pYr8
Posts: 13
Joined: 2011/12/27 15:24:47
Location: Texas

Re: Rollback an upgrade? Hardware not supported...

Post by pYr8 » 2011/12/28 21:04:33

Another note, it looks like the LVM version is from RHEL4 and the pair of drives are mirrored under that CERC card. This may account for not seeing the drives in /dev...
I'm still running on the RHEL3 kernel so if I were to roll back much of the rpms, including LVM would that be heading in the right direction?
If I could get this stabilized and install samba from sernet that would buy me time to get a new box configured with CentOS 6 / current SAMBA & shipping out to the client...

Thanks

pschaff
Retired Moderator
Posts: 18276
Joined: 2006/12/13 20:15:34
Location: Tidewater, Virginia, North America
Contact:

Re: Rollback an upgrade? Hardware not supported...

Post by pschaff » 2011/12/28 22:14:05

It's not clear to me where you are in this process, but if still trying to get back to a working 3.9, then yes - all relevant packages need to be latest 3.X versions. Anything replaced in the attempt to upgrade should be reverted, or at least anything that impacts the functionality you need.

Post Reply

Return to “CentOS 4 - General Support”