升级ESX 4.1 update1出错

在尝试将IBM x3850 X5 7145NB2上的VMware ESX 4.1升级到Update 1时,系统在升级后无法正常启动,停留在VSD-MOUNT阶段。问题似乎与存储设备的路径状态有关,出现警告提示‘NMP: nmp_SelectPathAndIssueCommand: PSP selected path in a bad state (standby) on device’。尽管有多个VMware KB文章和社区讨论,但没有找到确切的解决方案。尝试过拔插HBA卡以绕过问题,但并非长久之计。官方KB和社区帖子并未提供有效解决方法。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

环境:IBM x3850 X5 7145NB2主机,IBM DS 5020 FC存储,原系统VMware Esx 4.1 260247

通过Vmware update manager升级到VMware Esx 4.1 update1,主机自动重启后,ESX进不去系统!启动界面停留在VSD-MOUNT处

如果事先从HBA卡上拔掉光纤,还可以正常启动,再连上光纤照样能够HA、DRS……,只是拔来拔去的着实让人不爽

 

首先以VSD-MOUNT做为关键字搜索

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1012874&sliceId=1&docTypeID=DT_KB_1_1&dialogID=54054616&stateId=0%200%2054874630

 

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1012142&sliceId=1&docTypeID=DT_KB_1_1&dialogID=54054616&stateId=0%200%2054874630

这两个KB和我的情况都不一样,我/vmfs中esxconsole.vmdk和esxconsole-flat.vmdk均完好无损

http://communities.vmware.com/thread/222307和我的故障现象类似,但无法解决我的问题

 

查看vmkernel.1日志,发现不少警告,主要有

May  6 15:31:34 x5-1 vmkernel: 
May  6 15:31:34 x5-1 vmkernel: 0:05:09:30.755 cpu12:4260)VMWARE SCSI Id: Id for vmhba2:C0:T1:L0 
May  6 15:31:34 x5-1 vmkernel: 0x53 0x51 0x30 0x31 0x32 0x30 0x31 0x32 0x36 0x33 0x20 0x20 0x20 0x20 0x20 0x20 0x31 0x38 0x31 0x34 0x20 0x20 
May  6 15:31:34 x5-1 vmkernel: 0:05:09:30.755 cpu12:4260)WARNING: NMP: nmp_SelectPathAndIssueCommand: PSP selected path "vmhba2:C0:T1:L0" in a bad state (standby)on device "Unregistered Device".
May  6 15:31:34 x5-1 vmkernel: 0:05:09:30.755 cpu12:4260)WARNING: NMP: nmp_DeviceRetryCommand: Device "Unregistered Device": awaiting fast path state update for failover with I/O blocked. No prior reservation exists on the device.
May  6 15:31:34 x5-1 vmkernel: 0:05:09:30.755 cpu12:4260)WARNING: NMP: nmp_DeviceStartLoop: NMP Device "Unregistered Device" is blocked. Not starting I/O from device.
May  6 15:31:34 x5-1 vmkernel: 0:05:09:30.775 cpu0:4096)VMNIX: VmkDev: 2122: Added SCSI device vml0:3:0 (naa.60080e50001856f8000007dd4da7818c)
May  6 15:31:34 x5-1 vmkernel: 0:05:09:30.908 cpu0:4096)VMNIX: VmkDev: 2122: Added SCSI device vml0:4:0 (naa.60080e50001857c80000078a4d9be15e)
May  6 15:31:34 x5-1 vmkernel: 0:05:09:30.939 cpu0:4096)VMNIX: VmkDev: 2122: Added SCSI device vml0:5:0 (naa.60080e50001857c8000002f34ce99bb6)
May  6 15:31:34 x5-1 vmkernel: 0:05:09:30.971 cpu2:4268)NMP: nmp_CompleteCommandForPath: Command 0x12 (0x4102bef64640) to NMP device "mpx.vmhba5:C0:T0:L0" failed on physical path "vmhba5:C0:T0:L0" H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
May  6 15:31:34 x5-1 vmkernel: 0:05:09:30.971 cpu2:4268)ScsiDeviceIO: 1672: Command 0x12 to device "mpx.vmhba5:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
May  6 15:31:34 x5-1 vmkernel: 0:05:09:31.139 cpu4:4268)NMP: nmp_CompleteCommandForPath: Command 0x12 (0x4102bef64640) to NMP device "mpx.vmhba5:C0:T0:L0" failed on physical path "vmhba5:C0:T0:L0" H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
May  6 15:31:34 x5-1 vmkernel: 0:05:09:31.139 cpu4:4268)ScsiDeviceIO: 1672: Command 0x12 to device "mpx.vmhba5:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
May  6 15:32:13 x5-1 vmkernel: 0:05:10:10.755 cpu8:4246)ScsiDeviceIO: 1672: Command 0x1a to device "t10.________________" failed H:0x5 D:0x0 P:0x0 Possible sense data: 0x6 0x29 0x4.
May  6 15:32:13 x5-1 vmkernel: 0:05:10:10.755 cpu8:4246)WARNING: NMP: nmp_DeviceStartLoop: NMP Device "Unregistered Device" is blocked. Not starting I/O from device.
May  6 15:32:13 x5-1 vmkernel: 0:05:10:10.755 cpu12:4260)ScsiDeviceIO: 4494: Could not detect setting of QErr for device t10.________________. Error Failure. 
May  6 15:32:28 x5-1 vmkernel: 0:05:10:24.908 cpu2:4120)ScsiScan: 1059: Path 'vmhba2:C0:T0:L31': Vendor: 'IBM     '  Model: 'Universal Xport '  Rev: '1060'
May  6 15:32:28 x5-1 vmkernel: 0:05:10:24.908 cpu2:4120)ScsiScan: 1062: Path 'vmhba2:C0:T0:L31': Type: 0x0, ANSI rev: 5, TPGS: 0 (none)
May  6 15:32:28 x5-1 vmkernel: 0:05:10:24.909 cpu2:4120)ScsiScan: 1059: Path 'vmhba2:C0:T1:L31': Vendor: 'IBM     '  Model: 'Universal Xport '  Rev: '1060'
May  6 15:32:28 x5-1 vmkernel: 0:05:10:24.909 cpu2:4120)ScsiScan: 1062: Path 'vmhba2:C0:T1:L31': Type: 0x0, ANSI rev: 5, TPGS: 0 (none)
May  6 15:32:28 x5-1 vmkernel: 0:05:10:24.909 cpu2:4120)ScsiScan: 1059: Path 'vmhba2:C0:T1:L0': Vendor: 'IBM     '  Model: '1814      FAStT '  Rev: '1060'
May  6 15:32:28 x5-1 vmkernel: 0:05:10:24.909 cpu2:4120)ScsiScan: 1062: Path 'vmhba2:C0:T1:L0': Type: 0x0, ANSI rev: 5, TPGS: 0 (none)
May  6 15:32:28 x5-1 vmkernel: 0:05:10:24.909 cpu2:4120)ScsiScan: 1059: Path 'vmhba2:C0:T0:L0': Vendor: 'IBM     '  Model: '1814      FAStT '  Rev: '1060'
May  6 15:32:28 x5-1 vmkernel: 0:05:10:24.909 cpu2:4120)ScsiScan: 1062: Path 'vmhba2:C0:T0:L0': Type: 0x0, ANSI rev: 5, TPGS: 0 (none)
May  6 15:32:28 x5-1 vmkernel: 0:05:10:24.910 cpu2:4120)ScsiScan: 1059: Path 'vmhba2:C0:T0:L1': Vendor: 'IBM     '  Model: '1814      FAStT '  Rev: '1060'
May  6 15:32:28 x5-1 vmkernel: 0:05:10:24.910 cpu2:4120)ScsiScan: 1062: Path 'vmhba2:C0:T0:L1': Type: 0x0, ANSI rev: 5, TPGS: 0 (none)
May  6 15:32:28 x5-1 vmkernel: 0:05:10:24.910 cpu2:4120)ScsiScan: 1059: Path 'vmhba2:C0:T0:L2': Vendor: 'IBM     '  Model: '1814      FAStT '  Rev: '1060'
May  6 15:32:28 x5-1 vmkernel: 0:05:10:24.910 cpu2:4120)ScsiScan: 1062: Path 'vmhba2:C0:T0:L2': Type: 0x0, ANSI rev: 5, TPGS: 0 (none)
May  6 15:32:53 x5-1 vmkernel: 0:05:10:50.755 cpu8:4246)ScsiDeviceIO: 1672: Command 0x25 to device "t10.________________" failed H:0x5 D:0x0 P:0x0 Possible sense data: 0x6 0x29 0x4.
May  6 15:32:53 x5-1 vmkernel: 0:05:10:50.755 cpu12:4260)WARNING: ScsiCore: 1400: Invalid sense buffer: error=0x0, valid=0x0, segment=0x0, key=0x6
May  6 15:33:33 x5-1 vmkernel: 0:05:11:30.755 cpu8:4246)ScsiDeviceIO: 1672: Command 0x1a to device "t10.________________" failed H:0x5 D:0x0 P:0x0 Possible sense data: 0x6 0x29 0x4.
May  6 15:33:33 x5-1 vmkernel: 0:05:11:30.755 cpu12:4260)WARNING: ScsiDeviceIO: 5172: READ CAPACITY on device "t10.________________" from Plugin "NMP" failed. I/O error
May  6 15:33:33 x5-1 vmkernel: 0:05:11:30.755 cpu12:4260)WARNING: ScsiDevice: 1726: Full GetDeviceAttributes during registration of device 't10.________________': failed with I/O error
May  6 15:33:33 x5-1 vmkernel: 0:05:11:30.755 cpu12:4260)ScsiDevice: 2200: Successfully registered device "t10.________________" from plugin "NMP" of type 0

 

执行esxcli nmp device list,发现多出来了一个存储t10.________________

 

[root@x5-1 /]# esxcli nmp device list
naa.600605b002854b101557980f163b7fd6
    Device Display Name: Local IBM Disk (naa.600605b002854b101557980f163b7fd6)
    Storage Array Type: VMW_SATP_LOCAL
    Storage Array Type Device Config: SATP VMW_SATP_LOCAL does not support device configuration.
    Path Selection Policy: VMW_PSP_FIXED
    Path Selection Policy Device Config: {preferred=vmhba0:C2:T0:L0;current=vmhba0:C2:T0:L0}
    Working Paths: vmhba0:C2:T0:L0

naa.60080e5000182014000002ca4ce99c60
    Device Display Name: IBM Fibre Channel Disk (naa.60080e5000182014000002ca4ce99c60)
    Storage Array Type: VMW_SATP_LSI
    Storage Array Type Device Config: SATP VMW_SATP_LSI does not support device configuration.
    Path Selection Policy: VMW_PSP_MRU
    Path Selection Policy Device Config: Current Path=vmhba2:C0:T1:L31
    Working Paths: vmhba2:C0:T1:L31

mpx.vmhba5:C0:T0:L0
    Device Display Name: Local MATSHITA CD-ROM (mpx.vmhba5:C0:T0:L0)
    Storage Array Type: VMW_SATP_LOCAL
    Storage Array Type Device Config: SATP VMW_SATP_LOCAL does not support device configuration.
    Path Selection Policy: VMW_PSP_FIXED
    Path Selection Policy Device Config: {preferred=vmhba5:C0:T0:L0;current=vmhba5:C0:T0:L0}
    Working Paths: vmhba5:C0:T0:L0

naa.60080e50001856f8000007dd4da7818c
    Device Display Name: IBM Fibre Channel Disk (naa.60080e50001856f8000007dd4da7818c)
    Storage Array Type: VMW_SATP_LSI
    Storage Array Type Device Config: SATP VMW_SATP_LSI does not support device configuration.
    Path Selection Policy: VMW_PSP_MRU
    Path Selection Policy Device Config: Current Path=vmhba2:C0:T0:L0
    Working Paths: vmhba2:C0:T0:L0

naa.60080e50001857c8000002f34ce99bb6
    Device Display Name: IBM Fibre Channel Disk (naa.60080e50001857c8000002f34ce99bb6)
    Storage Array Type: VMW_SATP_LSI
    Storage Array Type Device Config: SATP VMW_SATP_LSI does not support device configuration.
    Path Selection Policy: VMW_PSP_MRU
    Path Selection Policy Device Config: Current Path=vmhba2:C0:T0:L31
    Working Paths: vmhba2:C0:T0:L31

t10.________________
    Device Display Name: IBM Fibre Channel Disk (t10.________________)
    Storage Array Type: VMW_SATP_LSI
    Storage Array Type Device Config: SATP VMW_SATP_LSI does not support device configuration.
    Path Selection Policy: VMW_PSP_MRU
    Path Selection Policy Device Config: Current Path=vmhba2:C0:T1:L0
    Working Paths: vmhba2:C0:T1:L0

[root@x5-1 /]#

升级ESX 4.1 update1出错 - 漂流瓶 - 六卖神贱的博客

 

http://communities.vmware.com/thread/242370十分相像

 但是想尽一切办法,在存储上取消map、再次map、添加lun、修改lun……都不行

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1014101

官方KB也没有更好的解决方法

 

怀疑可能是vmware update manager自动更新有问题,这次直接用esx 4.1 u1光盘安装,但不幸的是在选择硬盘的那个步骤居然找不到任何的驱动器!拔下HBA光纤则能找到local disk。而在安装ESX 4.1时这里不但可以找到local disk,还能找到FC LUN

 

最后的答案在http://www.vmware.com/resources/compatibility

升级ESX 4.1 update1出错 - 漂流瓶 - 六卖神贱的博客
原来DS5020不被ESX4.1 U1所支持,瀑布汗一下
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值