LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Fedora (http://www.linuxquestions.org/questions/fedora-35/)
-   -   FC5 upgrade to one FC4 on multi-boot system killed the others (http://www.linuxquestions.org/questions/fedora-35/fc5-upgrade-to-one-fc4-on-multi-boot-system-killed-the-others-427134/)

PTrenholme 03-21-2006 11:15 PM

FC5 upgrade to one FC4 on multi-boot system killed the others
 
I use a single boot partition for two FC4 installations (and several other systems). So I used the "upgrade" option on the DVD, specifying one of the two FC4 systems to be upgraded, and selected the "update GRUB" option when it was offered.

When the install finished, I discovered that all references to the unmodified FC4 installation had been removed from grub.conf, and, when I looked at the /boot partition, I discovered that the files needed to boot the FC4 installation had been removed from /boot. :cry:

O.K., I had a fairly recent backup of /boot so I thought I'd just replace the deleted files from it. That worked :), but the backup was made before the last kernel upgrade (to 1.1833 from 1.1831).

Now here's the part I don't understand: :scratch: I booted to the FC4 system, using the older 2.6.15-1.1831 kernel, removed the 1.1833 kernel, and ran a yum upgrade. I got the following error:
Code:

Running Transaction
  Installing: kernel-smp                  ######################### [1/1]
error: unpacking of archive failed on file /boot/System.map-2.6.15-1.1833_FC4smp;4420c1aa: cpio: open

It's not a space issue:
Code:

# df /boot
Filesystem          1K-blocks      Used Available Use% Mounted on
/dev/hdb2              101105    24980    70904  27% /boot

And the file isn't already in the /boot directory:
Code:

# ls -l /boot
total 15539
-rw-r--r--  1 root root  61558 Mar 21 18:56 config-2.6.15-1.1831_FC4smp
-rw-r--r--  1 root root  63847 Mar 14 14:19 config-2.6.15-1.2054_FC5smp
drwxr-xr-x  2 root root    1024 Mar 21 18:59 grub
drwxr-xr-x  10 root root    1024 Mar 13 14:59 init-1.1833
-rw-r--r--  1 root root 3645952 Mar 13 15:01 initrd-1.1833
-rw-r--r--  1 root root 1692048 Mar 13 15:02 initrd-1.1833.img
-rw-r--r--  1 root root 1691370 Mar 21 18:57 initrd-2.6.15-1.1831_FC4smp.img
-rw-r--r--  1 root root 1823569 Mar 21 07:15 initrd-2.6.15-1.2054_FC5smp.img
drwx------  2 root root  12288 Feb 23 10:03 lost+found
-rw-r--r--  1 root root  14336 Mar 11 11:52 memdisk.bin
-rw-r--r--  1 root root  94600 Feb  8 08:39 memtest86+-1.65
-rw-r--r--  1 root root  110592 Mar 11 11:53 sbootmgr.dsk
-rw-r--r--  1 root root  850103 Mar 21 18:58 System.map-2.6.15-1.1831_FC4smp
-rw-r--r--  1 root root  831559 Mar 14 14:19 System.map-2.6.15-1.2054_FC5smp
-rw-r--r--  1 root root 1692843 Mar 13 14:39 testinit.img
-rw-r--r--  1 root root 1657075 Mar 21 19:17 vmlinuz-2.6.15-1.1831_FC4smp
-rw-r--r--  1 root root 1564844 Mar 14 14:19 vmlinuz-2.6.15-1.2054_FC5smp

(If you're interested, the 1.1833 stuff in the above list is there because I needed to modify the "stock" initial ram disk so I could use a different logical volume for each FC4 installation.)

And I deleted the rpm file from the cache an downloaded a fresh copy, so its not a corrupted rpm.

So, does anyone have a clue? (This isn't an urgent problem -- 2.6.15-1.1831 works was well as 1.1833 for me. But I'd like to know why there's the problem getting the newer kernel to reinstall.)

And I thought I'd warn anyone running more that one FC4 system off the same /boot partition to create a backup before upgrading.


All times are GMT -5. The time now is 01:25 AM.