Date: Fri, 8 Aug 2003 11:18:29 -0700 From: Fred Condo <fred@condo.chico.ca.us> To: doug@allensystemconsultants.com Cc: freebsd-stable@freebsd.org Subject: Re: boot with dirty filesystem? Message-ID: <B5F5415B-C9CC-11D7-96F8-003065C7DFE8@condo.chico.ca.us> In-Reply-To: <20030808074942.21306.h008.c011.wm@mail.allensystemconsultants.com.criticalpath.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, Aug 8, 2003, at 07:49 US/Pacific, doug@allensystemconsultants.com wrote: > I have a small problem. I've had a machine go down and it came back > up with dirty filesystem on /var and /usr. fsck has solved the > problem with /var, after 10 times through. fsck seems unable to > resolve the inconsistencies with /usr however. fsck is running for > the 15th time right now. It looks to me like a probable bad sector on > the disk. > > My question is there a way to force the machine to boot with a dirty > filesystem, so that I can pull data from /etc to move to a new disk? > Barring that, is there still a procedure to force the system to boot, > update the inodes with whatever information it can find, and mark the > other files as unreadable? You don't need to mount /usr to copy /etc. Boot the system single-user. Mount a floppy on /mnt. cp -R /etc /mnt. Halt the system and pull the floppy.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B5F5415B-C9CC-11D7-96F8-003065C7DFE8>