From: forkosh@panix.com   
      
   Henrik Carlqvist  wrote:   
   > On Thu, 09 Feb 2023 06:11:13 +0000, John Forkosh wrote:   
   >> "corrupt partition" fatal warnings. Running  lilo -P ignore  let it run   
   >> to completion, but didn't actually install on root block ("boot =   
   >> /dev/sda4" in lilo.conf), as far as I can tell.   
   >   
   > Ah, I always install lilo in MBR (/dev/sda), and so did you to get it to   
   > work, but from another multi-boot install.   
      
   Yeah, that seems to be the most convenient approach for desktops,   
   where I typicaly use a 1TB ssd for /dev/sda and a much larger hdd   
   for /dev/sdb, with sda reserved for slackware installs, and sdb   
   for my work.   
      
   > It was many years since I installed lilo onto the boot block of a   
   > partition. To make it boot that way you will still need to configure some   
   > other boot loader to use that partition as a chain boot.   
      
   I've never actually intended to chain boot using the boot block.   
   Just run lilo that way to see that everything's working as it should.   
   I've always booted directly from the mbr, where lilo's installed   
   from the /dev/sda1 partition, with whatever -current64 is current   
   at the time. In this case -current64 was 9/1/19. Then I add sections   
   to sda1's lilo.conf like   
      # Linux bootable partition config begins   
      image = /mnt/sda2/boot/vmlinuz   
        root = /dev/sda2   
        label = slk150x64sda2   
        read-only  # Partitions should be mounted read-only for checking   
      # Linux bootable partition config ends   
   for partitions 2,3,4, as I install new -current64s, while leaving the   
   older ones still bootable, until I rotate back to sda1.   
      
   > My guess is that your problem came from different kernels/software having   
   > different opinions upon the geometry of the drive.   
      
   Hmm... that could be it, I suppose. So next time I re-install /dev/sda1   
   using the mbr for lilo, the problem should go away. And I guess I'll have   
   to eventually do that, but it's a bit scary since if the problem remains   
   then the box may not be bootable without reformatting sda, which will   
   wipe the other installs. Well, I guess it's inevitable, sooner or later.   
      
   > regards Henrik   
   Thanks again for all the helpful information.   
   --   
   John Forkosh  ( mailto:  j@f.com  where j=john and f=forkosh )   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)