Christian H. Toldnes wrote:
> > http://www.trustix.org/wiki/index.php/Swup#Enabling_kernel_upgrades > > in essence: > > - don't change grub.conf when using official kernels > - enable autoactivation of new kernels > - enable kernel upgrading via swup. > - use swup to upgrade your kernel, and reboot. > > Kind regards > > > c > > I had read that portion of the wiki before I did the upgrade, but I edited /etc/sysconfig/bootloader to change AUTOACTIVATE=yes *after* I "swup-ed" the new kernel. So, thinking that the order in which these steps are done is important, I did the following: I just removed the 2.4.31-6tr kernel with rpm, then swup-ed again to install it. Now, the links in /boot are correct. I have restored my grub.conf to original. I rebooted the machine using the default grub entry and uname -a shows: Linux saltydog 2.4.28-7tr #1 Sun Dec 19 01:04:25 CET 2004 i686 i686 i386 GNU/Linux /boot shows the following: vmlinuz -> vmlinuz-2.4.31-6tr vmlinuz.old -> vmlinuz-2.4.28-7tr Any other ideas? I am getting the feeling that I better look at my RAID-1 mirrors as the /boot partition is on /dev/md6 and I see the mirror set is marked as dirty, degraded as following: # mdadm --detail /dev/md6 /dev/md6: Version : 00.90.00 Creation Time : Wed Nov 9 11:37:53 2005 Raid Level : raid1 Array Size : 56128 (54.81 MiB 57.48 MB) Device Size : 56128 (54.81 MiB 57.48 MB) Raid Devices : 2 Total Devices : 1 Preferred Minor : 6 Persistence : Superblock is persistent Update Time : Thu Nov 10 17:06:16 2005 State : dirty, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 UUID : 11e322c5:e50a22cb:a500e1dc:b7e1a5d2 Events : 0.39 Number Major Minor RaidDevice State 0 0 0 0 faulty removed 1 22 65 1 active sync /dev/hdd1 Regards, Bruce _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
