Solved!
Go to SolutionR
RobertDudley
2 Intern
•
448 Posts
0
7090
January 15th, 2013 07:00
Microsoft boot from SAN lun 0 read-only attribute
When we provision a windows host on a VMAX we present a 50Gb boot lun at lun 0. When storage is presented on the initial install lun 0 is marked as read-only and the intel admin has to use the diskpart utility to clear the attribute. If we only present just a lun 0 it is not marked read-only; this happens when we present the boot lun and additional luns. This is all prior to loading the operating system or anything on our standard HP server with emulex LP11000/LP12000 HBA's. This is on a VMAX using thin provisioning and masking views; director flags are preset on at the HBA level. I am trying to find out what is causing the read-only attribute to be picked up by the server as the disk is read/write on the storage array.
HP server model is 380/580
Emulex HBA LP11000/12000
Windows 2008 R2 64bit
VMAX 20K runing 5876 enginuity
Thin provisioning
Masking view with dual pathing
Boot from SAN
RobertDudley
2 Intern
•
448 Posts
1696
0
Posted January 15th, 2013 08:00
No the ACLX device is not mapped to any front end port.
RobertDudley
2 Intern
•
448 Posts
1696
0
Posted January 15th, 2013 08:00
Yeah the funny things those admins do because they know better than we do.
Hi Robert, are you using multipathing software?
If yes, did you try to mask it only to one path first?
How did you implement the lun offset?
Did you use the DLA (dynamic Lun Addressing)?
DLA allows for Symmetrix devices, regardless of their LUN address on the front-end director, to start at address 0 for a given HBA and director port pairing. In addition, DLA can be used to directly specify a LUN address for a given device. The Symmetrix V-MAX, with the use of Auto-provisioning Groups, not only automates director LUN mapping but also utilizes DLA to simplify LUN addressing.
RobertDudley
2 Intern
•
448 Posts
1697
0
Posted January 15th, 2013 10:00
We are using the masking view feature that defaults the first lun to 0 not lun offset as this is a VMAX not a DMX4. You cannot run an EMCGrab on a host with no operating system as this is a boot from SAN environment and the host operating system is not yet installed.
SanjeevMalhotra
138 Posts
481
0
Posted January 15th, 2013 11:00
Also can you verify by presenting your boot lun to another Host as a data disk and check in diskpart if it shows Read-Only or Read-Write on the other host before presenting it to the Host in question in boot from SAN environment?
Also Reduce the server to a single path before attemptiong to boot from that LUN.
Kleanthis76
1 Rookie
•
27 Posts
2056
0
Posted January 24th, 2013 01:00
Hi Robert,
Based on the following MS article: http://support.microsoft.com/kb/2345135
this is the default behavior for your OS based on the SAN Policy.
Also you can check the white-paper from EMC: EMC Symmetrix with Windows Server 2003 and 2008 Best Practices planning on p. 20-21.
Regards,
Kleanthis