Just thought I'd give you an update. And, don't get all bogged down in this unless you have time and want to. Sorry, this is LONG. Please, don't try to deal with it all unless you have enough free time and are in the mood. But maybe you can at least
help me find a repair tool for the internal drive, which is significantly fragmented and Acronis says it is corrupted, which might be the fragmentation.
Bottom line is, best idea makes it appear this Imaging will be delayed while trying to address fragmentation/corruption on the internal "volume." It is 16% fragmented, and the OS Optimization tool will not run on it -- and being as a System Report I generated
with Acronis says the internal drive is "corrupted," I have to think that 16% fragmentation is the corruption. I'm talking of the internal drive, not the external drive.
That same Acronis System Report says there is no free space at all on the primary partition of the internal drive, nor on the last partition, what we have been calling #5. Those are the very two I'm having trouble with on the external drive.
But on the external drive, that "volume" is NOT 16% fragmented, it is only 3% fragmented --I now forget if the OS will run the Optimization on that one, but either way, it remains at 3%, either because it could not run or it ran and leaves that anyway.
Because it is 16% on the internal drive and not the external, that must to mean it happened during or since I upgraded to Win 10.
I also ran chkdsk on the external drive. It identified 7 files it said were corrupted, six small ones (one just a font) plus the Win 8.1 Image. These files likely were already corrupted in Win 8.1, so the image would have them, and that might
be why the Image is listed as corrupt -- it might actually be fine but has those six corrupt files in it. I wrote down the location string to each of them. I could delete the font, but I have no idea what those others are, would not want to delete
them without knowing. One is part of MS Office. A few were .db files, I suppose that means database.
My idea is that that fragmentation or corruption on the "volume" of the internal drive -- and I don't know that that is those six files I just mentioned, besides the Internal has a lot more fragmentation -- might be interfering with Acronis while its
imaging those files and so confusing it, and so Acronis is seeing no space on the external drive. I remind, Acronis System Report sees no free space on those two partitions on the INTERNAL drive, so we know something is going on with that that has nothing
to do with any possible linked partitions on the EXTERNAL drive. I don't even know if that is possible that something on the internal drive can screw up Acronis the reading on the external drive, but I suppose it could while Acronis is dealing with
those files from the Internal drive to make the image. Regardless, I would want to fix that before imaging it anyway. So, I figure fix that, then get back to the Imaging. it will either work or it won't.
But I have nothing but the OS Optimization tool to optimize or otherwise run repairs on the volume. And it won't run on it. I need help from anyone to help me find something to fix that. I know from experience that this is going to take some time.
Well, I saw that Partition Wizard has a tool to do a "Surface Scan." That's all it says. I says only "scan," not repair. Do you think I should run that and hope it repairs? I didn't want to, because you already expressed some concern about running
a third party repair on the drive -- I will have to run a third party repair on it now since I have to repair and the OS has nothing to do it with, at least not that I know of.
I also note, a guy in the Acronis forum ran a test regarding any temporary files put on the drive during the imaging process -- at least three there insisted it does do that, although no one knew how much space that needs. He ran the test with a little
less free space than I have and an Image that would be a little larger than I will have at normal compression -- it worked fine for him, so that is fairly good to indicate that is not the issue.
Following is the long thing I posted about all this today in the Acronis forum --above is a summary of it -- believe it or not, that;s a summary. More details below, but its long, so this might be a good place to stop. I attached the pertinent parts
of the System Report to that Forum post, if I can to this forum, I will do so -- but it is long to add into the body of this already long post:
I just came up with something interesting that raises real questions related to the free space -- on the internal drive, the source drive; this report is not from the target drive, the external drive. This from running a System Report after booting from my
Acronis TI disk. (I was not able to run that on the external drive, Acronis TI does not allow me to choose that drive, does only the internal drive -- maybe because the external drive, while the files on it should be bootable, a USB-connected hard drive is
not bootable on this machine.)
Bottom line, it says there is no free space on the primary partition of the internal drive nor on the main Recovery partition, and it says both those partitions are corrupted -- although, of course, who knows what the corruption is, major or minor (no issue
using using the machine, so I have to think it minor).
I'm attaching the pertinent part from the disks.txt file of the Acronis System Report -- just the pertinent parts of that, not the million miles more of code in between the two pertinent parts. Note: It lists partitions 1 through 6, but excluding #3. #3 is
the hidden 128 MB partition. #4 is the primary partition, and #6 is the main Recovery partition. You can see #4 and #6 are listed up top as corrupt. And if you then look below at Disk 1 Partition 4 and Disk 1 Partition 6, you will see in each:
FreeBlockCount: 0 (0b)
I will mention, I find it distrubing that in other places in Acronis TI, it says there is plenty of free space on the primary partition -- it is disturbing that Acronis is inconsistent about this. But perhaps the inconsistency is because of the effect
of the corruption.
So the question from this will be: Could this corruption on the internal, source drive be interfering in some way that Acronis TI reads the target drive, the external drive, as also not having enough space?
Regardless, it seems I will need to fix this corruption before Imaging -- how? I already know that "volume" is 16% fragmented as shown by the OS tools, as I wrote here yesterday, but the OS won't let me Optimize it. I have nothing else to use to fix anything.
(I am thrown by the OS tool in the same listing showing that C is 0% fragmented -- I thought C was the volume.)
I note, the OS shows the "volume" on the external drive is only 3% fragmented.
So if that fragmentation is the corruption, then maybe the corruption on the internal drive is not on the external drive, that is, the corruption happened after the migration and imaging to the external drive -- I can't know any more because Acronis doesn't
allow me to run System Report on the external drive.
I note, that OS Optimization window also shows that the main Recovery partition on both the internal and external drives is 1% fragmented, and while I can run the Optimization on those, it finishes with it still 1% fragmented. But at least those match for
internal and external, unlike the "volumes."
All else on the drives are listed as 0% fragmented. And everything is reported as healthy, including the volume that is 16% fragmented.
To keep all in context, let me explain:
The primary partition is the very one I'm trying to image to on the external target drive, and I keep getting told there is not enough space for the Image. This report, though, is for the same partition but on the internal drive.
Some background: I previously had Win 8.1 on the internal drive. I migrated the files over to the external drive, and they should be bootable (although this machine won't boot from an external USB-connected hard drive). I then booted from Acronis TI disk
and did the Image of the internal hard drive to the desktop folder of those migrated files on the external drive. The imaging worked perfectly, no issues. The only thing I've done with the external drive since is to move 17.6 GB of free space from the last
partition to the primary partition; that space was added to that partition during the migration.
I then upgraded the internal drive to Windows 10. And now I'm finally getting to trying to Image the Win 10 internal drive to the external, to the desktop folder -- and keep getting that message about needing more space.
A key thing to mention is that all other ways of looking at the free space on both the internal and external machine, from either the OS, from Partition Wizard, and even from Acronis TI, shows plenty of free space on the primary partition on the target
drive. But this Acronis System Report of the internal says no free space on that partition -- which is not the case, there is lots of free space on it.