On Tuesday 21 February 2006 18:36, Michelle Konzack wrote: > first I have tried to make an 'apt-get dist-upgrade' which was > working fine on both WS but since I have gotten a kernel upgrade > I had to reboot... Oops... > > "No operating system. Please insert system disk."
The debian-boot list, despite its name, is not about boot problems, but about development of the installation system. I have absolutely no idea how your boot got damaged. The most likely cause would be an update of lilo (through the backports you're using?). lilo often needs to be run again _before_ rebooting after an upgrade... > On both machines! I have used the netinstall 3.1r0a. Huh? Are you saying you did a dist-upgrade using a netinstall? I very much wonder how that would work... > OK, now, since the netinstall does not offer a "rescue" system, Although it does not have a full rescue system, it can still be used for rescue; see the Debian Installer FAQ. Also note that the Etch version of the installer does have a rescue option again (though it works totally different from Woody's rescue option). > OK, now I have downloaded a newer netinstall CD 3.1r1 and erased > the whole HDD's. rebooted to reinitialise the Harddrive and installed > using NEW partitions Sarge again. > > All was working fine but again, Booting failed. - WHY? No idea without description of errors... > OK, new installation and now at the end I was looking on VT3 <F3> and > have seen, that at the end of the installation (writing lilo), the > inataller was not able to find the partitions anymore, but THE ARE in > /proc visible. Please file an installation report [1] and attach the syslog and partman files from /var/log (gzipped). Another option is to switch to VT2, do 'chroot /target' and try to install lilo or grub manually before rebooting. That might provide some more detailed error messages. > Oh yes, i am using for installation Linux 2.4.27 but personaly Linux > 2.4.(31|32). So you are using a customized installer? Or are you just installing custom kernels during the installation? Anyway, can you reproduce the problems using the standard Sarge kernel? We can only support if you use "pure Sarge". Cheers, FJP [1] http://www.debian.org/devel/debian-installer/report-template
pgpmYAqjbykvk.pgp
Description: PGP signature
