Date: Tue, 6 Feb 2007 12:53:13 -0500 From: Jerry McAllister <jerrymc@msu.edu> To: Marty Landman <martster@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: recovery after power outage Message-ID: <20070206175313.GB16449@gizmo.acns.msu.edu> In-Reply-To: <70063950702060854t18e66adftf99e98547237836@mail.gmail.com> References: <70063950702060854t18e66adftf99e98547237836@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 06, 2007 at 11:54:17AM -0500, Marty Landman wrote: > My fbsd 6.0 box is having filesystem problems on boot since a blackout > yesterday. Here's a synopsis: > > /dev/ad0s1a: clean > /dev/ad0s1d: DEFER FOR BACKGROUND CHECKING > ...repeats for ad0s1f & e > then reports error=40<UNCORRECTABLE> for ad1 (twice) and reports an > unexpected inconsistency for my ad1s1c device which is the primary slave hd. > > Tells me to run fsck manually and asks which shell I want. Maybe this is my > fault for not partitioning appropriately, can't get to many commands > including fsck guess it's because of the fs problems. > > How can I try and recover from this? Well, do as it says - choose a shell and run fsck manually. Probably you want the default shell = /bin/sh. The output says ad0s1a is clean, so your fsck should be available. Just run /sbin/fsck /dev/ad1s1c. Actually that would be a somewhat unusual address - what they call a 'dangerously dedicated' disk. But I think fsck should be able to work through it. You will probably have to sit there and answer 'y' to a bunch of prompts or do fsck -y /dev/ad1s1c to force a y to everything. The fsck that runs at boot pops out and stops the boot if it runs in to anything it is scared to assume it will fix. But in most cases, there isn't anything you can do but answer 'y' anyway. If that causes something to be lost, you probably wouldn't be able to recover it anyway. When the manual fsck-s all finish - which can take a long time, then reboot and see what happens. It should come all the way up. It the manual fscks don't work, then you may have to try some extreme tactics to recover things on that partition or abandon it. If you end up rebuilding the drive, then the next time make a FreeBSD slice and then make a partition within that slice to avoid that 'dangerously dedicated' config. Good luck, ////jerry > > Marty > > -- > Web Installed Formmail - http://face2interface.com/formINSTal/ > Webmaster's BBS - http://bbs.face2interface.com/ > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070206175313.GB16449>