# Facing unmounting issue on Mender 1.7.0 - Yocto sumo

**URL:** <https://hub.mender.io/t/facing-unmounting-issue-on-mender-1-7-0-yocto-sumo/206>\
**Category:** General Discussions\
**Created:** [February 8, 2019, 12:23pm UTC](https://hub.mender.io/t/facing-unmounting-issue-on-mender-1-7-0-yocto-sumo/206 "2019-02-08T12:23:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ajithpv](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/ajithpv/32/728_2.png) [@ajithpv](https://hub.mender.io/u/ajithpv)\
**Post date:** [February 8, 2019, 12:23pm UTC](https://hub.mender.io/t/facing-unmounting-issue-on-mender-1-7-0-yocto-sumo/206/1 "2019-02-08T12:23:02Z")

</div>

Hi,  
I’m currently using mender 1.7.0 server and Yocto sumo branch on i.MX8 platform.  
The Rocko and 1.6.0 were worked on the same platform.  
But, I’m facing the below issue on Mender 1.7.0 with Sumo branch:

- The mender artifact update will fail with an error saying “_error: update image installation failed: invalid argument_”

By default, the inactive partition is mounted on the platform (even for mender 1.6.0 with Rocko). But it shows some issue for unmounting the inactive partition on sumo with mender 1.7.0.

When I manually unmounted the inactive partition, then it worked!

I have given the complete error log from the server side below:

> 2019-02-08 11:34:38 +0000 UTC debug: handle update fetch state  
> 2019-02-08 11:34:39 +0000 UTC debug: status reported, response 204 No Content  
> 2019-02-08 11:34:39 +0000 UTC debug: Received fetch update response &{200 OK 200 HTTP/1.1 1 1 map[Accept-Ranges:[bytes] X-Amz-Request-Id:[158160583A79D08C] X-Frame-Options:[DENY] Content-Length:[97919488] Connection:[keep-alive] Last-Modified:[Fri, 08 Feb 2019 11:34:23 GMT] Vary:[Origin] Server:[openresty/1.13.6.2] Date:[Fri, 08 Feb 2019 11:34:38 GMT] Content-Security-Policy:[block-all-mixed-content] Strict-Transport-Security:[max-age=63072000; includeSubdomains; preload] X-Content-Type-Options:[nosniff] Content-Type:[application/vnd.mender-artifact] Etag:[“ca6edf1704116bb612e1de959862beea”] X-Xss-Protection:[1; mode=block]] 0x44203ae340 97919488 false false map 0x4420381200 0x44200b04d0}+  
> 2019-02-08 11:34:39 +0000 UTC info: State transition: update-fetch [Download] → update-store [Download]  
> 2019-02-08 11:34:39 +0000 UTC debug: handle update install state  
> 2019-02-08 11:34:39 +0000 UTC debug: status reported, response 204 No Content  
> 2019-02-08 11:34:39 +0000 UTC debug: Read data from device manifest file: device\_type=imx8qxp\_ccu  
> 2019-02-08 11:34:39 +0000 UTC debug: Found needed line: device\_type=imx8qxp\_ccu  
> 2019-02-08 11:34:39 +0000 UTC debug: Current manifest data: imx8qxp\_ccu  
> 2019-02-08 11:34:39 +0000 UTC info: no public key was provided for authenticating the artifact  
> 2019-02-08 11:34:39 +0000 UTC debug: checking if device [imx8qxp\_ccu] is on compatibile device list: [imx8qxp\_ccu]  
> 2019-02-08 11:34:39 +0000 UTC debug: installing update ccu-core-image-minimal-imx8qxp\_ccu.ext4 of size 1568669696  
> 2019-02-08 11:34:39 +0000 UTC debug: Trying to install update of size: 1568669696  
> 2019-02-08 11:34:39 +0000 UTC debug: Active partition: /dev/mmcblk0p2  
> 2019-02-08 11:34:39 +0000 UTC debug: Detected inactive partition /dev/mmcblk0p3, based on active partition /dev/mmcblk0p2  
> 2019-02-08 11:34:39 +0000 UTC warning: Inactive partition “/dev/mmcblk0p3” is mounted at “/run/media/mmcblk0p3”. This might be caused by some “auto mount” service (e.g udisks2) that mounts all block devices. It is recommended to blacklist the partitions used by Mender to avoid any issues.  
> 2019-02-08 11:34:39 +0000 UTC warning: Performing umount on “/run/media/mmcblk0p3”.  
> 2019-02-08 11:34:39 +0000 UTC error: Error unmounting partition /dev/mmcblk0p3  
> 2019-02-08 11:34:39 +0000 UTC error: update image installation failed: invalid argument  
> 2019-02-08 11:34:39 +0000 UTC error: update install failed: installer: failed to read and install update: update: can not install update: &{ccu-core-image-minimal-imx8qxp\_ccu.ext4 384 1000 1000 1568669696 2019-02-08 11:26:28 +0000 UTC 48 ajithpv ajithpv 0 0 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC map}: update: can not install: invalid argument  
> 2019-02-08 11:34:39 +0000 UTC info: State transition: update-store [Download] → fetch-install-retry-wait [Download]  
> 2019-02-08 11:34:39 +0000 UTC debug: handle fetch install retry state  
> 2019-02-08 11:34:39 +0000 UTC debug: wait 1m0s before next fetch/install attempt  
> 2019-02-08 11:35:39 +0000 UTC debug: wait complete  
> 2019-02-08 11:35:39 +0000 UTC info: State transition: fetch-install-retry-wait [Download] → update-fetch [Download]  
> 2019-02-08 11:35:39 +0000 UTC debug: handle update fetch state  
> 2019-02-08 11:35:39 +0000 UTC debug: status reported, response 204 No Content  
> 2019-02-08 11:35:39 +0000 UTC debug: Received fetch update response &{200 OK 200 HTTP/1.1 1 1 map[Content-Type:[application/vnd.mender-artifact] X-Amz-Request-Id:[158160664A34B4C9] X-Xss-Protection:[1; mode=block] Strict-Transport-Security:[max-age=63072000; includeSubdomains; preload] X-Frame-Options:[DENY] Server:[openresty/1.13.6.2] Last-Modified:[Fri, 08 Feb 2019 11:34:23 GMT] Accept-Ranges:[bytes] Content-Security-Policy:[block-all-mixed-content] Etag:[“ca6edf1704116bb612e1de959862beea”] Date:[Fri, 08 Feb 2019 11:35:39 GMT] Connection:[keep-alive] Vary:[Origin] X-Content-Type-Options:[nosniff] Content-Length:[97919488]] 0x44203b9880 97919488 false false map 0x442024eb00 0x44200b0b00}+  
> 2019-02-08 11:35:39 +0000 UTC info: State transition: update-fetch [Download] → update-store [Download]  
> 2019-02-08 11:35:39 +0000 UTC debug: handle update install state  
> 2019-02-08 11:35:39 +0000 UTC debug: status reported, response 204 No Content  
> 2019-02-08 11:35:39 +0000 UTC debug: Read data from device manifest file: device\_type=imx8qxp\_ccu  
> 2019-02-08 11:35:39 +0000 UTC debug: Found needed line: device\_type=imx8qxp\_ccu  
> 2019-02-08 11:35:39 +0000 UTC debug: Current manifest data: imx8qxp\_ccu  
> 2019-02-08 11:35:39 +0000 UTC info: no public key was provided for authenticating the artifact  
> 2019-02-08 11:35:39 +0000 UTC debug: checking if device [imx8qxp\_ccu] is on compatibile device list: [imx8qxp\_ccu]  
> 2019-02-08 11:35:39 +0000 UTC debug: installing update ccu-core-image-minimal-imx8qxp\_ccu.ext4 of size 1568669696  
> 2019-02-08 11:35:39 +0000 UTC debug: Trying to install update of size: 1568669696  
> 2019-02-08 11:35:39 +0000 UTC debug: Inactive partition: /dev/mmcblk0p3  
> 2019-02-08 11:35:39 +0000 UTC warning: Inactive partition “/dev/mmcblk0p3” is mounted at “/run/media/mmcblk0p3”. This might be caused by some “auto mount” service (e.g udisks2) that mounts all block devices. It is recommended to blacklist the partitions used by Mender to avoid any issues.  
> 2019-02-08 11:35:39 +0000 UTC warning: Performing umount on “/run/media/mmcblk0p3”.  
> 2019-02-08 11:35:39 +0000 UTC error: Error unmounting partition /dev/mmcblk0p3  
> 2019-02-08 11:35:39 +0000 UTC error: update image installation failed: invalid argument  
> 2019-02-08 11:35:39 +0000 UTC error: update install failed: installer: failed to read and install update: update: can not install update: &{ccu-core-image-minimal-imx8qxp\_ccu.ext4 384 1000 1000 1568669696 2019-02-08 11:26:28 +0000 UTC 48 ajithpv ajithpv 0 0 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC map}: update: can not install: invalid argument  
> 2019-02-08 11:35:39 +0000 UTC info: State transition: update-store [Download] → fetch-install-retry-wait [Download]  
> 2019-02-08 11:35:39 +0000 UTC debug: handle fetch install retry state  
> 2019-02-08 11:35:39 +0000 UTC debug: wait 1m0s before next fetch/install attempt  
> 2019-02-08 11:36:39 +0000 UTC debug: wait complete  
> 2019-02-08 11:36:39 +0000 UTC info: State transition: fetch-install-retry-wait [Download] → update-fetch [Download]  
> 2019-02-08 11:36:39 +0000 UTC debug: handle update fetch state  
> 2019-02-08 11:36:39 +0000 UTC debug: status reported, response 204 No Content  
> 2019-02-08 11:36:39 +0000 UTC debug: Received fetch update response &{200 OK 200 HTTP/1.1 1 1 map[Last-Modified:[Fri, 08 Feb 2019 11:34:23 GMT] Strict-Transport-Security:[max-age=63072000; includeSubdomains; preload] Content-Length:[97919488] Content-Security-Policy:[block-all-mixed-content] Etag:[“ca6edf1704116bb612e1de959862beea”] X-Amz-Request-Id:[15816074549CD42A] Content-Type:[application/vnd.mender-artifact] Connection:[keep-alive] Vary:[Origin] Accept-Ranges:[bytes] X-Xss-Protection:[1; mode=block] X-Content-Type-Options:[nosniff] Server:[openresty/1.13.6.2] Date:[Fri, 08 Feb 2019 11:36:39 GMT] X-Frame-Options:[DENY]] 0x44201bc2e0 97919488 false false map 0x4420380300 0x44203a0160}+  
> 2019-02-08 11:36:39 +0000 UTC info: State transition: update-fetch [Download] → update-store [Download]  
> 2019-02-08 11:36:39 +0000 UTC debug: handle update install state  
> 2019-02-08 11:36:39 +0000 UTC debug: status reported, response 204 No Content  
> 2019-02-08 11:36:39 +0000 UTC debug: Read data from device manifest file: device\_type=imx8qxp\_ccu  
> 2019-02-08 11:36:39 +0000 UTC debug: Found needed line: device\_type=imx8qxp\_ccu  
> 2019-02-08 11:36:39 +0000 UTC debug: Current manifest data: imx8qxp\_ccu  
> 2019-02-08 11:36:39 +0000 UTC info: no public key was provided for authenticating the artifact  
> 2019-02-08 11:36:39 +0000 UTC debug: checking if device [imx8qxp\_ccu] is on compatibile device list: [imx8qxp\_ccu]  
> 2019-02-08 11:36:39 +0000 UTC debug: installing update ccu-core-image-minimal-imx8qxp\_ccu.ext4 of size 1568669696  
> 2019-02-08 11:36:39 +0000 UTC debug: Trying to install update of size: 1568669696  
> 2019-02-08 11:36:40 +0000 UTC debug: Inactive partition: /dev/mmcblk0p3  
> 2019-02-08 11:36:40 +0000 UTC warning: Inactive partition “/dev/mmcblk0p3” is mounted at “/run/media/mmcblk0p3”. This might be caused by some “auto mount” service (e.g udisks2) that mounts all block devices. It is recommended to blacklist the partitions used by Mender to avoid any issues.  
> 2019-02-08 11:36:40 +0000 UTC warning: Performing umount on “/run/media/mmcblk0p3”.  
> 2019-02-08 11:36:40 +0000 UTC error: Error unmounting partition /dev/mmcblk0p3  
> 2019-02-08 11:36:40 +0000 UTC error: update image installation failed: invalid argument  
> 2019-02-08 11:36:40 +0000 UTC error: update install failed: installer: failed to read and install update: update: can not install update: &{ccu-core-image-minimal-imx8qxp\_ccu.ext4 384 1000 1000 1568669696 2019-02-08 11:26:28 +0000 UTC 48 ajithpv ajithpv 0 0 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC map}: update: can not install: invalid argument  
> 2019-02-08 11:36:40 +0000 UTC info: State transition: update-store [Download] → fetch-install-retry-wait [Download]  
> 2019-02-08 11:36:40 +0000 UTC debug: handle fetch install retry state  
> 2019-02-08 11:36:40 +0000 UTC debug: wait 1m0s before next fetch/install attempt  
> 2019-02-08 11:37:40 +0000 UTC debug: wait complete  
> 2019-02-08 11:37:40 +0000 UTC info: State transition: fetch-install-retry-wait [Download] → update-fetch [Download]  
> 2019-02-08 11:37:40 +0000 UTC debug: handle update fetch state  
> 2019-02-08 11:37:40 +0000 UTC debug: status reported, response 204 No Content  
> 2019-02-08 11:37:40 +0000 UTC debug: Received fetch update response &{200 OK 200 HTTP/1.1 1 1 map[Date:[Fri, 08 Feb 2019 11:37:40 GMT] X-Content-Type-Options:[nosniff] Content-Length:[97919488] Connection:[keep-alive] Accept-Ranges:[bytes] Last-Modified:[Fri, 08 Feb 2019 11:34:23 GMT] Vary:[Origin] Strict-Transport-Security:[max-age=63072000; includeSubdomains; preload] Server:[openresty/1.13.6.2] Content-Type:[application/vnd.mender-artifact] X-Xss-Protection:[1; mode=block] X-Frame-Options:[DENY] Content-Security-Policy:[block-all-mixed-content] Etag:[“ca6edf1704116bb612e1de959862beea”] X-Amz-Request-Id:[158160826C3C2489]] 0x44201bc960 97919488 false false map 0x4420380800 0x44203a0f20}+  
> 2019-02-08 11:37:40 +0000 UTC info: State transition: update-fetch [Download] → update-store [Download]  
> 2019-02-08 11:37:40 +0000 UTC debug: handle update install state  
> 2019-02-08 11:37:40 +0000 UTC debug: status reported, response 204 No Content  
> 2019-02-08 11:37:40 +0000 UTC debug: Read data from device manifest file: device\_type=imx8qxp\_ccu  
> 2019-02-08 11:37:40 +0000 UTC debug: Found needed line: device\_type=imx8qxp\_ccu  
> 2019-02-08 11:37:40 +0000 UTC debug: Current manifest data: imx8qxp\_ccu  
> 2019-02-08 11:37:40 +0000 UTC info: no public key was provided for authenticating the artifact  
> 2019-02-08 11:37:40 +0000 UTC debug: checking if device [imx8qxp\_ccu] is on compatibile device list: [imx8qxp\_ccu]  
> 2019-02-08 11:37:40 +0000 UTC debug: installing update ccu-core-image-minimal-imx8qxp\_ccu.ext4 of size 1568669696  
> 2019-02-08 11:37:40 +0000 UTC debug: Trying to install update of size: 1568669696  
> 2019-02-08 11:37:40 +0000 UTC debug: Inactive partition: /dev/mmcblk0p3  
> 2019-02-08 11:37:40 +0000 UTC warning: Inactive partition “/dev/mmcblk0p3” is mounted at “/run/media/mmcblk0p3”. This might be caused by some “auto mount” service (e.g udisks2) that mounts all block devices. It is recommended to blacklist the partitions used by Mender to avoid any issues.  
> 2019-02-08 11:37:40 +0000 UTC warning: Performing umount on “/run/media/mmcblk0p3”.  
> 2019-02-08 11:37:40 +0000 UTC error: Error unmounting partition /dev/mmcblk0p3  
> 2019-02-08 11:37:40 +0000 UTC error: update image installation failed: invalid argument  
> 2019-02-08 11:37:40 +0000 UTC error: update install failed: installer: failed to read and install update: update: can not install update: &{ccu-core-image-minimal-imx8qxp\_ccu.ext4 384 1000 1000 1568669696 2019-02-08 11:26:28 +0000 UTC 48 ajithpv ajithpv 0 0 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC map}: update: can not install: invalid argument  
> 2019-02-08 11:37:40 +0000 UTC info: State transition: update-store [Download] → fetch-install-retry-wait [Download]  
> 2019-02-08 11:37:40 +0000 UTC debug: handle fetch install retry state  
> 2019-02-08 11:37:40 +0000 UTC info: State transition: fetch-install-retry-wait [Download] → update-status-report [none]  
> 2019-02-08 11:37:40 +0000 UTC debug: handle update status report state  
> 2019-02-08 11:37:40 +0000 UTC debug: status reported, response 204 No Content  
> 2019-02-08 11:37:40 +0000 UTC debug: attempting to upload deployment logs for failed update

The corresponding screen shot is given below:

 ![Screenshot%20from%202019-02-08%2017_07_54](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/1X/633cfead3ae4a016ec8166c9d046cf54b52b13b0.png)

 ![Screenshot%20from%202019-02-08%2017_08_34](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/1X/7ad3f694ce8c429e0de15de1013dae8640e10ab9.png)

May I know what is the issue and how to properly resolve this one?

---

<div class="post-metadata">

**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\
**Post date:** [February 8, 2019, 12:37pm UTC](https://hub.mender.io/t/facing-unmounting-issue-on-mender-1-7-0-yocto-sumo/206/2 "2019-02-08T12:37:46Z")

</div>

Similar [thread](https://groups.google.com/a/lists.mender.io/forum/m/#!search/extraconf/mender/7t_b6g2cC8U) on the mailing list.

I would focus on making sure that the inactive parts are not mounted, they really should not be.