From owner-freebsd-questions@FreeBSD.ORG  Thu Feb  5 18:00:14 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 08D7516A4CE
	for <freebsd-questions@FreeBSD.ORG>;
	Thu,  5 Feb 2004 18:00:14 -0800 (PST)
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5444643D5F
	for <freebsd-questions@FreeBSD.ORG>;
	Thu,  5 Feb 2004 18:00:02 -0800 (PST)
	(envelope-from phoffman@proper.com)
Received: from [63.202.92.155] (adsl-63-202-92-153.dsl.snfc21.pacbell.net
	[63.202.92.153])	(authenticated bits=0)
	by above.proper.com (8.12.11/8.12.8) with ESMTP id i161xvbU000417
	for <freebsd-questions@FreeBSD.ORG>;
	Thu, 5 Feb 2004 17:59:57 -0800 (PST)
	(envelope-from phoffman@proper.com)
Mime-Version: 1.0
X-Sender: phoffprop@mail.proper.com
Message-Id: <p0602045dbc48a3736106@[63.202.92.155]>
Date: Thu, 5 Feb 2004 17:59:59 -0800
To: freebsd-questions@FreeBSD.ORG
From: Paul Hoffman <phoffman@proper.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Subject: Disk no longer valid
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
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: Fri, 06 Feb 2004 02:00:14 -0000

Greetings. After rebooting a system that had been up for quite some 
time, I could not get the second drive (da1) to mount. The drive 
worked fine before I rebooted. dmesg reported:

. . .
da1s4: rejecting partition in BSD label: it isn't entirely within the slice
da1s4: start 63, end 71132959, size 71132897
da1s4d: start 0, end 71132959, size 71132960
. . .

When I tried to access the disk, dmesg said:

. . .
(da1:ahc0:0:1:0): SCB 0x36 - timed out
>>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<<
ahc0: Dumping Card State while idle, at SEQADDR 0x9
Card was paused
ACCUM = 0x0, SINDEX = 0x1e, DINDEX = 0xe4, ARG_2 = 0x0
HCNT = 0x0 SCBPTR = 0x17
SCSIPHASE[0x0] SCSISIGI[0x0] ERROR[0x0] SCSIBUSL[0x0]
[ lots more debugging info]
>>>>>>>>>>>>>>>>>
sg[0] - Addr 0x706d000 : Length 4096
sg[1] - Addr 0xdb6e000 : Length 4096
(da1:ahc0:0:1:0): Queuing a BDR SCB
(da1:ahc0:0:1:0): no longer in timeout, status = 34a
Feb  5 00:01:03 above /kernel: <<<<<<<<<<<<<<<< Dump Card State 
Ends >>>>>>>>>>>
>>>>>>>
(da1:ahc0:0:1:0): Invalidating pack
. . .

The drive was inaccessible. I rebooted again. dmesg still says:
. . .
da1s4: rejecting partition in BSD label: it isn't entirely within the slice
da1s4: start 63, end 71132959, size 71132897
da1s4d: start 0, end 71132959, size 71132960
. . .

but now I can access the disk fine.

Can I fix the drive without losing the information on it? If so, how?

--Paul Hoffman