From owner-freebsd-questions Sat Feb 28 12:21:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15515 for freebsd-questions-outgoing; Sat, 28 Feb 1998 12:21:52 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from citytel1.citytel.net (root@citytel1.citytel.net [204.244.99.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15502 for ; Sat, 28 Feb 1998 12:21:37 -0800 (PST) (envelope-from kwoody@citytel.net) Received: from mybsd.net (citytelprct93.citytel.net [204.244.99.46]) by citytel1.citytel.net (8.8.8/8.8.5) with ESMTP id MAA23529; Sat, 28 Feb 1998 12:22:59 -0800 (PST) Received: from mybsd.net (mybsd.net [192.168.0.2]) by mybsd.net (8.8.5/8.8.5) with SMTP id JAA02077; Sat, 28 Feb 1998 09:17:13 -0800 (PST) Date: Sat, 28 Feb 1998 09:17:13 -0800 (PST) From: Keith Woodworth To: Greg Lehey cc: FreeBSD Questions Subject: Re: best way to recover In-Reply-To: <19980228121737.28251@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 28 Feb 1998, Greg Lehey wrote: > >>> someone said that i should never run fsck on a "live" file system, > > Yup, that was me. > > >>> what do they mean by "live" > > Mounted. > > Well, that was clever after being warned, wasn't it? fsck works on > the character device and ignores the contents of cache, so it can see > deficiencies where none exist. If it "fixes" these deficiencies, it > corrupts the disk. Then I got really lucky a few days ago. My system had had an uptime of just over 60 days. One of my disks have started to make a high pitched whine so I was thinking about what might be the problem with it. I was working in an xterm and thought I'd take a gander at fsck man page. got distracted by a phone call and typed in fsck without man and it ran and said it found some error, want to fix? Sure I thought, realzing that I would have to reboot. Fixed and rebooted right from the xterm. Everything came back up perfectly. Either I got really lucky or there is something waiting to bite me in the ass RSN. Disk still makes a high-pitched whine off and on...think its my Western Digital, though BSD is on my quantum. A question though, if I take out my WD (wd0) which has the boot manager on it for f1 or f5 boot options, will I still be able to boot BSD? How to go about this so I can take out wd0 but still retain my BSD disk. Keith To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message