I would like to run my Reform Classic with a LUKS-encrypted NVMe. To do this, I ran the reform-setup-encrypted-disk script.
micha@reformmk:~$ sudo reform-setup-encrypted-disk
This will ERASE ALL DATA from your NVMe SSD.
Are you sure you want to proceed? [y/N] y
WARNING: Device /dev/nvme0n1 already contains a 'crypto_LUKS' superblock signature.
WARNING!
========
This will overwrite data on /dev/nvme0n1 irrevocably.
Are you sure? (Type 'yes' in capital letters): YES
Enter passphrase for /dev/nvme0n1:
Verify passphrase:
Enter passphrase for /dev/nvme0n1:
Physical volume "/dev/mapper/reform_crypt" successfully created.
Volume group "reformvg" successfully created
Logical volume "swap" created.
Setting up swapspace version 1, size = 31 GiB (33285992448 bytes)
no label, UUID=43df1ec2-13ca-45e4-bb68-4490213ced0a
Logical volume "root" created.
mke2fs 1.47.2 (1-Jan-2025)
Creating filesystem with 236059648 4k blocks and 59015168 inodes
Filesystem UUID: 0ebb05d5-b2c1-42cf-815e-2543aada1a1a
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 102400000, 214990848
Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done
The encrypted NVMe SSD is now set up. Do you want me to run reform-migrate now as well? [y/N] y
6,861,548,011 99% 13.90MB/s 0:07:50 (xfr#215221, to-chk=0/298336)
Your /boot partition will be on eMMC by default. Do you want it on the SD-Card instead? [y/N] N
I: Using partition on eMMC for /boot: /dev/mmcblk0p1.
This script selects your preferred boot medium. It writes your choice to the file /etc/fstab
This script will copy the contents from the old /boot partition
/dev/mmcblk1p1 (SD-card) to the new /boot partition mmcblk0p1 (eMMC) and delete all files from the latter that were not present in the former.
Are you sure that you want to remove the contents of mmcblk0p1 (eMMC)
and replace it with the contents of /dev/mmcblk1p1 (SD-card)? [y/N] y
commenting original /etc/fstab contents
update-initramfs: Generating /boot/initrd.img-6.16.3-mnt-reform-arm64
Using DTB: rockchip/rk3588-mnt-reform2-dsi.dtb
Installing /usr/lib/linux-image-6.16.3-mnt-reform-arm64/rockchip/rk3588-mnt-reform2-dsi.dtb into /boot/dtbs/6.16.3-mnt-reform-arm64/rockchip/rk3588-mnt-reform2-dsi.dtb
Taking backup of rk3588-mnt-reform2-dsi.dtb.
Installing new rk3588-mnt-reform2-dsi.dtb.
Ignoring old or unknown version 6.16.3-mnt-reform-arm64 (latest is 6.16.9-mnt-reform-arm64)
update-initramfs: Generating /boot/initrd.img-6.16.9-mnt-reform-arm64
Using DTB: rockchip/rk3588-mnt-reform2-dsi.dtb
Installing /usr/lib/linux-image-6.16.9-mnt-reform-arm64/rockchip/rk3588-mnt-reform2-dsi.dtb into /boot/dtbs/6.16.9-mnt-reform-arm64/rockchip/rk3588-mnt-reform2-dsi.dtb
Taking backup of rk3588-mnt-reform2-dsi.dtb.
Installing new rk3588-mnt-reform2-dsi.dtb.
flash-kernel: installing version 6.16.9-mnt-reform-arm64
Generating boot script u-boot image... done.
Taking backup of boot.scr.
Installing new boot.scr.
Your /boot partition is on emmc (/dev/mmcblk0p1).
I: u-boot will prefer the first partition on SD-card over the first partition on eMMC
I: Your current system has its /boot mounted from SD-card.
I: You requested to configure a new /boot on eMMC
I: Instead of just rebooting, power off the system.
I: Then remove the SD-card.
I: Lastly, power the system on again.
I: Power off your MNT Reform by running 'systemctl poweroff'.
0 logical volume(s) in volume group "reformvg" now active
You can now reboot into your encrypted System.
micha@reformmk:~$
After running the script and restarting, the screen remained dark.
To restore the old state, I ran the reform-migrate script. Unfortunately, this did not restore the original state. The screen remained dark even after running this script.
When I start with the SD card inserted with the latest image (reform-system-rk3588-dsi.img), the Reform boots up fine.
However, I notice that despite booting from the SD card, it wants me to log in with the original username and password.
Could it be that it boots from the SD card, but then somehow the eMMC comes into play?
To record the boot process, I followed your instructions:
You can connect the cable, start tio and then start the reform. That way you even are able to receive the very early boot messages and do not miss anything. Your reform should show up as acm0 and acm1 even before you have switched it on.
