Cannot Ping or SSH

[Aalok Surana]

This is a bit crazy, everything was working until I rebooted my Instance, I was trying to add another persistent disk and then I rebooted as I wanted to attach the new disk and things went downhill from there

This is what I have done to get back but it doesn't seem I am not going anywhere, I have lost valuable time.. 

1) Recreate the SSH keys but no go 

2) Delete the Persistent Disk no go

3) Created another instance still no go

4) Ping will not work from my client Mac and Win no go 

Here are some details, any help is appreciated!! 

default

Description

Default network for the project

Addresses

10.240.0.0/16

Gateway

10.240.0.1

Firewall rules

Create new

default-allow-icmp

Allow ICMP from anywhere

Source Ranges:

0.0.0.0/0

Allowed Protocols or Ports:

icmp

default-allow-internal

Allow internal traffic on the default network

Source Ranges:

10.240.0.0/16

Allowed Protocols or Ports:

tcp:1-65535

udp:1-65535

icmp

default-allow-ssh

Allow SSH from anywhere

Source Ranges:

0.0.0.0/0

Allowed Protocols or Ports:

tcp:22

Routes

Create new

default-route-b83adcd9b5db676c

Default route to the virtual network.

Instance Tags:

This route applies to all instances.

Destination IP range:

10.240.0.0/16

Priority

1000

gcutil --project=**** listroutes

+--------------------------------+---------+-------------------+----------+

| name                           | network | destination-range | priority |

+--------------------------------+---------+-------------------+----------+

| default-route-b83adcd9b5db676c | default | 10.240.0.0/16     |     1000 |

+--------------------------------+---------+-------------------+----------+

ourmachome:.ssh aloksurana$ gcutil listinstances

+------------+--------------+---------+---------------+-----------------+

| name       | zone         | status  | network-ip    | external-ip     |

+------------+--------------+---------+---------------+-----------------+

| instance-1 | asia-east1-b | RUNNING | 10.240.188.89 | 107.167.***.*** |

+------------+--------------+---------+---------------+-----------------+

ping 107.167.***.***

PING 107.167.***.*** (107.167.***.***): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

Request timeout for icmp_seq 2

Request timeout for icmp_seq 3

Request timeout for icmp_seq 4

[Marilu]

Hi Alkstar,

For the information provided, looks like you have deleted the Internet route that connects to the internet. https://developers.google.com/compute/docs/networking#defaultrout

In the web interface, add the default route as:

Marilu

[Aalok Surana]

Thanks, Okay I have added it and added a new instance-3 and seems like now i am able to connect to instance-3, I looked at thee log for instance-1, and seems like the machine is down.  here is the log for instance-1, does this mean my instance-1 is gone?  Sorry to ask you think question with this thread.. 

dracut Warning: No root device "block:/dev/disk/by-uuid/174d52a4-a6c9-4e90-b73d-dafa9d02f9bc" found

 %G

dracut Warning: Boot has failed. To debug this issue add "rdshell" to the kernel command line.

dracut Warning: Signal caught!

dracut Warning: Boot has failed. To debug this issue add "rdshell" to the kernel command line.
Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: init Not tainted 2.6.32-400.36.3.el6uek.x86_64 #1
Call Trace:
 [<ffffffff8145118b>] panic+0x7a/0x133
 [<ffffffff8105b096>] do_exit+0x7b/0x710
 [<ffffffff8111bcf9>] ? fput+0x1a/0x1c
 [<ffffffff8105b7ac>] do_group_exit+0x81/0xab
 [<ffffffff8105b7ed>] sys_exit_group+0x17/0x1b
 [<ffffffff81011d32>] system_call_fastpath+0x16/0x1b

[Marilu]

Hi Alkstar,

You mention before that you have deleted the persistent disk(PD) before, are you able to see the disk in you developers console in the 'Disk' section?

For the output you have provided, it looks like the PD is gone. If you still see it in your list of PD and you did some changes to it, you will need to revert any changes that might have caused not to be a root PD.  To access this PD, you can attach it to another instance as a second disk, mount it and revert the changes. 

You will need to detach the disk again and create a VM using this PD as a root PD. You can find more info about PD at https://developers.google.com/compute/docs/disks#attach_disk

Marilu 

[Marilu]

Hi Alkstar,

I mean boot PD, not root PD.

Marilu