edinhui
commented
7 years ago pcduino8_ubuntu14.04_20160102_preinstalled_opencv2.4.11.img is about 2.6GB, I don't know if it is related to the size.
Closed edinhui closed 6 years ago
edinhui
commented
7 years ago pcduino8_ubuntu14.04_20160102_preinstalled_opencv2.4.11.img is about 2.6GB, I don't know if it is related to the size.
jviotti
commented
7 years ago Hi @edinhui ,
That's indeed very weird. I wonder what could have caused the write operations to hang without any error message.
Is this something you can reproduce every single time? If so, does it always hang at that particular percentage?
lurch
commented
7 years ago I've just tested that image myself using both Etcher v1.0.0 and Etcher v1.1.0 and both were able to write it successfully. Is it possible that your SD card / Flash drive is faulty @edinhui ? Do you have a different card/drive you could try?
szotsaki
commented
7 years ago I also have this problem on openSUSE Leap 42.3, x64. Mine was stuck at 15% for an hour or so. So I closed it. Console didn't show anything useful (apart from the regular status info [13% reached, 14% reached, 15% reached]).
SD card is fully functional, tested with f3.
Edit: the interesting thing is, when 15% was reached, KDE shown that two "drives" (boot and the new OS itself) was mounted from the SD card.
lurch
commented
7 years ago What image were you trying to write @szotsaki ?
Edit: the interesting thing is, when 15% was reached, KDE shown that two "drives" (boot and the new OS itself) was mounted from the SD card.
Hmmm, sounds like the automounter is being a bit over-eager and mounting the partitions before we've finished writing the image :-/ Do you see the same behaviour if you try using dd instead of Etcher? (but if you've not used dd before, be very careful)
jviotti
commented
7 years ago Hmmm, sounds like the automounter is being a bit over-eager and mounting the partitions before we've finished writing the image :-/
@lurch We have an open descriptor to the block device, which should be preventing this. Are you aware of any other way to prevent mounting?
lurch
commented
7 years ago @jviotti Hmmm, is there any way that the child-writer process could die, without Etcher detecting it? That might explain why the devtools console (and Etcher's progress bar) stops updating, and why the open-descriptor to the block device gets released (allowing the automounter to then kick in) ?
jviotti
commented
7 years ago I double checked that we're handling child process exits correctly (and we do), but I now have another theory: this could happen if the IPC channel stops working for some reason.
jviotti
commented
7 years ago And I wonder if the culprit is https://github.com/resin-io/etcher/blob/master/lib/child-writer/writer-proxy.js#L121
utrescu
commented
7 years ago I have the same problem on Fedora 26. Stuck at a random % ( 75%, 80%, ... ) and there are no relevant info in logs.
I have found that the problem occurs when I open Etcher with sudo. Etcher hangs at some point...
sudo ./etcher
However If I open Etcher as regular user (and enters the sudo password in the popup window) all goes OK
jhermsmeier
commented
6 years ago This should be fixed by https://github.com/resin-io/etcher/pull/1843
PilnyTomas
commented
2 years ago By any chance, could this be power-related? I had the same issue (always stopped around 42%). At first, I had the USB card reader connected via USB hub in which was already a number of other devices connected. I tried to connect the USB card reader directly to the port without any other device drawing from that port and it worked the first time.
now is 20:50:06, there is no update for about 24 minutes.