NTFS is Inconsistent



  • I had no problem uploading an image from a stock windows 10 dell vostro. Once I removed the partitions and installed windows 10 pro volume licensed version I can no longer upload the image. I keep getting stuck on NTFS is inconsistent. Even after running chkdsk /f and rebooting 2 times. Before I shutdown the PC i run sysprep, generalize, shutdown option.

    i'm about to quit. What else can i do?

    ** Looking For Hard Drive(s) **

    ...... Displaying Available Devices
    RO RA SSZ BSZ StartSec Size Device
    rw 256 512 1024 0 159744000 /dev/ram0
    rw 256 512 4096 0 1000204886016 /dev/sda
    rw 256 512 4096 2048 523239424 /dev/sda1
    rw 256 512 4096 1024000 104857600 /dev/sda2
    rw 256 512 4096 1228800 16777216 /dev/sda3
    rw 256 512 4096 1261568 999556120576 /dev/sda4
    Disk /dev/ram0: 152.4 MiB, 159744000 bytes, 312000 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes

    Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disklabel type: gpt
    Disk identifier: 03E39A8C-CB66-490F-A307-4E35C04D659F

    Device Start End Sectors Size Type
    /dev/sda1 2048 1023999 1021952 499M Windows recovery environment
    /dev/sda2 1024000 1228799 204800 100M EFI System
    /dev/sda3 1228800 1261567 32768 16M Microsoft reserved
    /dev/sda4 1261568 1953519615 1952258048 930.9G Microsoft basic data

    all_hard_drives: /dev/sda

    disk_label: gpt /dev/sda

    partitions: /dev/sda1
    /dev/sda2
    /dev/sda3
    /dev/sda4

    ...... Found Drive(s)

    ...... Drive(s): /dev/sda

    ** Removing All Files For Existing Image: W10Pro **

    ** Creating Image Schema **
    mount: mounting none on /sys/firmware/efi/efivars failed: No such file or directory
    The protective MBR's 0xEE partition is oversized! Auto-repairing.

    The protective MBR's 0xEE partition is oversized! Auto-repairing.

    Current NVRAM Entries
    efibootmgr: EFI variables are not supported on this system.

    Calculating volume size for /dev/sda1
    Partclone v0.2.90 http://partclone.org
    Starting to clone device (/dev/sda1) to image (/dev/null)
    Reading Super Block
    we need memory: 24228 bytes
    image head 4160, bitmap 15968, crc 4100 bytes
    Calculating bitmap... Please wait...
    used_size:11
    volume_size:524

    Partition Volume Size
    volume_size:524

    Partition Used Size
    used_size:11

    Calculating volume size for /dev/sda2
    Partclone v0.2.90 http://partclone.org
    Starting to clone device (/dev/sda2) to image (/dev/null)
    Reading Super Block
    get device size 104857600 by ioctl BLKGETSIZE64,
    we need memory: 30276 bytes
    image head 4160, bitmap 25600, crc 516 bytes
    Calculating bitmap... Please wait...
    used_size:106
    volume_size:106

    Partition Volume Size
    volume_size:106

    Partition Used Size
    used_size:106

    Calculating volume size for /dev/sda3
    Partclone v0.2.90 http://partclone.org
    Starting to clone device (/dev/sda3) to image (/dev/null)
    Reading Super Block
    get device size 16777216 by ioctl BLKGETSIZE64,
    we need memory: 8772 bytes
    image head 4160, bitmap 4096, crc 516 bytes
    Calculating bitmap... Please wait...
    used_size:17
    volume_size:17

    Partition Volume Size
    volume_size:17

    Partition Used Size
    used_size:17

    ...... Shrinking NTFS Volume On /dev/sda4 (This May Take A Few Minutes)

    ** An Error Has Occurred **

    ...... NTFS is inconsistent. Run chkdsk /f on Windows then reboot it TWICE!



  • Are there any Windows updates waiting to be installed?



  • no but i did find out that the disk is formatted as GPT. would that cause an issue?



  • no, but since it's an EFI system you should be uploading with an EFI pxe boot or usb. From your logs you are uploading with a legacy bios boot option which can cause problems.



  • i built the PC again this time with a UEFI USB. It's a dell Vostro 3670, when i try to upload the image to CD i select onboard IPv4 and it attempts to boot over PXE but Dell loads SupportAssist instead. If I enable legacy boot ROM in BIOS it will PXE boot just fine.

    the wireshark pcap shows erro code, code: option negotiation failed, message: user aborted the transfer. Opcode: Error code (5), source file: pxeboot.0



  • what should the pxe mode be for uefi mode? it seems that is an issue using pxelinux doesnt help. if i select ipxe_efi64 i get a very different outcome when booting ipv4 in uefi mode. still fails with an error but at least it tells me i am connecting to the tftp server so my dhcp options are correct.