How to create Tru64 /dev devices for DKB SCSI CDROM drives

[Geert Van Pamel]

I have added a SCSI controller with 7 CDROM drives DKB in addition to my 7 SCSI disks DKA

From the console the devices are visible

>>>show dev
dka0.0.0.2000.0 DKA0 COMPAQ BD018122C9 B016
dka100.1.0.2000.0 DKA100 COMPAQ BD018122C9 B016
dka200.2.0.2000.0 DKA200 COMPAQ BD018122C9 B016
dka300.3.0.2000.0 DKA300 COMPAQ BD018122C9 B016
dka400.4.0.2000.0 DKA400 RRD45 0436
dka500.5.0.2000.0 DKA500 COMPAQ BD018122C9 B016
dka600.6.0.2000.0 DKA600 COMPAQ BD018122C9 B016

dkb0.0.0.2002.0 DKB0 SONY CD-ROM CDU-76S 1.1c
dkb100.1.0.2002.0 DKB100 SONY CD-ROM CDU-76S 1.1c
dkb200.2.0.2002.0 DKB200 SONY CD-ROM CDU-76S 1.1c
dkb300.3.0.2002.0 DKB300 SONY CD-ROM CDU-76S 1.1c
dkb400.4.0.2002.0 DKB400 SONY CD-ROM CDU-76S 1.1c
dkb500.5.0.2002.0 DKB500 SONY CD-ROM CDU-76S 1.1c
dkb600.6.0.2002.0 DKB600 SONY CD-ROM CDU-76S 1.1c

The DKA disks are mounted to /dev/rz0 .. /dev/rz6 but how can I mount the new DKB CDROM devices??

[Vladimir Fabecic]

Looks like it is TRU64 V4.0X.
Try this:
For dkb0:
# cd /dev
# ./MAKEDEV rz8*
For dkb100:
# cd /dev
# ./MAKEDEV rz9*
.
.
.
You mount them:
For dkb0:
# mount /dev/rz8c /mnt
.
.
etc

[Geert Van Pamel]

Actually I am running Tru64 V4.0F on an AlphaServer 1000A

I have tried what you described, but still get errors

probing hose 0, PCI
probing PCI-to-EISA bridge, bus 1
probing PCI-to-PCI bridge, bus 2
bus 2, slot 0 -- pka -- QLogic ISP10x0
bus 0, slot 11 -- ewa -- DE500-AA Network Controller
bus 0, slot 12 -- pkb -- NCR 53C810
bus 0, slot 13 -- vga -- S3 Trio64/Trio32
ed.ec.eb.....ea.e9.e8.e7.e6.e5.e4.e3.e2.e1.e0.
V5.7-80, built on Mar 27 2000 at 09:43:35
...

Testing the System
Testing the Disks (read only)
dkb0.0.0.12.0 has no media present or is disabled via the RUN/STOP switch
file open failed for dkb0.0.0.12.0

cd /dev
./MAKEDEV rz8*
MAKEDEV: special file(s) for rz8*:
rz8a rrz8a rz8b rrz8b rz8c rrz8c rz8d rrz8d rz8e rrz8e rz8f rrz8f rz8g rrz8g rz8h rrz8h

mount /dev/rz8c /mnt/cd1
Error: /dev/rz8c is an invalid device or cannot be opened.

For the character special devices I do not see the SCSI ID

file *rz8?
rrz8a: character special (8/16384)
rrz8b: character special (8/16385)
rrz8c: character special (8/16386)
rrz8d: character special (8/16387)
rrz8e: character special (8/16388)
rrz8f: character special (8/16389)
rrz8g: character special (8/16390)
rrz8h: character special (8/16391)
rz8a: block special (8/16384)
rz8b: block special (8/16385)
rz8c: block special (8/16386)
rz8d: block special (8/16387)
rz8e: block special (8/16388)
rz8f: block special (8/16389)
rz8g: block special (8/16390)
rz8h: block special (8/16391)

What does mean the above message dkb0.0.0.12.0 has no media present or is disabled via the RUN/STOP switch ??

Could it be that my SCSI card NCR 53C810 is malfunctioning?
Could it mean that my SCSI disks are not recognized? How could I enable them?

Still I see them from the console:

>>>sh dev
dka0.0.0.2000.0 DKA0 COMPAQ BD018122C9 B016
dka100.1.0.2000.0 DKA100 COMPAQ BD018122C9 B016
dka200.2.0.2000.0 DKA200 COMPAQ BD018122C9 B016
dka300.3.0.2000.0 DKA300 COMPAQ BD018122C9 B016
dka400.4.0.2000.0 DKA400 RRD45 0436
dka500.5.0.2000.0 DKA500 COMPAQ BD018122C9 B016
dka600.6.0.2000.0 DKA600 COMPAQ BD018122C9 B016
dkb0.0.0.12.0 DKB0 SONY CD-ROM CDU-76S 1.1c
dkb100.1.0.12.0 DKB100 SONY CD-ROM CDU-76S 1.1c
dkb200.2.0.12.0 DKB200 SONY CD-ROM CDU-76S 1.1c
dkb300.3.0.12.0 DKB300 SONY CD-ROM CDU-76S 1.1c
dkb400.4.0.12.0 DKB400 SONY CD-ROM CDU-76S 1.1c
dkb500.5.0.12.0 DKB500 SONY CD-ROM CDU-76S 1.1c
dkb600.6.0.12.0 DKB600 SONY CD-ROM CDU-76S 1.1c
dva0.0.0.1000.0 DVA0
ewa0.0.0.11.0 EWA0 00-00-F8-04-8A-FB
pka0.7.0.2000.0 PKA0 SCSI Bus ID 7 5.57
pkb0.7.0.12.0 PKB0 SCSI Bus ID 7

[Harmanjit_1]

Hi,

If you are not able to find the corresponding device name in OS or havn't tried. Pls. try the below and find the device name.

For Tru64 V4.0x
1) scu scan edt
2) scu show edt

You can see the corresponding device name for CD and then you can mount using mount command

For Tru64 V5.x
1) hwmgr scan scsi
2) hwmgr show scsi

you can check the device name and mount it.

[Anthon Vervoort]

Hello,

Are you really sure about 7 CDroms on port B of the scsi-bus??. It's seems more a that some devices there have the same ID or there is a Termination problem.

Anthon

[Vladimir Fabecic]

What does mean the above message dkb0.0.0.12.0 has no media present or is disabled via the RUN/STOP switch ??
That means CD ROM can not read the media. Could be dirty or bad CDROM drive, bad media etc.
You may also have SCSI termination problem but does not have to be.
Could it be that my SCSI card NCR 53C810 is malfunctioning?
Could be, but I do not think so.
Please send output of:
# scu show edt
Did you boot with genvmunix kernel and rebuild the kernel after adding new SCSI controller?

[amrelsayed]

looks like you didn't rebuild your kernel, after adding new scsi controller, make a new kernel but take care if your system are cluster ASE, andto build new kernel do the following:

>>>boot boot_device -fl s -fi genvmunix

after the system had been booted and it prompt at single user mode

# bcheckrc
# cp /vmunix /vmunix.dated
#cp /usr/sys/conf/SYSTEMNAME /usr/sys/conf/SYSTEMNAME
# sizer -n test
compare the new kernal file with the old one as
# diff /usr/sys/conf/SYSTEMNAME /tmp/TEST
then add the definition of the new scsi controller to the old kernal file

# doconfig -c SYSTEMNAME

then coppy the new vmunix to /vmunix
then reboot the machine, you will see all your CD-ROMs under /dev without using ./MAKEDEV.

all my best

[Geert Van Pamel]

Thanks,

In the end I have connected the SCSI card with the 7 CD-ROM drives to an Intel Pentium Red Hat Fedora 5. And I have mounted them via Samba. This way I can access 7 CD's from the LAN.

It all went automatic. No need to do a kernel build, and much more CD formats are accepted with Red Hat than with Tru64.