# Standalone install progress does not represent the full installation **URL:** \ **Category:** General Discussions\ **Created:** [May 3, 2022, 1:10pm UTC](https://hub.mender.io/t/standalone-install-progress-does-not-represent-the-full-installation/4922 "2022-05-03T13:10:44Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![jonesv](https://avatars.discourse-cdn.com/v4/letter/j/ac8455/32.png) [@jonesv](https://hub.mender.io/u/jonesv)\ **Post date:** [May 3, 2022, 1:10pm UTC](https://hub.mender.io/t/standalone-install-progress-does-not-represent-the-full-installation/4922/1 "2022-05-03T13:10:44Z")
When installing an artifact from the CLI, I get a progress bar, like so: ```auto $ mender install /tmp/update_artifact Installing Artifact of size 672247296... /etc/mender/scripts/Download_Enter_01: Update status: '' -> 'INSTALLING' .............................................................. - 100 % ``` Which would seem like it is writing the artifact to the “inactive partition”. In this example, the progress bar goes from 0% to 100% in around 70s. What I don’t get is that after this, it takes another 45s to reach the point where it says stuff like: ```auto ArtifactInstall_Enter_01: Change: 'INSTALLING' -> 'INSTALLING' ArtifactInstall_Leave_01: Change: 'INSTALLING' -> 'INSTALLED' Setting up /dev/mmcblk0p6 for use as /var filesystem for root /dev/mmcblk0p3 Use 'commit' to update, or 'rollback' to roll back the update. At least one payload requested a reboot of the device it updated. ``` Which means that the progress bar is actually not giving the progress of the install process. Reading through the code, it seems like the progress bar is related to the `Reader` on the artifact. So here is my question: after the installation process has read the full artifact, what takes another 45s before the installation is complete? And would there be a way to reflect that in the progress bar? It feels weird to have a progress bar that only accounts for 2/3 of the time… ---
**Author:** ![jonesv](https://avatars.discourse-cdn.com/v4/letter/j/ac8455/32.png) [@jonesv](https://hub.mender.io/u/jonesv)\ **Post date:** [May 3, 2022, 1:22pm UTC](https://hub.mender.io/t/standalone-install-progress-does-not-represent-the-full-installation/4922/2 "2022-05-03T13:22:59Z")
More specifically, the [progress bar](https://github.com/mendersoftware/progressbar) seems to be linked to the image `Reader` [here](https://github.com/mendersoftware/mender/blob/master/app/standalone.go#L93-L94), and I see the [following message](https://github.com/mendersoftware/mender/blob/master/installer/dual_rootfs_device.go#L217) appear around when the installation is _actually_ finished: ```auto Wrote %d/%d bytes to the inactive partition ``` Now `StoreUpdate` takes a `image io.Reader` as a parameter, and [copies it “to the inactive partition”](https://github.com/mendersoftware/mender/blob/master/installer/dual_rootfs_device.go#L206): ```auto n, err := io.Copy(dev, image) ``` I am not aware of all the details between the “progress reader” and this “image reader”, but naively I would have expected it to be the same, such that the progress bar reflects that copy. Am I completely off? And is the image copied twice, then, for some reason? ---
**Author:** ![jonesv](https://avatars.discourse-cdn.com/v4/letter/j/ac8455/32.png) [@jonesv](https://hub.mender.io/u/jonesv)\ **Post date:** [May 4, 2022, 10:06am UTC](https://hub.mender.io/t/standalone-install-progress-does-not-represent-the-full-installation/4922/3 "2022-05-04T10:06:11Z")
I had a closer look and, assuming that above, the “progress reader” is indeed the “image reader” (which would make total sense), then the next assumption is that `io.Copy` reads the whole image (which makes the progress bar reach 100%), but then the kernel still needs another 40s to finish writing (to `sync`, so to say). So I am trying to see if I can make `io.Copy` write in a synchronized way, so that the `Reader` represents what’s actually written on disk (and not what’s buffered somewhere on the kernel side). `io.Copy` seems to be using `out, err = os.OpenFile(device, flag, 0)` [here](https://github.com/mendersoftware/mender/blob/a62dcb734d7b552963972bc522f177b1f1f8a316/installer/block_device.go#L156). My next question is therefore whether using a flag like `O_SYNC` would help 😇. ---
**Author:** ![jonesv](https://avatars.discourse-cdn.com/v4/letter/j/ac8455/32.png) [@jonesv](https://hub.mender.io/u/jonesv)\ **Post date:** [May 4, 2022, 1:57pm UTC](https://hub.mender.io/t/standalone-install-progress-does-not-represent-the-full-installation/4922/4 "2022-05-04T13:57:30Z")
I tried to add `flag |= os.O_SYNC` [around here](https://github.com/mendersoftware/mender/blob/a62dcb734d7b552963972bc522f177b1f1f8a316/installer/block_device.go#L112), but it does not seem to make a difference. I would like to try `flag |= os.O_SYNC | os.O_DIRECT`, but I get the error: ```auto installer/block_device.go:116:28: undefined: os.O_DIRECT ``` I tried setting it by hardcoding 00040000 (as per [this resource](https://github.com/sabotage-linux/kernel-headers/blob/master/generic/include/asm-generic/fcntl.h#L48)), i.e. with `flag |= os.O_SYNC | 0o40000`, but while it compiles, it ends up giving an error when running `mender install `: > ERRO[0000] Download failed: Payload: can not install Payload: partition-root: Failed to write the update to the inactive partition: “/dev/mmcblk0p2”: Failed to open the device: “/dev/mmcblk0p2”: open /dev/mmcblk0p2: not a directory Open to suggestions 😊… ---
**Author:** ![jonesv](https://avatars.discourse-cdn.com/v4/letter/j/ac8455/32.png) [@jonesv](https://hub.mender.io/u/jonesv)\ **Post date:** [May 4, 2022, 8:58pm UTC](https://hub.mender.io/t/standalone-install-progress-does-not-represent-the-full-installation/4922/5 "2022-05-04T20:58:21Z")
Finally found it: it’s just that the progress bar reports 100% when it reaches 99%, I believe because that ends up looking better in the logs. In my opinion, that is confusing, and I would rather have the uglier log than have someone wonder what happens during those 40sec after the progress bar reported that it was finished: [fix: remove confusing hack in progress bar logic by JonasVautherin · Pull Request #990 · mendersoftware/mender · GitHub](https://github.com/mendersoftware/mender/pull/990)