Thanks for the quick feedback! :D It’s always a pleasure to be on this forum.
@Sebastian-Roth said in NTFS partitions corrupt after capturing resizable image:
Why do you choose resizable if you intend to make a backup copy of this laptop? This backup is supposed to go back to the same machine with the same disk and there shouldn’t be a need to use resizable image type for that reason!
Because it’s the default option, and when in doubt, default options are usually safe. In this case it’s not. I understand why this was a bad choice. Lesson learnt.
The non-resizable images type don’t take up more space for storing the image on your FOG server either.
Good to know!
May I suggest that there shoud be some help text or a link to the wiki in the GUI that warns users about the pros and cons of different types of images?
Did you disable Windows 10 fast boot and properly shutdown before you started the capture?
I always shut down from the command line before capturing. Is that sufficient? As far as I understand that disables fast boot for the next boot. That would be the same as “method 2” in the link you referred to, but a tad less hackish.
There is no way we can prevent users from all different kinds of situations. We try to make FOG with as much care as we can bit it’s like a swiss knife and if someone uses it the wrong way no one will blame the factory or engineers for having created a dangerous tool, right?!
This is true!! But maybe the default option should be the safe(-r) one?
Can you boot using a Windows 10 DVD and get into a CMD shell there and run
chkdsk command? What output do you get from that? We need a picture!
Yes (Win10 flash drive made with Rufus, actually). This is how I ran chkdsk. I took a few pictures, but it reported so many errors that most of them got lost off-screen. It also unlinked a lot of files and threw them in
Just before going home today (GMT+2 here), I tried something else. I restored again, from the Clonezilla backup I have, ran
C:) and copied the backup bootsector over the normal bootsector. Then I rebooted into recovery and used the HP factory reset option instead of Windows’ “reset PC” option. It seemed to work, but it was still running when I left. I’ll post again tomorrow with results!
Relevant Q&A: https://unix.stackexchange.com/questions/349677/unsuccessfully-resized-ntfs-partition-using-gparted-now-it-has-enlarged-partiti