One more Question though WAS RE: SUMMARY RE: Restoring a root dis k - I can boot to it!

From: <Cohen.Jessica_at_ic.gc.ca>
Date: Thu, 05 Feb 2004 16:32:58 -0500

One of the things that I still need to recreate is the /dev/cport/scp0 and
/dev/cport/scp1 files so that I can use KZPCCAgent to look remotely at my
KZPCC-CE raid controllers.

This is what I see when I type hwmgr -view devices:

 HWID: Device Name Mfg Model Location
 
----------------------------------------------------------------------------

--
   87: scp                           (unknown)        (unknown)
   88: /dev/kevm                                      
  108: /dev/disk/dsk0c               i2o_bs           iop-0-dev-3
  144: /dev/disk/floppy0c            3.5in floppy     fdi0-unit-0
  149: /dev/disk/cdrom0c    COMPAQ   CDR-8435         bus-1-targ-0-lun-0
  151: /dev/ntape/tape0     DEC      TZ89     (C) DEC bus-0-targ-4-lun-0
  153: (unknown)                     I2O              i2o0_cp
  154: (unknown)                     I2O              i2o1_cp
  164: /dev/ntape/tape1     DEC      TZ89     (C) DEC bus-0-targ-5-lun-0
  165: /dev/disk/dsk1c               i2o_bs           iop-0-dev-4
  166: /dev/disk/dsk2c               i2o_bs           iop-1-dev-1
  167: /dev/disk/dsk3c               i2o_bs           iop-1-dev-2
  168: /dev/disk/dsk4c               i2o_bs           iop-1-dev-3
I looked at our other ES40, and see that on that one the raid controllers
(also KZPCC-CE)are /dev/cport/scp1 and /dev/cport/scp0.  Can anyone tell me
how I recreate these devices?  With a more specific dsfmgr flag or with
hwmgr I guess?
Thanks,
Jessica
-----Original Message-----
From: Cohen, Jessica: DGRB 
Sent: Thursday, February 5, 2004 3:11 PM
To: tru64-unix-managers_at_ornl.gov
Subject: SUMMARY RE: Restoring a root disk - I can boot to it!
Sorry for the much-delayed summary
Basically we used dn_setup -clean, dn_setup -init, and dfsmfr -K to redo our
devices directory, at which point I was able to see the disks with disklabel
again.  The first time I still got strange results, but when I booted to the
disk by specifying it on the >>> line, and left the bootdef_dev parm empty,
it worked better.  Once I could see the disks with disklabel it was
straightforward recreating all my file domains.
Thanks to Nilesh M. Virani, John Lanier, Derek Haining, Dr. Thomas Blinn,
and Charles Ballowe for their help.
-----Original Message-----
From: Cohen, Jessica: DGRB 
Sent: Tuesday, February 3, 2004 1:43 AM
To: tru64-unix-managers_at_ornl.gov
Subject: Restoring a root disk - I can boot to it!
Hi, today we rewired our disk arrays on an ES40.  We didn't actually change
the root disk, although it was physically moved to another shelf, it is on
the same KZPCC raid controller and the same bus on that raid controller.
When I type show dev at the >>> prompt, I can see all 5 of our LUN's.  I
know from a hardware perspective which one is our boot disk
(dzb536.0.0.2004.0), and if I set bootdef_dev to this disk, I can
successfully boot to single user mode.
However, I can't tell which logical disk number this boot disk is.
I see root_device when I try df -k, and I tried using advscan on each of the
disks I see in the /dev/disk directory, and can't find the disk, or find the
usr_domain which is on the same disk.
I do have vrestores of /, /usr, and /var but when I boot from the 5.1 CD, I
can't see any of the disks, /dev/disk only contains floppy and cd's.  
When I boot from the boot disk I have /dev/disk entries from 0 to 5, even
though I only have 5 disks.
Can anyone tell me how I can tell what disk number I am booting off of, and
then specifically how I go about changing the domains so that I am mounting
/ and /usr and /var from the right disk?
Thanks,
Jessica Cohen

Received on Thu Feb 05 2004 - 21:34:32 NZDT