Date: Wed, 9 May 2001 23:56:28 +1000 From: Sue Blake <sue@welearn.com.au> To: DAC <usmc1@dslextreme.com> Cc: "freebsd-questions@FreeBSD.ORG" <freebsd-questions@FreeBSD.ORG> Subject: Problems after power outage Message-ID: <20010509235628.F26110@welearn.com.au> In-Reply-To: <200105081956.MAA03173@va1.dslextreme.com>; from usmc1@dslextreme.com on Tue, May 08, 2001 at 01:01:13PM -0800 References: <200105081956.MAA03173@va1.dslextreme.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 08, 2001 at 01:01:13PM -0800, DAC wrote:
>
> I recently had a power outage and my system shutdown inadvertantly ,
> upon reboot it stops half way there with this response:
> Doing initial Network setup;
> eval:1: Syntax error: end of file unexpected (expecting ")")
That last line is your error message, and the line before it gives
us the context.
The system cannot start up properly because something is broken. I
don't know what's wrong, but somebody else might. I'll try to
fill you in a bit so that you can understand any other responses.
I've also changed the subject line so that more people will take
notice if they are interested.
When it booted, it would have taken longer than usual, running fsck
over the disks (like chkdsk or whatever Microsoft calls that thing
these days). Did it complain at that time, saying unable to fsck one of
the filesystems? Were you perhaps editing a configuration file when the
system went down? If so, that half-finished edit might be the only
problem.
Because it can't start up the normal way, it is going into single
user mode to allow you (as root) to fix whatever needs fixing.
> Enter full pathname of shell or return for /bin/sh :
When it throws you into a root login, it doesn't know which
preferred shell to give you, so it asks. But /bin/sh is
probably the only shell program it can access at that point,
so just press Return to accept that shell...
> I hit return and it just goes to the command prompt "#"
...and then you're logged in as root to do your repairs.
You'll probably find that you can't access all commands because
only the root filesystem is mounted. Type 'mount' to see what's
mounted. Type 'cat /etc/fstab' to list all of your filesystems.
> What is the pathname of the shell (I guess I should be writing this
> down ,huh?)]
No, write this down instead. If you're ever using /bin/sh on FreeBSD
and you want to be able to get your command history using the up
arrow key, type this at the prompt:
set -o emacs
Hopefully somebody will recognise your problem and be able to
point you to the likely cause, and suggest how to fix it.
And hopefully the damage done is only something easily fixed.
Meanwhile if you can provide any other information that might
be relevant, please let us see it.
--
Regards,
-*Sue*-
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010509235628.F26110>