Driver Failure rpc error: code = Unknown desc = unable to create microvm: error decrypting volume: exit status 5

Questions / Help
1

I am following the Redis on Fly guide and it seems that volumes might be having a problem? I tried in SJC and LAX and had the same issue.

❯ fly vm status 88de6b42
Instance
  ID            = 88de6b42
  Process       =
  Version       = 1
  Region        = lax
  Desired       = run
  Status        = failed
  Health Checks =
  Restarts      = 0
  Created       = 28s ago

Recent Events
TIMESTAMP            TYPE            MESSAGE
2022-06-08T18:04:21Z Received        Task received by client
2022-06-08T18:04:21Z Task Setup      Building Task Directory
2022-06-08T18:04:25Z Driver Failure  rpc error: code = Unknown desc = unable to create microvm: error decrypting volume: exit status 5
2022-06-08T18:04:25Z Not Restarting  Error was unrecoverable
2022-06-08T18:04:25Z Alloc Unhealthy Unhealthy because of failed task
2022-06-08T18:04:25Z Killing         Sent interrupt. Waiting 5s before force killing
2022-06-08T18:04:26Z Killing         Sent interrupt. Waiting 5s before force killing

Checks
ID SERVICE STATE OUTPUT

Recent Logs
  2022-06-08T18:04:22.000 [info] Starting instance
  2022-06-08T18:04:23.000 [info] Configuring virtual machine
  2022-06-08T18:04:23.000 [info] Pulling container image
  2022-06-08T18:04:23.000 [info] Unpacking image
  2022-06-08T18:04:23.000 [info] Preparing kernel init
  2022-06-08T18:04:23.000 [info] Setting up volume 'redis_server'
  2022-06-08T18:04:23.000 [info] Opening encrypted volume
2

I just tried in MAD as well and got the exact same issue.

Recent Events
TIMESTAMP            TYPE            MESSAGE
2022-06-08T18:09:26Z Received        Task received by client
2022-06-08T18:09:26Z Task Setup      Building Task Directory
2022-06-08T18:09:31Z Driver Failure  rpc error: code = Unknown desc = unable to create microvm: error decrypting volume: exit status 5
2022-06-08T18:09:31Z Not Restarting  Error was unrecoverable
2022-06-08T18:09:31Z Alloc Unhealthy Unhealthy because of failed task
2022-06-08T18:09:32Z Killing         Sent interrupt. Waiting 5s before force killing
3

Hey there,

I am digging into this now. I’ll keep you posted.

1 Like
4

@juanuicich Super sorry for the trouble. Could you delete the volume and recreate it for us and see if things resolve?

5

OK, trying now.

6

Seems to be running now. Thank you @shaun.

08 Jun 2022 19:37:23.455 * Ready to accept connections

Anything I can do next time to avoid this or was it a platform issue?