Ubuntu VM stuck at 47% boot

Home / ubuntu / Ubuntu VM stuck at 47% boot

Question:
I had a power cut and ever since I have been unable to boot an ubuntu server. In VMware it gets to 47% in Powering on Virtual machine then stops, no errors appear, I looked in the log and this is what it says
2017-08-18T14:39:21.682Z| vmx| I120: Vigor_ClientRequestCb: failed to do op=3 on unregistered device ‘MKS’ (cmd=queryFields)
2017-08-18T14:39:21.683Z| vmx| I120: Vigor_ClientRequestCb: failed to do op=3 on unregistered device ‘Tools’ (cmd=queryFields)
2017-08-18T14:39:21.683Z| vmx| I120: Vigor_ClientRequestCb: failed to do op=3 on unregistered device ‘GuestInfo’ (cmd=queryFields)
2017-08-18T14:39:21.684Z| vmx| I120: Vigor_ClientRequestCb: failed to do op=3 on unregistered device ‘GuestPeriodic’ (cmd=queryFields)
2017-08-18T14:39:21.684Z| vmx| I120: Vigor_ClientRequestCb: failed to do op=3 on unregistered device ‘GuestAppMonitor’ (cmd=queryFields)
2017-08-18T14:39:21.685Z| vmx| I120: Vigor_ClientRequestCb: failed to do op=3 on unregistered device ‘MKS’ (cmd=queryFields)
2017-08-18T14:39:21.686Z| vmx| I120: Vigor_ClientRequestCb: failed to do op=3 on unregistered device ‘MKS’ (cmd=queryFields)
2017-08-18T14:39:21.687Z| vmx| I120: Vigor_ClientRequestCb: failed to do op=3 on unregistered device ‘MKS’ (cmd=queryFields)
2017-08-18T14:39:21.688Z| vmx| I120: Vigor_ClientRequestCb: failed to do op=3 on unregistered device ‘Tools’ (cmd=queryFields)
2017-08-18T14:39:21.689Z| vmx| I120: Vigor_ClientRequestCb: failed to do op=3 on unregistered device ‘GuestInfo’ (cmd=queryFields)
2017-08-18T14:39:21.689Z| vmx| I120: Vigor_ClientRequestCb: failed to do op=3 on unregistered device ‘GuestPeriodic’ (cmd=queryFields)
2017-08-18T14:39:21.689Z| vmx| I120: Vigor_ClientRequestCb: failed to do op=3 on unregistered device ‘GuestAppMonitor’ (cmd=queryFields)
2017-08-18T14:39:21.690Z| vmx| I120: Vigor_ClientRequestCb: failed to do op=3 on unregistered device ‘MKS’ (cmd=queryFields)
2017-08-18T14:39:21.691Z| vmx| I120: Vigor_ClientRequestCb: failed to do op=3 on unregistered device ‘MKS’ (cmd=queryFields)
2017-08-18T14:39:21.692Z| vmx| I120: Vigor_ClientRequestCb: failed to do op=3 on unregistered device ‘Tools’ (cmd=queryFields)
2017-08-18T14:39:21.692Z| vmx| I120: Vigor_ClientRequestCb: failed to do op=3 on unregistered device ‘GuestInfo’ (cmd=queryFields)
2017-08-18T14:39:21.692Z| vmx| I120: Vigor_ClientRequestCb: failed to do op=3 on unregistered device ‘GuestPeriodic’ (cmd=queryFields)
2017-08-18T14:39:21.692Z| vmx| I120: Vigor_ClientRequestCb: failed to do op=3 on unregistered device ‘GuestAppMonitor’ (cmd=queryFields)
2017-08-18T14:39:21.747Z| vmx| I120: Vigor_ClientRequestCb: failed to do op=3 on unregistered device ‘MKS’ (cmd=queryFields)
2017-08-18T14:39:21.748Z| vmx| I120: Vigor_ClientRequestCb: failed to do op=3 on unregistered device ‘Tools’ (cmd=queryFields)
2017-08-18T14:39:21.748Z| vmx| I120: Vigor_ClientRequestCb: failed to do op=3 on unregistered device ‘GuestInfo’ (cmd=queryFields)
2017-08-18T14:39:21.748Z| vmx| I120: Vigor_ClientRequestCb: failed to do op=3 on unregistered device ‘GuestPeriodic’ (cmd=queryFields)
2017-08-18T14:39:21.750Z| vmx| I120: Vigor_ClientRequestCb: failed to do op=3 on unregistered device ‘GuestAppMonitor’ (cmd=queryFields)
2017-08-18T14:39:25.142Z| vmx| I120: VigorTransportProcessClientPayload: opID=2D398DFF-000001C4-c9eb seq=54: Receiving Bootstrap.MessageReply request.
2017-08-18T14:39:25.142Z| vmx| I120: Vigor_MessageRevoke: message ‘msg.uuid.altered’ (seq 2681518) is revoked
2017-08-18T14:39:25.142Z| vmx| I120: VigorTransport_ServerSendResponse opID=2D398DFF-000001C4-c9eb seq=54: Completed Bootstrap request.
2017-08-18T14:39:25.142Z| vmx| I120: MsgQuestion: msg.uuid.altered reply=2
2017-08-18T14:39:25.142Z| vmx| I120: UUID: Writing uuid.bios value: ’56 4d ce 80 2d 03 a2 db-cc e7 a4 7b 0c d8 7a 3c’
2017-08-18T14:39:25.143Z| vmx| A115: ConfigDB: Setting uuid.bios = "56 4d ce 80 2d 03 a2 db-cc e7 a4 7b 0c d8 7a 3c"
2017-08-18T14:39:25.143Z| vmx| I120: UUID: Writing uuid.location value: ’56 4d ce 80 2d 03 a2 db-cc e7 a4 7b 0c d8 7a 3c’
2017-08-18T14:39:25.143Z| vmx| A115: ConfigDB: Setting uuid.location = "56 4d ce 80 2d 03 a2 db-cc e7 a4 7b 0c d8 7a 3c"
2017-08-18T14:39:25.152Z| vmx| I120: AIOGNRC: numThreads=2 ide=0, scsi=0, passthru=1
2017-08-18T14:39:25.152Z| vmx| I120: WORKER: Creating new group with numThreads=2 (2)
2017-08-18T14:39:25.153Z| vmx| I120: WORKER: Creating new group with numThreads=2 (4)
2017-08-18T14:39:25.153Z| vmx| A115: ConfigDB: Setting replay.supported = "FALSE"
2017-08-18T14:39:25.153Z| vmx| I120: StateLogger::nonDeterFxsaveBPs: 0x0 0x0
2017-08-18T14:39:25.153Z| vmx| I120: StateLogger::Replay State = 0
2017-08-18T14:39:25.153Z| vmx| I120: StateLogger::minDEThreshold: 115
2017-08-18T14:39:25.153Z| vmx| A115: ConfigDB: Setting replay.filename = ""
2017-08-18T14:39:25.154Z| vmx| I120: BusMem: Alloc’ing region MainMem flags 0x2402 numPages 16777216
2017-08-18T14:39:25.154Z| vmx| I120: WORKER: Creating new group with numThreads=1 (4)
2017-08-18T14:39:25.154Z| vmx| I120: MainMem: CPT PLS=1 PLR=0 BS=0 BlkP=64 Mult=3 W=25
2017-08-18T14:39:25.154Z| vmx| I120: MStat: Creating Stat vm.uptime
2017-08-18T14:39:25.154Z| vmx| I120: MStat: Creating Stat vm.suspendTime
2017-08-18T14:39:25.154Z| vmx| I120: MStat: Creating Stat vm.powerOnTimeStamp
2017-08-18T14:39:25.155Z| vmx| I120: VMXAIOMGR: Using: simple=Generic unbuf=Generic
2017-08-18T14:39:25.162Z| vmx| I120: WORKER: Creating new group with numThreads=1 (4)
2017-08-18T14:39:25.162Z| vmx| I120: MX: init lock: rank(intrLock)=0x7cc lid=14
2017-08-18T14:39:25.162Z| vmx| I120: BusMem: Alloc’ing region LocalApic flags 0x9230 numPages 8
2017-08-18T14:39:25.162Z| vmx| I120: MX: init lock: rank(apicLock0)=0x7cd lid=15
2017-08-18T14:39:25.162Z| vmx| I120: MX: init lock: rank(apicLock1)=0x7cd lid=16
2017-08-18T14:39:25.162Z| vmx| I120: MX: init lock: rank(apicLock2)=0x7cd lid=17
2017-08-18T14:39:25.162Z| vmx| I120: MX: init lock: rank(apicLock3)=0x7cd lid=18
2017-08-18T14:39:25.162Z| vmx| I120: MX: init lock: rank(apicLock4)=0x7cd lid=19
2017-08-18T14:39:25.162Z| vmx| I120: MX: init lock: rank(apicLock5)=0x7cd lid=20
2017-08-18T14:39:25.163Z| vmx| I120: MX: init lock: rank(apicLock6)=0x7cd lid=21
2017-08-18T14:39:25.163Z| vmx| I120: MX: init lock: rank(apicLock7)=0x7cd lid=22
2017-08-18T14:39:25.163Z| vmx| I120: BusMem: Alloc’ing region IOAPIC flags 0x1020 numPages 1
2017-08-18T14:39:25.163Z| vmx| I120: FTCpt: (0 unk) State transition FTCPT_UNSET -> FTCPT_NOT_CONFIGURED (0:1)
2017-08-18T14:39:25.170Z| vmx| I120: WORKER: Creating new group with numThreads=16 (4)
2017-08-18T14:39:25.171Z| vmx| I120: WORKER: Creating new group with numThreads=1 (4)
2017-08-18T14:39:25.172Z| vmx| I120: MigrateResetStaleVMDBHostLog: Hostlog ./WEBSERVER-2-966294dd.hlog doesn’t exist.
2017-08-18T14:39:25.183Z| vmx| I120: MigrateBusMemPrealloc: BusMem preallocation complete.
2017-08-18T14:39:25.183Z| vmx| I120: MX: init lock: rank(timeTracker)=0x7ce lid=23
2017-08-18T14:39:25.183Z| vmx| I120: MX: init lock: rank(vtscInfo)=0xfa lid=24
2017-08-18T14:39:25.184Z| vmx| I120: TimeTracker host to guest rate conversion 607863387570419 @ 2266747000Hz -> 0 @ 2266747000Hz
2017-08-18T14:39:25.184Z| vmx| I120: TimeTracker host to guest rate conversion ((x * 2147483648) >> 31) + -607863387570419
2017-08-18T14:39:25.184Z| vmx| I120: Disabling TSC scaling since host does not support it.
2017-08-18T14:39:25.184Z| vmx| I120: TSC offsetting enabled.
2017-08-18T14:39:25.184Z| vmx| I120: timeTracker.globalProgressMaxAllowanceMS: 2000
2017-08-18T14:39:25.184Z| vmx| I120: timeTracker.globalProgressToAllowanceNS: 1000
2017-08-18T14:39:25.217Z| vmx| A115: ConfigDB: Setting scsi0:0.redo = ""
2017-08-18T14:39:25.217Z| vmx| I120: DISK: OPEN scsi0:0 ‘/vmfs/volumes/1afbc72c-d64467f6/WEBSERVER-2/WEBSERVER-2-000001.vmdk’ persistent R[]
2017-08-18T14:40:05.269Z| vmx| I120: DISKLIB-VMFS : "/vmfs/volumes/1afbc72c-d64467f6/WEBSERVER-2/WEBSERVER-2-000001-delta.vmdk" : open successful (10) size = 476829245440, hd = 2615141. Type 8
2017-08-18T14:40:05.269Z| vmx| I120: DISKLIB-DSCPTR: Opened [0]: "WEBSERVER-2-000001-delta.vmdk" (0xa)
2017-08-18T14:40:05.269Z| vmx| I120: DISKLIB-LINK : Opened ‘/vmfs/volumes/1afbc72c-d64467f6/WEBSERVER-2/WEBSERVER-2-000001.vmdk’ (0xa): vmfsSparse, 4080218930 sectors / 1.9 TB.
2017-08-18T14:40:05.294Z| vmx| I120: DISKLIB-VMFS : "/vmfs/volumes/1afbc72c-d64467f6/WEBSERVER-2/WEBSERVER-2-flat.vmdk" : open successful (14) size = 2089072092160, hd = 4253562. Type 3
2017-08-18T14:40:05.294Z| vmx| I120: DISKLIB-DSCPTR: Opened [0]: "WEBSERVER-2-flat.vmdk" (0xe)
2017-08-18T14:40:05.294Z| vmx| I120: DISKLIB-LINK : Opened ‘/vmfs/volumes/1afbc72c-d64467f6/WEBSERVER-2/WEBSERVER-2.vmdk’ (0xe): vmfs, 4080218930 sectors / 1.9 TB.
2017-08-18T14:40:05.294Z| vmx| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain: numLinks = 2, numSubChains = 1
2017-08-18T14:40:05.294Z| vmx| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(0) fid = 4253562, extentType = 2
2017-08-18T14:40:05.294Z| vmx| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(1) fid = 2615141, extentType = 0

any ideas on how to recover this? I’m not to sure what a lot of this Log means. The webserver disk is 1.92TB.

To add it also seems to crash the host when it freezes. everything just says loading, I have to reboot the host for it to recover. I have tried it on 2 different hosts just incase it was a host issue Thanks


Answer:

Read more

Leave a Reply

Your email address will not be published. Required fields are marked *