New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to open an image from the mapped network drive #2858
Comments
[zrzka] This issue has attached support thread https://jel.ly.fish/#/support-thread~fd2d6412-7ae4-4e8b-a356-a551bc8b3f5c |
IIRC this is because the "mapped drive letter" is only visible to user-level processes, and isn't visible to admin-level processes. Slightly-related discussion in #1436 |
@lurch that makes sense, but this error appears immediately after the image selection. I mean, target device not selected yet, didn't click on the Flash button, just launched Etcher and selected an image. AFAIK elevated privileges are required when I click on the Flash button. |
Maybe there's something going wrong with https://github.com/balena-io/etcher/blob/master/lib/gui/app/os/windows-network-drives.js#L87 🤷♂️ |
@zrzka can you please try this command and paste the output here?
|
@zvin here's the output ...
... let me know if there's anything else I can do. |
@zrzka interesting, the second column should have the share address: something like What is the output of |
|
@zvin there's no share address, because it's VMware Fusion feature. One has to install VMware Tools (aka drivers for Windows) to make it working. Then the Fusion shares folders via these drivers. Not a typical network drive. Thus it will be always missing. I tried other programs and I can easily read / write files from / to these locations. |
I have a fix, but I can't push to GH right now. I'll ping you as soon as I have a version to test. |
@zrzka can you please test with https://github.com/balena-io/etcher/releases/tag/untagged-e2d9117a316adbb6a5d7 |
@zvin do I need any special permissions or ... because I've got 404 when clicking on the link. |
@zvin I can select my image, so, the issue seems to be fixed. But another issue appears when I hit the Flash button: {
"stack":"Error: ENOENT: no such file or directory, open 'Z:\\SharedWithVM\\subfolder\\balena-cloud-rpi3b-test-raspberrypi3-2.38.0+rev1-dev-v9.15.7.img.zip'",
"message":"ENOENT: no such file or directory, open 'Z:\\SharedWithVM\\subfolder\\balena-cloud-rpi3b-test-raspberrypi3-2.38.0+rev1-dev-v9.15.7.img.zip'",
"name":"Error",
"code":"ENOENT",
"syscall":"open",
"errno":-4058,
"image":"balena-cloud-rpi3b-test-raspberrypi3-2.38.0+rev1-dev-v9.15.7.img.zip"
} |
I was kind of expecting this. |
@zvin is the ProviderName being empty (and so being unable to get the underlying network share) an "unusual situation"? Maybe it'd be worth displaying an error message specifically about that, rather than falling through to the ENOENT error? 🤷♂️ |
@lurch we don't know if the read will fail in the writer process at this point. |
@zvin that was expected. Anyway, thanks for investing time to into this. I consider this as an edge case. I mean, why should I use balenaEtcher on Windows, running in VMware Fusion on a macOS when I can use balenaEtcher for macOS directly. Re warning / better error message - we know it, no? Something like ...
... I may be wrong, just thinking aloud about this. |
That's exactly what I was suggesting 😉 |
You can't be sure the writer process won't be able to read your image from here. |
Hitting issues like this with sshfs mounted folder, just like in #1436 |
Sorry to bump a 1.5 year old issue, but I'm also hitting this problem. My workaround has been to map the image using the However, suggesting people use Etcher for writing image files to SD cards for use in RPis, and some of our users don't read the warning on our instructions page about this behaviour. If it's possible, an error message indicating the inability to see a mapped network drive would be a tremendous help troubleshooting write issues, as this is the most common issue I'm seeing with our users. |
[zwhitchcox] This issue has attached support thread https://jel.ly.fish/a5c6201a-392f-4096-8d85-b0b7cbcc4807 |
Sorry, but where is this instruction page where this is mentioned? Link? I see no link to any instructions on https://www.balena.io/etcher/, but maybe I'm missing something.
This would be a very nice addition until the 'real problem' has a solution. And if this is really one of the most common errors people stumble on, then it is quite strange not even changing the error message has been fixed in the 3 years since it's been reported. |
I believe that we have the same issue with 1.7.9 Flashing sdcard.img.xz from a mapped network drive on Win10/Win11 causes "Attention Looks like Etcher lost access to the drive. Did it get unplugged" |
Same here on Windows10 ver 1.18.4 |
Just ran in to this same behavior on Windows 11 with version 1.18.4 with the error pointing at the USB drive being the problem when really it was the image being on a network drive. I was able to successfully load the same image over SMB from my Mac, then after discovering one of the other bug reports that led here I was able to also load the same image to the same USB drive after copying the image to a local disk. If this can't be easily fixed I strongly agree that at least fixing the error to tell the actual problem rather than sending users on a wild goose chase with their media would be very useful. |
I was able to add the file. WORKAROUND/ Please try and let me know if that works out for you. Copy the file to your desktop and select the file straight from the desktop. Simple as that. |
Really? this is not a valid workaround. there is a reason we have the .iso/.whatever on a network drive. it makes 0 sense to need to transfer (for example) a 6GB windows server iso to my desktop just to flash it. it should be able to read from the network share. |
VMware Fusion can share folders from the host OS. It's implemented via mapped network drives.
When I open an image from
Z:\SharedWithVM\...
, etcher thinks that the location isC:\SharedWithVM\...
(Z
->C
) and fails to open the image. Nothing interesting in logs, justENOENT
with wrong path:I've found an old issue with suggested workaround (comes from the Microsoft Support). I have this value already set ...
... and it still doesn't work.
It works if the image is copied to a local drive.
The text was updated successfully, but these errors were encountered: