topic Re: Cant delete Lun in Disk Enclosures

Cant delete Lun

Darren Murray — Tue, 31 Jul 2001 04:00:17 GMT

Hi ,

Im getting this error message when trying to unbind luns

Error in command execution, "RMT_AM60ERRORSTATUS_MSG"

AM60ERR : ERR_COMMAND_FAILED
AM60ERR QUAL : DELETE_LUN
MODULE_CODE_ID : SUBSYSTEM
COMMAND STATE : A device error was returned
DEVICE ACCESS STATUS: SCSI Device Lock Not Granted

amcfg: Error in command executionns

Re: Cant delete Lun

Mark van Hassel — Tue, 31 Jul 2001 06:45:30 GMT

Hi Darren,

It could be one of the following:

- there is still a file system mounted on the LUN

- Another system still has access to that LUN.

If the FC60 is shared by multiple systems you can try to delete the LUN from another system.
(the array daemon needs to own the lock).

Re: Cant delete Lun

Darren Murray — Tue, 31 Jul 2001 07:10:56 GMT

Hi,
It was a new system and had the luns created by default. I have tried from the other servers as well. There was 6 Luns created and was able to delete 3 of them by stopping and starting the array daemon on the servers.
I cant see any file systems mounted on the server or in /etc/mnttab
Any other suggestions
Daz

Re: Cant delete Lun

Mark van Hassel — Tue, 31 Jul 2001 08:30:58 GMT

Daren,

What is the output of amdsp -l [S/N] ?

Re: Cant delete Lun

Insu Kim — Tue, 31 Jul 2001 12:17:05 GMT

First, please make sure that "AM60Srvr" is running by executing "ps -ef|grep -i am60".
I saw AM60 server dying intermittenly before.
sometimes, AM60 server can be disappeared the time when you made an attempt to delete LUN(s) in spite of yourself.
I also saw this.

And then, there is a AM60 patch that you have to apply to ensure any known bug fixes.
The latest patch is not loaded at installation time in general as a part of bundle patch.
You have to download it on the internet and load it using swinstall.

After that, issue "amdsp -a to see if everything in the array is in a good state.
Based on my experience, sometimes, this problem can happen if cables and terminators are not screwed tightenly.

Finally, check out host fiber channel adaptors, cables, GBIC(s) and give it a try again.

This problem can happen if one of the things listed here are not complete.
Please check the easiest things out first such as patch.

Hope this helps,

Re: Cant delete Lun

Bill McNAMARA_1 — Tue, 31 Jul 2001 14:21:07 GMT

Are you in a service guard or shared FC60 environment?

Later,
Bill

Re: Cant delete Lun

Darren Murray — Tue, 31 Jul 2001 16:55:27 GMT

Re: Cant delete Lun

Mark van Hassel — Wed, 01 Aug 2001 06:52:49 GMT

Hi Darren,

The documentation says that one cannot unbind LUN 0. What you have to do is replace it, this can be done using "amcfg -R" (see man page) or you can use SAM by selecting the LUN and then select "Actions", "Disk Array Maintenance" and then choose "Replace".

Good luck !

Re: Cant delete Lun

Bill McNAMARA_1 — Wed, 01 Aug 2001 09:46:29 GMT

LUN 0 contains array configuration and firmware information required to boot the array, you can modify it or add to it as you like but not delete it.
man amcfg

Later,
Bill

Re: Cant delete Lun

Darren Murray — Wed, 01 Aug 2001 23:37:49 GMT

I am trying to replace the LUN 0, I only did the delete on the other LUNs.

amcfg -R A:0 -d 1:0,3:0,5:0 -r 5 -s 32 array id

Cheers
Darren

Re: Cant delete Lun

Darren Murray — Thu, 02 Aug 2001 01:04:54 GMT

Problem solved.

The problem was with Veritas Volume Manager locking the disk and not letting the LUN be replaced. This wasnt being showed through SAM
vxdiskadm was used and the disk was taken offline.

cheers
Darren