NavigationContentFooter
Jump toSuggest an edit

Dealing with the end of life of the bootscript feature

Reviewed on 21 February 2024 • Published on 20 February 2023

Some legacy Instance types (e.g. VC1-x, X64-x, Start1-x) supported the option to use a bootscript (a preconfigured boot configuration) to start your Instance. This boot method was also available on DEV1-x, GP1-x, and STARDUST1 Instances. This feature is now deprecated and will no longer be supported.

If you are still using one of these Instance types with a bootscript, you have to change your boot configuration in order to keep your Instance operational.

You can find information about the Instances quotas allocated to your account at the following link: Understanding Organization quotas.

Note

If you want to keep using legacy Instance types, you will not be able to create them through the console interface. However, you can still create them using the Scaleway CLI as you normally would or through the Instances API, as long as you stay within your allocated quotas. Check your Organization’s quota usage in the Scaleway console.

Important

To ensure the continued stability of your service, it is crucial to follow the procedures outlined below, as the bootscript feature enters the decommissioning phase. Failure to do so may result in service instability for your Instances.

Before you start

To complete the actions presented below, you must have:

  • A Scaleway account logged into the console
  • Owner status or IAM permissions allowing you to perform actions in the intended Organization
  • An SSH key
  • An Instance using a bootscript

How do I know if I am impacted?

If your Instance is using the bootscript option to boot in normal mode you are impacted. You can check which boot mode is used by your Instance directly in the Scaleway console.

  1. Click Instances in the Compute section of the side menu. The Instances page displays.
  2. Click the name of the Instance you want to check. The Instance overview displays.
  3. Click the Advanced Settings tab.
  4. Check the Boot Mode of your Instance. If it uses local boot you are not concerned by the migration. If you are using a bootscript your intervention is required.

Migration options for Instances using bootscripts

Important

Local volume(s) that do not support UEFI cannot be used to boot any other type of Instance. You must retrieve and migrate manually your data to an Instance that supports UEFI boot. Unfortunately, Scaleway cannot access your data to identify if you are using an OS image with or without UEFI partitions. To do so, connect to your Instance using SSH and run the following command to list the EFI directories:

ls -ld /sys/firmware/efi

If you can see the following output, your Instance uses UEFI boot:

root@my-virtual-instance:~# ls -ld /sys/firmware/efi
drwxr-xr-x 6 root root 0 Feb 20 11:16 /sys/firmware/EFI

In this case, use option 1 to migrate your Instance. If you see ls: cannot access /sys/firmware/efi: No such file or directory, the UEFI directories are not present on your Instance. Migrate your data using options 2, 3, or 4.

Change the boot type of the Instance to local boot

Tip

This option is the recommended procedure for most Instance types.

This section applies if your Instance supports UEFI boot. To continue using your current Instance, change the boot type of the Instance to Local boot:

  1. Click Instances in the Compute section of the side menu. The Instances page displays.
  2. Click the Instance you wish to start with a local boot.
  3. Use the toggle «Toogle Icon» icon in the top right corner of the screen to power off your Instance.
  4. Click the Advanced settings tab.
  5. In the Boot mode section, select Use local boot.
  6. Click Save.
  7. Use the toggle «Toogle Icon» icon in the top right corner of the screen to power on your Instance. Your Instance starts using local boot.
  8. Check that the Instance is booting correctly with the local boot method and that its services are behaving correctly.
Note
  • If changing the boot type from bootscript to local boot is not successfully achieved via option 1, you can always use option 2 or 3 to migrate your Instance data to a new one.
  • If you are a STARDUST1 user, we recommend that you put your VM into standby mode. This ensures your Instance will not lose its slot in the case of availability shortages.
Docs APIScaleway consoleDedibox consoleScaleway LearningScaleway.comPricingBlogCarreer
© 2023-2024 – Scaleway