This post is more than 5 years old
116 Posts
0
2220
W2k3 host showing LUNZ (x8) as disks (1-8) unknown/unreadable in disk management
Hi
Just noticed that one of our hosts W2K3 32bit attached to a Clariion CX340f is looking unusual.
In that its showing LUNZ (x8) as disks (1-8) unknown/unreadable in disk management. I know its the LUNZ because displaying properties reports that.
This didnt use to be the case.
The host has 3 LUN's presented which are unaffected access wise with one physical disk shown in disk management for each LUN. PowerPath is in use - 5.1
Powerpath shows all 8 paths to each actual LUN as good and I/O is occuring.
Can anyone advise on this? - we have a number of w2k3 hosts connected to the same array that dont exhibit this behaviour.
Thanks
Nick
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
May 8th, 2012 06:00
create a dummy 1g LUN and drop it in the storage group, it should take host id 0 and LUNZ will go away. You can tell your system admin to ignore the 1G LUN.
Anirudh_Banerje
59 Posts
0
May 8th, 2012 02:00
Hi,
Check the below primus articles from powerlink to know more about LUN Z
emc65060
In order to get rid of LUN Z, the below primus may help you.
emc170849
Thanks
nicbone
116 Posts
0
May 8th, 2012 06:00
Thank you - that has done the job indeed.
Suprised it occured as no changes array side to the LUN id's have been made.
I'm a UNIX/storage person mainly - will put it down to Windows "plug and play" at this stage.
nicbone
116 Posts
0
May 8th, 2012 06:00
Thanks for the response.
This is a FC attached host and it does have LUN's attached so i dont see emc170849 as fitting my situation.
nicbone
116 Posts
0
May 8th, 2012 06:00
No i have Host ID's (from clariion side stg group) of 1,2 & 3
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
May 8th, 2012 06:00
do you have a LUN at host id 0 ? (check storage group)
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
May 8th, 2012 07:00
somebody could have reclaimed the very first LUN that was presented to that host.