Opened drive \.\PHYSICALDRIVE7 for write access Will use 'F:' as volume mountpoint I/O boundary checks disabled Analyzing existing boot records... Opened drive \.\PHYSICALDRIVE2 for write access Will use 'F:' as volume mountpoint I/O boundary checks disabled Analyzing existing boot records... I think I need to think about this a little bit more before I produce another version to test, that can attempt to fix your issue. Rufus version: 2.7.831 (Test4) Windows version: Windows 10 64-bit (Build 10240) Syslinux versions: 4.07/2013-07-25, 6.03/2014-10-06 Grub versions: 0.4.6a, 2.02~beta2 Locale ID: 0x0809 Found USB 3.0 device 'Seagate Expansion USB Device' (0BC1A) Device eliminated because it was detected as an USB Hard Drive (score 33 0) If this device is not an USB Hard Drive, please e-mail the author of this application NOTE: You can enable the listing of USB Hard Drives in 'Advanced Options' (after clicking the white triangle) 0 devices found Found USB 3.0 device 'Seagate Expansion USB Device' (0BC1A) 1 device found Disk type: Fixed, Sector Size: 512 bytes Cylinders: 243201, Tracks Per Cylinder: 255, Sectors Per Track: 63 Partition type: MBR, NB Partitions: 1 Disk ID: 0x02B2718A Drive has a Syslinux Master Boot Record Partition 1: Type: FAT32 LBA (0x0c) Size: 1.8 TB (2000397884928 bytes) Start Sector: 2048, Boot: Yes, Recognized: Yes Scanning image... Confirmed new volume has a secondary FAT32 boot sector Setting secondary FAT32 boot sector for boot... Considering that you are the first person to report this, I would think this is an issue with your hardware or software environment or the specific USB → SATA controller that is used in that Seagate HDD enclosure you have. i tried with a different flash drive and it did work that time but since it was only USB 2.0 i couldn't get the OS running (since it requires USB 3.0 with 20mb/s write speed).
Drive has a Windows 7 Master Boot Record Volume has an unknown Partition Boot Record Deleting partitions... Drive has an unknown Master Boot Record Drive has a FAT32 DOS Partition Boot Record Deleting partitions... ISO analysis: Image is an ISO9660 image Will use '/isolinux/isolinux.cfg' for Syslinux Detected Syslinux version: 4.04/0x4e86cf20 (from '/isolinux/isolinux.bin') Disk image analysis: Image has an unknown Master Boot Record Image is a bootable disk image ISO label: 'Android-x86 Live CD' Size: 2258632704 bytes Has a 4GB file: No Uses Bootmgr: No Uses EFI: No Uses Grub 2: No Uses Grub4DOS: No Uses isolinux: Yes (4.04) With an old menu.c32: No With an old vesamenu.c32: No Uses Kolibri OS: No Uses React OS: No Uses Win PE: No Using image: Remix_OS_for_PC_64_B2016011201_Format operation started Requesting disk access... I would still be very interested to hear what happens when you try with a flash drive or a different enclosure, or with the same enclosure, but on a different PC. I'll try the seagate hdd on another pc now to see if that does me any good.
The problem: you have installed a new kernel with smxi, or you believe you have, but when you reboot, there is no sign of the kernel in your grub boot menu of kernels or operating systems.
This issue is something I just learned the cause of.
In addition, GDisk provides help from the command-line.
Note: GDisk does not function correctly in some instances when the computer has Go Back installed.
GDisk32 Norton Ghost 2002, 2003, and Symantec Ghost 7.5, 8.x include two versions of GDisk: and GDisk32
Unfortunately, there are times we get stuck during the process.
The following error message which reads: "Windows could not format a partition on disk 0. you can now complete the installation without problems.
This document describes the options available for each operation.
The seven operations are: These commands can be run from the DOS command-line or from a batch file (/BATCH).