Chapter 7. Recovery Procedures; User Id And System Access; Accessing A File Module As Root; Recovering From Losing The Root Password - IBM Storwize V7000 Unified Series Problem Determination Manual

Chapter 7. Recovery procedures

This section covers the recovery procedures for the file modules and control
enclosure.

User ID and system access

This section covers the recovery procedures for the topics that support the user ID
and system access.

Accessing a file module as root

Some procedures require that you log on to a file module as root.
You can use the following methods to access a file module as root.
Access a file module as root.
v Type the following command in an X terminal, for example, a Windows or a
v Use a Windows application like PuTTY to ssh to port 1602 of a file module

Recovering from losing the root password

Some recovery procedures require the root password to be entered for the file
module.
If you have forgotten the file module root password, you can change it from any
file module user ID that has sufficient authority to run the chrootpwd command
successfully. If you do not have a user ID or if you have lost the password, then
use this procedure to recover. You must have physical access to the file module to
perform this procedure. Plug a keyboard and video monitor (KVM) directly into
the front of one of the file modules. Stall the boot sequence at the Linux Grub boot
loader screen.
To recover a lost root password, perform the following steps:
1. Check that the system is in good health by using the management GUI. Fix any
2. Use the management GUI to identify the file module that is not the active
3. Log in to the management CLI as admin.
4. To boot the Grub boot loader into single-user mode, log in as admin on the
© Copyright IBM Corp. 2011, 2012
Linux operating system:
ssh -p 1602 root@<file module IP>
service IP and log in as root with the root password that you recorded in your
access information. See "Record access information" on page 3.
hardware errors that do not require the root password.
management node and plug the KVM into that file module.
a. Issue the suspendnode command to remove the file module that is not the
active management node from the system so that you can reboot it in
single-user mode.
b. To remove the mgmt001st001 file module from the system, issue the
following command
suspendnode mgmt001st001
KVM. Issue the following Linux command:
255