From owner-freebsd-questions@FreeBSD.ORG  Tue Jan  6 08:32:33 2004
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 5ABF916A4CE
	for <freebsd-questions@freebsd.org>;
	Tue,  6 Jan 2004 08:32:33 -0800 (PST)
Received: from web41113.mail.yahoo.com (web41113.mail.yahoo.com
	[66.218.93.29])	by mx1.FreeBSD.org (Postfix) with SMTP id 0480D43D1D
	for <freebsd-questions@freebsd.org>;
	Tue,  6 Jan 2004 08:32:32 -0800 (PST)
	(envelope-from scott@sremick.net)
Message-ID: <20040106163231.34956.qmail@web41113.mail.yahoo.com>
Received: from [199.172.45.60] by web41113.mail.yahoo.com via HTTP;
	Tue, 06 Jan 2004 08:32:31 PST
X-RocketYMMF: siremick
Date: Tue, 6 Jan 2004 08:32:31 -0800 (PST)
From: "Scott I. Remick" <scott@sremick.net>
To: Sergey 'DoubleF' Zaharchenko <doublef@tele-kom.ru>
In-Reply-To: <20040106183141.7fe07b82.doublef@tele-kom.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: freebsd-questions@freebsd.org
Subject: Re: "Cannot find file system superblock" error - how to recover?
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: scott@sremick.net
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jan 2004 16:32:33 -0000

--- Sergey 'DoubleF' Zaharchenko <doublef@tele-kom.ru> wrote:
> Sorry that was to be $ bsdlabel -R -n /dev/ad6s1c dislabel.ad6s1c.new :(

No worries... I figured it out :)

> Indeed it's not like in 4.x, where they were the same. And what about 
> 
> # ls -l /dev/ad6s1a /dev/ad6s1b
> 
> (these minor numbers don't seem to be in order).

Neither exists. Just so you know: My motherboard (Asus A7V133) has 2
integrated IDE controllers. Besides the native VIA controller there is a
Promise ATA100. The following are the relevant snippets from dmesg:

atapci0: <VIA 82C686B UDMA100 controller> port 0xd800-0xd80f at device 4.1
on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0

atapci1: <Promise PDC20265 UDMA100 controller> port
0x8000-0x803f,0x8400-0x8403,0x8800-0x8807,0x9000-0x9003,0x9400-0x9407 mem
0xd4000000-0xd401ffff irq 10 at device 17.0 on pci0
ata2: at 0x9400 on atapci1
ata3: at 0x8800 on atapci1

ad4: 19595MB <MAXTOR 6L020L1> [39813/16/63] at ata2-master UDMA100
ad6: 76345MB <MAXTOR 6L080J4> [155114/16/63] at ata3-master UDMA100
acd0: CDROM <CRD-8400B> at ata0-master PIO4
Mounting root from ufs:/dev/ad4s1a
cd0 at ata0 bus 0 target 0 lun 0
cd0: <LG CD-ROM CRD-8400B 1.03> Removable CD-ROM SCSI-0 device
cd0: 16.000MB/s transfers
cd0: cd present [279440 x 2048 byte records]

(yes, I use atapicam)

and ls /dev/ad*:

crw-r-----  1 root  operator    4,  10 Dec 29 08:11 /dev/ad4
crw-r-----  1 root  operator    4,  12 Dec 29 08:11 /dev/ad4s1
crw-r-----  1 root  operator    4,  14 Dec 29 03:11 /dev/ad4s1a
crw-r-----  1 root  operator    4,  15 Dec 29 08:11 /dev/ad4s1b
crw-r-----  1 root  operator    4,  16 Dec 29 08:11 /dev/ad4s1c
crw-r-----  1 root  operator    4,  17 Dec 29 03:11 /dev/ad4s1d
crw-r-----  1 root  operator    4,  18 Dec 29 03:11 /dev/ad4s1e
crw-r-----  1 root  operator    4,  19 Dec 29 03:11 /dev/ad4s1f
crw-r-----  1 root  operator    4,  13 Dec 29 08:11 /dev/ad6
crw-r-----  1 root  operator    4,  20 Dec 29 08:11 /dev/ad6s1
crw-r-----  1 root  operator    4,  21 Dec 29 08:11 /dev/ad6s1c
crw-r-----  1 root  operator    4,  22 Dec 29 08:11 /dev/ad6s1e

Let me know if you come up with any suggestions on what I should try next.
Thanks ever so much!