Date: Thu, 11 Jul 2002 01:13:29 -0700 From: David Schultz <dschultz@uclink.Berkeley.EDU> To: Ian Dowse <iedowse@maths.tcd.ie> Cc: current@FreeBSD.ORG Subject: Re: -CURRENT trashes disk label Message-ID: <20020711081329.GA568@HAL9000.wox.org> In-Reply-To: <200207110902.aa74600@salmon.maths.tcd.ie> References: <20020711074618.GA382@HAL9000.wox.org> <200207110902.aa74600@salmon.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake Ian Dowse <iedowse@maths.tcd.ie>: > In message <20020711074618.GA382@HAL9000.wox.org>, David Schultz writes: > >I just made world on -CURRENT (cvsup a few hours ago), booted > >using a new GENERIC kernel and ran mergemaster. Before I > >installed world, I mounted the root partition for my more stable > >development environment (4.6-RELEASE) to copy my firewall rules > >over. In summary: > > ># fsck /dev/ad1s1a > >** /dev/ad1s1a > >BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE > >/dev/ad1s1a: INCOMPLETE LABEL: type 4.2BSD fsize 0, frag 0, cpg 0, size 524288 > > You just need to "fsck -b16 /dev/ad1s1a", or alternatively upgrade > to the latest -STABLE fsck, which fixes this issue. There are a few > new superblock fields in use in -CURRENT that trigger some unnecessary > fsck sanity checks. Excellent, upgrading fsck did the trick. Thanks for the quick reply! (By the way, shouldn't fsdb still work, even if it's confused? If a superblock glitch makes it refuse to start, that sort of defeats the purpose.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020711081329.GA568>