From owner-freebsd-questions Sun Sep 9 22:22:49 2001 Delivered-To: freebsd-questions@freebsd.org Received: from hobbiton.shire.net (frogmorton.shire.net [204.228.145.136]) by hub.freebsd.org (Postfix) with ESMTP id 8224037B409 for ; Sun, 9 Sep 2001 22:22:39 -0700 (PDT) Received: from nh-merrimack1a-425.bur.adelphia.net ([24.49.145.169] helo=[192.168.99.123]) by hobbiton.shire.net with asmtp (Exim 3.22 #6) id 15gJVM-0007nK-00; Sun, 09 Sep 2001 23:21:08 -0600 Date: Mon, 10 Sep 2001 01:21:25 -0400 From: "Chad Leigh, Shire.Net LLC" Reply-To: chad@shire.net To: "freebsd-questions@freebsd.org" Cc: "chad@shire.net" Subject: Re: CCD question Message-ID: <3652472609.1000084885@[192.168.99.123]> In-Reply-To: <3645783421.1000078196@[192.168.99.123]> X-Mailer: Mulberry/2.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Doing some more research, it appears that the in-memory disk label and the on disk label are not in synch. I had a third disk that was never part of the ccd, just a regular ufs disk, on the controller, that was not mountable either. Using disklabel to examine it had the same symptoms as the 2 ccd disks in question. using % disklabel da2 would not work but % disklabel /dev/da2 would. I did an fsck on this non ccd disk and now it mounts just fine. But of course I cannot fsck the ccd component disks. Here is an example of the in memory and on disk abels being different (notice the c partition in the -r raw on disk label): megumi# disklabel /dev/da0 # /dev/da0: type: SCSI disk: QUANTUM label: XP39100W flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 1106 sectors/unit: 17781520 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 17781520 0 unused 0 0 # (Cyl. 0 - 1106*) megumi# disklabel -r /dev/da0 # /dev/da0: type: SCSI disk: QUANTUM label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 1106 sectors/unit: 17781520 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 17781520 0 4.2BSD 0 0 0 # (Cyl. 0 - 1106*) Warning, partition c is not marked as unused! Warning, An incorrect partition c may cause problems for standard system utilities megumi# ---------------------- Does this matter? I need to get this "ccd" disk back and running asap. Thanks Chad --On Sunday, September 09, 2001 11:29 PM -0400 "Chad Leigh, Shire.Net LLC" wrote: > I have a pair of disks that were mirrored together with ccd. > > The machine started to have problems so I rebuilt the machine and > installed 4.4-RC4 on it from scratch. The normal use disks are on a > different controller and are not the previous ccd disks. The previous > ccd disks have not been touched. > > I added the pseudo-device ccd stuff to the kernel and rebuilt the kernel. > > I did the MAKEDEV ccd0 stuff in /dev > > When I try and use ccdconfig to configure a ccd, using just one disk (ie, > simulating a recovery) I get the following error, which I don't > understand: > > megumi# ccdconfig ccd0 32 0 /dev/da0c > ccdconfig: ioctl (CCDIOCSET): /dev/ccd0c: Invalid argument > megumi# > > The same thing happens if I put in the MIRROR flag and both disks. > > The disks should still be disklabeled correctly etc from the old machine. > > Any hints on the meaning of the above message would be appreciated. > > thanks > Chad > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message