View the status of disks and confirm that the disks are added properly:
Command Action
1 New Disks
2 Remove Half Disk
3 Repair Disk
4 Remove Full Disks
5 Status(Raid)
6 Status(All Disks)
9 <= Return
Command:5 |
|
[Status(Raid)] | Member |
Name Partition Status |
md6 |
| resync=DELAYED | (2)hadc7 | (5)hadd7 |
md5 |
| resync=DELAYED | (2)hadc6 | (5)hadd6 |
md4 |
| resync=DELAYED | (2)hadc5 | (5)hadd5 |
md3 | / | resync3.9% | (2)hadc1 | (5)hadd1 |
md1 | duplex | (0)hada2 | (3)hadb2 | |
md2 | /boot | duplex | (0)hada3 | (3)hadb3 |
md0 | duplex | (0)hada1 | (3)hadb1 |
TIPS:
If you attempt to start ftdiskadm more than once at a time, “Cannot start” is displayed. If this message is displayed even when only one ftdiskadm is started, it may have been terminated without clearing the information. In such a case, run ftdiskcleanup and then start ftdiskadm.
The trace log of ftdiskadm is recorded to the /var/log/ftdiskadm directory. If the files occupies a large part of the disk space, delete them from the oldest.
Boot disks are inserted into the Slot0 and Slot3 normally. If you can only boot the system in the simplex mode, insert a boot disk into the Slot0 and boot the system.
After the disk is expanded and the system is restarted, the name of the disk device used by diskdump is changed. Refer to “DUMP INITIALIZATION” and modify "/etc/sysconfig/diskdump.”
