Date: Thu, 30 Aug 2001 06:35:31 +0000 (GMT) From: "P. U. (Uli) Kruppa" <root@pukruppa.de> To: Mike Meyer <mwm@mired.org> Cc: <questions@FreeBSD.ORG> Subject: Re: BAD SUPER BLOCK Message-ID: <20010829162432.S1147-100000@localhost> In-Reply-To: <15244.10947.452112.110319@guru.mired.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 28 Aug 2001, Mike Meyer wrote: > P. U. (Uli) Kruppa <root@pukruppa.de> types: > > Micke Josefsson wrote: > > > I think this the time to use one of the extra superblocks on the disk. Try > > > fsck -b 32 /dev/ad0s2e > > > > I tried > > fsck -b 32 /dev/ad0s2e > > but I get an > > illegal option --b > > and I did not find anything equivalent in # man fsck > > By the way: I run FreeBSD -CURRENT . > > First, unless you've got a good reason - and wanting functionality > that's not in -STABLE is NOT a good reason - you shouldn't be running > -CURRENT. See section 20.2.1.2 of the handbook for good reasons for > the two good reasons for running -CURRENT. There is a very good reason to run -CURRENT : You hear about things like SUPER BLOCKS . When I want functionality I will simply boot into my MS-WINDOWS , but I will never know how it works and what it does. And: -CURRENT really runs very well. I use it on my private PC for about 3 months and do not have more problems than I had with my last -RELEASE . > The best course of action would be to ask on the -current mail list to > see if anyone there is interested in looking into this, as there's a > good chance you've stumbled on a bug in the experimental file system > snapshot code that's being used in -CURRENT. If you aren't on the > -current mail list, you should be - that's even more critical than > being on the -stable list if you are tracking -stable, and the latter > is pretty much a requirement. I am on freebsd-current mailing list, but I did not see this as a -CURRENT problem. But someone seems to have worked on my problem in the meantime. After a cvsup last night I could do # fsck /dev/ad0s2e and a friendly dialog guided me on the way to repair my partition. FOR THE ARCHIVE: I had to reconstruct an "emergency"-directory system in /var to be able to boot my machine. Then I could cvsup and everything seems to be working now. Uli. *--------------------------------------* | www.pukruppa.de www.2000d.de | | Wuppertal - Germany | *--------------------------------------* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010829162432.S1147-100000>