Lock the drive to prevent failure on verification

[sajolida]

Hi Etcher, sajolida from Tails behind the keyboard.

We've been recommending Etcher to install Tails since 2019 and we're now serving close to 1000 downloads of Etcher every day! We chose Etcher because it is very easy to use and cross-platform.

So first of all, thanks a bunch! 🤟

People have been reporting verification failures on our GitLab: https://gitlab.tails.boum.org/tails/tails/-/issues/17634

And I've tracked them down to this thread on your forum: https://forums.balena.io/t/checksums-do-not-match/36537

To summarizes this thread, on some Windows installations a partition on the device is being opened in the background and Windows creates a "System Volume Information" folder in it. As a result, the checksum verification fails.

As per comment 38 by @zvin, I understand that the solution to these failures would be to lock the drive on Windows.

I couldn't find any issue related to this on your GitHub, so here is one :) I hope it helps and I hope it's feasible.

• Etcher version: I tried both 1.5.79 and 1.5.81. People on your forum reported this issue as early as 1.5.57.
• Operating system and architecture: Windows 10 64-bit.
• Image flashed: Tails, both ISO and USB images in my case. Raspberry Buster on the thread on your forum.
• Do you see any meaningful error information in the DevTools? I can't reproduce this issue myself.

[thundron]

@sajolida thanks for the report :) I wouldn't know how to lock access to a drive on Windows, as far as I know there's a setting on Windows for the creation of that folder which doesn't look like it's easy to circumvent (more on that here) so this might be something up to the user to do. We can add it to the docs probably since it affects quite many users

[lurch]

https://docs.microsoft.com/en-us/windows/win32/api/winioctl/ni-winioctl-fsctl_lock_volume ?

[thundron]

https://docs.microsoft.com/en-us/windows/win32/api/winioctl/ni-winioctl-fsctl_lock_volume ?

Interesting, I did some experiments and it looks like it could be a viable option, unfortunately we'll need to work on it some time because on current etcher-sdk it gives some errors when trying to lock the drive and/or open with the O_EXLOCK flag on Windows (on macOS it has no issues though and we already do it)

[jellyfish-bot]

[dfunckt] This issue has attached support thread https://jel.ly.fish/edbe9ef6-9607-4eaa-aaf3-56c60af29c94

[jellyfish-bot]

[gelbal] This issue has attached support thread https://jel.ly.fish/a2704e7b-1a15-4124-b5a4-f9204e17e4bb

[jellyfish-bot]

[ereski] This issue has attached support thread https://jel.ly.fish/30aef278-637a-4e90-bb25-5362d456c726

[jellyfish-bot]

[zvin] This issue has attached support thread https://jel.ly.fish/f3cef795-f19b-4afc-940b-294cee8f6ecf

[jellyfish-bot]

[pipex] This issue has attached support thread https://jel.ly.fish/47f1bf68-9cac-41c5-926d-0d0751cf176b

[jellyfish-bot]

[zvin] This issue has attached support thread https://jel.ly.fish/81f9076d-7436-4635-a885-020794244c1b

[jellyfish-bot]

[gelbal] This issue has attached support thread https://jel.ly.fish/2a4f2787-f759-4b7f-a442-ef92e9984ea1

[jellyfish-bot]

[pipex] This issue has attached support thread https://jel.ly.fish/a9790098-b0bd-4299-9de1-43eb335eb392