From bb@suse.com Sat Mar 21 02:35:45 1998 From: bb@suse.com To: users@lists.opensuse.org Subject: Re: [S.u.S.E. Linux] none@root:/ Power outage : How Do I Recover Date: Sat, 21 Mar 1998 03:35:45 +0100 Message-ID: <6ev921$j4r$1@Galois.suse.de> In-Reply-To: <[S.u.S.E. Linux] none@root:/ Power outage : How Do I Recover> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4306099952165986631==" --===============4306099952165986631== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Tom Schaefer wrote: >=20 > This problem has bugged me since I've been using Linux and since it > doesn't happen all the time, I can never remember the simplest recovery > for this problem. > I wind up booting up with boot diskettes and hacking shit till it works > right, never being sure about what it was I did to fix it. >=20 > Currently, I have a user who is not real technical and she has to enter > commands that I give her over the phone, several hundred miles away. >=20 > Scenario: Power outage caused the system to go down rudely. >=20 > Power up and the system comes up with the none(a)root:/ or something > message. / is not mounted. >=20 > I have had the user run fsck, e2fsck in hopes that it would reset > whatever flag it is that is causing that damn message to come up and not > properly mount or start the system. I wish you guys had a simple doc > somewhere for this, it's extremely frustrating because e2fsck and fsck > don't really work according to the damn man pages.I've done the remount > of root and then had her run fsck and e2fsck and that didn't fix > anything either. >=20 > She has no rescue diskette, and even if she did, yast is too complicated > for her to figure out. >=20 > Why don't you guys just setup the boot process to do it like SCO does, > run the real fsck and make it really check the drive instead of the soft > check. >=20 > What needs to be fixed so it will boot up properly? Usualy the best thing is to start the system in single user mode, check=20 the filesystems and reboot to your regular runlevel. This can be done by giving 'S' as parameter at the LILO promt: boot: S Where is the name of your LILO bootconfiguration (TAB shows you all possibilities). Then log on as root. At this point / will be mounted read only, and all the other partitions are still unmounted.=20 Now go on and check every partition: e2fsck /dev/... You may want to give 'Y' as answer for every e2fsck question, usualy this is the best choice. Then log off and reboot as usual. If you are lucky the machine comes up without any problem. But you are realy in trouble if not... Ciao, BB --=20 Bodo Bauer S.u.S.E., LLC fon +1-510-835 7873=20 bb(a)suse.de 458 Santa Clara Avenue fax +1-510-835 7875 http://www= .suse.com> Oakland CA, 94610 USA -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e --===============4306099952165986631==--