We have an HP Storageworks 1/8 G2 Autoloader Tape drive that the Firmware seems to be frozen on it. The front control panel is locked, the web based GUI will not come up, and can't access from the OS. The last time this happened I had to pull the power plug, waited about 20 seconds, plugged back in and when it finished the boot up, I was able to access from the front control panel and the web based GUI. However the only way the HP-UX 11.31 server would re-recognize it was to reboot the server itself also. I've also tried unplugging and re-plugging in the cable in the back in case it's a connection issue. There are no fault lights or other indications on the drive and HP has ran diagnostics from the server itself with no indicators.
My question is, does anyone know what might be causing it to freeze?
On the server side with OMNISV down, I'm still seeing this, which I think might be preventing the server from recognizing the tape drive after its turned back on:
# ps -ef | grep omni | grep -v grep
root 2257 2256 0 Oct 12 ? 0:00 /opt/omni/lbin/bma -name drive1 -policy 10 -type 13 -library tape_library -seg 2000 -dev /dev/rmt/4mn 1 -blk 256 -dev_serial HU
root 2256 1128 0 Oct 12 ? 0:00 /opt/omni/lbin/bma -name drive1 -policy 10 -type 13 -library tape_library -seg 2000 -dev /dev/rmt/4mn 1 -blk 256 -dev_serial HU
and if I do a ptree I am getting this:
# ptree -s 2256
2256 /opt/omni/lbin/bma -name drive1 -policy 10 -type 13 -library ta
2257 /opt/omni/lbin/bma -name drive1 -policy 10 -type 13 -library ta
2258 uma -pol 10 -dev /dev/rmt/4mn 1 -type 13 -ioctl /dev/rchgr/auto
My concern is if its ok to kill 2256 since its a child of inetd with users on the system? Additionally, should I kill 2257/2258 first or just 2256?
Thanks ahead of time for any assistance I can get.
P.S. This thread has been moved from Tape Backup (Small and Medium Business) to Data Protector Support and News Forum. -HP Forum Moderator