Installing Win7 and shrinking HDD.

[SecretCode]

You'll install windows on your second drive by unplugging your first one. I think this is important ...

Anyway, when you re-plug your first drive, with Kubuntu on it, and boot Kubuntu, you should run sudo update-grub and that should detect the windows and give you dual boot without having to mess around with the drive cables again.

[RibaFish66]

Ok i unplugged the SATA from my drive where is Kubuntu and installed Win7 on 60 GB unloacated place which i created with gparted.But after plugging SATAback to the drive it boots straight to Windows 7 so i cant run

sudo update-grub

Any help?
Sorry my bad i managed to boot into Kubuntu and update grub.It works like you said.Many thanks to you and if you werent so far away i l buy you a beer

[SecretCode]

That means the 1TB is being selected by your BIOS as the boot drive. You'll need to edit the boot order in your BIOS settings - it's different on every motherboard but it's the menu that allows you to set the boot priority order including USB, CD/DVD, and hard drives. (Actually some BIOSes don't have multiple entries for internal drives, only "boot from first HDD"; in that case you would have to ensure that the smaller HDD is listed first in wherever SATA drives parameters are set in your BIOS.)

[RibaFish66]

Very strange thing happened.I installed motherboard drivers in Win 7 so that i can use internet and everything worked fine.I booted into Kubuntu and deleted Win7 partition in gparted (everything went fine) and my full space returned.I updated the grub once again so that it doesnt display that boot screen again and it worked.But the internet speed in Kubuntu was very bad and not consistent so i installed my Realtek drivers for Linux once again and the speed is consistent and fine.Did MBO drivers for Windows somehow screw Realtek drivers i had installed for Kubuntu?

[SecretCode]

Have you finished using Win7 already?

I can't explain that slow internet situation - there's no way an update in Windows should have touched the drivers installed in Kubuntu. But the boot process can change something at the BIOS or firmware level ... a firmware switch or something. When I boot Win 7 after having been using any Linux, it always crashes the first time with an nvstor.sys blue-screen. But thereafter booting it is fine.

[RibaFish66]

Have you finished using Win7 already?

I can't explain that slow internet situation - there's no way an update in Windows should have touched the drivers installed in Kubuntu. But the boot process can change something at the BIOS or firmware level ... a firmware switch or something. When I boot Win 7 after having been using any Linux, it always crashes the first time with an nvstor.sys blue-screen. But thereafter booting it is fine.

I deleted te Windows 7 cause i wanted to see if i could delete the partition without any problems.Now i went again to gparted and i resized my 1 TB drive to 60 GB,I clicked apply and it went so slowly and estimated time was 4 hours but last time it was finished in the matter of minutes.So i canceled the operation,restarted my PC and tried again but this time when i click apply after resizing the drive it gives me some kinda error nad tells me i need to go to gparted website!!!!
This is the error log from Gparted:

GParted 0.8.1 --enable-libparted-dmraid

Libparted 2.3

Shrink /dev/sdb1 from 931.51 GiB to 873.76 GiB  00:00:02    ( ERROR )
    	
calibrate /dev/sdb1  00:00:00    ( SUCCESS )
    	
path: /dev/sdb1
start: 2048
end: 1953525167
size: 1953523120 (931.51 GiB)
check file system on /dev/sdb1 for errors and (if possible) fix them  00:00:00    ( SUCCESS )
    	
ntfsresize -P -i -f -v /dev/sdb1
    	
ntfsresize v2011.4.12AR.4 (libntfs-3g)
Device name : /dev/sdb1
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 936190366208 bytes (936191 MB)
Current device size: 1000203837440 bytes (1000204 MB)
Checking for bad sectors ...
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 69010 MB (7.4%)
Collecting resizing constraints ...
Estimating smallest shrunken size supported ...
File feature Last used at By inode
$MFT : 3222 MB 0
Multi-Record : 237398 MB 462
$MFTMirr : 1 MB 1
Sparse : 122300 MB 497
Ordinary : 237430 MB 927
You might resize at 69009215488 bytes or 69010 MB (freeing 867181 MB).
Please make a test run using both the -n and -s options before real resizing!
shrink file system  00:00:01    ( ERROR )
    	
run simulation  00:00:01    ( SUCCESS )
    	
ntfsresize -P --force /dev/sdb1 -s 938191355903 --no-action
    	
ntfsresize v2011.4.12AR.4 (libntfs-3g)
Device name : /dev/sdb1
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 936190366208 bytes (936191 MB)
Current device size: 1000203837440 bytes (1000204 MB)
New volume size : 938191348224 bytes (938192 MB)
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 69010 MB (7.4%)
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:00    ( ERROR )
    	
ntfsresize -P --force /dev/sdb1 -s 938191355903
    	
ntfsresize v2011.4.12AR.4 (libntfs-3g)
Device name : /dev/sdb1
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 936190366208 bytes (936191 MB)
Current device size: 1000203837440 bytes (1000204 MB)
New volume size : 938191348224 bytes (938192 MB)
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 69010 MB (7.4%)
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])? OK quitting. NO CHANGES have been made to your NTFS volume.
check file system on /dev/sdb1 for errors and (if possible) fix them  00:00:00    ( SUCCESS )
    	
ntfsresize -P -i -f -v /dev/sdb1
    	
ntfsresize v2011.4.12AR.4 (libntfs-3g)
Device name : /dev/sdb1
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 936190366208 bytes (936191 MB)
Current device size: 1000203837440 bytes (1000204 MB)
Checking for bad sectors ...
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 69010 MB (7.4%)
Collecting resizing constraints ...
Estimating smallest shrunken size supported ...
File feature Last used at By inode
$MFT : 3222 MB 0
Multi-Record : 237398 MB 462
$MFTMirr : 1 MB 1
Sparse : 122300 MB 497
Ordinary : 237430 MB 927
You might resize at 69009215488 bytes or 69010 MB (freeing 867181 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:01    ( ERROR )
    	
run simulation  00:00:01    ( SUCCESS )
    	
ntfsresize -P --force /dev/sdb1 --no-action
    	
ntfsresize v2011.4.12AR.4 (libntfs-3g)
Device name : /dev/sdb1
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 936190366208 bytes (936191 MB)
Current device size: 1000203837440 bytes (1000204 MB)
New volume size : 1000203833856 bytes (1000204 MB)
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 69010 MB (7.4%)
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:00    ( ERROR )
    	
ntfsresize -P --force /dev/sdb1
    	
ntfsresize v2011.4.12AR.4 (libntfs-3g)
Device name : /dev/sdb1
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 936190366208 bytes (936191 MB)
Current device size: 1000203837440 bytes (1000204 MB)
New volume size : 1000203833856 bytes (1000204 MB)
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 69010 MB (7.4%)
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])? OK quitting. NO CHANGES have been made to your NTFS volume.

This is the error log from KDE partition manager:

Move partition ‘/dev/sdb1’ to the right by 63.28 GiB and shrink it from 0.91 TiB to 0.85 TiB 
Job: Check file system on partition ‘/dev/sdb1’ 
Command: ntfsresize -P -i -f -v /dev/sdb1 
ntfsresize v2011.4.12AR.4 (libntfs-3g)
Device name        : /dev/sdb1
NTFS volume version: 3.1
Cluster size       : 4096 bytes
Current volume size: 936190366208 bytes (936191 MB)
Current device size: 1000203837440 bytes (1000204 MB)
Checking for bad sectors ...
Checking filesystem consistency ...
Accounting clusters ...
Space in use       : 69010 MB (7.4%)
Collecting resizing constraints ...
Estimating smallest shrunken size supported ...
File feature         Last used at      By inode
$MFT               :      3222 MB             0
Multi-Record       :    237398 MB           462
$MFTMirr           :         1 MB             1
Sparse             :    122300 MB           497
Ordinary           :    237430 MB           927
You might resize at 69009215488 bytes or 69010 MB (freeing 867181 MB).
Please make a test run using both the -n and -s options before real resizing! 
Check file system on partition ‘/dev/sdb1’: Success

Job: Resize file system on partition ‘/dev/sdb1’ to 1,820,807,100 sectors 
Resizing file system from 1,953,523,120 to 1,820,807,100 sectors. 

Command: ntfsresize -P -f /dev/sdb1 -s 932253235200 
ntfsresize v2011.4.12AR.4 (libntfs-3g)
Device name        : /dev/sdb1
NTFS volume version: 3.1
Cluster size       : 4096 bytes
Current volume size: 936190366208 bytes (936191 MB)
Current device size: 1000203837440 bytes (1000204 MB)
New volume size    : 932253229568 bytes (932254 MB)
Checking filesystem consistency ...
Accounting clusters ...
Space in use       : 69010 MB (7.4%)
Collecting resizing constraints ...
Needed relocations : 0 (0 MB)
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])? OK quitting. NO CHANGES have been made to your NTFS volume. 
Resize file system on partition ‘/dev/sdb1’ to 1,820,807,100 sectors: Error

Resize/move failed: Could not resize file system to shrink partition ‘/dev/sdb1’. 

Resizing/moving partition ‘/dev/sdb1’ failed. 
Move partition ‘/dev/sdb1’ to the right by 63.28 GiB and shrink it from 0.91 TiB to 0.85 TiB: Error

[SecretCode]

That's worrying.

If you have interrupted a partitioning operation in the middle you may have got into trouble.

That very last line of the second listing may indicate why it was so slow:

Move partition ‘/dev/sdb1’ to the right by 63.28 GiB and shrink it from 0.91 TiB to 0.85 TiB: Error

If you move a partition - e.g. by changing the free space before it instead of after - then the partition manager will take a very long time. You should only resize and use free space afterwards - which is presumably what you did in the first attempt before installing windows.

Is this what's happened?