[Cooker] 9.0b4 upgrade from 8.2
I've downloaded and burned the ISOs for 9.2b4, and run an upgrade install against my 8.2 setup, but during teh setup process both the bootloader and bootdisk sections failed. It seems to have failed to run mkinitd, as looking in /boot now there are no files for the 2.4.19 kernel. Needless to say the machine doesn't boot now. Any suggestions on how to bypass mkinitrd manually through rescue? cheers guys daniel vincent
Re: [Cooker] 9.0b4 upgrade from 8.2
On Sun, 25 Aug 2002 12:00:32 +0100 [EMAIL PROTECTED] wrote: It seems to have failed to run mkinitd, as looking in /boot now there are no files for the 2.4.19 kernel. Needless to say the machine doesn't boot now. should still be able to boot with your 8.2 kernel or floppy. I ran into the same upgrading 2 slightly behind cooker systems to B4. The 2.4.19-5 kernel is installed but no initrd image is created and the 2.4.19-5 entry in lilo.conf is filled with garbage such as the ram disk size in the append line. For me the simplest way to fix the problem was to boot the system with an old kernel. Delete the 2.4.19-5 entry in lilo.conf. rpm -e kernel-2.4.19-5 Manually install the kernel-2.4.19-5 from cd1 (an initrd image Is created) Run lilo Edit lilo.conf, making 2419-5 the default. Reboot system. 2419-5 now boots happily. Charles
Re: [Cooker] 9.0b4 upgrade from 8.2
On Sunday 25 August 2002 07:57, Charles A Edwards wrote: On Sun, 25 Aug 2002 12:00:32 +0100 [EMAIL PROTECTED] wrote: It seems to have failed to run mkinitd, as looking in /boot now there are no files for the 2.4.19 kernel. Needless to say the machine doesn't boot now. should still be able to boot with your 8.2 kernel or floppy. I ran into the same upgrading 2 slightly behind cooker systems to B4. The 2.4.19-5 kernel is installed but no initrd image is created and the 2.4.19-5 entry in lilo.conf is filled with garbage such as the ram disk size in the append line. I encountered the problem about a week ago, updating sevral packages on a cooker only machine that is normally kept up-to-date. My hypothesis is that when devfsd is upgraded, bad things happen with the dev-fs such that a re-boot is needed to load the new devfsd to set things strait. When the mikinitrd failed, it reported that there were no available loop devices, so I booted a rescue image, and had no problem re-installing the most recent kernel, mkinitrd and all. Has there been any indication as to why/where the mkinitrd step of the kernel upgrade was failing in other cases? Since they were going from re-booted/shut-down systems, I would not expect the devfs problem to be the cause since I was upgrading a running machine. -Chuck -- +-% He's a real UNIX Man $-+-+ \ Sitting in his UNIX LAN \ Charles A. Shirley \ \ Making all his UNIX plans \ cashirley (at) comcast (dot) net \ +--# For nobody @--+-+
Re: [Cooker] 9.0b4 upgrade from 8.2
On Sun, 25 Aug 2002 08:19:39 -0400 Chuck Shirley [EMAIL PROTECTED] wrote: I encountered the problem about a week ago, updating sevral packages on a cooker only machine that is normally kept up-to-date. My hypothesis is that when devfsd is upgraded, bad things happen with the dev-fs such that a re-boot is needed to load the new devfsd to set things strait. When the mikinitrd failed, it reported that there were no available loop devices, so I booted a rescue image, and had no problem re-installing the most recent kernel, mkinitrd and all. Has there been any indication as to why/where the mkinitrd step of the kernel upgrade was failing in other cases? The dev/MAKEDEV was a separate and 1 shot issue caused by going from the 'old' to 'new' and would have no effect on an Install since no partitions are mounted. As to the failure of mkinitrd in the B4 upgrade I would suspect this to be a DrakeX problem. Charles -- Fortune's real live weird band names #672: Stinky Fire Engine -- Charles A Edwards [EMAIL PROTECTED] --
