Re: Partition Manager: Unable to resize linux partition to use free space BEFORE part
No apologies are necessary and no offense was taken. Miscommunication can and does occur, and as such things go this wasn't a huge one.
Originally Posted by iclestu
This sounds like a bug in the program's handling of CHS addresses vs. LBA addresses. If you don't know what that means, it's the ancient and (today) useless mode of identifying sectors vs. the newer mode. Both modes are built into MBR partition tables, but CHS mode is useless today because it tops out at a bit under 8 GiB. Nonetheless, both need to be computed.
Job: Set geometry of partition ‘/dev/sda4’: Start sector: 351,775,305, length: 255,433,500
Could not set geometry for partition ‘/dev/sda4’ while trying to resize/move it.
Another possibility is that it's an issue related to partition alignment -- on "cylinder" boundaries (obsolete and useless today) vs. on 1 MiB boundaries (which optimizes performance for some modern disks). These two possibilities could actually be related -- if the program requires that partitions start and end on cylinder boundaries, it might not like existing partitions that don't do so, and might issue an error like the one you've quoted.
Either way, it's a bug that's deeper than the user interface. It might be possible to work around it by leaving a small gap between your partitions -- but as you've moved on to GParted, I guess you won't be testing that.
No, the Windows partition (/dev/sda2) problem is unrelated to the error in adjusting /dev/sda4 -- the two are on different partitions and can't be related.
Seems there are two unrelated things at work as Gparted shows an error with the Windows partition. See attached. in retrospect, i notice that neither utility showed the free space in this partition..... I am guessing this is what is causing the above error and that the gui bug is unrelated?
Yes, the GUI bug is unrelated to either of these other issues.
In sum, you've found two distinct bugs in the program and an unrelated bit of data corruption on one partition.
Running CHKDSK from Windows is the only way I know of to fix problems on NTFS. Linux has no good NTFS maintenance tools. (There is one called ntfsfix, but it just does a few very simple tests and then flags the filesystem as requiring further checks under Windows.)
I boot into windows (groaaannnn - i KNOW how many updates its waiting on, been a while!) and do a couple of chkdsk's as suggested by Gparted then see if I can change it?
If I've suggested a solution to a problem and you're not the original poster, do not try my solution! Problems can seem similar but be different, and a good solution to one problem can make another worse. Post a new thread with your problem details.