So the trouble I’ve had with this box is that it falls in the middle of the bios/UEFI game. I’m dealing with Win7 (doesn’t play UEFI) and an i210 NIC (doesn’t seem to play Legacy). Upping to Win10, and booting fully UEFI would be the fix for this last quibble with this box.

@george1421

I feel like a bit of a dummy. It works now, and I suspect I just needed to run the “chkdsk /f” from prompt instead of what I figure is the less thorough one from disk properties. For completeness I’ve included what didn’t work.

Nice thought, but the thread you note doesn’t hold my solution.
https://forums.fogproject.org/topic/10824/image-upload-deploy-taking-a-long-time/43
Bit locker is off as evidenced by the encryption control commands.
manage-bde -off
manage-bde -status

“Way 1” from the FOG wiki made no change either.
https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit

I believe command prompt “chkdsk /F” corrected the issue. I had previously just used disk check from disk properties, which doesn’t lock the drive. This was, however, in conjunction with a bios setting dealing with power saving that was causing hangs.

@Sebastian-Roth

lspci -nn showed the drive to be in raid mode

using a tutorial on bcdedit via cmd for safemode boot I was able to change the setting without reinstalling windows

now the machine is imaged

resolved and thankyou

coming back to this with a fresh mind and some new info helped

@george1421

Tried disabling Spanning tree with no effect.

It turned out to be a bios/UEFI setting “option rom launch policies.” New to me. In my defense, this box’s bios is pretty massive and clumsy to navigate through, but works now!
I feel stupid, but my issue appears resolved! Thank you very much George. I might not have ever stumbled through those screens again if it weren’t for you.

As an aside, the MAC address cloning is a little odd as fog find and tries to get an IP on the wrong NIC first, before it gives up and tries the next NIC.

@Sebastian-Roth

I’ve typically just restarted, but Fast start was enabled too.

A cold boot with fast-start disabled allowed a good capture.

Thanks so much.

Running FOG 1.5.6

Error(5): Could not map attribute 0x80 in inode 24291: Input/output error

This is a follow up to
https://forums.fogproject.org/topic/13334/mismatched-drive-sizes-in-win10-after-incomplete-capture-with-1-5-5

After correcting the FS size, I ran Windows DISM clean and chkdsk /f which completed succesfully; they gave no errors. I then captured a raw image of the box which completed succesfully.

Attempting to capture a resized image of this computer gave me this error

I ran chkdsk /f on the box, which completed clean before and after the imaging attempt.

Any thoughts on cause or resolution to the error?

Checking file system on
The type of the file system is NTFS.
Volume label is HP.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure …
576000 file records processed.
File verification completed.
12848 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage …
26147 reparse records processed.
657814 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
26147 reparse records processed.

Stage 3: Examining security descriptors …
Cleaning up 5 unused index entries from index $SII of file 0x9.
Cleaning up 5 unused index entries from index $SDH of file 0x9.
Cleaning up 5 unused security descriptors.
Security descriptor verification completed.
40908 data files processed.
CHKDSK is verifying Usn Journal…
36582096 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

223223172 KB total disk space.
66502968 KB in 158976 files.
128652 KB in 40909 indexes.
0 KB in bad sectors.
698964 KB in use by the system.
65536 KB occupied by the log file.
155892588 KB available on disk.

  4096 bytes in each allocation unit.

55805793 total allocation units on disk.
38973147 allocation units available on disk.

Internal Info:
00 ca 08 00 d8 0c 03 00 63 aa 05 00 00 00 00 00 …c…
76 01 00 00 ad 64 00 00 00 00 00 00 00 00 00 00 v…d…

Windows has finished checking your disk.
Please wait while your computer restarts.

@Sebastian-Roth
Gparted fixed it with the “check” command, running what appeared to be the same commands I entered at terminal.

I’ll try to capture it again after I’m more confident the box is ok.

thanks guys

@Tom-Elliott
I double checked. It is MBR and system is on the small 500MB partition.

@Sebastian-Roth

note: -v gave no further info

What now?

@Sebastian-Roth

no apparent change

@Sebastian-Roth
ntfsfix processed, but the FS is still the same size. I guess now I try the previous command again to see if the bootsector error has been cleared to run the resize?

@Sebastian-Roth

The sector and cluster ratios seem appropriate for the partition size. Will the error cause issue?

Any guidance is appreciated. I can google some commands and pretend I know what I’m doing, but I’d rather not botch the box further.

@Sebastian-Roth

I obscured it, but, in file explorer, the 59.8GB is total size.

So using 1.5.5 I tried to capture a win10 box. It failed at 85% (as shown by the bar in fog’s “active tasks”), but rebooted to windows. Fine, but the windows machine still has a minimized OS/system partition.

incongruencies-
Win10 drive list shows OS partition as 60GB and throws errors as it being full.
Admin tools>comp management>storage>disk management- shows the partition as the expected ~180GB size

Any advice on how to un-hose this drive without borking it further? Hopefully someone better versed in this kind of thing might understand the discrepancy.

I have updated to fog 1.5.6, but still hope to salvage the workstation.