Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 12 Jun 2008 22:09:33 -0400
From:      Steve Bertrand <steve@ibctech.ca>
To:        Dan Nelson <dnelson@allantgroup.com>
Cc:        freebsd-questions@freebsd.org, Glenn Gillis <glenn@elaw.org>
Subject:   Re: Tried to symlink /etc to another disk, now stuck
Message-ID:  <4851D6DD.8090801@ibctech.ca>
In-Reply-To: <4851D328.8060107@ibctech.ca>
References:  <84a992f30806121702r39f132a8y11f8e410221e132c@mail.gmail.com>	<20080613012029.GA16341@dan.emsphone.com> <4851D328.8060107@ibctech.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
Steve Bertrand wrote:
> Dan Nelson wrote:

> I'm off to try it. I've got a system here with a da device. I'll fsck up 
> /etc/fstab, reboot, and report back with the appropriate mountroot> 
> prompt entry...

# cat /etc/fstab

# Device                Mountpoint      FStype  Options         Dump 
Pass#
/dev/da0a               /               ufs     rw,noatime      1       1
md                      /tmp            mfs     rw,-s32M,nosuid,noatime 
0       0

(..snip..)

..change /etc/fstab to mount root to /dev/ad15a, reboot:

mountroot>

# mountroot>ufs:/dev/da0a {ENTER}

...machine boots up.

To the OP...if you know what your disk type is, you CAN get it to 
continue to mount root at the mountroot prompt.

Furthering that, you can also fsck and mount your other disk mountpoints 
in order to gain access to your editing binaries.

There is no need to use an external resource to boot the machine from if 
you are already aware that the only thing that got fsck'd up is the 
mountpoints in the fstab (or, like in this case, the file was 
unavailable entirely). The disk structure is still the same, and the 
system can see this with manual intervention.

OP: at the mountroot> prompt, try this: ufs:/dev/ad0s1a

and see if you get anywhere.

Steve



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4851D6DD.8090801>