Closed zeroecco closed 1 year ago
screenshot from the nightly build
I tried to reproduce the issue, but was unable to. I built ops from the master branch and used it to create a test image, an empty volume (same 128GB size as yours) and run an instance (same availability zone and same instance type). When I attach the volume to the instance, it is mounted correctly. I tested with both attaching the volume to an already running instance, and starting the instance with the volume already attached; in both cases, the volume is mounted correctly. From your logs it looks like some kind of filesystem corruption happened. Did the issue occur when attaching a newly created volume on a newly created instance, or did it happen after stopping and restarting the instance, or after detaching and reattaching the volume?
just restarting the instance let to this failure. I ended up abandoning running sigp/lighthouse on unikernels for the moment so I do not have any additional information at this time. I will close this issue as user error
my ops based on master branch for the proxmox features recently added:
my ops config:
commands ran in order:
after instance in AWS starts I get this error: