On Tue, 3 Feb 2004 23:05:05 -0800 (PST) "Scott I. Remick" <[EMAIL PROTECTED]> probably wrote:
> --- Sergey 'DoubleF' Zaharchenko <[EMAIL PROTECTED]> wrote:
> > Sorry, you were recovering an 80G disk, and now you say the 80G has 4.9
> > on it. Did you erase anything? Is this a remote machine?
> No, it was not the drive that had the OS on it. It was originally mounted as
> /data on a system that had FreeBSD 5.1 installed on a separate drive. We
> determined the 80GB was UFS1. You wanted to try troubleshooting using
> FreeBSD 4.9, so I obtained a spare system which I installed FreeBSD
> 4.9-RELEASE on. I then moved the 80GB from the 5.1 system (which is actually
> 5.2 now) and installed it into the 4.9 system on the 2nd controller. So now
> 4.9 is installed on a 20GB on /dev/ad0, and our problem 80GB is /dev/ad2.
Thank you for the explanation.
> > You can boot 4.9, right? Examine the output of disklabel ...s1 and
> > ...s1c to make heart feel better.
> bash-2.05b# disklabel /dev/ad2s1
[snip]
> 8 partitions:
> # size offset fstype [fsize bsize bps/cpg]
> c: 156344517 0 unused 0 0 # (Cyl. 0 - 9731*)
> e: 156344517 0 4.2BSD 2048 16384 89 # (Cyl. 0 - 9731*)
> bash-2.05b# disklabel /dev/ad2s1c
[snip]
> 8 partitions:
> # size offset fstype [fsize bsize bps/cpg]
> c: 156344517 0 unused 0 0 # (Cyl. 0 - 9731*)
> e: 156344517 0 4.2BSD 2048 16384 89 # (Cyl. 0 - 9731*)
Good:)
Well, as it's UFS1 as we've figured out, the next logical thing would be to
try mounting /dev/ad2s1c r/o, and if that fails, try fscking it.
--
DoubleF
The faster we go, the rounder we get.
-- The Grateful Dead
pgp00000.pgp
Description: PGP signature
