On Monday 16 May 2011 17:03:36 Stroller wrote: > On 16/5/2011, at 4:35pm, Mick wrote: > >> GParted is the next choice, then - I understand it to be more than "just > >> a graphical front-end", and I don't think you'll have such good results > >> trying to use command-line tools to expand NTFS partitions. > > > > ... > > After your dd the data over to the new disk you will need to run > > gparted as suggested by Stroller, or use ntfsresize which is what > > gparted uses anyway. > > I believe that GParted uses the ntfsresize *libraries* directly, rather > than the ntfsresize command-line program. > > I believe that's why GParted behaves *better* than ntfsresize - I'm sure > there has been at least one occasion on which I found it better to use > GParted than ntfsresize (which wouldn't do what I wanted). > > I made the quoted statement for a reason.
You could be right, I don't know what gparted runs exactly, but recall from the gparted logs that it runs some sort of script where it sequentially runs ntfsresize (the command, I suppose) --check, then performs a dry run with the --no-action option, then --force to resize the fs and mark it for a consistency check with chkdsk when it finally boots into MSWindows, then I think it checks it again. This is all from memory, so it may do other stuff too, like check for bad sectors, etc. Did you check that the problems you experienced were not due to different ntfsresize versions? -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
