Mailinglist Archive: opensuse (3784 mails)
| < Previous | Next > |
Re: [SLE] Corrupted rc.config file
- From: "Karol Pietrzak" <noodlez84@xxxxxxxxxxxxx>
- Date: Mon, 8 Oct 2001 13:22:14 -0400
- Message-id: <3BC1A886.32590.225FEB@localhost>
On 8 Oct 2001, Trey Gruel wrote:
>
> i used yast2 to change a couple settings (turned off apm and isapnp) on my
> suse 7.1 pro box and now it won't boot. i get the error:
>
> /etc/init.d/boot: .: /etc/rc.config: cannot execute binary file
>
> and the boot process stops after mounting the /proc and /dev/pts
> filesystems. the machine is not hung (i can type to my hearts content,
> but it accomplishes nothing) but cannot complete the boot process.
>
> does anyone know a way around this so i can restore my old rc.config file?
I don't think there's a way to restore it, but try this:
o at the LILO prompt, put 1 at the end of what you usually
put, telling Linux to start in runlevel 1, single user mode
(this should work, almost w/o a doubt)
o run 'SuSEconfig'. If there are any errors in your
/etc/rc.config, the util will probably tell you. It will also
commit your changes.
o reboot in your usual runlevel and see what happens
If that doesn't work, here's something else you should try:
o mark up and your /etc/rc.config and enable "SuSEconfig" will
"fix" your config files
o enable boot logging (IIRC, also in /etc/rc.config)
o check out /var/log/boot.msg and see what happens.
--
noodlez: Karol Pietrzak
PGP KeyID: 0x3A1446A0
>
> i used yast2 to change a couple settings (turned off apm and isapnp) on my
> suse 7.1 pro box and now it won't boot. i get the error:
>
> /etc/init.d/boot: .: /etc/rc.config: cannot execute binary file
>
> and the boot process stops after mounting the /proc and /dev/pts
> filesystems. the machine is not hung (i can type to my hearts content,
> but it accomplishes nothing) but cannot complete the boot process.
>
> does anyone know a way around this so i can restore my old rc.config file?
I don't think there's a way to restore it, but try this:
o at the LILO prompt, put 1 at the end of what you usually
put, telling Linux to start in runlevel 1, single user mode
(this should work, almost w/o a doubt)
o run 'SuSEconfig'. If there are any errors in your
/etc/rc.config, the util will probably tell you. It will also
commit your changes.
o reboot in your usual runlevel and see what happens
If that doesn't work, here's something else you should try:
o mark up and your /etc/rc.config and enable "SuSEconfig" will
"fix" your config files
o enable boot logging (IIRC, also in /etc/rc.config)
o check out /var/log/boot.msg and see what happens.
--
noodlez: Karol Pietrzak
PGP KeyID: 0x3A1446A0
| < Previous | Next > |