My LiteLLM suddenly stopped working. I checked the log, and it seems the filesystem is corrupted?
2025-01-12T15:49:33.573 proxy[6e8254d9b2d058] nrt [info] Starting machine
2025-01-12T15:49:33.678 app[6e8254d9b2d058] nrt [info] 2025-01-12T15:49:33.678727304 [01JF5DKY06PKPC1C6CK21X2RTV:main] Running Firecracker v1.7.0
2025-01-12T15:49:34.382 app[6e8254d9b2d058] nrt [info] INFO Starting init (commit: 0a21fde6)...
2025-01-12T15:49:34.383 app[6e8254d9b2d058] nrt [info] [ 0.621124] blk_update_request: I/O error, dev vda, sector 2 op 0x0:(READ) flags 0x1000 phys_seg 1 prio class 0
2025-01-12T15:49:34.384 app[6e8254d9b2d058] nrt [info] [ 0.622113] EXT4-fs (vda): unable to read superblock
2025-01-12T15:49:34.384 app[6e8254d9b2d058] nrt [info] ERROR Error: couldn't mount /dev/vda onto /lower/dev/vda, because: EIO: I/O error
2025-01-12T15:49:34.385 app[6e8254d9b2d058] nrt [info] [ 0.623361] reboot: Restarting system
2025-01-12T15:49:34.453 app[6e8254d9b2d058] nrt [warn] Virtual machine exited abruptly
2025-01-12T15:49:38.212 runner[6e8254d9b2d058] nrt [info] machine exited with exit code 0, not restarting
2025-01-12T15:49:38.574 proxy[6e8254d9b2d058] nrt [error] [PM03] could not wake up machine due to a timeout requesting from the machines API
2025-01-12T15:49:40.577 proxy[6e8254d9b2d058] nrt [info] Starting machine
2025-01-12T15:49:40.578 proxy[6e8254d9b2d058] nrt [error] [PM01] machines API returned an error: "machine still attempting to start"
2025-01-12T15:49:42.581 proxy[6e8254d9b2d058] nrt [info] Starting machine
2025-01-12T15:49:42.583 proxy[6e8254d9b2d058] nrt [error] [PM01] machines API returned an error: "machine still attempting to start"
2025-01-12T15:49:44.547 proxy[6e8254d9b2d058] nrt [info] Starting machine
2025-01-12T15:49:44.640 app[6e8254d9b2d058] nrt [info] 2025-01-12T15:49:44.639974026 [01JF5DKY06PKPC1C6CK21X2RTV:main] Running Firecracker v1.7.0
2025-01-12T15:49:45.337 app[6e8254d9b2d058] nrt [info] INFO Starting init (commit: 0a21fde6)...