VMware Cloud Community
ahcup
Contributor
Contributor
‎03-21-2017 11:07 PM

Power outage causing attached LUN to be degraded state

There a power outage affecting all my servers.

One of my ESXi cannot be recovered as it throws me this error.
SAMSUNG LUN storage is a attached HDD. I tried rescanning the directory but it still doesnt work.

VM kernal log says [CODE]

2017-03-22T04:21:57.636Z cpu1:33823)WARNING: LVM: 13049: An attached device went offline. t10.ATA_____SAMSUNG_HD103SJ_______________________________S26BJ9FZ503140:1 file system [datastore1, 4e785bc7-dd89be4e-6cdc-b8ac6f9ce0d2]

2017-03-22T04:21:59.667Z cpu5:33862)<3>ata3.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-03-22T04:21:59.670Z cpu3:33862)<3>ata3.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-03-22T04:21:59.684Z cpu3:33862)<3>ata3.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-03-22T04:21:59.685Z cpu3:33862)<3>ata3.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-03-22T04:21:59.685Z cpu3:33862)<3>ata3.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-03-22T04:21:59.686Z cpu3:33862)<3>ata3.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-03-22T04:21:59.687Z cpu3:33862)<3>ata3.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-03-22T04:21:59.688Z cpu3:33862)<3>ata3.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-03-22T04:21:59.689Z cpu3:33862)FSS: 5051: No FS driver claimed device 'mpx.vmhba34:C0:T0:L0': Not supported

2017-03-22T04:21:59.689Z cpu3:33862)Vol3: 714: Couldn't read volume header from control: Not supported

2017-03-22T04:21:59.689Z cpu3:33862)Vol3: 714: Couldn't read volume header from control: Not supported

2017-03-22T04:21:59.689Z cpu3:33862)FSS: 5051: No FS driver claimed device 'control': Not supported

2017-03-22T04:21:59.700Z cpu3:33862)VC: 1958: Device rescan time 10 msec (total number of devices 7)

2017-03-22T04:21:59.700Z cpu3:33862)VC: 1961: Filesystem probe time 23 msec (devices probed 6 of 7)

2017-03-22T04:21:59.700Z cpu3:33862)VC: 1963: Refresh open volume time 0 msec

2017-03-22T04:21:59.701Z cpu1:33862)<3>ata3.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-03-22T04:21:59.704Z cpu1:33862)<3>ata3.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-03-22T04:21:59.715Z cpu1:33862)<3>ata3.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-03-22T04:21:59.716Z cpu1:33862)<3>ata3.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-03-22T04:21:59.716Z cpu1:33862)<3>ata3.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-03-22T04:21:59.717Z cpu1:33862)<3>ata3.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-03-22T04:21:59.718Z cpu2:33862)<3>ata3.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-03-22T04:21:59.719Z cpu2:33862)<3>ata3.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-03-22T04:21:59.720Z cpu2:33862)FSS: 5051: No FS driver claimed device 'mpx.vmhba34:C0:T0:L0': Not supported

2017-03-22T04:21:59.724Z cpu2:33862)Vol3: 714:

[/CODE]

pastedImage_0.png

pastedImage_1.png

pastedImage_2.png

pastedImage_4.png

Anyone please help out if i can restore the datastore without affect any data integrity

2 Replies
RajeevVCP4
Expert
Expert
‎03-22-2017 12:27 AM

This is PDL condition , you need to reboot ESXi host.

or try to follow this KB

Cannot remount a datastore after an unplanned permanent device loss (PDL) (2014155) | VMware KB

Rajeev Chauhan
VCIX-DCV6.5/VSAN/VXRAIL
Please mark help full or correct if my answer is use full for you
ahcup
Contributor
Contributor
‎03-22-2017 01:22 AM

When i list the devices ..

pastedImage_0.png

there is no vms using any of the world id.

pastedImage_1.png

tried the KB and still didn't work..

0 Kudos