Rufus 3.10 Portable

[Cora Auch]

Ive 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.

[Update 22.04.]: Rufus hat die Version 3.10 als finale Version bereitgestellt. An der Changelog hat sich gegenber der Beta nichts weiter gendert. Die 3.10 ist nun auch auf der Rufus-Webseite.

fr USB-Sticks ist es bestens geeignet ( wenn man es richtig benutzt) , aber ich mache mir fr ISO-Dateien Multiboot Partitionen (auf SSD) und das geht mit Rufus nicht, mache alles mit Windows Boardmitteln ( Powershell / robocopy)

Das ist natrlich die Perfektion wre auch eine Idee aber lohnt sich bei mir nicht, da ich Images (zumeist Clonezilla, Gparted oder Windows) zu selten verwende und dann vorher immer die aktuelle Version aus dem Netz ziehe und auf den Stick kopiere (ohne Rufus).

rufus brauche ich gar nicht mehr.

ich habe mir ein iodd 2531 gehuse besorgt und ne 500gb ssd eingebaut.

die isos kommen in den iso ordner und kann im men ausgewhlt werden, es knnen so viele isos im ordner wie die ssd es her gibt.

es knnen auch bis zu 4 vhds angelegt werden, win2go 32 und 64 bit z.b.

beim booten kann man auch zwischen mbr oder uefi whlen.

ich kannte das bis letztes jahr nicht, es ist einfach genial.

und nein, ich arbeite da nicht

ich habe hier viele tipps gefunden und dachte ich teile das mal.

I have an ASUS Prime B760M-A D4, i7-12700 with BIOS ver. 0807. I have Configured (2) Seagate 2TB SATA HDD in a RAID1 in the BIOS with VMD for SATA enabled. Windows Serer 2022 Standard loads fine and I have no other errors. I have all the latest drivers from ASUS loaded and the latest Windows updates.

This is a new install on known good hardware. The issue is that when I attempt to load the Hyper-V feature and set the system to reboot, after a good POST and the BIOS hands the system off to the OS, the OS hangs at the blue MS window screen. It is as if it is hanging on a driver. If I manually shut down and got to the recovery environment and set the system to boot to safe mode, it reboots, attempts safe mode, fails, then reboots and rolls back the Hyper-V install. I have attempted this 2x and get the same results.

Yes, I know this platform is not intended to run a server OS, but we have been running server OSs on "workstation" grade platforms for decades and we understand the performance limitations. So, please do not hide behind that as your answer.

As you mentioned, this issue could be related to the compatibility of the components. The motherboard does not support Windows servers and even though it can be installed, it could raise unexpected issues.

Thank you for letting me know this mobo is not designed for Windows Server. We certainly understand that element and have chosen to press forward with the configuration attempt as we have done in the past. I have looked at the suggestions you recommended, and my configuration is set to allow Hyper-V to install as it has in all previous iterations from the 600 chipset down to the 100 chipset. I was not concerned that the i7-12700 was at fault, but rather the new instruction set regarding VRoC and VMD. These are the new wrinkle in the UEFI/BIOS configuration that hides the RAID array behind a new layer. Systems that used IRSTe do not have this problem.

I have installed Hyper-V for Windows 10 on the aforementioned configuration without issue. So, my question is, what is it about the VRoC/VMD instructions that allow Hyper-V to function with Windows 10 and not Server 2022 on this platform?

I wanted to ask you if you could help or guide me. As I read your post that your build is ASUS Prime B760M-A D4, i7-12700. I have almost the same motherboard Asus Prime B760-PLUS D4 and I am having trouble installing Windows Server 2022 Standard because I cannot find the appropriate drivers for the disk controller.

Sorry to hear you are running into issues as well. My issue turned out to be a faulty Windows Server 2022 Feb 2023 Cumulative Update KB5022842. Though MS never officially declared that they "fixed" this particular issue w/ Hyper-V, the update was superseded by the March 2022 CU KB5023705 about a week after I posted about this. I know this might sound trite but download and load the latest drivers from the ASUS global site for your mobo. I have found that the global site tends to have newer divers than the country specific sites.

I have attached a driver set that has been working for me. I download the OS ISO, use Rufus-3.10 to create a UEFI GPT USB 3.0 bootable version of the ISO and then create folders with SATA, VROC f-6, and LAN drivers for each motherboard I work with.

As an unrelated sidebar - If you don't like having the reserve partition at the end of an 10/11/22 OS install, I have attached a zipped set of files that includes a .bat file and two supporting .txt files with instructions on how to create a better arranged set of partitions during OS install. No warranty or responsibility for affects to your system(s) given or implied. Use at your own discretion. Yes, it is a .bat file and not PowerShell. I am an old-school PC hack/builder from the 1990s. Don't make me smack you with my 12 inch 512K ISA slot video card!

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

3a8082e126