Linux: Resize NTFS Partition

Hi ..
trying to resize NTFS partition in Linux using ntfsresize.  Getting the following error:
"volume is scheduled for check"

I tried option -f also but it did not resize the partition.
Any idea ....
Thank you for Your Quick Prompts.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David FavorLinux/LXD/WordPress/Hosting SavantCommented:
Looks like your disk is dirty. provides what appears to be the answer.
David FavorLinux/LXD/WordPress/Hosting SavantCommented:
Another simple test.

You might try just rebooting, at which time a correct fsck invocation will likely be run to clean your disk...

Where clean just means running the normal fsck housekeeping. So nothing really wrong with your disk. It's just been running a while + has been flagged to have housekeeping run. Till the housekeeping step runs, you won't be able to do any format change operations, like a resize.
NetRock6Author Commented:
Thanks David.
I saw that answer already and tried 'sudo ntfsfix /dev/sdb1' and still resulted in the same error with ntfsresize.
Also, the system does not have -d option for ntfsfix since ntfsfix is an older version and upgrading it is not an option.
is there any other command line utility to use instead....
Thank you and appreciate your quick reply ....
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

NetRock6Author Commented:
sck invocation will likely be run to clean your disk
Causing a blue screen in windows ....
nociSoftware EngineerCommented:
Are there any applications active to that device? One can only do a correct filesystem check when a device is:

either unmounted
or mounted in a stable state (read only) with no active transactions, and all buffers flushed.

Best is to unmount the disk and then check the device or mount it readonly and check the device.
After that you can resize it and mount it again for use.
Use a Windows boot disk (either CD/DVD or USB), and during install, use SHIFT+F10 to reach a command box.
Then use chkdsk to get the NTFS to a clean state again (assuming no hardware errors are encountered)
NetRock6Author Commented:
I am migrating Windows 10 to a bigger drive. That is why i need to resize it.
I have partitioned the larger drive first by taking the whole size of the drive then,
I took the MBR of the smaller drive using the followings comamnd:
dd if=/dev/sda of=drivea.mbr bs=512 count=1 

Open in new window

and then restore to the bigger drive(sdb) using:
dd of=drivea.mbr of=/dev/sdb bs=512 count=1

Open in new window

I believe this is breaking the ntfsresize. I might need to restore only bs=446 into the larger drive.  
anyone knows the proper procedures migrating from smaller size drive to a larger drive for
windows 10 in the Linux environment.

Thank You for your great help.

NetRock6Author Commented:
Also when I use bs=446, although the bootable flag is set on the larger drive but cannot boot from it.
I get the error: "Booting from the hard drive" with a blinking cursor.... ;(
David FavorLinux/LXD/WordPress/Hosting SavantCommented:
Still best to "clean" your disk first (remove the dirty flag).

If you do anything else, except this step first, you may end up in a situation where you have to completely reformat the drive to get out of the bind you create by missing the clean step.
NetRock6Author Commented:
If I use bs=446, ntfsresize does not complaint anymore, it resizes the disk.
Also if you're migrating from Win10 to a bigger drive, a one on one copy means Win10 will still boot up in the new drive. Making a simple partition bigger (new space is right behind the old partition), can be done LIVE within from the booted Win10 machine (diskmgmt.msc). Obviously, still do a chkdsk (followed by a reboot to actually let it run) before doing it.
NetRock6Author Commented:
I repeated the procedure mentioned in my post above, it worked without any issues.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.