Unable to install Crostini Linux environmemnt

:pushpin:Question Description

Have you searched the community for related issues?

  • [ ] No similar issues found.

Please describe the problem you’ve encountered in detail:

  • Description:
    Error installing Linux
    Error downloading the virtual machine. Please try again.

:computer:System & Device Information

Dell Latitude E5550

  • Hardware & System Configuration:

    • Processor: Intel i5 5th generation
    • Graphics Card(Please specify if there’s a discrete graphics card): Intel HD5500
    • RAM: 16 GB
    • FydeOS Version: 17
  • Relevant System Logs:

    • Open the Chromium browser and enter /var/log/messages to retrieve logs.
    • Log Details:
      2023-10-23T02:45:57.070685Z WARNING dlcservice[1761]: WARNING dlcservice: [bus.cc(644)] Bus::SendWithReplyAndBlock took 21014ms to process message: type=method_call, path=/org/chromium/ImageLoader, interface=org.chromium.ImageLoaderInterface, member=LoadDlcImage
      2023-10-23T02:45:57.070726Z ERR dlcservice[1761]: ERROR dlcservice: [dlc.cc(707)] MountInternal(…): Domain=dlcservice, Code=failedToMountImage, Message=Imageloader LoadDlcImage() call failed.
      2023-10-23T02:45:57.071022Z ERR kernel: [ 5801.194219] device-mapper: table: 254:4: verity: Device must be readonly
      2023-10-23T02:45:57.071034Z WARNING kernel: [ 5801.194221] device-mapper: ioctl: error adding target to table
      2023-10-23T02:45:57.070756Z INFO dlcservice[1761]: INFO dlcservice: [dlc.cc(861)] Changing DLC=termina-dlc state to NOT_INSTALLED
      2023-10-23T02:45:57.070908Z INFO dlcservice[1761]: INFO dlcservice: [metrics.cc(74)] InstallResult metric sent:9
      2023-10-23T02:45:57.070914Z ERR dlcservice[1761]: ERROR dlcservice: [dlc.cc(611)] Mount failed during install finalization for DLC=termina-dlc
      2023-10-23T02:45:57.070920Z ERR dlcservice[1761]: ERROR dlcservice: [dlc_service.cc(353)] Failed to finish install.
      2023-10-23T02:45:57.078293Z ERR kernel: [ 5801.202259] device-mapper: verity: 7:11: metadata block 106407 is corrupted
      2023-10-23T02:45:57.078314Z ERR kernel: [ 5801.202305] device-mapper: verity: verification failure occurred: integrity failure
      2023-10-23T02:45:57.078341Z ERR kernel: [ 5801.202309] Buffer I/O error on dev dm-4, logical block 106384, async page read
      2023-10-23T02:45:57.086027Z ERR kernel: [ 5801.209762] device-mapper: verity: 7:11: metadata block 106407 is corrupted
      2023-10-23T02:45:57.086050Z ERR kernel: [ 5801.209825] device-mapper: verity: verification failure occurred: integrity failure
      2023-10-23T02:45:57.086867Z ERR kernel: [ 5801.210347] device-mapper: verity: 7:11: metadata block 106407 is corrupted
      2023-10-23T02:45:57.086883Z ERR kernel: [ 5801.210392] device-mapper: verity: verification failure occurred: integrity failure
      2023-10-23T02:45:57.086887Z ERR kernel: [ 5801.210396] Buffer I/O error on dev dm-4, logical block 106384, async page read
      2023-10-23T02:45:57.093033Z ERR kernel: [ 5801.216861] device-mapper: verity: 7:11: metadata block 106407 is corrupted
      2023-10-23T02:45:57.093053Z ERR kernel: [ 5801.216904] device-mapper: verity: verification failure occurred: integrity failure
      2023-10-23T02:45:57.093812Z ERR kernel: [ 5801.217792] device-mapper: verity: 7:11: metadata block 106407 is corrupted
      2023-10-23T02:45:57.093835Z ERR kernel: [ 5801.217837] device-mapper: verity: verification failure occurred: integrity failure
      2023-10-23T02:45:57.093839Z ERR kernel: [ 5801.217841] Buffer I/O error on dev dm-4, logical block 106384, async page read
      2023-10-23T02:45:57.098409Z ERR kernel: [ 5801.222448] Buffer I/O error on dev dm-4, logical block 106384, async page read
      2023-10-23T02:45:57.102846Z ERR kernel: [ 5801.226885] Buffer I/O error on dev dm-4, logical block 106384, async page read
      2023-10-23T02:45:57.108019Z ERR kernel: [ 5801.231686] Buffer I/O error on dev dm-4, logical block 106384, async page read
      2023-10-23T02:45:57.114023Z ERR kernel: [ 5801.237333] Buffer I/O error on dev dm-4, logical block 106384, async page read
      2023-10-23T02:45:57.118029Z ERR kernel: [ 5801.241687] Buffer I/O error on dev dm-4, logical block 106384, async page read
      2023-10-23T02:45:57.307962Z ERR kernel: [ 5801.431945] device-mapper: verity: 7:11: reached maximum errors
      2023-10-23T02:46:17.090875Z INFO imageloader[18644]: parent socket has shutdown.
      2023-10-23T02:46:50.655559Z NOTICE temp_logger[19044]: acpitz:25C acpitz:27C TVGA:0C acpitz:29C x86_pkg_temp:49C iwlwifi_1:35C TMEM:37C INT3400_Thermal:20C B0D4:47C TSKN:46C NGFF:36C PL1:15.000W
      2023-10-23T02:47:41.262316Z INFO ml_service[18241]: SIGKILL sent to the worker process: 38
      2023-10-23T02:47:50.780809Z NOTICE temp_logger[19138]: acpitz:25C acpitz:27C TVGA:0C acpitz:29C x86_pkg_temp:49C iwlwifi_1:36C TMEM:37C INT3400_Thermal:20C B0D4:48C TSKN:45C NGFF:36C PL1:15.000W
      2023-10-23T02:48:50.916260Z NOTICE temp_logger[19230]: acpitz:25C acpitz:27C TVGA:0C acpitz:29C x86_pkg_temp:47C iwlwifi_1:36C TMEM:37C INT3400_Thermal:20C B0D4:46C TSKN:45C NGFF:36C PL1:15.000W
      2023-10-23T02:49:45.555319Z WARNING metrics_daemon[3862]: WARNING metrics_daemon: [process_meter.cc(255)] Unknown chrome process type in /usr/bin/crosh
      2023-10-23T02:49:45.555342Z WARNING metrics_daemon[3862]: WARNING metrics_daemon: [process_meter.cc(255)] Unknown chrome process type in /usr/bin/crosh
      2023-10-23T02:49:45.555347Z WARNING metrics_daemon[3862]: WARNING metrics_daemon: [process_meter.cc(255)] Unknown chrome process type in /bin/bash

Note: If you’ve lost your FydeOS subscription, please refer to this FAQ for assistance.


Just reflash it again and try instaling linux again.
Or ctrl alt t
vmc stop termina
vmc start termina
vmc launch termina

open terminal see if it works and installs.
also force shutdown by right clicking it at the buttom bar icon.

I reflashed it using the install icon to a new SSD & tried to install crostini even before activating Android, didn’t work.
Tried
vmc stop termina
vmc start termina
but not
vmc launch termina
termina is not available I think…
vmc start termina
&
vmc launch termina
get a blank cursor with no outcome.

er. got this for
vmc launch termina
Error: operation vm_launch failed: “Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.”

&
vmc start termina gives eventually:
Error: operation vm_start failed: DLC service failed to install module termina-dlc: Failed to install DLC
ERROR - ERROR: command failed

I can install ubuntu xenial with crouton, but the graphics is very poor for the X-Server desktop.

vmc start only works on chromeOS
on fydeOS its vmc launch instead.

However for that to ‘work’ u have to first shut it down
then vmc stop termina
idk if vmc destroy termina works
But give it a go
then start crostini penguin see if it fixes.
If nothing works and yes u should wait once u first boot for things to complete fetch your backups and maybe do a reboot first and only after start the linux installation.

It does not download the virtual machine, so there is no way any command will work for termina.
As I said I already reflashed it.
It doesn’t matter, this is a hobby for me, my main computer is Windows 10/11.

On crosh mate ! U have to put them on ctrl alt t crosh shell command the vmc stop launch etc… I believe u did that no?

Of course on crosh, incidentally I dug back an old Chromebook that I modded & flashed with the cyan release (Acer C720P), & it runs crostini perfectly.

crosh> vmc stop launch
crosh> vmc stop termina
crosh> vmc launch termina
Error: operation vm_launch failed: “Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.”
ERROR - ERROR: command failed
crosh>

Tbh I think there might be some issue with the v17 of fydeos you havent been the only one reporting this issue. On the arm64 boards its not ocasional tbh it works well

Sadly.
I tried to install it on an SSD to an official Chromebook Acer C740P which is I suppose ARM64, but it also failed, this time no error message just stuck on downloading virtual machine message.
Can I have a link to the previous version that worked (maybe 16.X?)

Thats not arm64 its an intel ma brather… But yeah linux should work… thats wierd…

Fyde just released this: https://github.com/openFyde/overlay-amd64-openfyde/releases/tag/r114-r2

Try it.

You’re right I forgot, old age makes me forgetful.
Acer C720P & C740P are both x86_64 Intel.
I will soon try the new release, thanks for the link.
I doubt it will work though…
Does the previous working release include Linux OOB (i.e. onboard), or did you have to download the Virtual Machine?

I am pleased to say that crostini finally installed with this build you gave me the link to DarkevilPT

@penguin:~$ uname -a
Linux penguin 5.15.108-18935-g287d5228d900 #1 SMP PREEMPT Tue Oct 3 12:04:34 PDT 2023 x86_64 GNU/Linux

1 Like

Too quick to claim victory, crostini is again disabled after reboot, machine say repairing itself, then have to reenter all details, after that when trying to download again the linux virtual machine & container it says update FydeOS, when I look to update it says you have the latest version, this is clearly a bug they need to repair.

Yeah but you can try openfyde as well. Anyway yes they have to look at that.

The link you gave me was for openfyde, or maybe I downloaded the wrong one?

Never mind I found the fydeOS version & I expect it to have the same problem for crostini penguin activation, I send feedback so they tackle the issue.
Yeah this link:

Finally so far rebooting & repairing (I don’t know why it does that) didn’t damage the crostini option & I can get a penguin terminal.
I haven’t activated Android yet & expect another cycle of repairing & re-entering all the setup details.
*** this time no repairing*** even after gapps activation
Hopefully this will not disable crostini again.
Side-note: Android didn’t cause any problems even with gapps installed.
I listed the bugs in my last feedback.
Cheers for the convo.

1 Like

Pleased to let you know that even the installed in full to a SSD FydeOS gets crostini activated, this release FydeOS v17.0-SP2 solved the bug.
The other bugs I don’t know.
(validation of Google account ID, sleep disabling wake up were other bugs I cited).
I left this in the feedback section of the OS through about window.
Now I can play with Linux on fydeOS :slight_smile:

If you didnt had the latest version installed before and had bugs with it… theres not much fyde can do…

About the Google Device Activation that has been spoken out its easy.

To become certified with access to the play store you have to:
1 - Install a device ID apk to get this Device ID and register it on your google account.
2 - Register it here: https://www.google.com/android/uncertified/
3 - Give it a day till google approval happens. (Hours minutes or maybe 1 day not in our control).