From owner-freebsd-questions@FreeBSD.ORG Tue Jul 25 01:19:40 2006 Return-Path: X-Original-To: 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 D070716A4DE for ; Tue, 25 Jul 2006 01:19:40 +0000 (UTC) (envelope-from joshua.lewis@familyfunzone.net) Received: from smtpout13-02.prod.mesa1.secureserver.net (smtpout13-02.prod.mesa1.secureserver.net [68.178.232.6]) by mx1.FreeBSD.org (Postfix) with SMTP id 606C543D45 for ; Tue, 25 Jul 2006 01:19:40 +0000 (GMT) (envelope-from joshua.lewis@familyfunzone.net) Received: (qmail 19623 invoked from network); 25 Jul 2006 01:19:39 -0000 Received: from unknown (HELO gem-wbe01.mesa1.secureserver.net) (64.202.189.26) by smtpout13-02.prod.mesa1.secureserver.net with SMTP; 25 Jul 2006 01:19:39 -0000 Received: (qmail 12968 invoked by uid 99); 25 Jul 2006 01:19:39 -0000 Date: Mon, 24 Jul 2006 18:19:39 -0700 From: Joshua Lewis To: freebsd-questions@freebsd.org Message-ID: <20060724181939.e72c8bd2fa3c8298c4bf39a8c4c61b77.cfec2272ae.wbe@email.secureserver.net> User-Agent: Web-Based Email 4.3.16 X-Originating-IP: 64.57.168.66 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Mount an unknown drive X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jul 2006 01:19:40 -0000 I have a server that has been inoperative for the last few months (FreeBSD 6.0). I decided to turn on the system and it goes right to a boot prompt. So I downloaded FreeSBIE and am trying to mount the old drive to see if there is any data on the drive worth saving. When I try to mount /dev/ad0s1f /mnt I get a device busy message. Am I even trying to mount the correct slice. I have tried s1a - s1f. Is it possible it was already mounted and that is why it says it is busy. There is nothing in dmesg that shows asd0*. Sincerely, Joshua Lewis