* William Douglas: Here's what "parted -l" shows me after I finished creating partitions. I selected these types and sizes based on a working Clear Linux server installation I have made in VirtualBox. Model: QEMU QEMU HARDDISK (scsi) Disk /dev/sda: 20.5GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 1049kB 150MB 149MB fat32 EFI boot, legacy_boot, esp 2 150MB 418MB 268MB linux-swap(v1) linux-swap 3 418MB 20.5GB 20.1GB ext4 / The legacy_boot flag was an addition I made after an error message shown by "swupd repair"; see below. I cloned mixer-tools master branch, installed the "golang" package in the Debian 10 rescue system, then executed go run main.go -state /mnt/sda3/state -output /mnt/sda3/output \ https://cdn.download.clearlinux.org/update/32730/ os-core \ os-core-update kernel-native systemd-networkd-autostart That created a tree of directories in /mnt/sda3/output which looked OK to me. I (re)mounted a couple of devices, as I would for a Gentoo installation, and entered the new environment: mount --types proc /proc /mnt/sda3/output/proc mount --rbind /sys /mnt/sda3/output/sys mount --make-rslave /mnt/sda3/output/sys mount --rbind /dev /mnt/sda3/output/dev mount --make-rslave /mnt/sda3/output/dev chroot /mnt/sda3/output /bin/bash Running "swupd repair" resulted in the following: -----8<----- snip -----8<----- snip -----8<----- Diagnosing version 32730 Downloading missing manifests... Checking for corrupt files [100%] [100%] [100%] Adding any missing files [100%] Repairing corrupt files [100%] Removing extraneous files [100%] Inspected 17948 files Calling post-update helper scripts External command: none External command: [ERROR] cbm (../src/bootman/bootman.c:L740): Failed to parse given uname release: 4.19.101 External command: [WARNING] cbm (../src/bootman/bootman.c:L90): Unable to parse the currently running kernel: 4.19.101 External command: [ERROR] cbm (../src/bootloaders/syslinux-common.c:L288): No boot partition found, you need to mark the boot partition with "legacy_boot" flag. External command: [FATAL] cbm (../src/bootman/bootman.c:L163): Cannot initialise bootloader syslinux External command: Running in chroot, ignoring request: daemon-reload External command: Running in chroot, ignoring request: restart Repair successful -----8<----- snip -----8<----- snip -----8<----- I then ran "clr-boot-manager update" which was also partially unsuccessful -----8<----- snip -----8<----- snip -----8<----- [ERROR] cbm (../src/bootman/bootman.c:L740): Failed to parse given uname release: 4.19.101 [WARNING] cbm (../src/bootman/bootman.c:L90): Unable to parse the currently running kernel: 4.19.101 [ERROR] cbm (../src/bootman/update.c:L189): Cannot determine the currently running kernel Warning: The kernel is still using the old partition table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) The operation has completed successfully. -----8<----- snip -----8<----- snip -----8<----- I did not expect to be able to boot, but tried anyway. That leaves me with the messages Booting fomr Hard Disk... SYSLINUX 6.03 EDD Copyright (C) 1994-2014 H. Peter Anvin et al WARNING: No configuration file found boot: _ At the "boot:" prompt I can enter whatever I want, without discernible effect. I don't even know if this message is related to Clear Linux or just something caused by the Hoster's VM bootstrapping being unable to find anything to boot. I am not sure how to proceed from here. -Ralph