From owner-freebsd-questions@FreeBSD.ORG Wed May 21 05:11:12 2003 Return-Path: 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 32D4F37B401 for ; Wed, 21 May 2003 05:11:12 -0700 (PDT) Received: from sccrmhc01.attbi.com (sccrmhc01.attbi.com [204.127.202.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D59243F3F for ; Wed, 21 May 2003 05:11:11 -0700 (PDT) (envelope-from mav@wastegate.net) Received: from wastegate.net (12-226-185-104.client.attbi.com[12.226.185.104]) by attbi.com (sccrmhc01) with ESMTP id <2003052112111000100rufh5e>; Wed, 21 May 2003 12:11:10 +0000 Received: from MOTHER (mother.wg.local [192.168.1.5]) by wastegate.net (Postfix) with ESMTP id A00A248463; Wed, 21 May 2003 08:18:10 -0400 (EDT) From: "Doug Reynolds" To: "Bsd Neophyte" , "Matthew Seaman" Date: Wed, 21 May 2003 08:14:41 -0400 Priority: Normal X-Mailer: PMMail 2000 Professional (2.20.2657) For Windows 2000 (5.1.2600;1) In-Reply-To: <20030518231813.GA97646@happy-idiot-talk.infracaninophile.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <20030521121810.A00A248463@wastegate.net> cc: "freebsd-questions@freebsd.org" Subject: Re: need help repairing this system... mount issues X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2003 12:11:12 -0000 X-List-Received-Date: Wed, 21 May 2003 12:11:12 -0000 On Mon, 19 May 2003 00:18:13 +0100, Matthew Seaman wrote: >On Sun, May 18, 2003 at 03:26:29PM -0700, Bsd Neophyte wrote: >> a previous system failed, as a result, i was forced to move the HD to a >> new system. unfortuantely, the systems are quite different. the last one >> was a full integrated cel633 and the new system is a dual p3700 with all >> individualized components. >> >> after a great deal of effort, was finally able to get my system to boot >> the root partition. i changed the type of kernel being booted to >> kernel.GENERIC and i had to really struggle to find out the new disk >> labels. >> >> well i found that now the disk was no longer da0 but da4. so i had to >> boot by entering "ufs:/dev/ad4s1a" >> >> i am able to boot, but i'm having some issues now. >> >> i've tried "mount /dev/ad4s1e /usr" but this wont work. i get the >> following error: "mount: /dev/ad4s1a: No such file or directory" >> >> i decided to look under /dev, for some reason under the disk pointers (is >> that what they are called?) only go up to da3, there is no mention of da4. >> i really don't know what to do to mount /usr. > >Uh -- which sort of disk drive do you have? IDE/ATA use the 'ad' >driver, SCSI use 'da'. You seem to be confusing the two. If you've >got SCSI disks, then you'ld have to boot from ufs:/dev/da4s1a and try >and mount /dev/da4s1e. On the other hand if you've dot IDE drives >then you should be looking for the device files matching /dev/ad4* If >the device files are missing, you can generate them from single user >mode by: > > # cd /dev > # ./MAKEDEV ad4 > >which should create a whole set of device files ad4, ad4s1, ad4s1a, >ad4s1b etc. > >However, that's unlikely as most systems can only take 4 ATA drives >(ad0, ad1, ad2 and ad3). if you have an addon Promise/Maxtor ATA card, or any addon ATA/IDE controller, it jumps to ad4 --- doug reynolds | the maverick | mav@wastegate.net