6.2 diskadm(1M) command
Usage: diskadm action pathname ...
- Meaning
- Displayed when there is an error in the way a command option was used.
diskadm: Not support.
- Meaning
- The model not supported executed the command
- Action
- Enter a correct path name. Also make sure that the SCF driver package is installed properly.
diskadm: Only root is allowed to execute this program.
- Meaning
- The command was executed using user privileges other than root.
- Action
- Execute the command using root user privileges.
diskadm: Path name: Incorrect controller.
- Meaning
- A controller that does not exist was specified as a path name, or could not access the SCSI Fault LED device driver.
- Action
- Enter a correct path name. Also make sure that the SCF driver package is installed properly.
diskadm: Path name: Incorrect controller is specified, or specified controller is not supported.
- Meaning
- A controller that does not exist was specified as a path name, or A controller not supported by the diskadm command was specified, or could not access the SCSI Fault LED device driver.
- Action
- Enter a correct path name. Also make sure that the SCF driver package is installed properly.
diskadm: Path name: Illegal path name.
- Meaning
- An illegal path name was specified.
- Action
- Enter a correct path name.
diskadm: Path name: No such device.
- Meaning
- A controller that does not exist was specified as a path name.
- Action
- Enter a correct path name.
diskadm: /dev/FJSVhwr/fled: open() failed: System call error message
- Meaning
- For GP7000F model 200/200R/400/400A/400R/600/600R and PRIMEPOWER 1/200/400/600
Failed to open the Fault LED device driver.
- For PRIMEPOWER 250/450/650/850/900/1500/2500/HPC2500
Failed to open the SCF driver.
- Action
- Make sure that the SCF driver package is installed properly.
diskadm: ioctl() --- FLED_IOC_GET_PROP failed: System call error message
- Meaning
- For GP7000F model 200/200R/400/400A/400R/600/600R and PRIMEPOWER 1/200/400/600
ioctl(2) to the Fault LED device driver failed and the property (led-control-0/1) could not be read.
- For PRIMEPOWER 250/450/650/850/900/1500/2500/HPC2500
ioctl(2) to the SCF driver failed and the property (led-control-0 for 79) could not be read.
- Action
- Make sure that the SCF driver package is installed properly.
diskadm: ioctl() --- FLED_IOC_POWER failed: System call error message
- Meaning
- ioctl(2) to the Fault LED device driver failed and the write to or read from a register failed.
- Action
- Make sure that the SCF driver package is installed properly.
diskadm: ioctl() --- FLED_IOC_POWER_GET failed: System call error message
- Meaning
- ioctl(2) to the SCF driver failed and the write to or read from a register failed.
- Action
- Make sure that the SCF driver package is installed properly.
diskadm: strdup() failed: System call error message
- Meaning
- strdup(3C) failed.
- Action
- Allocate memory or a swap area.
diskadm: malloc() failed: System call error message
- Meaning
- malloc(3C) failed.
- Action
- Allocate memory or a swap area.
diskadm: /dev/rdsk: opendir() failed: System call error message
- Meaning
- /dev/rdsk opendir(3C) failed.
- Action
- Check the /dev/rdsk directory.
diskadm: getcwd() failed: System call error message
- Meaning
- getcwd(3C) failed.
- Action
- Use fsck(1M) to make sure that the root file system has not been damaged.
diskadm: path name: lstat() failed: System call error message
- Meaning
- lstat(2) failed.
- Action
- Use fsck(1M) to make sure that the root file system has not been damaged.
diskadm: path name: readlink() failed: System call error message
- Meaning
- readlink(2) failed.
- Action
- Use fsck(1M) to make sure that the root file system has not been damaged.
diskadm: path name: chdir() failed: System call error message
- Meaning
- chdir(2) failed.
- Action
- Use fsck(1M) to make sure that the root file system has not been damaged.
diskadm: path name: disk not responding.
- Meaning
- Disk controller is not responding or disk is not installed.
- Action
- Check if the disk is installed correctly. Check if disk controller is working correctly.
Warning: Cannot lstat file name
- Meaning
- File lstat(2) failed. (File name is the file under /dev/rdsk)
- Action
- Check the /dev/rdsk directory.
Warning: file name is not a symbolic link
- Meaning
- A file other than a symbolic link is in the /dev/rdsk directory.
- Action
- There is problem with the /dev/rdsk directory. Reboot the system using boot -r.
Warning: path name: already started, but trying again.
- Meaning
- The device is already booted but diskadm is trying again.
Warning: path name: already stopped, but trying again.
- Meaning
- The device is already stopped, but diskadm is trying again.
diskadm: /dev/FJSVhwr opendir() failed: System call error message
- Meaning
- /dev/FJSVhwr opendir(3C) failed.
- Action
- Make sure that the SCF driver package is installed properly.
diskadm: ioctl() --- SFLED_IOC_LIST failed: System call error message
- Meaning
- ioctl(2) to the SCSI Fault LED device driver failed.
- Action
- Check the state of SCSI Fault LED device.
diskadm: ioctl() --- SFLED_IOC_OFF failed: System call error message
- Meaning
- ioctl(2) to the SCSI Fault LED device driver failed.
- Action
- Check the state of SCSI Fault LED device.
diskadm: ioctl() --- SFLED_IOC_ON failed: System call error message
- Meaning
- ioctl(2) to the SCSI Fault LED device driver failed.
- Action
- Check the state of SCSI Fault LED device.
diskadm: /dev/FJSVhwr/sfledX: open failed: Device Busy
- Meaning
- Another diskadm command is being executed.
- Action
- Execute the command again.
diskadm: /dev/es/sesX: open failed: Device Busy
- Meaning
- Another diskadm command is being executed, or failed to open the SES device driver.
- Action
- Execute the command again.
diskadm: /dev/openprom: open() failed: System call error message
- Meaning
- Failed to open /dev/openprom.
- Action
- Check the /dev/openprom file.
diskadm: ioctl() --- OPROMNXTPROP failed: System call error message
- Meaning
- ioctl(2) to the /dev/openprom failed.
- Action
- Check the /dev/openprom file.
diskadm: ioctl() --- OPROMGETPROP failed: System call error message
- Meaning
- ioctl(2) to the /dev/openprom failed.
- Action
- Check the /dev/openprom file.
diskadm: ioctl() --- OPROMNEXT failed: System call error message
- Meaning
- ioctl(2) to the /dev/openprom failed.
- Action
- Check the /dev/openprom file.
diskadm: ioctl() --- OPROMCHILD failed: System call error message
- Meaning
- ioctl(2) to the /dev/openprom failed.
- Action
- Check the /dev/openprom file.
diskadm: ioctl() --- SESIOC_GETNOBJ failed: System call error message
- Meaning
- ioctl(2) to the SES device driver failed.
- Action
- Check the /dev/es/sesX file.
diskadm: ioctl() --- SESIOC_SETNOBJ failed: System call error message
- Meaning
- ioctl(2) to the SES device driver failed.
- Action
- Check the /dev/es/sesX file.
diskadm: ioctl() --- USCSICMD failed: System call error message
- Meaning
- ioctl(2) to the SES device driver failed.
- Action
- Check the /dev/es/sesX file.
diskadm: sysinfo() failed: System call error message
- Meaning
- sysinfo(2) to the SES device driver failed.
- Action
- Check the /dev/es/sesX file.
All Rights Reserved, Copyright(C) FUJITSU LIMITED 2005