the wonders of SCSI

[Conor P. Cahill]

In article <1990May27.092900.828 at wolves.uucp> ggw at wolves.UUCP (Gregory G. Woodbury) writes:
>These drives fsck and mount quite well.  (even if the /etc/partitions no
>longer correctly ids the drives! HELP on recovery for /etc/partitions is
>also needed.)

There is an option on the mkpart(1M) command which builds a copy of 
the /etc/partitions from the vtoc itself.  See the man page for more
info.

>  The maxtor and adaptec 1542A (intr and dma and such are
>all correct.) are in place and work (sort of!).  I can mkfs/fsck/fsstat
>the scsi drive (as /dev/dsk/c1d0s0 or c1d0p0) BUT! no variant of
>/etc/mount will let me mount the device any where on the filesystem!
>
>	mount: /dev/dsk/c1d0s0 no such device

"no such device" is the ENXIO error number which usually means the 
device driver for /dev/dsk/c1d0s0 is not configured into the kernel.

I would verify the major/minor device number for the c1d0s0 entry.

I find it hard to believe that the fsck actually worked on the 
disk drive through that /dev entry (c1d0s0).

Another possibility may be that you set up the file system to be a 2K
file system and the 2K stuff isn't compiled into the kernel.

>stringing the mount command is non-revealing.  It doesnt even go look at
>the device before telling that.

What mount does do is pass you arguments as appropriate to the mount 
system call.  It does not directly access your file system.



-- 
Conor P. Cahill            (703)430-9247        Virtual Technologies, Inc.,
uunet!virtech!cpcahil                           46030 Manekin Plaza, Suite 160
                                                Sterling, VA 22170