Error Resizing Partition/Installing BT5

[Danny09]

Hello all!

I'm having a problem installing Backtrack 5 on my new laptop as a dual boot with Win7. After booting into a LiveUSB and running the installer I get this error when selecting the 'install side by side' option :

"An error occurred while writing the changes to the storage devices.

The resize operation has been aborted."

When I try and do the same resize operation in GParted I get this error:

"An error occurred while applying the operations"

It also gives a massive error dumpt/report:

GParted 0.5.1

Libparted 2.2
Shrink /dev/sdb3 from 445.99 GiB to 325.99 GiB  00:00:07    ( ERROR )
     	
calibrate /dev/sdb3  00:00:01    ( SUCCESS )
     	
path: /dev/sdb3
start: 41463808
end: 976771071
size: 935307264 (445.99 GiB)
check file system on /dev/sdb3 for errors and (if possible) fix them  00:00:02    ( SUCCESS )
     	
ntfsresize -P -i -f -v /dev/sdb3
     	
ntfsresize v2.0.0 (libntfs 10:0:0)
Device name : /dev/sdb3
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 478877315584 bytes (478878 MB)
Current device size: 478877319168 bytes (478878 MB)
Checking for bad sectors ...
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 58417 MB (12.2%)
Collecting resizing constraints ...
Estimating smallest shrunken size supported ...
File feature Last used at By inode
$MFT : 37337 MB 0
Multi-Record : 246922 MB 60992
$MFTMirr : 1 MB 1
Compressed : 246921 MB 61366
Sparse : 246765 MB 68500
Ordinary : 254874 MB 78017
You might resize at 58416926720 bytes or 58417 MB (freeing 420461 MB).
Please make a test run using both the -n and -s options before real resizing!
shrink file system  00:00:02    ( ERROR )
     	
run simulation  00:00:02    ( SUCCESS )
     	
ntfsresize -P --force /dev/sdb3 -s 350026768383 --no-action
     	
ntfsresize v2.0.0 (libntfs 10:0:0)
Device name : /dev/sdb3
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 478877315584 bytes (478878 MB)
Current device size: 478877319168 bytes (478878 MB)
New volume size : 350026760704 bytes (350027 MB)
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 58417 MB (12.2%)
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:00    ( ERROR )
     	
ntfsresize -P --force /dev/sdb3 -s 350026768383
     	
ntfsresize v2.0.0 (libntfs 10:0:0)
ERROR(95): Opening '/dev/sdb3' as NTFS failed: Operation not supported
The NTFS journal file is unclean. Please shutdown Windows properly before
using this software! Note, if you have run chkdsk previously then boot
Windows again which will automatically initialize the journal correctly.
check file system on /dev/sdb3 for errors and (if possible) fix them  00:00:02    ( SUCCESS )
     	
ntfsresize -P -i -f -v /dev/sdb3
     	
ntfsresize v2.0.0 (libntfs 10:0:0)
Device name : /dev/sdb3
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 478877315584 bytes (478878 MB)
Current device size: 478877319168 bytes (478878 MB)
Checking for bad sectors ...
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 58417 MB (12.2%)
Collecting resizing constraints ...
Estimating smallest shrunken size supported ...
File feature Last used at By inode
$MFT : 37337 MB 0
Multi-Record : 246922 MB 60992
$MFTMirr : 1 MB 1
Compressed : 246921 MB 61366
Sparse : 246765 MB 68500
Ordinary : 254874 MB 78017
You might resize at 58416926720 bytes or 58417 MB (freeing 420461 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:00    ( ERROR )
     	
run simulation  00:00:00    ( SUCCESS )
     	
ntfsresize -P --force /dev/sdb3 --no-action
     	
ntfsresize v2.0.0 (libntfs 10:0:0)
Device name : /dev/sdb3
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 478877315584 bytes (478878 MB)
Current device size: 478877319168 bytes (478878 MB)
New volume size : 478877315584 bytes (478878 MB)
Nothing to do: NTFS volume size is already OK.
real resize  00:00:00    ( ERROR )
     	
ntfsresize -P --force /dev/sdb3
     	
ntfsresize v2.0.0 (libntfs 10:0:0)
ERROR(95): Opening '/dev/sdb3' as NTFS failed: Operation not supported
The NTFS journal file is unclean. Please shutdown Windows properly before
using this software! Note, if you have run chkdsk previously then boot
Windows again which will automatically initialize the journal correctly.

========================================

Does anyone have any idea what I'm doing wrong? Any help is greatly appreciated, thanks in advance!

[bareem]

ntfsresize v2.0.0 (libntfs 10:0:0)
ERROR(95): Opening '/dev/sdb3' as NTFS failed: Operation not supported
The NTFS journal file is unclean. Please shutdown Windows properly before
using this software! Note, if you have run chkdsk previously then boot
Windows again which will automatically initialize the journal correctly.


I think it's due to the fact something goes wrong when you shut down win7 and the NTFS file table is probabily not correctly updated .
Try to launch win7, then go to the cmd and run a chkdsk, properly shut down win7 and then try again with the BT installation.

[Archangel-Amael]

Indeed try the tips from the above post. If you haven't created a backup of your win7 partition data might want to do so.
Also make sure you know exactly how many partitions your machine has. Every win7 system I have seen has more than one partition to begin with. 1 with the OS and one that is used for recovery in case something goes wrong. This will show up as such in windows, but BT/linux may not recognize this partition for what it is, but rather as just a partition.

[Archangel-Amael]

Indeed try the tips from the above post. If you haven't created a backup of your win7 partition data might want to do so.
Also make sure you know exactly how many partitions your machine has. Every win7 system I have seen has more than one partition to begin with. 1 with the OS and one that is used for recovery in case something goes wrong. This will show up as such in windows, but BT/linux may not recognize this partition for what it is, but rather as just a partition.