From owner-freebsd-stable Tue May 18 9:32:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from news.IAEhv.nl (news.IAE.nl [194.151.64.4]) by hub.freebsd.org (Postfix) with ESMTP id 2667F14E52 for ; Tue, 18 May 1999 09:32:50 -0700 (PDT) (envelope-from devet@adv.iae.nl) Received: (from uucp@localhost) by news.IAEhv.nl (8.9.1/8.9.1) with IAEhv.nl id SAA13427; Tue, 18 May 1999 18:32:36 +0200 (MET DST) Received: (from devet@localhost) by adv.iae.nl (8.9.3/8.8.6) id SAA10570; Tue, 18 May 1999 18:29:54 +0200 (CEST) Date: Tue, 18 May 1999 18:29:54 +0200 (CEST) From: Arjan de Vet Message-Id: <199905181629.SAA10570@adv.iae.nl> To: alick@fas.ru Subject: Re: Can't load 3.2-STABLE kernel X-Newsgroups: list.freebsd.stable In-Reply-To: <19990518171440.A359@fas.ru> Organization: Internet Access Eindhoven, the Netherlands Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19990518171440.A359@fas.ru> you write: >/kernel text=0x119656 >elf_loadexec: archsw.readin failed >can't load module /kernel: input/output error I had the same error when I ported the 1GB KVM changes to 3.1-stable some time ago (before they were merged from current). The new kernel could not be loaded anymore by the old bootblocks. The solution is to update the bootblocks with something like disklabel -B da0 if da0 is your boot disk. Make sure the contents of /boot is up to date. See the manual page of disklabel for more details. Arjan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message