Unable to mount volume and start machine in Singapore

Questions / Help
,
1

I have a machine in Singapore that seems to have died a couple of days ago

Attempting to start it shows the logs:

2024-11-30T15:32:13.190 proxy[148e259df1d578] sin [info] Starting machine
2024-11-30T15:32:13.310 app[148e259df1d578] sin [info] 2024-11-30T15:32:13.310091013 [01J9K0N5MCD2VRZ372HKV4XW85:main] Running Firecracker v1.7.0
2024-11-30T15:32:13.918 app[148e259df1d578] sin [info] INFO Starting init (commit: 04656915)...
2024-11-30T15:32:13.920 app[148e259df1d578] sin [info] [ 0.525445] blk_update_request: I/O error, dev vda, sector 2 op 0x0:(READ) flags 0x1000 phys_seg 1 prio class 0
2024-11-30T15:32:13.920 app[148e259df1d578] sin [info] [ 0.526542] EXT4-fs (vda): unable to read superblock
2024-11-30T15:32:13.921 app[148e259df1d578] sin [info] ERROR Error: couldn't mount /dev/vda onto /lower/dev/vda, because: EIO: I/O error
2024-11-30T15:32:13.922 app[148e259df1d578] sin [info] [ 0.528027] reboot: Restarting system
2024-11-30T15:32:14.007 app[148e259df1d578] sin [warn] Virtual machine exited abruptly

Is there any path to fixing this, or am I looking at having to restore from backups and recreate the volume?

2

Hm… A couple of other people were hit by this in Singapore recently as well, :umbrella::

https://community.fly.io/t/fly-singapore-database-randomly-died/22835

Restoring from a snapshot is the surest bet, but in principle there might be some possibility of detaching the existing volume and assigning it to a fresh Machine. What kind of application is this?

4

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.