hard drive not mounted

[junaid akhtar]

there are 2 sas 146 gb hardives in bl860c server.These only show on line .When we try to mount it gives message  drive is off line.

any help

[Torsten.]

Can you please show an "ioscan -fn" and your mount command including the error message?

[junaid akhtar]

Spoiler

we are using vms.8.3 1H1.which comand we use.when run command show dev/full,it  gives device online and no errors.did we need restart after replaing the HDD as it si shotswap.Did VMS atuomatically  configure new disk.

Disk SMPK81$DKA100:, device type HP EG0146FARTR, is online, file-oriented
    device, shareable, available to cluster, error logging is enabled.

    Error count                    0    Operations completed            2407172
    Owner process                 ""    Owner UIC                      [SYSTEM]
    Owner process ID        00000000    Dev Prot            S:RWPL,O:RWPL,G:R,W
    Reference count                0    Default buffer size                 512
    Current preferred CPU Id       0    Fastpath                              1
    WWID   02000008:5000-00E1-12E2-A0A2
    Total blocks           286749488    Sectors per track                    96
    Total cylinders            31115    Tracks per cylinder                  96

[Torsten.]

Better to ask the OpenVMS forum ... http://h30499.www3.hp.com/t5/OpenVMS/ct-p/itrc-288

[Hoff]

The disks on VMS do not automatically mount themselves, so the usual disk repair sequence for a disk warm-swap (where the storage hardware supports a warm swap) is a DISMOUNT command for the disk, the swap, and then a MOUNT command.  Here, that would be:

$ DISMOUNT SMPK81$DKA100:

swap

$ MOUNT /SYSTEM SMPK81$DKA100: [volume label]

The volume label is site-specific (and disk device-specific) and depends entirely on the particular contents of the device.  If this is a disk swap, then this disk will be scratch and will either have no label, or will have a label that should be overwritten, and you'll either need to reinitialize the disk (with the INITIALIZE command) and reload it, or use BACKUP /IMAGE or similar to reload its contents, or to use any particular existing RAID mechanism that might be present to repopulate its contents.  (Some additional details on this topic are below.)

The typical way that a system manager will configure a disk to mount at bootstrap on an OpenVMS server involves the system manager adding explicit MOUNT commands into (usually) the site-specific system startup command procedure; editing the SYS$MANAGER:SYSTARTUP_VMS.COM file.

Device autoconfiguration (but not auto-mount) occurs at bootstrap.  OpenVMS does not automatically configure new devices, once booted.  The configuration of disks can be requested via SYSMAN IO AUTO command and will usually find new disks, though this won't necessarily bring any arbitrary devices or device types online.

If there was a SMPK81$DKA100: disk device present prior to the disk swap, then there is no need to invoke an autoconfigure pass.  OpenVMS will size and configure for the disk as part of the MOUNT operation.

There are other considerations, such as whether this volume is part of a hardware RAID configuration, or part of a host-based volume shadowing configuration, or how the data is reloaded onto this disk.  Right now, I don't have enough information on what was on this disk prior to the failure, whether there were backups, or lower-level details of the storage hardware involved such as the potential use of hardware RAID on whatever controller involved.  Some OpenVMS I64 storage controllers support RAID, and some don't.  Some OpenVMS I64 sites use host-based volume shadowing, and some don't.  Some sites do disk backups, and some don't.  If you want more details on the recovery, we'll need more details ont he configuration.

The OpenVMS system management documentation (two volumes, an essentials book and a more advanced book) has an overview of the tasks that anOpenVMS system manager can need to perform with the commands and details, and there are chapters included in that documentation specifically on configuring and mounting disks.  The OpenVMS documentation is available via the www.hp.com/go/openvms/doc web site.  Given you're apparently unfamiliar with OpenVMS system management, I would encourage skimming these two manuals as it'll save you some confusion, some time, and while avoiding the potential for data corruptions or data loss.

I'd also encourage working to obtain an escalation path for your OpenVMS system management questions, as that'll be far faster and far more tailored to your environment.  With that assistance, you can also ensure that you have proper and reliable and consistent backups for recovery from errors or from server security breaches or software errors, as well as procedures in place for effectively performing disk swaps and related procedures.

That device model string certainly also has potential for some juvenile humor, but that's another topic.