From owner-freebsd-current Sun Sep 26 8:57:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 8C9C1150FB for ; Sun, 26 Sep 1999 08:57:34 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from d197.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id BAA20884; Mon, 27 Sep 1999 01:57:57 +1000 Date: Mon, 27 Sep 1999 01:57:18 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Cejka Rudolf Cc: current@FreeBSD.ORG Subject: Re: Boot problems with new -current In-Reply-To: <19990926121308.A1826@dcse.fee.vutbr.cz> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 26 Sep 1999, Cejka Rudolf wrote: > Ok: Just run "disklabel -r -e ad0", clear word "badsect" > in "Flags:" line and booting of new kernels is back... I think phk set to switch back to the wd driver to run disklabel, but that shouldn't be necessary -- a new label can certainly be written using the ad driver, so something would have to be broken for an old or broken label not to be modifiable. > Soren Schmidt wrote (1999/09/25): > > > The ATA driver has no bad144 support, thats probably why you get > > the above message. The reason is that modern ATA disks does internal > > bad block remapping (just as SCSI), and if you have used up all > > the spares you better swap that disk for another one, its going > > bad on you no matter what... > > But in earlier versions ATA driver worked for me. Does this mean that That was because earlier versions of the ad driver were too broken to handle the bad block table properly. They silently ignored the error of having one, and would probably have corrupted your data if the table was non-null. Your table seems to have been null, so there were no problems. > flag "badsect" was silently ignored and now it have an effect on > a panic? Isn't a big warning message sufficient instead of a panic? It's just an error. IIRC, the panic was because your root file system became inaccessible. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message