[Tobiasly]

OK, I'm starting to get honked off at this thing. This upgrade that was supposed to take a few hours to get at least a blank but workable state is now taking days. Not that I didn't expect that to happen...

My first problem came with my RAID drives. I have 3 SCSI drives, partitioned identically. The / and /boot partitions are RAID 1 (2 + 1 spare), and most everything else is RAID 5. So when I went into 8.0 setup, I told it to keep the partitions, but reformat them and start over (I never ever simply "upgrade" an OS).

Well, at some point a while back, my /dev/sda had a brain fart and the RAID switched it off like it should have (I think the cable was loose and got bumped or something). I thought I added it back in though, but apparently not on the /boot partition -- it was still using just /dev/sdb and sdc. So apparently Disk Druid, when installing 8.0, noticed that sda wasn't being used in the corresponding "md" device, and left it that way. I told it to use all three drives, but I think it decided /dev/sda should be the spare insead of sdc.

Not that big a problem, except that it loaded the boot loader onto the /dev/sda device (the actual BIOS boot device that corresponded to the md /boot mount point), but wrote the GRUB files to the "md" device, which had /dev/sda removed! In a RAID 1 array, every drive gets the same image, but /dev/sda didn't get the image the installer thought it would, since it was removed.

So, after installing, I reboot the system and see all my old GRUB configs! It took me a good several hours to figure that one out. I mounted each of the RAID 1 member drives separately, figured out what was going on, and attempted to hot-add sda back in. But /proc/mdstat didn't show it being resynced, and the new files weren't copied over, so I simply copied them over myself. Mistake -- I guess the new GRUB files weren't on the same sector, because then the system wouldn't even boot.

So, I bit the bullet, quit being a GUI wuss, used fdisk to delete those fucking partitions and set 'em up the right way, and drove on. I don't like how Disk Druid wants to move your partitions around and rename them and shit anyway. I have those partitions in a particular physical order for a reason, thank you very much.

Now, the next prob. I have two ethernet cards -- eth0 connects to my home LAN, and eth1 connects to my cable modem. Forget that multi-homed shit. eth1 is getting configured through DHCP just fine, but I can't get to anything external -- no web, no pings, nothing. When I try to ping the DNS servers I'm assigned, it times out. The problem is with this box, 'cause it works fine when I hook the cable modem up to another box (I get the same DNS servers and everything). I can't resolve any hostnames either -- even if I specify which DNS server to use with "dig". resolv.conf looks fine.

So I read the ping man page, and saw a "-I" parameter where you can specify which device you want to ping <I>from</I>. So I did a "ping -I /dev/eth1 xxx.yyy..." and it worked. So it appears that the problem is, that the box doesn't know that it should use eth1 for external stuff and eth0 for internal. I don't know how it knew that before, but it used to work. I have a sneaking suspicion it has something to do with the fact that Red Hat replaced the previous "pump" DHCP client with "dhclient", and it's not setting some parameter correctly.

Any ideas on this one?