I got some sleep and thought about it some more and was wondering if
it is possible that FreeSBIE (Running FreeBSD 5.3) simply can't read
my drive that was formated durring an install of 6.0. Or has it not
changed enough to cause that problem?
There is a:
/dev/ad0s1a
/dev/ad0s1b
/dev/ad0s1c
/dev/ad0s1d
/dev/ad0s1e
/dev/ad0s1f
I treid to mount all of those last night.
mount /dev/ad0s1f /mnt
I also tried
mount -t ufs /dev/ad0s1f /mnt
Same results every time. The device is busy.
Sincerely,
Joshua Lewis
-------- Original Message --------
Subject: Re: Mount an unknown drive
From: Lowell Gilbert <[EMAIL PROTECTED]>
Date: Tue, July 25, 2006 10:22 am
To: Joshua Lewis <[EMAIL PROTECTED]>
Cc: freebsd-questions@freebsd.org
Joshua Lewis <[EMAIL PROTECTED]> writes:
> 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*.
Look in /dev for ad*.
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
