Emerging Service Issue - Block Storage - All Regions

We have finished rolling back the change, and haven’t observed any additional issues with the Block Storage service. We will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

A recent system update introduced an unexpected behavior impacting encrypted block storage volumes configured for direct disk I/O and we are in the process of rolling back this change. Customers with their deployment(s) configured in this fashion will experience problems attaching and accessing encrypted volumes to their respective Linodes.

If you believe you may be impacted by this bug, you can mitigate this behavior by either detaching and reattaching your volume to your Linode while it is powered on, or rebooting your node.

A recent code-change introduced a bug impacting encrypted block storage volumes configured for direct disk I/O. Customers may experience problems attaching and accessing encrypted volumes to their respective Linodes.

If your deployment is configured in this fashion or you believe you may be impacted you can mitigate this by detaching and reattaching your volume to your Linode while it is powered on. Please do not reboot your node with the volume attached as this can result in disk corruption and data loss.

Investigation into the recent issue continues. Currently, we recommend users refrain from rebooting Linodes utilizing direct disk boot with encrypted block storage to mitigate potential risk.

Our team is investigating an emerging service issue affecting Block Storage in all regions. We will share additional updates as we have more information.