-----BEGIN PGP SIGNED MESSAGE-----
Sorry for the delayed summary, I first checked all answer to
come up with the notion that I really have a hw fault in this
case.
Answers from:
alan_at_nabeth.cxo.dec.com,
Dr. Tom Blinn, 603-884-0646" <tpb_at_doctor.zk3.dec.com>,
Morgan Rogers <Morgan.Rogers_at_imserv.invensys.com>
appended.
Thanks for the answers anyway, sure someone will be able to use it.
BTW, it is a SCSI disk on the primary SCSI controller,
and neither scu nor hwmgr were able to see the disk,
although it shows for "show dev" before booting.
|=>
|=> -----BEGIN PGP SIGNED MESSAGE-----
|=>
|=>
|=> I am not able to find the correct/simple way to create the device
|=> files for new disks under TU64v5.0a.
|=>
|=> The archive also seems to show questions but provides no working
|=> answers for me.
|=>
|=> in the boot-prom mode I can see my second disk on amn XP1000, but
|=> the booted system cannot see it, not even in scu show edt as long
|=> as the device files do not exist.
|=>
|=> So how do I add new disks to a running TU64v5.0a system ?
|=>
|=> (With other systems of this type I simply removed / by rm -rf /*
|=> and reinstalled the complete system, which worked but is not the
|=> recommended way, I'd guess.)
|=>
|=> The problem seems to be related to the installation process
|=> keeping and restoring an old hardware config before starting a
|=> new OS installation, since without removing the OS beforehand I
|=> was not even able to get teh new disks on a newly installed
|=> system !
|=>
|=>
|=>
|=> Tschüß,
|=> Dieter
|=>
|=> _____________________________*__________________________________
|=> / * dieter.meinert_at_aip.de \
|=> \ Dieter Meinert (- **
http://www.aip.de/~dieter/ \
|=> \__________________A______*__*___________________________________/
|=> (public pgp key from
http://www.aip.de/~dieter/)
|=>
|=> -----BEGIN PGP SIGNATURE-----
|=>
|=> iQCVAwUBOfB41fYksnFoaQ6JAQHd/QQA3PR56eWLegTuDMs7nogASMt63c7tRmSy
|=> lHUtuP1C7QnI+s2aWapRJYz1FhDy3RMXPZMVQWmANMRkWoSY5baGLdl+fCXqW339
|=> ccKvQqpMDx9/68qN6O+DJr1W3UvFmz/cc+MxG/XIDWrG4ty30jZXU7AvyFxjcENd
|=> 5H3h0N83EFA=
|=> =bQII
|=> -----END PGP SIGNATURE-----
|=>
Tschüß,
Dieter
_____________________________*__________________________________
/ * dieter.meinert_at_aip.de \
\ Dieter Meinert (- **
http://www.aip.de/~dieter/ \
\__________________A______*__*___________________________________/
(public pgp key from
http://www.aip.de/~dieter/)
From: alan_at_nabeth.cxo.dec.com
What kind of disk? What kind of I/O adapter?
Assuming SCSI... Use scu(8) to scan the particular bus
to see if the driver can see the device. Then use the
hardware manager (hwmgr) to see if sees the device. If
not, try an explicit scan. If that works, then I think
you can use dsfmgr to create the special files. These
commands have manual pages and may even be documented in
the system management guide.
If scu(8) does see the disk and hwmgr(8) doesn't, then
you may need to create a /etc/ddr.dbase entry for the
device. Previously only used the SCSI bus, target and
LUN to determine device uniqueness. V5 also depends on
the drive serial number (as kept in the Inquiry pages).
3rd party drives that don't have one of these, or don't
use that is unique, could cause problems. There have
been summaries (one fairly recent I think), where this
problem occured on RAID arrays. The individual device
solution should be much the same.
If the scu(8) can't see the drive, the problem is pretty
far down in the SCSI driver.
From: "Dr. Tom Blinn, 603-884-0646" <tpb_at_doctor.zk3.dec.com>
If your system is not AUTOMATICALLY CREATING all of the necessary
device special files during the system startup, then something is
quite wrong.
As the system transitions from single user mode to multiuser mode,
or if you run the "bcheckrc" script in single user mode, a set of
steps are taken to find every active disk and assure that device
special files exist.
If this isn't happening, then perhaps there is something wrong with
the hardware.
The "scu show edt" has NOTHING to do with the device special files,
it has everything to do with what devices are seen at boot time.
If your disk isn't showing up there, something else is wrong.
Tom
Dr. Thomas P. Blinn + UNIX Software Group + Compaq Computer Corporation
110 Spit Brook Road, MS ZKO3-2/W17 Nashua, New Hampshire 03062-2698
Technology Partnership Engineering Phone: (603) 884-0646
Internet: tpb_at_zk3.dec.com Compaq's Easynet: alpha::tpb
ACM Member: tpblinn_at_acm.org PC_at_Home: tom_at_felines.mv.net
From: Morgan Rogers <Morgan.Rogers_at_imserv.invensys.com>
Have a look at 'hwmgr'.
It will be something like 'hwmgr -scan scsi'
This pretty much replaces scu, should create your device files too.
Morgan.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: latin1
iQCVAwUBOffwwvYksnFoaQ6JAQHg8QQA2ugj+LvraafJbW86dYHUs63fd7Oj6sux
OM5QaggqC/3vY+3cplw1CkHd1fY6g+Ami9kSerYECoTORXvKribwS0DYOdcsRq93
P8wyb6yLQOE0QyZY/AiEWP0Ot37KKbi3Dc169ozTsgfnfdzlfX6cyIf20NWNWoTt
AgwGZTPphCg=
=5Df8
-----END PGP SIGNATURE-----
Received on Thu Oct 26 2000 - 08:54:05 NZDT