From owner-freebsd-questions Mon Oct 22 16:39:26 2001 Delivered-To: freebsd-questions@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id D8AC137B407 for ; Mon, 22 Oct 2001 16:39:21 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 23 Oct 2001 00:39:21 +0100 (BST) To: Joshua Holland Cc: questions@FreeBSD.org Subject: Re: mount root fail In-Reply-To: Your message of "Mon, 22 Oct 2001 17:24:18 CDT." Date: Tue, 23 Oct 2001 00:39:20 +0100 From: Ian Dowse Message-ID: <200110230039.aa57644@salmon.maths.tcd.ie> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , Joshua Holland writes: >first disk is now being recognized as ad6. I can only mount it as >read only now (ufs:ad6s1a), and I can't run fsck, which is still >looking for ad4. I can't change fstab since it's ro. Also, ad6 is >not in /dev (nor the second disk, which is ad10). What's going on? >Why did ad4 become ad6? Is there a way to get it back to ad4? A useful trick to mount a root filesystem read-write when you don't have a device for it in /dev is to create a device node on a small MFS filesystem. e.g: # mount_mfs -T fd1440 none /mnt # cd /mnt # sh /dev/MAKEDEV ad6s1a # fsck /mnt/ad6s1a # mount -u -o rw /mnt/ad6s1a / # cd /dev # sh MAKEDEV ad6s1a Then you can fsck and mount other filesystems, and fix the broken /etc/fstab entries. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message