Subject: FydeOS v23.0-SP1 multi-boot install fails on Lenovo ThinkCentre M720q — cryptohome error in live USB and loop/partx failure in dual-boot installer
Hello FydeOS team,
I’m reporting a repeatable issue with FydeOS for PC Intel Modern v23.0-SP1 on a Lenovo ThinkCentre M720q.
Hardware
PC: Lenovo ThinkCentre M720q
CPU: Intel Core i5-9500T
GPU: Intel UHD Graphics 630
RAM: 8 GB
Internal storage: Toshiba MQ04ABF100, ~1 TB HDD
OS currently installed: Windows 10
Partition table: GPT
BIOS configuration
I have already verified:
UEFI Only
CSM disabled
Secure Boot disabled
SATA controller enabled
SATA drive enabled
SATA mode: AHCI
Hard Disk Pre-delay disabled
BitLocker is disabled on both Windows and the data partition.
FydeOS image
Downloaded image: FydeOS_for_PC_iris_v23.0-SP1-io.bin.zip
Installer build shown:
16700.56.23.51 (Release Build v23.0-SP1) stable-channel amd64-fydeos_iris-io
USB creation methods tried:
balenaEtcher
Rufus
Both produced the same result.
Dual-boot layout
I created a dedicated target partition on the internal GPT disk:
/dev/sda1 — 100 MB EFI System Partition
/dev/sda3 — Windows C: (~476.78 GB)
/dev/sda4 — data partition (~405.27 GB)
/dev/sda5 — dedicated FydeOS target (~48.83 GB)
Windows Recovery partition — ~530 MB
The FydeOS target was initially NTFS and later ended up reported as RAW after the failed install. I did not manually reformat it after the failure.
Installer boot options tried
I tried all three boot-entry options:
Add a UEFI boot menu option for me
Configure rEFInd for me
Do nothing here, I will configure it myself
All three failed to produce a bootable FydeOS install.
Installation errors observed
First error
During one attempt:
Safe format /dev/sda5
Un-mounting the partition:/dev/sda5
umount: /tmp/install_kernel_Mgyqu: target is busy.
The partition is being used, abort.
Error occurred, the log file: /tmp/fydeos_dualboot.log
The installer continued after this point.
Later log sequence
I also captured:
GptValidityCheck() returned 0: GPT_SUCCESS
Setting boot target to /dev/loop13p3:
Partition PartitionNum(3), Slot A
Running EfiPostInstall.
Creating EFI boot entry.
GenerateFileDevicePathFromEsp triggered efi error 1:
linux.cc:449:device_get rc=1
readlink of /sys/block/loop13/device failed:
No such file or directory
Adding EFI Boot entry.
ChromeosChrootPostinst complete
Installation to ‘/dev/loop13’ complete.
Please shutdown, remove the USB device, cross your fingers, and reboot.
Recycling system resources…
partx: /dev/loop13: error deleting partition 12
Result after reboot
After removing the USB and rebooting:
Lenovo F12 boot menu showed only:
Windows Boot Manager
USB device
No FydeOS boot entry appeared
Checking the ESP from Windows showed only:
EFI\Microsoft
EFI\Boot
There was no obvious FydeOS/ChromeOS EFI directory.
Current state of the target partition
After the failed install, Windows Disk Management and DiskPart report the 48.83 GB target as:
File system: RAW
Status: Healthy
Drive letter: none
Label: none
Not read-only
Not hidden
Not BitLocker encrypted
Live USB / first-boot issue
I can boot into the FydeOS live/setup environment, but first-run account setup always fails with:
Something went wrong
Sorry, your password could not be verified.
Please check your keyboard layout and try again.
Could not mount cryptohome.
This happens with:
FydeOS account login
local account setup
Google account login
The error is the same regardless of login method.
USB used
16 GB Sony USB stick
Same stick works for Windows and Linux flashing/testing
I do not believe the USB stick itself is the root cause
What I’m asking
Please confirm whether this is:
a known issue in FydeOS v23.0-SP1 Intel Modern
related to a dual-boot installer / loop device cleanup bug
related to the cryptohome mount failure in the live setup environment
something specific to the Lenovo ThinkCentre M720q / i5-9500T / UHD 630 platform
If helpful, I can provide the full sequence of installer screenshots/log screenshots, including the final partx error and the cryptohome failure on live boot.
Thank you.
Here is the link of logs screenshot in zip file format it is 240 mb because it is phone captured images as installation screen don’t have any way to download logs in text file :- https://drive.google.com/file/d/1NqrILqxhb3Bc90kVzsb1LA6H8VxXaHsQ/view?usp=drivesdk