Date: Mon, 27 May 1996 00:36:09 GMT From: James Raynard <fqueries@jraynard.demon.co.uk> To: hey@tuns.ca Cc: questions@freebsd.org Subject: Re: Help Message-ID: <199605270036.AAA00862@jraynard.demon.co.uk> In-Reply-To: <199605261938.MAA11110@freefall.freebsd.org> (hey@tuns.ca)
next in thread | previous in thread | raw e-mail | index | archive | help
> /dev/rsd0a: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY > Automatic file system chek failed ... help! At boot time, fsck is run with the -p option from /etc/rc. This puts it in a non-interactive mode where it can only fix a limited set of file-system inconsistencies. The message is telling you fsck has found an inconsistency that is beyond its capabilities to fix and that you should run it by hand (without the -p option). See the fsck man page for a fuller explanation. > During the bootting of the system, I have no chance to interrupt it to > do anything. You can send fsck a QUIT signal (control-backslash), according to the man page. A better way is probably to type '-s' at the boot prompt and boot in single-user mode. > Please advice me what should I do in order to access the hadr disk to get > all my files out if the system have to reinstalled. Hmm. Even if you have another FreeBSD disk in the machine, mount won't look at it until you've fsck'd it. You do take regular backups, don't you? 8-) It's difficult to predict how bad the damage might be. The only time this has happened to me was when I put some bad SIMMs in my machine and everything started segfaulting just after the system went multi-user. Unfortunately, use of the damaged files was the /var/spool/news directory (I start up innd from rc.local), so I ended up with a trashed news spool. 8-( On the other hand, you may not even lose any files at all. -- James Raynard, Edinburgh, Scotland jraynard@dial.pipex.com james@jraynard.demon.co.uk
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605270036.AAA00862>