Not NTFS Partition error 34 during capture
-
@sebastian-roth said in Not NTFS Partition error 34 during capture:
Maybe try scheduling a debug upload task and when you get to the terminal run
fixparts /dev/sda2and answery(es),w(rite),y(es). After that start the upload process by issuingfogcommand. Please see if things changed.I didn’t get time yesterday to focus on this. Here’s the output I received.
I’m not sure this procedure is correct. /dev/sda2 being a partition shouldn’t have a partition table…
I rolled back to the snapshot and ran again with “fixparts /dev/sda” and received no warnings, did a write anyway. Reran the “fog” the process again even though there were no changes. I watched closer all the lines that go by, and notices a few of interest.
It finds and identifies 2 NTFS partitions. Ntfs resize happens without error. Problem only appears with the actual partclone capture.
Clearing the ntfs flag … Failed???
This is just before fog saves the new partition layout and starts the partclone captures.
-
If I change the image settings to “Multiple partition image - single disk (not resizable) -(2)”, the upload proceeds. This tells me the problem is with the partition resize.
This might present me a problem. Previous years we had 500g-1tb spinning drives, this year we switched to 250g ssd drives. The reported device size in Partclone is 267.9g.
I swapped back to zstd compression and 200m split. The capture failed out with this. Trying again with gzip.
edit: Missed the image
-
@john-sartoris Way too many pictures with minimal text inbetween makes it hard to follow.
That all said.
/dev/sda2 does not have a partition table.
FOG’s capture system works as such:
Get the current layout.
Attempt to shrink partitions as possible/required. (All partitions)
Once all partitions are shrunk, get the partition table of the disk.
The problem seems to be something with /dev/sda2 though we don’t know what. Something is causing partclone to not even be able to mount /dev/sda2. -
@tom-elliott said in Not NTFS Partition error 34 during capture:
@john-sartoris Way too many pictures with minimal text inbetween makes it hard to follow.
Sorry about that. I figured that would be the best way to capture the sequence of output from fog. The actual problem isn’t giving much information. Hopefully something else inline would stand out to someone with more detailed experience.
-
@John-Sartoris Maybe provide more information on the partition layout. See in
d1.partitionsandd1.minimum.partitionsin the image directory on your server. -
@sebastian-roth said in Not NTFS Partition error 34 during capture:
@John-Sartoris Maybe provide more information on the partition layout. See in
d1.partitionsandd1.minimum.partitionsin the image directory on your server.d1.minimum.partitions is not in the /images/dev/082… upload folder
d1.partitions
label: dos label-id: 0x86308630 device: /dev/sda unit: sectors /dev/sda1 : start= 2048, size= 1024000, type=7, bootable /dev/sda2 : start= 1026048, size= 523259904, type=7 -
@john-sartoris said in Not NTFS Partition error 34 during capture:
d1.minimum.partitions is not in the /images/dev/082… upload folder
This is because the image is set to non-resizable right now. Nevertheless the partition layout is pretty straight forward and I can’t think of why this wouldn’t work with resizable. At least when looking at the partitions. Possibly there is something going wrong when FOG does shrink the partitions before capturing those. You might want to try
ntfsfix -b -d /dev/sda2in another debug upload session. This is what FOG is doing when it says “Clearing ntfs flag”. -
It’s reporting 2 NTFS partitions. Is this correct with your partition layout?
A default Windows installation will only have one.
-
@quazz said in Not NTFS Partition error 34 during capture:
It’s reporting 2 NTFS partitions. Is this correct with your partition layout?
A default Windows installation will only have one.
If you manually create a full disk partition during the installer, 1 is correct. If you install to a blank disk, the installer will create 2. The first being 100-500mb depending on version. It has been this way since Win7, I think. This small partition is the “Active” boot partition and to the best of my knowledge is used for booting bitlocker encrypted partitions. The primary boot files and some system level things need to remain unencrypted. Fog has specific rules to leave these small partitions basically untouched.
-
@john-sartoris That partition should be FAT32.
-
@quazz said in Not NTFS Partition error 34 during capture:
@john-sartoris That partition should be FAT32.
Not on anything that I have encountered. The EFI partition will be fat32, but the boot has always been NTFS for me. I haven’t gotten into efi much on windows machines.
-
@john-sartoris Hmm, seems they’ve switched back and forth between the two on several occassions, bah.
