From owner-freebsd-questions Thu Aug 17 5:32: 9 2000 Delivered-To: freebsd-questions@freebsd.org Received: from oak.drexeltech.com (oak.drexeltech.com [64.39.31.169]) by hub.freebsd.org (Postfix) with ESMTP id F3C1137B6A5 for ; Thu, 17 Aug 2000 05:31:59 -0700 (PDT) Received: from elmo.johnturner.com (3ff8e366.dsl.flashcom.net [63.248.227.102]) by oak.drexeltech.com (8.9.3/8.9.3) with ESMTP id HAA19894 for ; Thu, 17 Aug 2000 07:40:56 -0500 (CDT) (envelope-from john@johnturner.com) Message-Id: <4.3.2.7.0.20000817081433.00afed08@mail.johnturner.com> X-Sender: jturner@mail.johnturner.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 17 Aug 2000 08:31:55 -0400 To: freebsd-questions@freebsd.org From: John Turner Subject: HELP: disk formatting and partitioning Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello - I'm building a server with 4 36Gb SCSI drives. drive0 is the main boot drive. drive1 is the secondary boot drive (more about that in second) drive2 is dedicated to logs drive3 is also dedicated to logs By "secondary boot drive" I mean that it is a duplicate of drive0. My company's policy is to keep an offline copy of the main boot drive in all servers, if something should happen to the boot drive, the server can be brought up on the second boot drive using the FreeBSD boot manager. I've read the man pages for newfs, disklabel, mount, and fsck many, many, many times. I've been through the disk tutorial at freebsd.org. I've been through both disk tutorials at mostgraveconcern.com/freebsd (thanks Dan!). This is the first time my company has had to build a server requiring so much space for logs (almost 80Gb). I still cannot get this server ready. I am trying to do this: 1) install FreeBSD from CD-ROM onto drive0 using a normal partition scheme (/, /usr, /var, /tmp, etc). 2) install FreeBSD from CD-ROM onto drive1 using same partition scheme and options as the install on drive0. 3) Create drive2 and drive3 as dedicated drives mounted at separate mount points on drive0 (/mnt/log1 and /mnt/log2). Verify that log1 and log2 are available to the OS on drive0 after a reboot. 4) Reboot, and come up on drive1 using FreeBSD boot manager. Verify that drive2 and drive3 can be mounted and that both are accessible to the backup system drive (drive1), at the same mount points as drive0. After many, many tries, several reinstalls, and even a couple SCSI low-level formats, I am still having problems. Can anyone provide me with some steps that will help me reach my objective? Are there any other online disk management tutorials that are more recent (the one at freebsd.org is from 1997, and after following its command line instructions, the machine failed to boot, even from CD-ROM!!) or deal with situations that aren't workstation-based (adding a second drive, IDE, etc)? I simply want the option to boot from either drive0 or drive1 using the FreeBSD boot manager (both drives are identical thanks to nightly cron jobs running dd) and I would like drive2 and drive3 to be available no matter which boot drive is active, at the same mount points. I can get the server running on drive0, with drive2 and drive3 working correctly. However, the same drives cannot be mounted when booting to drive1 (I get all sorts of fsck messages, bad superblock errors, etc). Thanks in advance for any help, and I will gladly create a step-by-step tutorial once I get it up and running if anyone can shed some light on setting these drives up correctly. - John Turner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message