Description | A bad drive cannot be removed if a medium is still in it. |
Explanation | When trying to remove a drive from the FSE implementation, the command |
| fsedrive |
| drive cannot be removed from the system. |
Workaround | If the medium could not be unloaded, you must identify the reason and unload the medium |
| manually. |
| Then place the medium into a free slot in the FSE library and enter the command |
| fselibrary |
| to trigger an inventory update and rescan the inventory. When complete, remove the drive |
| using the command |
| fsedrive |
| again. |
Description | After reconfiguring an FSE drive, the FSE implementation loads or unloads a different FSE drive |
| instead of the newly reconfigured drive. |
Explanation | During reconfiguration, the Library Agent is not notified about the new drive device file or ID, |
| and still uses the old device file or ID. |
| Linux specific |
| Library Agent uses drive device files for addressing FSE drives. |
| Windows specific |
| Library Agent uses drive device IDs for addressing FSE drives. |
Workaround | After an FSE drive is reconfigured with a modified ControlDevice variable, restart the FSE |
| implementation using the fse |
HP StorageWorks File System Extender Software user guide 251