need help repairing this system... mount issues

[Doug Reynolds]

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 at wastegate.net