Date: Wed, 20 Oct 1999 10:06:57 +0100 (BST) From: Mark Powell <M.S.Powell@salford.ac.uk> To: "Joe \"Marcus\" Clarke" <marcus@miami.edu> Cc: freebsd-stable@freebsd.org Subject: Re: How to fix cant load /kernel - NFS corruption? Message-ID: <Pine.BSF.4.05.9910200919080.67104-100000@localhost> In-Reply-To: <Pine.OSF.4.10.9910200155480.9385-100000@jaguar.ir.miami.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 20 Oct 1999, Joe "Marcus" Clarke wrote:
> Are you sure the kernel in root is an ELF kernel? I persoanlly haven't
> seen this error, but it looks like the file type for /kernel is not known
> to the loader.
That's what I thought. However, I've done a straight copy of the whole OS
from the other machine. Even trying to boot kernel.GENERIC gives the same
error.
Okay, tried file and all three kernels in the root are corrupted. They
are the correct length, but kernel and kernel.old have a extra 0 byte at
the start. kernel.GENERIC has an 0x0a. Everything else is out a byte, so I
can only assume what was the last byte is missing. I ftpped the kernel
again from the other machine and rebooted. It came up, but I noticed lots
of "syntax error: '(' unexpected" during boot. Looks like loads of
executables are corrupted. Checked a few data files and some of those are
corrupted too. Hmmm, looks like an nfs problem? This ain't supposed to
happen? I've done machine copies in the past using tar and rsh, but that
doesn't seem possible with the fixit floppy <sigh>
> Can you run ``file /kernel'' on it from the fixit floppy?
> Also, according to Kirk's talk at FreeBSDCon, it seems SoftUpdates can (or
> will) allow for crashed systems to come back up without needing to run
> fsck.
Yeah, I've read that document. However, I notice from looking at the
source to fsck, that it makes some assumptions about a fs if the soft
updates flag is set. I had the soft updates flag set, but didn't actually
mount the fs with soft updates on, because I took the option out of the
kernel. I had the fs mounted async. I'm wondering if having the flag on
was what caused the fs corruption. Although I am aware of the possibilty
of fs corruption, just using async. This is the first time it's ever
happened though.
> I don't think all the support is there yet, but Kirk seems
> confident that softupdate is good, and is going to get a lot better. He's
> in the process now of trying to sell it to the major industry hitters.
> After that, it should become the default in FreeBSD.
Well I don't want this to happen again so I'll try soft updates rather
than stick with async.
Mark Powell - UNIX System Administrator - Clifford Whitworth Building
A.I.S., University of Salford, Salford, Manchester, UK.
Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key
M.S.Powell@ais.salfrd.ac.uk (spell salford correctly to reply to me)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9910200919080.67104-100000>