Failed while updating the boot sectors for disk1 partition1

Posted by / 21-Jun-2016 22:35

Failed while updating the boot sectors for disk1 partition1

Using Standard FAT32 partition boot record Confirmed new volume has a primary FAT32 boot sector Setting primary FAT32 boot sector for boot... Set bootable USB partition as 0x80 Using Syslinux MBR Found volume GUID \? \Volume\ was already mounted as F:\ Installing Syslinux 4.04... \Volume for write access Could not write Syslinux boot record: [0x00000000] The operation completed successfully. \Volume\ was already mounted as F:\ Re-mounted volume as 'F:' after error 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: 0x26A61F82 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 ... I don't know the exact ISO you used or what OS you are running, which makes it SUPER DIFFICULT to test and help you out... 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: 0x26A61F82 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... Closed Windows format prompt Formatting (Large FAT32)... \Volume for write access Size : 1.8 TB 3907027119 sectors Cluster size 32768 bytes, 512 Bytes Per Sector Volume ID is 1ee5 32 Reserved Sectors, 476816 Sectors per FAT, 2 FATs 61032397 Total clusters 61032396 Free Clusters Clearing out 953728 sectors for reserved sectors, FATs and root cluster... FAT #0 sector at address: 32 FAT #1 sector at address: 476848 Writing partition boot record... Drive has a Zeroed Master Boot Record Partition is already FAT32 LBA... Closed Windows format prompt Formatting (Large FAT32)... \Volume for write access Size : 1.8 TB 3907027119 sectors Cluster size 32768 bytes, 512 Bytes Per Sector Volume ID is 1ee52 32 Reserved Sectors, 476816 Sectors per FAT, 2 FATs 61032397 Total clusters 61032396 Free Clusters Clearing out 953728 sectors for reserved sectors, FATs and root cluster... FAT #0 sector at address: 32 FAT #1 sector at address: 476848 Writing partition boot record... Drive has a Zeroed Master Boot Record Partition is already FAT32 LBA...Since I know using the Disk Part command works, that is the procedure I described in my article.Now, that being said, I'm open to the possibility that I may be wrong about the Disk Management Console and would ask that anyone who has been able to successfully prepare a bootable USB flash drive from the Disk Management Console, please let us know how you went about it. Opened drive \.\PHYSICALDRIVE2 for write access Will use 'F:' as volume mountpoint I/O boundary checks disabled Analyzing existing boot records... Confirmed new volume has a secondary FAT32 boot sector Setting secondary FAT32 boot sector for boot... 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... Using Standard FAT32 partition boot record Confirmed new volume has a primary FAT32 boot sector Setting primary FAT32 boot sector for boot... Set bootable USB partition as 0x80 Using Syslinux MBR Found volume GUID \? \Volume\ was already mounted as F:\ Installing Syslinux 4.04... \Volume for write access Could not write Syslinux boot record: [0x00000000] The operation completed successfully. \Volume\ was already mounted as F:\ Re-mounted volume as 'F:' after error 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: 0x26A908BF 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 Rufus version: 2.6.818 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: 0x26A908BF 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 I tested the image creation and saw no issue on my machine. \Volume for write access Size : 931.5 GB 1953523119 sectors Cluster size 32768 bytes, 512 Bytes Per Sector Volume ID is 1809:1a35 32 Reserved Sectors, 238409 Sectors per FAT, 2 FATs 30516347 Total clusters 30516346 Free Clusters Clearing out 476914 sectors for reserved sectors, FATs and root cluster... FAT #0 sector at address: 32 FAT #1 sector at address: 238441 Writing partition boot record... Drive has a Zeroed Master Boot Record Partition is already FAT32 LBA... TBL (220 bytes) Extracting: F:\efi\boot\(493 bytes) Extracting: F:\(1.3 MB) Extracting: F:\(2.8 MB) Extracting: F:\isolinux\TRANS. \Volume for write access Size : 1.8 TB 3907027119 sectors Cluster size 32768 bytes, 512 Bytes Per Sector Volume ID is 13ec:1b3c 32 Reserved Sectors, 476816 Sectors per FAT, 2 FATs 61032397 Total clusters 61032396 Free Clusters Clearing out 953728 sectors for reserved sectors, FATs and root cluster... FAT #0 sector at address: 32 FAT #1 sector at address: 476848 Writing partition boot record... Drive has a Zeroed Master Boot Record Partition is already FAT32 LBA...

Using a bootable USB to install an operating system (OS) not only makes the installation faster, but also saves a DVD!

Step 1: Insert your USB (4GB preferable) stick to the system and backup all the data from the USB as we are going to format the USB to make it as bootable. To do this, type in CMD in Start menu search field and hit Ctrl Shift Enter.

Alternatively, navigate to Start right click on Command Prompt and select run as administrator.

Now, copy all the files from the Windows 7 folder to the USB flash drive. Remember to change the first boot device to your USB drive in the BIOS.

You should be able to install Windows 7 from your USB flash drive now.

failed while updating the boot sectors for disk1 partition1-21failed while updating the boot sectors for disk1 partition1-30failed while updating the boot sectors for disk1 partition1-84

Drive has a Syslinux Master Boot Record Drive has a FAT32 DOS Partition Boot Record Deleting partitions... Here is my log output: Rufus version: 2.6.818 Windows version: Windows 10 64-bit (Build 10586) 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 Desk USB Device' (0BC12) Device eliminated because it was detected as an USB Hard Drive (score 13 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 Desk USB Device' (0BC12) 1 device found Disk type: Fixed, Sector Size: 512 bytes Cylinders: 121601, Tracks Per Cylinder: 255, Sectors Per Track: 63 Partition type: MBR, NB Partitions: 1 Disk ID: 0x005CD6EF Drive has a Windows 7 Master Boot Record Partition 1: Type: NTFS (0x07) Size: 931.5 GB (1000203837440 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... Created: F:Created: F:Found USB 3.0 device 'Seagate Expansion Desk USB Device' (0BC12) Using label for drive F: 'Android-x86 Live CD' 1 device found Disk type: Fixed, Sector Size: 512 bytes Cylinders: 121601, Tracks Per Cylinder: 255, Sectors Per Track: 63 Partition type: MBR, NB Partitions: 1 Disk ID: 0x00440CB7 Drive has a Syslinux Master Boot Record Partition 1: Type: FAT32 LBA (0x0c) Size: 931.5 GB (1000203836928 bytes) Start Sector: 2048, Boot: Yes, Recognized: Yes Rufus version: 2.7.828 (Test2) 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: 0x26A908BF Drive has an unknown 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... \Volume\ was already mounted as F:\ Re-mounted volume as 'F:' after error 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 I guess I could add a retry for the write operation, when it says that zero bytes were written, but I'm not sure this will actually fix anything, as I am wondering if this could have anything to do with the HD possibly using a 4096-bytes sector size behind the scenes (even though the enclosure reports , but I know Seagate enclosures can be weird). \Volume for write access Size : 1.8 TB 3907027119 sectors Cluster size 32768 bytes, 512 Bytes Per Sector Volume ID is 19e63 32 Reserved Sectors, 476816 Sectors per FAT, 2 FATs 61032397 Total clusters 61032396 Free Clusters Clearing out 953728 sectors for reserved sectors, FATs and root cluster... FAT #0 sector at address: 32 FAT #1 sector at address: 476848 Writing partition boot record... Drive has a Zeroed Master Boot Record Partition is already FAT32 LBA...

One thought on “failed while updating the boot sectors for disk1 partition1”

  1. You may even find that online dating isn’t right for you – if that’s the case, all the better to find out without investing much into the process.