Trouble installing new disk in 5.1A : cannot create device files

From: Richard Paladino (paladino_at_iii.com)
Date: 08/11/04

  • Next message: Michael W: "Large File Copy" 
    Date: Wed, 11 Aug 2004 10:52:47 -0700
To: tru64-unix-managers@ornl.gov

    Hi All,

    This is my first time posting to this list... Thanks in advance for your help.

    I am having a problem installing a new disk on an Alpha DS10 running
    5.1A. Most of the machines I administer still run 4.0f, so I'm a bit of a
    novice with 5.1A's hardware management tools.

    The disk is recognized at the firmware level but does not show up when the
    system is booted into single user mode. The new disk is an LVD 18GB and is
    installed on a 2nd controller. The new disk is internal while the other 4
    are in a cabinet.

    Here is the firmware display:

    >>>show dev
    dka0.0.0.14.0 DKA0 SEAGATE ST39236LW 0010
    dka100.1.0.14.0 DKA100 SEAGATE ST39236LW 0010
    dka200.2.0.14.0 DKA200 SEAGATE ST39236LW 0010
    dka300.3.0.14.0 DKA300 SEAGATE ST39236LW 0010
    dkb0.0.0.15.0 DKB0 SEAGATE ST318406LC 010A
    dqa0.0.0.13.0 DQA0 Compaq CRD-8402B 1.03
    dva0.0.0.0.0 DVA0
    mka600.6.0.14.0 MKA600 HP C1537A L005
    ewa0.0.0.9.0 EWA0 00-10-64-30-15-F7
    ewb0.0.0.11.0 EWB0 00-10-64-30-16-34
    pka0.7.0.14.0 PKA0 SCSI Bus ID 7 5.57
    pkb0.7.0.15.0 PKB0 SCSI Bus ID 7

    It's clearly being recognized as DKB0 on PKB0.

    However, in single-user mode:

    # /sbin/scu show edt

    CAM Equipment Device Table (EDT) Information:

         Bus/Target/Lun Device Type ANSI Vendor ID Product ID Revision N/W
         -------------- ----------- ------ --------- ---------------- -------- ---
          0 0 0 CD-ROM SCSI-2 COMPAQ CRD-8402B 1.03 N
          2 0 0 Direct SCSI-3 SEAGATE ST39236LW 0010 W
          2 1 0 Direct SCSI-3 SEAGATE ST39236LW 0010 W
          2 2 0 Direct SCSI-3 SEAGATE ST39236LW 0010 W
          2 3 0 Direct SCSI-3 SEAGATE ST39236LW 0010 W
          2 6 0 Sequential SCSI-2 HP C1537A L005 N

    My understanding is that MAKEDEV is no longer used in 5.1A, and that the
    system is supposed to recognize the device and create the appropriate
    device files. In this case I think they should be /dev/disk/dsk4*, but
    they don't exist so I can't label this disk:

    # cd /dev/disk
    # ls
    cdrom0a dsk0d dsk1a dsk1f dsk2c dsk2h dsk3e floppy0c
    cdrom0c dsk0e dsk1b dsk1g dsk2d dsk3a dsk3f
    dsk0a dsk0f dsk1c dsk1h dsk2e dsk3b dsk3g
    dsk0b dsk0g dsk1d dsk2a dsk2f dsk3c dsk3h
    dsk0c dsk0h dsk1e dsk2b dsk2g dsk3d floppy0a

    Can anyone help?

    Thanks,
    Richard

  • Next message: Michael W: "Large File Copy"

    Relevant Pages

    • Re: Installing OSX on new drive problem
      ... disk is checking for specs that are no longer there, as your HD is different from the original. ... I've swapped drives into PowerBooks and not had any problem installing. ... You are aware that there is no such thing as a "reformat" for ATA ...
      (comp.sys.mac.system)
    • Re: Installing OSX on new drive problem
      ... I've swapped drives into PowerBooks and not had any problem installing. ... You are aware that there is no such thing as a "reformat" for ATA ... There is an "erase" function in Disk Utility, ...
      (comp.sys.mac.system)
    • Re: cant boot freebsd 5.2.1 any more
      ... >> I have a freebsd 5.2.1 file server ... >> I prepped the disk by using sysinstall, ... >> run fsck manually and i'm into single user mode. ...
      (comp.unix.bsd.freebsd.misc)
    • Re: How to get or change root password
      ... I dont see an option for single user mode. ... Does it have a 'real' disk or a silicon disk? ... the desktop system can be booted up and the ... blank the root password). ...
      (comp.os.linux.misc)
    • Re: I bet you wish...
      ... of what looks like becoming a regular series of David's Astonishing ... Apple Adventures. ... If it seems to be booting (there is disk activity noise from the CD drive, but not anything regular and repeating which would indicate stuck reading a damaged disk) but the screen is still doing nothing, I'd say take it or send it back to Apple for repair/replacement. ... Single user mode is early in the startup process, and so could bypass something that is causing the screen not to activate. ...
      (comp.sys.mac.system)