3 Replies Latest reply on Feb 2, 2017 11:46 PM by linotelera

    SOS!!! After a power failure, VMs can not be powered on.  I just get this message for SSH:"input/output error"

    PeterZhang2017 Lurker

      Hello everybody,

       

      Could someone help me, please?

       

      I have a server with LSI MegaRAID SAS 9361-8i. I used five HDD to built a VD. The VD is RAID 5. The server is running vmware ESXi 6.5. After a power failure, I cannot power on four VMs that they were powered on in the RAID 5 VD when the power failure happened. I can power on two VMs that they were powered off in the RAID 5 VD when the power failure happened. I used SSH to connect to ESXi host. When I used cat command to display the VM's log file and configuration file, I just got this message:" input/output error"I. Now I wonder if someone can help me.

       

      Thank you very much

       

      Peter

       

      I ran VOMA to check for VMFS errors.

      # voma -m vmfs -f check -d /vmfs/devices/disks/naa.600608e000100000b366597b3be8d703:1

      Here is the result:

      Checking if device is actively used by other hosts

      Running VMFS Checker version 2.1 in check mode

      Initializing LVM metadata, Basic Checks will be done

      Phase 1: Checking VMFS header and resource files

         Detected VMFS-6 file system (labeled:'datastore19-SAS') with UUID:5859c19e-671fd344-09e4-0cc47ae1d9dc, Version 6:81

         Found stale lock [type 10c00003 offset 1440088064 v 16, hb offset 3768320

                      gen 323, mode 1, owner 58853761-46b87feb-c37e-0cc47ae1d9dc mtime 23742

                      num 0 gblnum 0 gblgen 0 gblbrk 0]

         …

      Phase 2: Checking VMFS heartbeat region

      Marking Journal addr (9, 0) in use

      Phase 3: Checking all file descriptors.

         Found stale lock [type 10c00001 offset 7577600 v 148, hb offset 3768320

                      gen 323, mode 1, owner 58853761-46b87feb-c37e-0cc47ae1d9dc mtime 6492

                      num 0 gblnum 0 gblgen 0 gblbrk 0]

         …

      ON-DISK ERROR: Invalid address in PB : addrType 0x2 at PB 0 entry 0

      ON-DISK ERROR: Duplicate addresses found: <FDA cnum 38 rnum 35>  <1, -1> (SFB tbz 25 cow 0 cnum 0 rnum 0)

      ON-DISK ERROR: Invalid address in PB : addrType 0x5 at PB 0 entry 528

      ON-DISK ERROR: Invalid address in PB : addrType 0x5 at PB 0 entry 529

      ON-DISK ERROR: Invalid LFB address PB2 cow 0 cnum 22906492245 rnum 85, at Idx 7696

      ON-DISK ERROR: Invalid LFB address PB2 cow 0 cnum 22906492245 rnum 85, at Idx 7703

      ON-DISK ERROR: Invalid LFB address Null address, at Idx 7704

      ON-DISK ERROR: Invalid LFB address PB2 cow 0 cnum 22906492245 rnum 85, at Idx 7728

      ON-DISK ERROR: Invalid LFB address Null address, at Idx 7736

      ON-DISK ERROR: Invalid LFB address Null address, at Idx 7737

      ON-DISK ERROR: <FD c52 r47> : Invalid block count 32768 should be 0.

      ON-DISK ERROR: <FD c52 r47> : Invalid Large block count 64 should be 0.

      ON-DISK ERROR: <FD c52 r47> : Invalid Pointer block count 0 should be 4.

      ON-DISK ERROR: <FD c52 r47> : Invalid Epoch Block Count 32768 should be 0

         Found stale lock [type 10c00001 offset 464076800 v 32, hb offset 3768320

                      gen 323, mode 1, owner 58853761-46b87feb-c37e-0cc47ae1d9dc mtime 2461

                      num 0 gblnum 0 gblgen 0 gblbrk 0]

         …

      Phase 4: Checking pathname and connectivity.

      Phase 5: Checking resource reference counts.

      ON-DISK ERROR: LFB inconsistency found: (1854,1) allocated in bitmap, but never used

       

      Total Errors Found: 10649