Rufus Failed To Extract Iso

[Jen Ondrey]

Im trying to install Ubuntu 16.04 from a USB drive. I'm using Rufus to create a bootable stick, but everytime I click start, it starts, and then gives the error ISO image extraction failure. What can I do?

for me the case was that I deleted the rufus_files folder rufus created when it's ran for the very first time. Actually, I keep a different folder for softwares, so i only copied .exe after i did my first iso extraction with rufus and deleted the folder (rufus_files).

I was trying to create the bootable USB from my office laptop and got in to this issue. I have read many solutions and it didn't work out.From one answer they said it might be due to the anti-virus effect and i tried using my personal laptop and it did work out.

In my case, the USB drive was encrypted with BitLocker. I had to remove BitLocker from the drive before it worked. In Windows, just search for BitLocker from the start menu, and see if BitLocker-To-Go is enabled for your drive. Disabling it, then trying Rufus again to write Ubuntu to the drive worked.

ii tried DD mode, but my pc wouldnt read the live usb in DD mode

does anyone know why kaos is difficult to install ?

i was able to install opensuse and ubuntu without any hassle or fiddling with different modes.

will kaos ever reach a point where it will be straight-forward and easy to install without worrying about modes and stuff like most major linux distros ?

Use supported way to create Live Media and there is no issue.

Your error is a sign you used Rufus to create Live media, noted many places not to use.

KaOS ie easy to use and install, IF you follow the Guides to create reliable media.

_flash/

If you do not wish to follow the KaOS options for that, you will never be able to use this distro. dd is the same for all distros, so post the exact command you used.

demm

i tried downloading the isowriter for linux but couldnt figure out how to run it, all i got was a bunch of files when i extracted it, so i tried suse studio image writer for windows, but it only uses .raw files, and my kaos is an .iso file , so it wouldnt even work , then i tried rosa image writer , but when installing i get this message

Hello! Well, you should follow this to provide information to the forum: , and use quotes for post the output of the error. OK, so that issue seems to be related that you have used Rufus to create the live usb, and it isn't supported. I don't know how dd didn't work for you... ? You can try one of the following options: _flash/ . And as always, make sure to check md5sum.

Bye

Imagewriter won't work until you compile it or install a precompiled package. The best way for you is to use dd to write the ISO to the usb. Learn how to do it here: -to-copy-an-iso-image-onto-usb-with-dd#351815

do you know where can i get a precompiled package of it to where i can just open and run it ?are there any easy graphical ways of installing kaos good ?i tried the windows writers opensuse writer and rosa, but they didnt work and rosa writer gave me this error on all 3 of my usb sticks![ _Canvas.png][1]

and suse witer uses .raw but my kaos is .iso files, and i didnt understand anything i read in the link you showed me , i dont really know much about command lines and stuff like that

Since you have OpenSuse installed, why not use that to create media, if none of the instructions are clear enough for you? Imagewriter is a tool created by OpenSuse, so they have it in their repos, probably in their default installs too.

demm actually fjmorzan solved all of my problems,in the end all i had to do was use suse windows writer, rename the iso to .raw, thats the most easiest way to do it, i was running around trying different methods and doing so much to get it to work, and the docs mentioned nothing of having to rename .iso to .raw whilst using susewriter in windows.i got kaos up and running now,it looks really good, and i was liking it becuase its a rolling release kde focused distro s,omething brand new,and i was ready to make it my main os, but unfortunatly its not just for me becuase very recently I discovered that you can only stricly use 64bit code, no 32bit software, and i need wine ,skype,playonlinux and stuff like that to have my complete linux setup, i am so upset because i know that i am gonna have to get rid of it and go back to the 'buntu distros.

adrialgo

Great Rufus worked for you this time, but that does not mean you should start spamming this forum with claims no-one has reproduced yet. Rufus has failed users hundreds, maybe even thousands of times, so one successful use is no reason to ignore all failures.

If new Rufus has changed, it needs to be properly tested as working for all before anyone should recommend it.

I've followed the instructions for installing and using Clonezilla, unpacking the .zip file onto my USB "E:" drive running the \utils\win64\syslinux64 -d \syslinux -sfmar E: command, verifying that this copies ldlinux.c32 and ldlinux.sys onto E:\syslinux, then restarting my computer (a Windows 7 laptop), and interrupting the startup to specify the boot device. At that point, I get a DOS-style menu with entries

* ATAPI CD0:* ATA HDD0:* USB HDD:* PCI LAN:

I select the USB HDD: entry and hit , but all that happens is that the selection jumps back to the first entry and then nothing happens. Fortunately, when I select ATA HDD0: (or reboot with interrupting) Windows 7 boots up OK, but unfortunately I'm no closer to backing up my hard drive onto the USB drive.

Chuck, I downloaded Rufus and fired it up, and I have the Rufus 3.10.1647 window open. I see under BOOT SELECTION that it's asking for file (e.g., ubuntu...iso). I don't know what file it's looking for, nor where to get it. I did download CloneZilla itself, but that's a .zip file that I extracted to my USB drive (the volume I want to make bootable), but I don't know if that's relevant? Can you explain further?

Rufus now is working for me, producing a bootable USB drive. It turns out that I had to make one modification to get the drive to boot: I had to change the image mode from ISO to DD. Once I did that, I was able to boot up from the USB drive (after changing the boot order to go to the USB drive first). And then... CloneZilla came up! I started following the instructions there and got to the final (I think...) "are you sure you want to continue (y/n)" BUT then the actual imaging operation failed with an error that the target directory /home/partimag/ was not writable.

When I went into the command line prompt and did ls -al /home/ I saw that the permissions for partimag were root root r-xr-xr-x; indeed not writable, although I noticed another directory /home/user that was (user) writable. I thought maybe I could change the permissions on /home/partimag/ (which would have to be chmod ugo+w) but since my command line session was logged in as user (not root) I couldn't even do the chmod.

You are off to a good start. But it sounds like you are trying to save the image on the same USB drive that you booted with Clonezilla Live. This is possible but not recommended. The best option is to use a small USB boot drive with Clonezilla Live installed (which you have just created) and then use another USB drive to hold the saved image(s).

Chuck, I managed to use Rufus to create a bootable volume containing CloneZilla on an old 16GB memory stick. That booted fine, and once it did, I started CloneZilla; I pulled out the 16GB stick just to make sure I didn't try to write on it. CloneZilla proceeded until the point where I was asked to select the device to mount /home/partimag, I was given three choices:

I chose sdc2 figuring that's where I want the image of sda1 to be stored. I hit , but then got an ominous message Looks like /home/partimag is not mounted normally. It then asked if I wanted to try forcing the mount, telling me "it could be dangerous", but I tried it, alas, still to no avail.

Strongly suggest you create a directory in that 4TB disk.

Choose this directory as the place to save your image.

Ideally you formatted that disk as GPT and either a ext4 or ntfs file system (not fat32).

Progress, but not all there yet: I reformatted the 4TB drive several times, the last using diskmgr, and it appears to have used some extended format because the drive was partitioned into one partition for the entire 4TB.

With that, I have actually been able to successfully mount /home/partimag on the 4TB drive, and then proceed to write the image of my C: drive to the 4TB drive. However, when I ran the post-write check, and in a separate stand-alone check, the check encountered a CRC error at block_id=1488834. I then repeated the same process, and got the same result (although the CRC error was in a different block.

Chuck, I followed the instructions in "check-your-hard-disk...": the program reported no problems on the Windows 7 drive, nor on the USB external drive (the latter ran VERY fast, I guess because it has only the two largish broken image files). I guess I'll just try, try again.

That is good news that the file systems (software) are in good shape on both drives. Next I would run the Disks application Short S.M.A.R.T. test from a live Linux USB drive if you want to check the (hardware) health of your drives. Then if everything is still good you can create another image with Clonezilla Live.

alright so basically whenever i try to download popOs i run into a problem where i dont load straight into the os, rather i load into the Rescueshell where i type commands. I tried doing resume-boot but nothing happened. Help would be appreciated. note that i can download note that i can download psxitarch and other distros like fedora with the normal rescueshell method.

noob404 popos_21_10_im_ps4linux.img.xz

when i type resume-boot i guess the command isnt recognised or something like that because it just passes me down to type another command. Literally no response to the command resume-boot whatsoever.

3a8082e126