Missing Architecture Disk

[tb-berkah]

Hi, i have some problem to access my VM, because my architecture disk is missing. how i can fix this problem? 

*Note : i'm already to create new VM+Disk and that's architecture not missing

[kolban]

Can you elaborate on what you mean by an "architecture disk"?  Maybe describe what you are trying to achieve and the steps you have performed.   Do you perhaps mean a boot disk?

[tb-berkah]

the first of all we have problem with the payment, and the instance is down (off), after we success to pay the bill and start this VM+Services, this VM cannot start, then show this error and the architecture disk on VM not show x86/64.

Note: i'v already to try create second VM in same instance and that's normal, but when i start first VM always show the error and architecture on disk is missing.

[kolban]

Howdy ... first let me state that I'm just a community user like yourself.  I have no ability to look at your specific issues.  A formal support ticket would be required for that and routed to a support engineer.  That said, what I think I am hearing is that you created a Google Cloud Compute Engine, had some issues with billing/payment, shut down the instance and now when you try and restart it, you are getting some problems.  I am sensing that you think the problem is related to a "boot disk" (my words).

What I'd suggest is that you drill into the problem using this recipe.

1. Identify the Compute Engine instance.  Post back what state it is in "running", "stopped" etc
2. Look at the configuration of the Compute Engine.  That will include what the identity of the boot disk is.  Make a note of its identity.
3. Look at the available boot disks and validate that the boot disk is present.
4. Assuming it is and that the machine is running, look at the serial console logs of the machine.  That will tell us whether it was able to start "cleanly".

[tb-berkah]

ya i think i need formal support ticket to fix this issue, how to get a formal support ticket? . apart from that, i'v already to do your suggest and this is the result.

1. i'v already to check state of instance and this instance in "running" state

2. i'v already to check machine configuration and here are the results. in architecture field doesn't display any value,there should be a boot disk in there right?

because if i create a new vm that architecture field is display boot disk 

3. and i check boot disk, here are the results. in architecture field doesn't display any value

4. and if i run connect serial console logs, display thats message. my question is how come this vm is getting a metadata error that is unreachable by the network while other vm's are running properly? shouldn't all vm's get the same error if the metadata can't be accessed by the network?

 Error main.go:229: network error when requesting metadata, make sure your instance has an active network and can reach the metadata server: Get http://169.254.169.254/computeMetadata/v1/?recursive=true&alt=json&wait_for_change=true&last_etag=c6d9c9b2ac284f61&timeout_sec=60: dial tcp 169.254.169.254:80: i/o timeout

[Pritishinde]

Were you able to fix this? I am facing the same issue. Please help