title: Google compute engine, instance dead? How to reach?
body: <p>I have a small instance running in GCE, had some troubles with the MongoDb so after some tries decided to reset the instance. But... it didn't seem to come back online. So i stopped the instance and restarted it.
  It is an Bitnami MEAN stack which starts apache and stuff at startup.</p>
  
  <p>But... i can't reach the instance! No SCP, no SSH, no webservice running. When i try to connect via SSH (in GCE) it times out, cant make connection on port 22. In the information it says 'The instance is booting up and sshd is not running yet', which is possible of course.... But i cant reach the instance in no possible manner not even after an hour wait :) Not sure what's happening if i cant connect to it somehow :(
  There is some activity in the console... some CPU usage, mostly 0%, some incomming traffic but no outgoing...
  I hope someone can give me a hint here!</p>
  
  <p>Update 1
  After the helpfull tip form Serhii... if found this in the logs...</p>
  
  <pre><code>Booting from Hard Disk 0...
  [    0.872447] piix4_smbus 0000:00:01.3: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr
  /dev/sda1 contains a file system with errors, check forced.
  /dev/sda1: Inodes that were part of a corrupted orphan linked list found.  
  
  /dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
      (i.e., without -a or -p options)
  fsck exited with status code 4
  The root filesystem on /dev/sda1 requires a manual fsck
  </code></pre>
  
  <p>Update 2...
  So, i need to fsck the drive...
  Created a snapshot, made a new disk from that snapshot, added the new disk as an extra disk to another instance. Now that instance wont boot with the same problem... removing the extra disk fixed it again. So adding the disk makes it crash even though it isn't the boot-disk?</p>