c9::500110a0008c72fa med-changer connected configured failed
Yes, typically I managed not to cover what to do in the state 'failed', there are many possibilities, as you will understand you can only cover some, hence my description of the most common.
Failed state looks to me like a library issue - there is a level of communication (you can see it) but it is not responding correctly.
I would recommend to speak with the hardware vendor and perhaps os support, but hardware vendor first.
This :
modunload -i $(echo $(modinfo |grep "sg (SCSA" |awk '{print $1}'))
should work, but for whatever reason is not working for you, so this is an explnation of what it should do.
It uses the modinfo command to get the instance number of the SG driver and ‘pastes’ this into the modunload command, which ‘stops’ the driver.
For example :
root@womble netbackup $ modinfo |grep "sg (SCSA"
189 7b7e0000 37a8 338 1 sg (SCSA Generic Revision: 3.7)
We only want the instance number (1st field) so the same command with the awk bit gives :
root@womble netbackup $ modinfo |grep "sg (SCSA" |awk '{print $1}'
189
To unload this we could do :
modunload –i 189
But is you put a command inside $( ) then it will use only the output of the command :
Easiest shown with echo ...
root@womble netbackup $ echo date
date
But use $() and it will not echo date, but will echo the output of date ...
root@womble netbackup $ echo $(date)
Fri Jan 4 12:08:03 GMT 2013
Hence ...
modunload -i $(echo $(modinfo |grep "sg (SCSA" |awk '{print $1}')
So to do this manually, this command will give the instance number of the driver
modinfo |grep "sg (SCSA" |awk '{print $1}'
This will unload it :
modunload –i <instance number >
Martin
