From: tabanna
Did you tried the physical integrity of the disk - let's say using DiskDupe or something of the kind ? Did you tried booting from the recovery disk as well ?
Oleg ~ thanks a ton :) Something VEry odd, is happening here ~ It seems that LILO is over-riding the BIOS instruction to boot from Drive A: { fd0 } ................ I have 3 Linux systems on my Hard Disk : SuSE 6.2 SuSE 7.0 Mandrake ALL three are set up to share the same boot Partition /dev/hda1 which is ext2 file system { there is NO DOS partition on my Hard Disk } With the ONE exception of "Toms Killer Boot Disk", NO Linux bootable floppy will boot from /dev/fd0 ! It appears that the /boot partition /dev/hda1 has taken control of my system ! Any ideas { I do not believe the floppies to be corrupted } thanks best wishes <p>> ---------- Original Message ----------------------------------
This happened, suddenly.
My SuSE official distro Boot Disk used to work flawlessly.
Suddenly, it will not boot %#$@
any ideas ? . . . I have tried re-setting BIOS defaults, but still have this problem :(
thanks
Hi, SuSErs :)
~ Am having a problem, booting from /dev/fd0 _____________________________________________________
After my BIOS message reports: 'Verifying DMI Pool Data . . . . ' "Boot failed" appears, and the system hangs :(
..........................
My floppy drive is able to Boot DOS Disks OK , but I get "Boot failed" , from ALL my Linux Boot Disks
with, ONE exception : 'Tom's Killer Boot Disk' DOES Boot OK .. . . Good 'ole Tom ! ................................
Any ideas, please, what may be the mysterious cause .. . . did 3 of my Linux Boot Disks, ALL, get hit my a Cosmic Ray $#@% {{{ LILO works OK }
thanks
best wishes
Richard --
-- ____________ sent on Linux ____________ 100% Virus Free! AMD Inside