FedoraQt / MediaWriter

Fedora Media Writer - Write Fedora Images to Portable Media
GNU General Public License v2.0
743 stars 161 forks source link

Checking the written data - prog. sems to have stalled #148

Closed deafandy closed 5 years ago

deafandy commented 6 years ago

so, it's been about 20 minutes, and it's still stuck on checking the written data... i'm guessing it shouldn't take this long...?

specs: portable HDD on USB 2.0; i5 2500K (stock speed) on gigabyte GA-Z68XP-UDP3; 8GB ram; HD7850 graphics (yes it's an old beast, but it runs pretty fast and smooth and rarely crashes) i want to (try and) install fedora on a laptop, not this PC. the laptop is an Acer cloudbook, N3050 CPU, 2GB ram

deafandy commented 6 years ago

okay... just tried again with version 4.1.0 ... appeared to have worked - "your drive may appear smaller" - no kidding, it's not even showing in 'my computer'...

MartinBriza commented 6 years ago

If it got to checking written data, the flash drive should be already overwritten with the image you had chosen. Can you please check if it's bootable? Also it not showing up in "My computer" is normal. If you want to see it again, start FMW and plug the drive in. An option will pop up to return everything to how it was before.

wolfv6 commented 6 years ago

I got the same error installing Fedora Workstation 27, and I am using the same USB stick that worked when installing Fedora Workstation 26.

On the second try it "Finished!"

MartinBriza commented 6 years ago

Did you use the "write after downloading" checkbox or did you start writing manually? edit: Also, @wolfv6 , what OS did you use?

wolfv6 commented 6 years ago

@MartinBriza I was using Fedora Workstation 26.

lizalc commented 6 years ago

I've run into this issue as well. For me, it's only been hit when selecting the "write after downloading" checkbox. The ISO appears to be written, it's just MediaWriter hangs and and won't finish verifying the write (I've waited at least ten minutes after the progress bar finished).

This has happened on an up to date Windows 10 and Fedora Workstation 27 using MediaWriter version 4.1.1. No crash log is generated and nothing is output about it when running MediaWriter from the command line.

ghost commented 6 years ago

Same results as @shvr here, except for using Fedora Media Writer on Fedora Workstation 27.

ghost commented 6 years ago

I got the same stall on the checking the written data just now on updated Windows 10. Also, under apps and features instead of reporting the writer version it shows up as "${VERSIONMAJOR.${VERSIONMINOR}"... but I downloaded it about half an hour ago if that indicates the version, for Fedora 28.

With a second write it finishes promptly.

SteeveDroz commented 6 years ago

I may have a lead: when clicking the "write after downloading" checkbox, a prompt asks for my password. The download time may be longer than the time the password is stored.

Try not to use that option, unless your download speed makes us all envious.

I had the same problem. Clicking "cancel" and then "Create liveUSB" again worked fine.

JLMOX commented 6 years ago

SteeveDross' solution worked fine (cancel then press Create Live USB again). On my second attempt I got the message finished.

jermch commented 6 years ago

Downloaded FedoraMediaWriter-win32-4.1.1.exe on 7/31. Same issue as I selected the write after downloading" option. The FMW app was not responding as it stopped during verifying . I was however able to boot and install from the USB media.

Developers should look into this issue. I have a very fast connection... did not see any prompt for password though.

d-laing commented 6 years ago

I just hit the same issue using Fedora 28. Cancelling and then trying again doesn't work for me.

d-laing commented 6 years ago

I resolved the issue by logging into Fedora as the root user and then running MediaWriter from there, using a blank USB drive. As suggested above, I deselected the "Write after downloading" checkbox.

ghost commented 6 years ago

I had the same issue when I checked "write after downloading", but it worked after re-writing the disk.

ghost commented 5 years ago

Same problem. Windows 10 1803

squishydough commented 5 years ago

I've had the same issue. Windows 10, all updated. Just downloaded Fedora Media Writer an hour ago. I did check to automatically write after download on the attempt that stalled on "Checking the written data."

polatsinan commented 5 years ago

Have the same problem, it takes forever to check the written data. Windows 10 and checked the box to start write after downloading. The issue was opened a year ago, still no fix?

isaiahtaylor commented 5 years ago

Just had this issue after checking "write after downloading."

MartinBriza commented 5 years ago

Oh yeah, I've got to admit that feature doesn't work exactly as I'd like it to. I'll try to do something about it. Also, I'm sorry for keeping you guys waiting so long, I've not been completely present in this repo for a while now... I'll try to be a better maintainer

ghost commented 5 years ago

same issue (and fix) for f29 dont check the box and if you did; cancel and create USB once again

vaporwavie commented 5 years ago

Can confirm: this also happened to me. The way around is basically what @SteeveDroz said. Just to clarify and also to be in the same boat, I checked the "Write after downloading" checkbox before starting the whole process for the first time.

MartinBriza commented 5 years ago

Good news guys! I seem to have a fix for this. For the curious developers, it's in the fix/delayed-write branch. Expect a new release soonish.

MartinBriza commented 5 years ago

Fixed with 5a38833deda9ed4cc57a3d95424466848e0b4279

kevr commented 5 years ago

Downloaded FedoraMediaWriter-win32-4.1.1.exe on 7/31. Same issue as I selected the write after downloading" option. The FMW app was not responding as it stopped during verifying . I was however able to boot and install from the USB media.

Developers should look into this issue. I have a very fast connection... did not see any prompt for password though.

Gotta be the douchiest issue post I've ever seen.