mvCLI commands

Learn about the mvCLI commands. They are for SATA drives that are directly connected to the system backplane without using a PCIe adapter.

Running the mvCLI commands from the HMC operating system

The mvCLI commands are supplied in the HMC operating system. You need root access to run the command. If the HMC operating system is available, to run the command, use:
su -
and enter the root password to start mvCLI:
/opt/marvell/bin/mvcli
To exit mvCLI mode, enter the command:
exit

Entering "help" at the mvcli command prompt lists the mvcli commands.

Installing mvCLI in the Petitboot environment

To use the mvCLI commands, the mvcli utility must be available. If you need to install the mvcli utility, use the Petitboot command line to mount the storage that contains the mvcli utility using the following procedure. The installation lasts during the current Petitboot session; once you reboot, the installation does not persist.

  1. From the Petitboot menu, select Exit to shell.
  2. To use the mvcli utility at the Petitboot shell:
    • If you have the HMC Recovery ISO file mounted using the Virtual Storage menu option in the Remote Console, or on a USB key inserted on one of the USB port of the system:
      • At the petitboot shell, copy the mvcli utility from /var/petitboot/mnt/dev/sr0/util/marvell directory to /tmp, then make the mvcli utility executable before running it.
        cp /var/petitboot/mnt/dev/sr0/util/marvell/mvcli /tmp
        chmod +x /tmp/mvcli
      • To run the command; use:
        modprobe sg
        /tmp/mvcli
    • If you need to obtain the mvcli utility over the network, you must first configure the network.
      • At the petitboot shell, run the following commands to configure the network:
        ip addr add xxx,xxx,xxx,xxx/yyy,yyy.yyy.yyy dev ETHERNET_DEVICE
        ip route add default via zzz.zzz.zzz.zzz

        where: xxx.xxx.xxx.xxx is the IPV4 ip address; yyy.yyy.yyy.yyy is the IPV4 network mask; zzz.zzz.zzz.zzz is the IPV4 gateway address; and ETHERNET_DEVICE is the network interface name you can obtain from running ip addr show

      • After you configure the network, you can use the scp or wget commands to copy the mvcli utility:
        scp USER_ID@HOST_NAME:PATH_TO_CMD/mvcli /tmp

        Or:

        wget http://HOSTNAME/PATH_TO_CMD/mvcli -P /tmp

        Where: USER_ID is the user name to use on the HOST_NAME where the mvcli utility is located. HOSTNAME is the host name or IP address where the mvcli utility is located

      • Make the mvcli utility executable before running it.
        chmod +x /tmp/mvcli
      • To run the command; use:
        /tmp/mvcli
    • If you have the mvcli utility on a USB drive, ensure that the USB drive is formatted as "vfat".
      • If you have the USB drive inserted and then boot, the USB drive might be automatically mounted. To see if the USB drive is mounted, from the petiboot shell, run this command :
        mount

        If the USB drive mounted automatically, is will show the USB drive as: /dev/mapper/sdb1 mounted on /var/petitboot/mnt/dev/sdb1

      • The drive mounts as read-only; you need to unmount then remount the USB drive as read-write. At the petitboot shell, unmount the USB drive using this command:
        umount /var/petitboot/mnt/dev/sdb1
      • At the petitboot shell, re-mount the USB drive in read-write mode using these commands:
        mkdir /tmp/media
        mount /dev/mapper/sdb1 /tmp/media
        modprobe sg
      • To run the command; use:
        /tmp/media/mvcli

mvCLI commands

To check the status of the RAID virtual disk, run the following command:
info -o vd
The results are similar to this listing:
Virtual Disk Information
-------------------------
id:                  0
name:                HMC Disk
status:              online
Stripe size:         64
RAID mode:           RAID1
Cache mode:          Off
size:                1907649 M
BGA status:          N/A
Block ids:           0 4
# of PDs:            2
PD RAID setup:       0 1

Total # of VD:       1
To show all physical disks and IDs, run the following command:
info -o pd

The physical disk ID (PD ID) matches the slot in which the drive is plugged in the system, with 0 being the leftmost slot.

The results are similar to this listing:
Physical Disk Information
----------------------------
Adapter:             0
PD ID:               0
Type:                SATA PD
Linked at:           HBA port 0
Size:                1953514584 K
Write cache:         supported (on)
SMART:               supported (on)
NCQ:                 supported (on)
48 bits LBA:         supported
supported speed:     1.5 3 6 Gb/s
Current speed:       6 Gb/s
model:               ST2000NM0024-1HT174
Serial:              Z4H0E1G1
Firmware version:    SN06
Locate LED status:   off
block ids:           0
associated VDs:      0
PD valid size:       0 K


Adapter:             0
PD ID:               1
Type:                SATA PD
Linked at:           HBA port 1
Size:                1953514584 K
Write cache:         supported (on)
SMART:               supported (on)
NCQ:                 supported (on)
48 bits LBA:         supported
supported speed:     1.5 3 6 Gb/s
Current speed:       6 Gb/s
model:               ST2000NM0024-1HT174
Serial:              Z4H03KCM
Firmware version:    SN05
Locate LED status:   off
block ids:           4
associated VDs:      0
PD valid size:       0 K


Total # of PD:       2
To list the serial number of a drive, run the following command:
info -o pd -i <id of drive>
To show all host bus adapters (HBAs), run the following command:
info -o hba
The smart command shows the status of various sensors and metrics for the drive. Use the command to periodically check the state of the drives. An error is logged in the Service Focal Point error log and a call-home is made when the smart command indicates a problem. The format of the smart command is
smart -p PD_ID
If you run this command:
smart -p 0
The results are similar to this listing:
SMART STATUS RETURN: OK.

Smart Info
ID      Attribute Name          Current Worst   Threshhold      RawValue        Status
01      Read Error Rate         76      64      44              00000000F5E0    OK
03      Spin-Up Time            98      96      0               000000000000    OK
04      Start/Stop Count        100     100     20              0000000000C8    OK
05      Reallocated Sectors     100     100     10              000000000000    OK
07      Seek Error Rate         88      60      45              0000000091DC    OK
09      Power-On Hours Count    96      96      0               0000000010FD    OK
0A      Spin Retry Count        100     100     97              000000000000    OK
0C      Power Cycle Count       100     100     20              0000000000C6    OK
B8      End-to-End error        100     100     99              000000000000    OK
BB      Reported Uncorrectable  100     100     0               000000000000    OK
BC      Command Timeout         100     100     0               000000000000    OK
BD      High Fly Writes         100     100     0               000000000000    OK
BE      Temperature Diff        73      66      40              00000000001B    OK
BF      G-sense error rate      100     100     0               000000000000    OK
C0      Power-off retract       100     100     0               0000000000F5    OK
C1      Load/Unload cycle       100     100     0               0000000001AA    OK
C2      HDA temperature         27      40      0               00000000001B    OK
C3      ECC recovered           76      6       0               00000000F5E0    OK
C5      Current pending         100     100     0               000000000000    OK
C6      Offline scan wrong      100     100     0               000000000000    OK
C7      UDMA CRC error rate     200     200     0               000000000000    OK