Gidday all,
I received 11 relies, including 4 within 15 minutes, who all provided pretty
much the same answer with minor variances on how to including suggestions as
to why. Since this machine is a member of a cluster and one of the steps in
upgrading the cluster software from 1.5 --> 1.6 involved resetting the scsi
IDs for the disks I suspect this caused the tape drive reset. (Thanks to
Alan and Irvan who alerted me to this)
Essentially
cd /dev
rm *rmt*
./MAKEDEV tzxx (where xx are found from (bus * 8) + target-id)
Dr Tom Blinn provided the easiest option for finding the correct numbers.
"Use "sizer -n FOO" to create /tmp/FOO.devs. Check the files for the
devices required."
This has solved the problem!
Thanks to all those who replied
Wayne
-----Original Message-----
From: Blom, Wayne [mailto:Wayne.Blom_at_au.faulding.com]
Sent: Thursday, August 10, 2000 6:38 PM
To: True64 Unix Managers (E-mail)
Subject: Upgrade 4.0e --> 4.0f caused lost devices
Gidday all,
Last night we upgraded from 4.0e to 4.0f. When the machine was up and
running again the disk drives were all available but the tape units were
not.
The device files were still there but they did not point to the hardware.
I ran a doconfig, no good.
I ran a MAKEFILE std which created new device files for the tapes.
Originally there were the following devices;
/dev/nrmt0h
/dev/nrmt1h
/dev/nrmt2h
/dev/nrmt3h
NOW...
/dev/nrmt4h ! equals what was 0
/dev/nrmt5h ! equals what was 1
/dev/nrmt6h ! equals what was 2
/dev/nrmt7h ! equals what was 3
What has happend?
and more importantly how do I get it back to normal?
Does anyone have any suggestions??
Thanks
Wayne Blom
System Specialist
Technical Development Healthcare
F H Faulding & Co Limited
Ground Floor
1 Station St
Hindmarsh SA 5007
Ph: +61 8 8241 8334
FAX: +61 8 8241 8357
Mobile: +61 0419 808 496
Email: wayne.blom_at_au.faulding.com
Received on Fri Aug 11 2000 - 01:42:16 NZST