nvme0n1p2 fatclone c: is not in a valid state

[Psycholiquid]

@Tom-Elliott I’ll give that a try

[george1421]

not sure I’ve I’m sending you on a wild goose chase or not. I just remember reading about win10 systems where the hard drive is left in an inconsistent state after capture of win10.

If I remember correctly, win 10 doesn’t actually shut down the system when you shut it down, it actually suspends the system to allow for faster startup. This is causing an issue with imaging.

One would think a shutdown issues by sysprep would address this. One fix I saw was to power off the machine during a reboot, when the system was in the bios part. Then capture the machine from there.

My point to this is the error may not be a fog issue, but a windows image capture one. (I’m trying to find the supporting documentation to my remembrance).

[Psycholiquid]

@george1421 I am at the end of believing that. If you watch the boot up process it doesn’t actually uefi boot it immediately spins the dots and the logon comes on. It is hard to tell though due to the nvme drive being so fast.

[george1421]

@Psycholiquid Sorry I was in error, this is on the upload side and what I was reading about was actually after the image was deployed you would have to run through some kind of disk fix to basically delete the hibernation file that was in use when the system was captured. I’m still trying to find that article (I read way to much stuff and remember way to little).

[Psycholiquid]

@george1421 Also I have run chkdsk multiple times and it doesn’t help. Seems to be that same partition over and over. windows sucks, I don’t think they even thought about this when they designed it. In order ot get my vol license image onto a surface I have to upgrade the surface OS, I can’t just install it. So that means I have to do reg hacks and such just to be able to sysprep it. I have heard the same complaints form people who use MDT also, so its not like they are trying to squeeze people out.

[Psycholiquid]

how do I get debug to show up in the FOG menu?

[Psycholiquid]

@Psycholiquid nvm I found it.

[Psycholiquid]

@Tom-Elliott This is what I was afraid of, the disk is GPT because that is the UEFI way it was setup. Which is which way most computers are going (All Surfaces are this way)

So where do I go from here?

[Sebastian Roth]

@Psycholiquid While you are in debug mode, can you run fsck /dev/nvme0n1p2

Is this the exact error you are seeing in partclone “Filesystem isn’t in valid state. May be it is not cleanly unmounted.”???

[Psycholiquid]

fsck.vfat: not found
error 2 while executing fsck.vfat /dev/nvme0n1p2

[Psycholiquid]

@Sebastian-Roth Yes that is the error I am seeing in partclone.

[Psycholiquid]

@Sebastian-Roth I can tell you that is the EFI partition of windows that is used to boot it, but I have made sure I am shutting it down cleanly. I have even set the sysprep to shutdown rather than reboot.

[Sebastian Roth]

@Psycholiquid Are you able to mount the partition in debug mode?

mkdir -p /mnt
mount -t vfat /dev/nvme0n1p2 /mnt
ls -al /mnt
umount /mnt

[Psycholiquid]

@Sebastian-Roth yes it does mount and I can see the file structure

[Tom Elliott]

@Psycholiquid What if you add 1 to the d1.fixed_size_partitions file? Will it work then? It looks like it’s growing the EE partition when it really shouldn’t be.

[Sebastian Roth]

@Psycholiquid Looking through the partclone code I found out that there is a thing called “clean shutdown bit/flag” within the FAT (file allocation table). This sounds like it could be related to the NTFS dirty bit but is definitely a whole lot different - after all it’s FAT not NTFS. When searching the web for FAT and dirty bit a lot of people point you to the 0x41 byte (0x25 fog FAT16) of the partition which seams to be some kind of mount/fs-check/dirty marker as well but it’s definitely not the one partclone is complaining about! The one I found is relevant sits in the second reserved FAT entry. This is the best/simplest description I could find - and here another one. With that information I was able to replicate the error message you are seeing. The problem is I used a hex editor and dd to modify this on disk - so I don’t have an easy solution yet. Interestingly enough - even if partclone complains about it I could still mount the filesystem (just as you could). So I have no idea why partclone is checking this flag (where mount is not!) and who/what set this on your system?!?

I haven’t found any tool that would set/unset this “clean shutdown flag” for you. Linux fsck only un/sets the dirty bit AFAIK. Some say you can use windows chkdsk tool but I am not able to confirm this. In your case nvme0n1p2 is the EFI boot partition and I am not sure if you are able to run chkdsk on this partition from within a running windows system?!

I guess we could come up with some C-code to do this for you. Here is a nice example on how to read that flag.

I wonder if anyone else has looked into this yet? Is anyone aware of the difference between dirty bit and clean shutdown bit here in the forums??

[george1421]

@Sebastian-Roth While I don’t have an answer for you on the shutdown part, I wonder if the developers of partclone would have checked this flag on a fat partition, just because of the nature of the fat I would suspect its not necessary. They must do this for a reason. Maybe they can provide a switch to ignore or even reset this bit in the disk structure if possible. Windows 10 is here to stay so they will run across this issue more often than not.

I wonder if the state of this flag could be dependent on the issue I posted before (from memory). I wonder if when the system is sysprepp’d instead of shutdown you pick reboot and then power off the device when it is working through post before it boots. (it may be impossible to catch because of the speed of the system).

[Psycholiquid]

@Sebastian-Roth I was trying the chkdsk this morning within windows I had to add a drive letter to the partition. Not sure if it will work yet, taking a raw image of the machine (of course that works but not efficient) to make the powers that be happy.

chkdsk is what I usually did to any drive that gave this problem. Let me roll it back to the current bad state and try that and I will let you know the results.

[Psycholiquid]

@george1421 I tried both reboot and shutdown, I am not sure catching it while it is EFI booting would have an effect, since it is already flagged as soon as it goes down. I think it is getting flagged during the sysprep due to I have rebooted it multiple times. Or maybe even being flagged during the switch to Audit mode. I am attempting the clear from within windows this morning to see if it helps.

[Psycholiquid]

@Tom-Elliott said:

@Psycholiquid What if you add 1 to the d1.fixed_size_partitions file? Will it work then? It looks like it’s growing the EE partition when it really shouldn’t be.

Not real sure what your talking about here.