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.
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
- Open the Chromium browser and enter
Note: If you’ve lost your FydeOS subscription, please refer to this FAQ for assistance.