Postgres machine failed to start

Questions / Help
, ,
1

I’m not sure what causes this error as it was working on the past months but today sadly it doesn’t work anymore. Here is the machine id: 784e675fd240d8

here is the log of the machine:

2025-03-17T20:22:49.944 app[784e675fd240d8] bom [info] [ 0.765475] reboot: Restarting system

2025-03-17T20:22:50.014 app[784e675fd240d8] bom [warn] Virtual machine exited abruptly

2025-03-17T20:23:00.014 app[784e675fd240d8] bom [info] 2025-03-17T20:23:00.014007444 [01JHKYVB9N5GWHNJGXMW7HM3AC:main] Running Firecracker v1.7.0

2025-03-17T20:23:00.909 app[784e675fd240d8] bom [info] INFO Starting init (commit: 1df1d0a0)…

2025-03-17T20:23:00.910 app[784e675fd240d8] bom [info] [ 0.814432] I/O error, dev vda, sector 2 op 0x0:(READ) flags 0x1000 phys_seg 1 prio class 0

2025-03-17T20:23:00.911 app[784e675fd240d8] bom [info] [ 0.815111] EXT4-fs (vda): unable to read superblock

2025-03-17T20:23:00.911 app[784e675fd240d8] bom [info] ERROR Error: couldn’t mount /dev/vda onto /lower/dev/vda, because: EIO: I/O error

2025-03-17T20:23:00.912 app[784e675fd240d8] bom [info] [ 0.816309] reboot: Restarting system

2025-03-17T20:23:00.979 app[784e675fd240d8] bom [warn] Virtual machine exited abruptly

2025-03-17T20:26:00.164 app[784e675fd240d8] bom [info] 2025-03-17T20:26:00.164648295 [01JHKYVB9N5GWHNJGXMW7HM3AC:main] Running Firecracker v1.7.0

2025-03-17T20:26:01.025 app[784e675fd240d8] bom [info] INFO Starting init (commit: 1df1d0a0)…

2025-03-17T20:26:01.027 app[784e675fd240d8] bom [info] [ 0.778822] I/O error, dev vda, sector 2 op 0x0:(READ) flags 0x1000 phys_seg 1 prio class 0

2025-03-17T20:26:01.027 app[784e675fd240d8] bom [info] [ 0.779420] EXT4-fs (vda): unable to read superblock

2025-03-17T20:26:01.028 app[784e675fd240d8] bom [info] ERROR Error: couldn’t mount /dev/vda onto /lower/dev/vda, because: EIO: I/O error

2025-03-17T20:26:01.028 app[784e675fd240d8] bom [info] [ 0.780491] reboot: Restarting system

2025-03-17T20:26:01.093 app[784e675fd240d8] bom [warn] Virtual machine exited abruptly

2

“Doesn’t work” is not really an actionable fault report. Can you try starting it? Can you tell us something about the app/machine? What region is it in? Did you do anything or change anything recently?

3

I am not sure what’s the problem. When I hit start it says “Machine failed to start: Unknown response while starting machine” I haven’t changed anything recently and the region is Mumbai, India (BOM)

4

Aha, you’ve added a log to your post; good idea. This is likely the cause of your problem:

That’s an EXT4 filing system error. This forum seems to be seeing a few folks who’re running self-managed Postgres with FS corruption.

I’d suggest examining your options to see if fsck can be run on the volume, though a Fly employee on the other thread says that is not possible as of January. If you can’t access a mountable filing system, maybe ping Support instead.

5

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