VM-11: The model number of the drive appears as 'Model: mtip32xx' for some drives
and as 'Model: Micron P420m-MTF' for others when listing devices using the esxcfg-
scsidevs -l command
Model number reporting is based on the device identifier type. For P320h drives, the
product identifier field (
mtip32xx
), which is a static field, is reported. For P420m drives,
the model number (
P420m-MTF
), which is gathered by the device rather than a static
field, is reported. This provides backward-compatibility with drivers including and prior
to version 2.4.10.
This model number reporting is implemented in driver version 2.5.5 and ensures that
datastore signatures are compatible with the next version of VSphere 2013 (v5.5). It also
ensures that P420m drives formatted on ESXi 5.0 or 5.1 systems do not have to regener-
ate signatures (only P320h drives must regenerate signatures).
VM-12: What steps should I perform on my system before upgrading from ESX 5.0/5.1
to ESX 5.5?
1. Migrate all of your virtual machines and datastores off of the P320h/P420m drive.
2. Uninstall the Micron driver for ESX 5.0/5.1. (This driver cannot be used with the
ESX 5.5 inbox driver.)
3. Perform the kernel upgrade process according to the VMware documentation. The
inbox driver for the P320h/P420m is automatically installed during this process.
4. Reformat all P320h/P420m drives within the ESX 5.5 environment.
5. Create new datastores using the P320h/P420m drives in ESX 5.5.
6. Copy all of your migrated data back to the new datastore(s) created in ESX 5.5.
Note:
If you are using a P320h drive and upgraded the kernel before migrating your data
from the datastores created in ESX 5.0/5.1, follow the instructions in
VM-13
, and then
continue with the installation steps above.
Note:
If you are using a P420m drive, you should not encounter any migration issues
from ESX 5.0/5.1 to ESX 5.5. However, it is recommended to migrate any data in your
datastores before upgrading the kernel version.
VM-13: I have a system with P320h drives and upgraded from ESX 5.0/5.1 to 5.5, but I
did not transfer the datastores. How do I access the datastores created during the ESX
5.0/5.1 installation?
Note:
This issue applies to P320h drives and should not occur with P420m drives.
Note:
The driver will not load on an AMD + ATI chipset-based server, currently identi-
fied as HP Proliant DL385 G7 and G8 servers. There is no workaround for this system.
The cause of this issue has to do with the signature change between ESX 5.5 and ESX
5.0/5.1 datastores with P320h drives. The ESX 5.5 kernel may not recognize the signa-
tures of datastores using the P320h created in ESX 5.0/5.1; therefore, any pre-existing
datastores may not mount after the ESX 5.5 kernel loads because the datastores are not
recognized by the kernel. A temporary workaround is to manually re-import each data-
store with their existing signature; however, this re-import process must be repeated
upon each reboot.
The following VMware articles provide steps on how to re-import and maintain the sig-
nature of your existing datastores:
•
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&doc-
Type=kc&externalId=1011387
P420m/P320h HHHL PCIe SSD Installation Guide
Troubleshooting
PDF: 09005aef8497e00a
P420m_P320h_HHHL_installation_guide.pdf - Rev. V 12/14 EN
42
Micron Technology, Inc. reserves the right to change products or specifications without notice.
©
2012 Micron Technology, Inc. All rights reserved.
