Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-spam!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!hpcea!hplchm!cjames
From: cjames@hplchm.UUCP
Newsgroups: comp.sys.hp
Subject: Re: hp9000 internal disk drives
Message-ID: <1390001@hplchm.HP.COM>
Date: Wed, 18-Nov-87 12:15:15 EST
Article-I.D.: hplchm.1390001
Posted: Wed Nov 18 12:15:15 1987
Date-Received: Sat, 21-Nov-87 14:20:52 EST
References: <4570@iuvax.UUCP>
Organization: HP Labs Chemical Systems Dept, Palo Alto
Lines: 29

>I ran mkdev with the correct lines
>uncommented, and the files fd.0, fd.1, rfd.0, and rfd.1 were created
>in the /dev directory.  I then tried to run mediainit on one of the 
>drives, but got the error message "no such device". 

This is almost always caused either by having the address set wrong on the
device, by having it on the wrong HPIB, or by having two devices at the
same address on one bus.

Here's an example from of two "raw" disks I use:
crw-rw-rw-   1 root     other      4 0x0e0100 Sep 11 16:14 1s0
crw-rw-rw-   1 root     other      4 0x070100 Jun  2 12:14 701s0

The 1st, named "1s0" is HPIB 14 ("0e"), address 1 ("01"), drive 0 ("00"). 
The 2nd, named "701s0" is HPIB 7 ("07"), address 1 ("01"), drive 0 ("00").

Other things to watch for: Did you change the device's address when it
was on?  Most devices only look at their address switches at power-up, so
you can only change the address when they are off.  If you accidentally
put two devices at the same address, usually BOTH will detect the error
and go off-line; both may have to be turned off and back on before the
system will work again.

Hope this helps!

Craig James

The above opinions are mine and should not be construed as advice from
the Hewlett-Packard Company.