Date: Fri, 16 Mar 2007 12:55:20 -0700 (PDT) From: youshi10@u.washington.edu To: freebsd-questions@freebsd.org Subject: Re: Corrupted OS Message-ID: <Pine.LNX.4.43.0703161255200.30672@hymn07.u.washington.edu> In-Reply-To: <747837.8276.qm@web62213.mail.re1.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 16 Mar 2007, Drew Jenkins wrote: > How do I access it (through SSH) if it's unmounted? > Drew2 > > Jerry McAllister <jerrymc@msu.edu> wrote: On Fri, Mar 16, 2007 at 09:11:58AM -0700, Drew Jenkins wrote: > >> Jerry McAllister wrote: On Fri, Mar 16, 2007 at 07:16:33AM -0700, Drew Jenkins wrote: >> >>> 2Kevin Kinsey wrote:> > synch your source to 6.2 >>> > > >>> > > How? And is this necessary since it's already at 6.2? >>> > >>> > The command below, "cvsup -g -L 2 supfile". Assuming, of > course, that >>> > the supfile is valid. Is it necessary? Depends; if you're convinced >>> > that something is wrong with your current installation, then you might >>> > not need to, because you can rebuild exactly the system that you >>> > *should* have (for example, perhaps you fat-fingered a chmod or rm >>> > call?). >>> >> >>> Can you finally learn to break you lines at about 70 characters in length. >>> Having them run on long makes it much more difficult to make responses. >>> Most Email clients allow you to configure it to break lines. If yours >>> does not, just hit a a RETURN/ENTER about there each time. >> >> Yahoo's new beta must be the problem. Let's see if the old yahoo system works. Just switched back. Let me know. >> >>> That I don't quite get. If you are just adding a disk to your machine, >>> it is not likely to corript the rest of the system unless you execute >>> something on that disk. >> >> Which I did. Trust me. I've ruled everything else out. It's the HD. >> >>> When you fdisk, bsdlabel and newfs it, it is >>> wiped and the previous contents are gone. If you precede that with >>> a nice dd to overwrite initial sectors with zeros, then it is even >>> more wiped before you even get to the fdisk. >> >> Can I bsdlabel, newfs and fdisk that disk without wiping the other disks, >> and do it remotely? > > Yes. You just have to have everything on that disk unmounted. > Then you can run fdisk either directly or via sysinstall. I have > lost track of where you have stuff you want to protect, etc, etc. > But a separate disk that you want to wipe and start over again on > can be fdisked, bsdlabeled and newfsed independently from the one > you are booted from and not affect anything on any other disk and > you don't need to be able to touch it, just unmount what is > currently there. > > ////jerry > >> >>> Or are you trying to add this disk to a mirror in such a way that >>> the raid controller thinks it is the good disk and the other is >>> corrupt and tries to rebuild the mirror with the contents of the >>> added disk? That you don't want to do. >> >> That I am not doing. There are two other disks in the box that are SCSIs. >> >>> My thoughts are that something is happening that you haven't declared >>> yet. An HD does not go out and zap files. That is like saying one >>> book on a shelf skipped over and trashed the contents of another book >>> on a shelf. >> >> You misread. The files were on the new HD. The "action scripts", or s/w that calls those dbase files, are on the SCSI drives. >> >> TIA, >> Drew In true grumpier old men style: "you mount the disk son :)" (after logging in via ssh). Jerry can provide you with the RAID specific details. -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.43.0703161255200.30672>