Re: [S.u.S.E. Linux] Problems with Boot/Recovery Disk [was Re: Rescue disk]
Van: Howard Arons <hlarons@ComCAT.COM> Aan: suse-linux-e@suse.com Onderwerp: [S.u.S.E. Linux] Problems with Boot/Recovery Disk [was Re: Rescue disk] Datum: woensdag 12 augustus 1998 18:28
On Aug 11, 1998, Hubert Mantel wrote:
Hi,
On Mon, 10 Aug 1998, Howard Arons wrote:
[...]
I tried a dd of the SuSE CD /disks/scsi11, which is supposed to be
for
the FD 16xx card, but it won't boot. It says "Loading initdisk.gz" followed by "Boot failed; press any key to retry". Bummer. Maybe scsi11 contains no IDE/EIDE drivers?
No, this normally is caused by a defective floppy. It's very early in
Why don't you let suse create a recoverdisk for you. Then it contains your current kernel. (You should have done that before a crash ofcourse). ---------- the
boot process and the kernel has not yet been loaded. Another reason _could_ be a corrupted disk image on the CD.
Right you are. I ran 'badblocks -v -w /dev/fd0 1440' to test the floppy. No errors. I ran 'dd if=/cdrom/disks/scsi11 of=/dev/fd0'. Boots fine if 'linux fdomain=<addr>,<irq>'is entered at the boot prompt.
Well, I think your self-compiled kernel lacks some needed options. You need:
CONFIG_BINFMT_AOUT=y (for size reasons, linuxrc is a.out) CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_INITRD=y CONFIG_MINIX_FS=y
You caught me there! In my newbie ignorance, I compiled with CONFIG_BINFMT_AOUT=m CONFIG_BLK_DEV_RAM=m CONFIG_MINIX_FS=m "CONFIG_BLK_DEV_INITRD" is _not_ present in either my new OR my original .config file. Based on the SuSE manual I assumed I didn't need it.
-o) Hubert /\\ _\_v
Thanks again for your help. Howard Arons -- Powered by SuSE Linux 5.2 -- kernel 2.0.33 Communications by Mutt 0.89 - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
On Aug 12, 1998, R Doetjes wrote:
Why don't you let suse create a recoverdisk for you. Then it contains your current kernel. (You should have done that before a crash ofcourse).
Well, that's what started all this off :-) I used YaST to make a recovery disk, but that isn't bootable--you need to boot a disk that will run linuxrc, and offer you the option to use the recovery system from either a floppy or the CD. My problems (solved now, thanks to Hubert) was making that boot disk. Howard Arons -- Powered by SuSE Linux 5.2 -- kernel 2.0.33 Communications by Mutt 0.89 - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
participants (2)
-
hlarons@ComCAT.COM
-
raymond.doetjes@tip.nl