Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
i just downloaded a copy of ubuntu 19.10 and attempted to use etcher or woeusb to create a usb key and get the below messages. i have tried in both programs with the key premounted and unmounted. i also have rosa, but for some reason it only runs if i launch it from rooted dolphin. i have checked the ubuntu iso and it's perfect, so not the issue. i've also used "sudo shred -s $((2048*512)) -vzn0 /dev/sde" to reset the key to factory default then formatted it and still the errors. running kununtu 19.10 64 bit on a am3+ 6300 system.
Code:
Something went wrong. If it is a compressed image, please check that the archive is not corrupPed.
Code:
Installation failed!
Exit code: 256
Log:
WoeUSB v@@WOEUSB_VERSION@@
==============================
Error: Target device is currently busy, unmount all mounted partitions in target device then try again
Target device is busy, please make sure you unmount all filesystems on target device or shutdown the computer before detaching it.
Last edited by Grave Digger; 11-13-2019 at 08:59 AM.
why not use dd instead?
make sure usb not mounted in a file manager even,also, as well. do not have a file manager open to connect to it. open terminal issue 'lsblk' to see if system sees it, then run your software, or try using dd instead.
Code:
#dd if=iso of=/dev/sdc bs=1MB conv=sync
sdc = make sure it is the correct device port, use lsblk to get this.
why not use dd instead?
make sure usb not mounted in a file manager even,also, as well. do not have a file manager open to connect to it. open terminal issue 'lsblk' to see if system sees it, then run your software, or try using dd instead.
Code:
#dd if=iso of=/dev/sdc bs=1MB conv=sync
sdc = make sure it is the correct device port, use lsblk to get this.
thanks for the imput butreally does it matter which command i used as long is it achieved it's purpose? that said a team member on the etcher forums suggested i use the deb file instead of the appimage file. while waiting for a response from either there or here i decided to see if unetbootion had finally updated their ppa to work with kubuntu 19.10 and they had. installed it created the key without resetting it as i should be able to, boot and was able to boot the uefi potion on the key. then i uninstalled the etcher appimage, installed it's deb, create ny usb key without resetting the key first, booted, and was able to boot the uefi option. all looks good now. not sure what rosa's issue with having to be run through a rooted dolpgin, but i've got both unet and etcher working properly so not going to worry about rosa. thanks again for the info.
[QUOTE=Grave Digger;6057270]thanks for the imput but really does it matter which command i used as long is it achieved it's purpose? [quote]
As I aid, use your software or dd, as options, and I'd the method to your madness should not matter as long as it is an means to your ends.
Quote:
Originally Posted by Grave Digger
that said a team member on the etcher forums suggested i use the deb file instead of the appimage file. while waiting for a response from either there or here i decided to see if unetbootion had finally updated their ppa to work with kubuntu 19.10 and they had. installed it created the key without resetting it as i should be able to, boot and was able to boot the uefi potion on the key. then i uninstalled the etcher appimage, installed it's deb, create ny usb key without resetting the key first, booted, and was able to boot the uefi option. all looks good now. not sure what rosa's issue with having to be run through a rooted dolpgin, but i've got both unet and etcher working properly so not going to worry about rosa. thanks again for the info.
guess i should of mentioned i am far more comforable with gui for anything disk related. thay's cause i've a nasty habit of hitting the wrong keys a lot. i could just see wanting sde and hitting a, b, d, etc... instead of the e and not catching it till after i hit enter.
guess i should of mentioned i am far more comforable with gui for anything disk related. thay's cause i've a nasty habit of hitting the wrong keys a lot. i could just see wanting sde and hitting a, b, d, etc... instead of the e and not catching it till after i hit enter.
been there done that, more than once, causes one to look closer at their work.
i'm weighing in on this since i just tried to use woeusb to create a windows live pe using GandalfsWindows10PE.iso which woe is specifically designed for along with regular windows iso's. i'm only running kununtu 19.10 and tell everyone for a fact when i was running both linux and 10 there were plenty of times i did not want to reboot and boot into 10 just to create a windows key, and to be honest there is no reason to have to do so. i have used woe on cinnamon, neon, and kubuntu to create my 10 meadia without issue in the past, but for some reason i cannot under kubuntu 19.10. this issue is to try to get woe to work like it's suppose to. rather the op wants to login to windows isn't the issue,they just want to create the key without leacing their linux environment. as techowned5 said it may be an issue with the op's flash drive, i know in my case it is not. i have 4 drives, 2 16gig, and 2 8gig. i can create any linux live environment on any of them without issue using either unetboot or etcher. what i normall have is the live for the os i'm actually running, a live for one i want to test, parted magic live, and the gandalf's for trouble shooting win 10 machines. all of which i've created in the past without issue under the above mentioned os's. the error code i get with woe is 512.
since a couple of completely unhelpful members think it's cute to hijack the one thread about woeusb i'll just ask here do you know of another gui usb key creator for creating windows boot media? thanks
I have found it very difficult sometimes to assist folks over typewritten messages. LQ members by far try their best to offer free help and what they believe is the best for the OP's.
"unmount all mounted partitions in target device" would be my place to start.
That program you have should be a choice to use.
The old instructions for making a usb within windows should work in linux. I can't seem to find them just now.
after some more extensive testing looks like the drive will work find for creating a linux live key, but not for creating a win 10 key. not surprised since in years past iv'e seen hdd's windows didn't like, nut linux didn't have any issue with. oh well looks like time for a replacement key. thanks for attempting to help with this.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.