[S.u.S.E. Linux] Rescue disk
Boy am I glad SuSE has rescue from floppy. I was experimenting with different versions of ncurses yesterday, and one time after installing the august9 patchlevel of 4.2 to /usr/lib, I had rm'ed libncurses from /lib without moving the new so's to /lib. As a result, I had a system that would hang at boot. My SuSE cd + rescue floppy let me mount my root partition and cp libncurses from the floppy to /lib. It was the first time I needed my rescue disk, and boy, was I glad to have it. Make one today if you don't have one! Actually, I think you can rescue via the cd alone too. Phew!!! -- .---. /#######\## -==============================================- ;##### ;# Mike's WindowMaker ;##### ;# <A HREF="http://tasteslikechicken.ml.org/windowmaker.html"><A HREF="http://tasteslikechicken.ml.org/windowmaker.html</A">http://tasteslikechicken.ml.org/windowmaker.html \# /## -==============================================- ####'---'#### - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi, On Mon, 10 Aug 1998, Michael Lankton wrote:
Boy am I glad SuSE has rescue from floppy. I was experimenting with different versions of ncurses yesterday, and one time after installing the august9 patchlevel of 4.2 to /usr/lib, I had rm'ed libncurses from /lib without moving the new so's to /lib. As a result, I had a system that would hang at boot. My SuSE cd + rescue floppy let me mount my root partition and cp libncurses from the floppy to /lib. It was the first time I needed my rescue disk, and boy, was I glad to have it. Make one today if you don't have one! Actually, I think you can rescue via the cd alone too.
Yes. And if you use the Live-CD (which is bootable), you can even rescue your system under X (given you have enough memory ;-) Admitted: There has been a bug on 5.2 where always the german keymap has been loaded...
Phew!!! -- .---. /#######\## -==============================================- ;##### ;# Mike's WindowMaker ;##### ;# <A HREF="http://tasteslikechicken.ml.org/windowmaker.html"><A HREF="http://tasteslikechicken.ml.org/windowmaker.html</A">http://tasteslikechicken.ml.org/windowmaker.html \# /## -==============================================- ####'---'####
-o) Hubert /\\ _\_v - 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 10, 1998, Michael Lankton wrote:
Boy am I glad SuSE has rescue from floppy. I was experimenting with
[...]
Make one today if you don't have one!
Well, while we're on this subject...How do I create a _boot_ disk that: (a) mimics the action of the SuSE-included boot floppy that invokes linuxrc, so that a rescue floppy can be used; (b) allows me to mount my CD-ROM (SCSI on Future Domain 16xx card). 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? OTOH, when I do a dd of the SuSE CD /disks/eide01, the floppy boots into linuxrc OK, but all attempts to load the FutureDomain driver fails, no matter how I try to supply the init parameters. If I "edit" the eide01 boot disk by substituting my kernel for the one named Linux, linuxrc is bypassed. I hate depending on that one SuSE-supplied boot floppy. 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
Hi, On Mon, 10 Aug 1998, Howard Arons wrote:
Well, while we're on this subject...How do I create a _boot_ disk that:
(a) mimics the action of the SuSE-included boot floppy that invokes linuxrc, so that a rescue floppy can be used;
(b) allows me to mount my CD-ROM (SCSI on Future Domain 16xx card).
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 the boot process and the kernel has not yet been loaded. Another reason _could_ be a corrupted disk image on the CD.
OTOH, when I do a dd of the SuSE CD /disks/eide01, the floppy boots into linuxrc OK, but all attempts to load the FutureDomain driver fails, no matter how I try to supply the init parameters.
I wonder how you managed to install under that circumstances...
If I "edit" the eide01 boot disk by substituting my kernel for the one named Linux, linuxrc is bypassed.
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 I assume support for a.out and for initdisk are missing in your kernel. Otherwise you did it the right way: Just copy this kernel to one of our bootdisks (make sure its name is "Linux"). If space is tight, you can of course delete some of the module files (scsi-mod.gz and so on, but NOT initdisk.gz as it contains the linuxrc).
I hate depending on that one SuSE-supplied boot floppy.
Howard Arons -o) Hubert /\\ _\_v
- 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 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 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
Hi, On Wed, 12 Aug 1998, Howard Arons wrote: [...]
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.
CONFIG_BLK_DEV_INITRD is only there if the Ramdisk driver is configured to be compiled into the kernel. It does not make any sense otherwise. Normally, you do not need it ;-)
Thanks again for your help. Howard Arons -o) Hubert /\\ _\_v
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
participants (3)
-
hlarons＠ComCAT.COM -
mantel＠suse.de -
satan3＠home.com