From owner-freebsd-questions Thu Feb 25 5:42:49 1999 Delivered-To: freebsd-questions@freebsd.org Received: from torrent.hydro.on.ca (beck.Hydro.ON.CA [192.75.134.5]) by hub.freebsd.org (Postfix) with SMTP id 4B9EF14D92 for ; Thu, 25 Feb 1999 05:42:41 -0800 (PST) (envelope-from Jim.Service@oht.hydro.on.ca) Received: id IAA06669; Thu, 25 Feb 1999 08:48:01 -0500 Received: by gateway id IAA24675; Thu, 25 Feb 1999 08:42:13 -0500 (EST) Received: by gateway id IAA29327; Thu, 25 Feb 1999 08:42:12 -0500 Received: by gateway id ; Thu, 25 Feb 1999 08:43:47 -0500 Message-ID: From: SERVICE Jim -TS+NP DVLPMT To: "'Koji Baba'" Cc: freebsd-questions@FreeBSD.ORG Subject: RE: New kernel is "Invalid format!" Date: Thu, 25 Feb 1999 08:43:55 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Been there, done that! The boot process has changed (at least from v2.2.8 to 3.1) presumably because of the change from a.out to elf executables. If you upgrade an existing FreeBSD system without using the boot floppies then it looks like you need to use disklabel to install new bootblocks. This is done automatically if you upgrade via the floppies. James (Jim) R.R. Service jservice@yahoo.com > -----Original Message----- > From: Koji Baba [mailto:baba@kddcom.co.jp] > Sent: 24 February, 1999 00:05 > To: freebsd-questions@FreeBSD.ORG > Subject: New kernel is "Invalid format!" > > > Please give me any info. > > I updated from 3.0-RELEASE to 3.1-RELEASE by binary update. > After finishing whole sequence, boot says following. > > dosdev = 80, biosdrive = 0, unit = 0, major = 4 > Invalid format! > > But I can boot up by kernel.prev as before updating. > > H/W around boot device is > Adaptec AIC-7865 (on borad) > Seagate ST32155W To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message