Topic: [SOLVED] Move /dev/sda5 (NTFS) to the right and shrink it ERROR
Hi Guys, I was just trying to adjust the size of one of mi partitions and something has apparently gone wrong. If you can help you are welcome! I'm not an expert and besides all warnings and advices I haven't done a backup of my information (I know what you would think of me) but I'm in real trouble.
Thank you very much in advance!
THE LOG...
GParted 0.4.8
Libparted 1.9.0
Move /dev/sda5 to the right and shrink it from 801.36 GiB to 600.00 GiB 07:52:27 ( ERROR )
calibrate /dev/sda5 00:00:02 ( SUCCESS )
path: /dev/sda5
start: 272960478
end: 1953525167
size: 1680564690 (801.36 GiB)
calculate new size and position of /dev/sda5 00:00:00 ( SUCCESS )
requested start: 695229003
requested end: 1953520064
requested size: 1258291062 (600.00 GiB)
new start: 695228940
new end: 1953520064
new size: 1258291125 (600.00 GiB)
check file system on /dev/sda5 for errors and (if possible) fix them 00:00:06 ( SUCCESS )
ntfsresize -P -i -f -v /dev/sda5
ntfsresize v2.0.0 (libntfs 10:0:0)
Device name : /dev/sda5
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 860449120768 bytes (860450 MB)
Current device size: 860449121280 bytes (860450 MB)
Checking for bad sectors ...
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 470842 MB (54.7%)
Collecting resizing constraints ...
Estimating smallest shrunken size supported ...
File feature Last used at By inode
$MFT : 327817 MB 0
Multi-Record : 555217 MB 115146
$MFTMirr : 1 MB 1
Compressed : 554271 MB 78838
Ordinary : 556102 MB 115123
You might resize at 470841589760 bytes or 470842 MB (freeing 389608 MB).
Please make a test run using both the -n and -s options before real resizing!
shrink file system 00:00:10 ( SUCCESS )
run simulation 00:00:04 ( SUCCESS )
ntfsresize -P --force /dev/sda5 -s 644245055999 --no-action
ntfsresize v2.0.0 (libntfs 10:0:0)
Device name : /dev/sda5
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 860449120768 bytes (860450 MB)
Current device size: 860449121280 bytes (860450 MB)
New volume size : 644245049856 bytes (644246 MB)
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 470842 MB (54.7%)
Collecting resizing constraints ...
Needed relocations : 0 (0 MB)
Schedule chkdsk for NTFS consistency check at Windows boot time ...
Resetting $LogFile ... (this might take a while)
Updating $BadClust file ...
Updating $Bitmap file ...
Updating Boot record ...
The read-only test run ended successfully.
real resize 00:00:06 ( SUCCESS )
ntfsresize -P --force /dev/sda5 -s 644245055999
ntfsresize v2.0.0 (libntfs 10:0:0)
Device name : /dev/sda5
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 860449120768 bytes (860450 MB)
Current device size: 860449121280 bytes (860450 MB)
New volume size : 644245049856 bytes (644246 MB)
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 470842 MB (54.7%)
Collecting resizing constraints ...
Needed relocations : 0 (0 MB)
Schedule chkdsk for NTFS consistency check at Windows boot time ...
Resetting $LogFile ... (this might take a while)
Updating $BadClust file ...
Updating $Bitmap file ...
Updating Boot record ...
Syncing device ...
Successfully resized NTFS on device '/dev/sda5'.
You can go on to shrink the device for example with Linux fdisk.
IMPORTANT: When recreating the partition, make sure that you
1) create it at the same disk sector (use sector as the unit!)
2) create it with the same partition type (usually 7, HPFS/NTFS)
3) do not make it smaller than the new NTFS filesystem size
4) set the bootable flag for the partition if it existed before
Otherwise you won't be able to access NTFS or can't boot from the disk!
If you make a mistake and don't have a partition table backup then you
can recover the partition table by TestDisk or Parted's rescue mode.
shrink partition from 801.36 GiB to 600.00 GiB 00:00:01 ( SUCCESS )
old start: 272960478
old end: 1953525167
old size: 1680564690 (801.36 GiB)
new start: 272960478
new end: 1531251602
new size: 1258291125 (600.00 GiB)
check file system on /dev/sda5 for errors and (if possible) fix them 00:00:04 ( SUCCESS )
ntfsresize -P -i -f -v /dev/sda5
ntfsresize v2.0.0 (libntfs 10:0:0)
Device name : /dev/sda5
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 644245049856 bytes (644246 MB)
Current device size: 860449121280 bytes (860450 MB)
Checking for bad sectors ...
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 470835 MB (73.1%)
Collecting resizing constraints ...
Estimating smallest shrunken size supported ...
File feature Last used at By inode
$MFT : 327817 MB 0
Multi-Record : 555217 MB 115146
$MFTMirr : 1 MB 1
Compressed : 554271 MB 78838
Ordinary : 556102 MB 115123
You might resize at 470834991104 bytes or 470835 MB (freeing 173411 MB).
Please make a test run using both the -n and -s options before real resizing!
grow file system to fill the partition 00:00:09 ( SUCCESS )
run simulation 00:00:05 ( SUCCESS )
ntfsresize -P --force /dev/sda5 --no-action
ntfsresize v2.0.0 (libntfs 10:0:0)
Device name : /dev/sda5
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 644245049856 bytes (644246 MB)
Current device size: 860449121280 bytes (860450 MB)
New volume size : 860449116672 bytes (860450 MB)
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 470835 MB (73.1%)
Collecting resizing constraints ...
Schedule chkdsk for NTFS consistency check at Windows boot time ...
Resetting $LogFile ... (this might take a while)
Updating $BadClust file ...
Updating $Bitmap file ...
Updating Boot record ...
The read-only test run ended successfully.
real resize 00:00:04 ( SUCCESS )
ntfsresize -P --force /dev/sda5
ntfsresize v2.0.0 (libntfs 10:0:0)
Device name : /dev/sda5
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 644245049856 bytes (644246 MB)
Current device size: 860449121280 bytes (860450 MB)
New volume size : 860449116672 bytes (860450 MB)
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 470835 MB (73.1%)
Collecting resizing constraints ...
WARNING: Every sanity check passed and only the dangerous operations left.
Make sure that important data has been backed up! Power outage or computer
crash may result major data loss!
Are you sure you want to proceed (y/[n])? Schedule chkdsk for NTFS consistency check at Windows boot time ...
Resetting $LogFile ... (this might take a while)
Updating $BadClust file ...
Updating $Bitmap file ...
Updating Boot record ...
Syncing device ...
Successfully resized NTFS on device '/dev/sda5'.
calculate new size and position of /dev/sda5 00:00:00 ( SUCCESS )
requested start: 695228940
requested end: 1953520064
requested size: 1258291125 (600.00 GiB)
new start: 695228940
new end: 1953520064
new size: 1258291125 (600.00 GiB)
check file system on /dev/sda5 for errors and (if possible) fix them 00:00:05 ( SUCCESS )
ntfsresize -P -i -f -v /dev/sda5
ntfsresize v2.0.0 (libntfs 10:0:0)
Device name : /dev/sda5
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 860449116672 bytes (860450 MB)
Current device size: 860449121280 bytes (860450 MB)
Checking for bad sectors ...
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 470842 MB (54.7%)
Collecting resizing constraints ...
Estimating smallest shrunken size supported ...
File feature Last used at By inode
$MFT : 327817 MB 0
Multi-Record : 555217 MB 115146
$MFTMirr : 1 MB 1
Compressed : 554271 MB 78838
Ordinary : 556102 MB 115123
You might resize at 470841589760 bytes or 470842 MB (freeing 389608 MB).
Please make a test run using both the -n and -s options before real resizing!
move file system to the right 07:51:48 ( SUCCESS )
perform read-only test 02:26:35 ( SUCCESS )
using internal algorithm
read 1258291125 sectors
finding optimal blocksize
read 65536 sectors using a blocksize of 128 sectors 00:00:03 ( SUCCESS )
65536 of 65536 read
3.01886 seconds
read 65536 sectors using a blocksize of 256 sectors 00:00:03 ( SUCCESS )
65536 of 65536 read
3.70014 seconds
read 65536 sectors using a blocksize of 512 sectors 00:00:02 ( SUCCESS )
65536 of 65536 read
1.43703 seconds
read 65536 sectors using a blocksize of 1024 sectors 00:00:01 ( SUCCESS )
65536 of 65536 read
1.10518 seconds
read 65536 sectors using a blocksize of 2048 sectors 00:00:01 ( SUCCESS )
65536 of 65536 read
1.01409 seconds
read 65536 sectors using a blocksize of 4096 sectors 00:00:01 ( SUCCESS )
65536 of 65536 read
0.745188 seconds
read 65536 sectors using a blocksize of 8192 sectors 00:00:01 ( SUCCESS )
65536 of 65536 read
0.909588 seconds
read 65536 sectors using a blocksize of 16384 sectors 00:00:00 ( SUCCESS )
65536 of 65536 read
0.678442 seconds
read 65536 sectors using a blocksize of 32768 sectors 00:00:01 ( SUCCESS )
65536 of 65536 read
0.599121 seconds
read 65536 sectors using a blocksize of 65536 sectors 00:00:01 ( SUCCESS )
65536 of 65536 read
0.681358 seconds
optimal blocksize is 32768 sectors (16.00 MiB)
read 1257635765 sectors using a blocksize of 32768 sectors 02:26:21 ( SUCCESS )
1257635765 of 1257635765 read
1258291125 sectors read
perform real move 05:25:13 ( SUCCESS )
using internal algorithm
copy 1258291125 sectors
finding optimal blocksize
copy 65536 sectors using a blocksize of 64 sectors 00:00:04 ( SUCCESS )
65536 of 65536 copied
4.10719 seconds
copy 65536 sectors using a blocksize of 128 sectors 00:00:04 ( SUCCESS )
65536 of 65536 copied
3.84044 seconds
copy 65536 sectors using a blocksize of 256 sectors 00:00:05 ( SUCCESS )
65536 of 65536 copied
4.98139 seconds
copy 65536 sectors using a blocksize of 512 sectors 00:00:05 ( SUCCESS )
65536 of 65536 copied
4.77386 seconds
copy 65536 sectors using a blocksize of 1024 sectors 00:00:02 ( SUCCESS )
65536 of 65536 copied
2.7315 seconds
copy 65536 sectors using a blocksize of 2048 sectors 00:00:03 ( SUCCESS )
65536 of 65536 copied
2.87319 seconds
copy 65536 sectors using a blocksize of 4096 sectors 00:00:03 ( SUCCESS )
65536 of 65536 copied
2.41651 seconds
copy 65536 sectors using a blocksize of 8192 sectors 00:00:02 ( SUCCESS )
65536 of 65536 copied
2.02755 seconds
copy 65536 sectors using a blocksize of 16384 sectors 00:00:01 ( SUCCESS )
65536 of 65536 copied
1.61813 seconds
copy 65536 sectors using a blocksize of 32768 sectors 00:00:02 ( SUCCESS )
65536 of 65536 copied
1.49475 seconds
copy 65536 sectors using a blocksize of 65536 sectors 00:00:01 ( SUCCESS )
65536 of 65536 copied
1.39247 seconds
optimal blocksize is 65536 sectors (32.00 MiB)
copy 1257570229 sectors using a blocksize of 65536 sectors 05:24:41 ( SUCCESS )
1257570229 of 1257570229 copied
1258291125 sectors copied
move partition to the right 00:00:01 ( SUCCESS )
old start: 272960478
old end: 1531251602
old size: 1258291125 (600.00 GiB)
new start: 695228940
new end: 1953520064
new size: 1258291125 (600.00 GiB)
update boot sector of ntfs file system on /dev/sda5 00:00:00 ( SUCCESS )
check file system on /dev/sda5 for errors and (if possible) fix them 00:00:01 ( ERROR )
ntfsresize -P -i -f -v /dev/sda5
ntfsresize v2.0.0 (libntfs 10:0:0)
Device name : /dev/sda5
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 860449116672 bytes (860450 MB)
Current device size: 644245056000 bytes (644246 MB)
ERROR: Current NTFS volume size is bigger than the device size!
Corrupt partition table or incorrect device partitioning?
libparted messages ( INFO )
Error informing the kernel about modifications to partition /dev/sda4 -- Device or resource busy. This means Linux won't know about any changes you made to /dev/sda4 until you reboot -- so you shouldn't mount it or use it in any way before rebooting.
The kernel was unable to re-read the partition table on /dev/sda (Device or resource busy). This means Linux won't know anything about the modifications you made until you reboot. You should reboot your computer before doing anything with /dev/sda.