You are not logged in.

#1 2010-08-19 05:40:46

655321
Member
From: Costa Rica
Registered: 2009-12-08
Posts: 412
Website

[SOLVED] Cant use unallocated space after removing windows partitions

Hello all, I was dual-booting arch and Windows 7, but now I dont want windows 7, to make it dual boot I needed to create an extended partition and get all arch partitions in there (/boot, /home, and /)

Now that I dont want windows 7, I want to give all the space that was previosly occupied by windows to arch, but gparted wont let me increase the partition size no idea why.

Here is my fdisk -l :

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048    30716279    15357116   1c  Hidden W95 FAT32 (LBA)
/dev/sda3       186996600   625137344   219070372+   f  W95 Ext'd (LBA)
/dev/sda5       416423680   416616396       96358+  83  Linux
/dev/sda6       416616460   475205451    29294496   83  Linux
/dev/sda7       475205515   617136974    70965730   83  Linux
/dev/sda8       617137038   625137344     4000153+  82  Linux swap / Solaris

sda1 is the laptop recovery partition, in case I want to sell this laptop I should be able to get it to its factory default with this partition

I removed sda2 and sda4 as you can see, which was Windows 7 OS and DATA partitions, how can I use this space with arch?

regards

Last edited by 655321 (2010-10-07 00:50:13)


Linux user #498977
With microsoft you get windows and gates, with linux you get the whole house!
My Blog about ArchLinux and other stuff

Offline

#2 2010-08-19 08:35:20

while
Member
Registered: 2010-05-14
Posts: 35

Re: [SOLVED] Cant use unallocated space after removing windows partitions

Which partition did you try to increase in gparted? If I don't remember it wrong you can only increase the partition next to the removed one.

Offline

#3 2010-08-19 08:40:52

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: [SOLVED] Cant use unallocated space after removing windows partitions

Gparted is a great tool and it's as easy as it gets to do what you need to do. First remove the old  Windows partitions then "grow" the desired partitions.

Offline

#4 2010-08-19 08:43:11

655321
Member
From: Costa Rica
Registered: 2009-12-08
Posts: 412
Website

Re: [SOLVED] Cant use unallocated space after removing windows partitions

while,

I want to give my root partition about 20 Gigs more, and the rest to my home partition. My root would be sda6 and my home sda7.

So,if what you are telling me is right, I can only increase sda3?

Karol,

By grow I think you mean, the resize/move option, I have tried this and it wont let me grow to use the unallocated space


Linux user #498977
With microsoft you get windows and gates, with linux you get the whole house!
My Blog about ArchLinux and other stuff

Offline

#5 2010-08-19 08:46:02

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: [SOLVED] Cant use unallocated space after removing windows partitions

10 GB Windows
20 GB Windows
20 GB Linux
20 GB Linux

remove Windows partitions

30 GB free
20 GB Linux
20 GB Linux

resize first Linux partition and move the rest of free (unallocated) space

25 GB Linux
25 GB free
20 GB Linux

resize the second Linux partition

25 GB Linux
45 GB Linux

Offline

#6 2010-08-19 08:50:39

Kosmonavt
Member
Registered: 2010-02-15
Posts: 100

Re: [SOLVED] Cant use unallocated space after removing windows partitions

Like you have Linux partitions inside Extended, you'll need to resize Extended first.

Offline

#7 2010-08-19 08:59:00

655321
Member
From: Costa Rica
Registered: 2009-12-08
Posts: 412
Website

Re: [SOLVED] Cant use unallocated space after removing windows partitions

Kosmonavt wrote:

Like you have Linux partitions inside Extended, you'll need to resize Extended first.

Yeah just noticed that! thx for the tip, now the only remaining problem is the unallocated space inside the extended partition, like "while" said, I can only resize the partition next to it, and that is the /boot partition, what Im going to do is to resize the /boot partition to use all the unallocated space, then I can drag the other end of this partition to move it and finally resize the root and home partitions.

One more question, Is there any problems/drawbacks having all the arch system and mount points inside an extended/logical partitions?


Linux user #498977
With microsoft you get windows and gates, with linux you get the whole house!
My Blog about ArchLinux and other stuff

Offline

#8 2010-08-19 09:03:47

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: [SOLVED] Cant use unallocated space after removing windows partitions

655321 wrote:
Kosmonavt wrote:

Like you have Linux partitions inside Extended, you'll need to resize Extended first.

Yeah just noticed that! thx for the tip, now the only remaining problem is the unallocated space inside the extended partition, like "while" said, I can only resize the partition next to it, and that is the /boot partition, what Im going to do is to resize the /boot partition to use all the unallocated space, then I can drag the other end of this partition to move it and finally resize the root and home partitions.

One more question, Is there any problems/drawbacks having all the arch system and mount points inside an extended/logical partitions?

IIRC there are 3 numbers: free space "before", partition size and free space "after" - you *can* move the free space around.

Wait a sec, I'm gonna boot the liveCD.

Offline

#9 2010-08-19 09:05:34

Inxsible
Forum Fellow
From: Chicago
Registered: 2008-06-09
Posts: 9,183

Re: [SOLVED] Cant use unallocated space after removing windows partitions

655321 wrote:

Yeah just noticed that! thx for the tip, now the only remaining problem is the unallocated space inside the extended partition, like "while" said, I can only resize the partition next to it, and that is the /boot partition, what Im going to do is to resize the /boot partition to use all the unallocated space, then I can drag the other end of this partition to move it and finally resize the root and home partitions.

One more question, Is there any problems/drawbacks having all the arch system and mount points inside an extended/logical partitions?

you can also move partitions instead on resizing.

no there are no drawbacks but I would have just created a primary partition. dd'ed my existing install into the new partition and then removed the extended partition and then merged the space.

Playing with partitions and ddis extremely dangerous if you don't know what you are doing. Consider yourself warned.


Forum Rules

There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !

Offline

#10 2010-08-19 09:10:49

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: [SOLVED] Cant use unallocated space after removing windows partitions

When you click resize/move you can enter 3 numbers: free space preceding, new size and free space following - you can move all the free space where you need it i.e. next to the partitions you're going to resize. No need to resize /boot, just move the free space around - e.g. set free space preceding to zero.

Offline

#11 2010-08-19 09:11:22

655321
Member
From: Costa Rica
Registered: 2009-12-08
Posts: 412
Website

Re: [SOLVED] Cant use unallocated space after removing windows partitions

Holy &*^%$#@ I started all partition operations, and just noticed I left my laptop charger at work! Hope 5 hours will be enough to get all this done (gparted is working as I type)

I have worked with partitions before but never have had this kind of setup, I do know what im doing and also I case I dont, I have a backup big_smile


Linux user #498977
With microsoft you get windows and gates, with linux you get the whole house!
My Blog about ArchLinux and other stuff

Offline

#12 2010-08-19 09:15:42

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: [SOLVED] Cant use unallocated space after removing windows partitions

655321 wrote:

Holy &*^%$#@ I started all partition operations, and just noticed I left my laptop charger at work! Hope 5 hours will be enough to get all this done (gparted is working as I type)

I have worked with partitions before but never have had this kind of setup, I do know what im doing and also I case I dont, I have a backup big_smile

This is one reason I read the forums: thrilling amusement :-)

5hrs should be enough, but maybe you can drive to work and back or borrow a charger from your neighbors, just in case.

Offline

#13 2010-08-19 09:26:38

655321
Member
From: Costa Rica
Registered: 2009-12-08
Posts: 412
Website

Re: [SOLVED] Cant use unallocated space after removing windows partitions

I just found 1 charger (of my external hard drive) that fits into the laptop, but Im scared that it should fry my battery. Is it safe to connect a charger different from the supplied one?

Borrowing a charger isnt an option cause its 4am here lol.

Battery is at 66%, 2 of 5 operations done, I guess the longest part would be moving /home (about 27gigs), root needs to move about 6.7 gigs of data.

I think time will be enough, but Im worried big_smile

Last edited by 655321 (2010-08-19 09:32:46)


Linux user #498977
With microsoft you get windows and gates, with linux you get the whole house!
My Blog about ArchLinux and other stuff

Offline

#14 2010-08-19 09:32:41

Inxsible
Forum Fellow
From: Chicago
Registered: 2008-06-09
Posts: 9,183

Re: [SOLVED] Cant use unallocated space after removing windows partitions

655321 wrote:

I just found 1 charger (of my external hard drive) that fits into the laptop, but Im scared that it should fry my battery. Is it safe to connect a charger different from the supplied one?

Borrowing a charger isnt an option cause its 4am here lol.

No. I wouldn't risk my laptop being fried.

how long do you think the battery is gonna last? GParted shouldn't take more than an hour -- as long as you are not moving data around. Simple extensions of partitions or resizing hardly takes a few minutes.


Forum Rules

There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !

Offline

#15 2010-08-19 09:33:01

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: [SOLVED] Cant use unallocated space after removing windows partitions

655321 wrote:

I just found 1 charger (of my external hard drive) that fits into the laptop, but Im scared that it should fry my battery. Is it safe to connect a charger different from the supplied one?

I'm not sure if it's safe, so I wouldn't do it if I were you. You can pray to Murphy to let the partitioning finish before the battery runs out but I heard he was in a bad mood today ;P

655321 wrote:

Borrowing a charger isnt an option cause its 4am here lol.

Who knows, I'm often wide awake at 4 am - I love the sunrise :-D

Offline

#16 2010-08-19 09:35:13

655321
Member
From: Costa Rica
Registered: 2009-12-08
Posts: 412
Website

Re: [SOLVED] Cant use unallocated space after removing windows partitions

I edited my last post with some info about battery and data to move, I will be coming back with the battery status, just for the forums amusement lol.

Hope this ends good big_smile

-Battery: BAT0-
State        : discharging (load: 19110 mW)
Capacity        : 52738 mWh / 81200 mWh (64.95%)
Battery Technology        : rechargeable (LIon)
Model Number        : UL50-58

Draining very slow, so far so good

Last edited by 655321 (2010-08-19 09:37:03)


Linux user #498977
With microsoft you get windows and gates, with linux you get the whole house!
My Blog about ArchLinux and other stuff

Offline

#17 2010-08-19 11:00:56

stqn
Member
Registered: 2010-03-19
Posts: 1,191
Website

Re: [SOLVED] Cant use unallocated space after removing windows partitions

Eh eh, that was funny smile. I hope your battery lasts long enough.

+1 for not using the external hard disk charger: I think you'd at least burn the charger, because it probably does 10W and your laptop 20W... Though I'm not sure, not an electrician I am.

Offline

#18 2010-08-19 11:08:27

655321
Member
From: Costa Rica
Registered: 2009-12-08
Posts: 412
Website

Re: [SOLVED] Cant use unallocated space after removing windows partitions

stqn wrote:

Eh eh, that was funny smile. I hope your battery lasts long enough.

+1 for not using the external hard disk charger: I think you'd at least burn the charger, because it probably does 10W and your laptop 20W... Though I'm not sure, not an electrician I am.

Its about to finish and there is some power left:


-Battery: BAT0-
State        : discharging (load: 16506 mW)
Capacity        : 24416 mWh / 81200 mWh (30.07%)
Battery Technology        : rechargeable (LIon)
Model Number        : UL50-58

However, my battery has totally drained like 15 min ago, I am using emergency power sources, I really need some sleep, soooo tired, 5:00 am here.

I checked both chargers specs, Both had same input Voltage but different DC output, So pretty much I would have fried my battery big_smile

If anyone is interested, here is the complete output of all the operations performed:

Parted 0.5.2

Libparted 2.2

Move /dev/sda5 to the left and grow it from 94.10 MiB to 184.01 GiB  00:07:35    ( SUCCESS )
        
calibrate /dev/sda5  00:00:01    ( SUCCESS )
        
path: /dev/sda5
start: 416423680
end: 416616396
size: 192717 (94.10 MiB)
calculate new size and position of /dev/sda5  00:00:00    ( SUCCESS )
        
requested start: 30716343
requested end: 416613644
requested size: 385897302 (184.01 GiB)
new start: 30716343
new end: 416613644
new size: 385897302 (184.01 GiB)
check file system on /dev/sda5 for errors and (if possible) fix them  00:00:00    ( SUCCESS )
        
e2fsck -f -y -v /dev/sda5
        
Superblock last write time is in the future.
(by less than a day, probably due to the hardware clock being incorrectly set). Fix? yes

Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

archboot: ***** FILE SYSTEM WAS MODIFIED *****

30 inodes used (0.12%)
2 non-contiguous files (6.7%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 9/4/0
15343 blocks used (15.92%)
0 bad blocks
0 large files

18 regular files
3 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
21 files
e2fsck 1.41.11 (14-Mar-2010)
move partition to the left  00:00:01    ( SUCCESS )
        
old start: 416423680
old end: 416616396
old size: 192717 (94.10 MiB)
new start: 30716343
new end: 30909059
new size: 192717 (94.10 MiB)
move file system to the left  00:00:07    ( SUCCESS )
        
using internal algorithm
copy 192717 sectors
finding optimal blocksize
        
copy 65536 sectors using a blocksize of 64 sectors  00:00:03    ( SUCCESS )
        
65536 of 65536 copied
3.11777 seconds
copy 65536 sectors using a blocksize of 128 sectors  00:00:02    ( SUCCESS )
        
65536 of 65536 copied
2.3274 seconds
optimal blocksize is 128 sectors (64.00 KiB)
copy 61645 sectors using a blocksize of 128 sectors  00:00:02    ( SUCCESS )
        
61645 of 61645 copied
192717 sectors copied
check file system on /dev/sda5 for errors and (if possible) fix them  00:00:01    ( SUCCESS )
        
e2fsck -f -y -v /dev/sda5
        
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

30 inodes used (0.12%)
2 non-contiguous files (6.7%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 9/4/0
15343 blocks used (15.92%)
0 bad blocks
0 large files

18 regular files
3 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
21 files
e2fsck 1.41.11 (14-Mar-2010)
grow file system to fill the partition  00:00:00    ( SUCCESS )
        
resize2fs /dev/sda5
        
resize2fs 1.41.11 (14-Mar-2010)
The filesystem is already 96356 blocks long. Nothing to do!

calculate new size and position of /dev/sda5  00:00:00    ( SUCCESS )
        
requested start: 30716343
requested end: 416613644
requested size: 385897302 (184.01 GiB)
new start: 30716343
new end: 416613644
new size: 385897302 (184.01 GiB)
check file system on /dev/sda5 for errors and (if possible) fix them  00:00:01    ( SUCCESS )
        
e2fsck -f -y -v /dev/sda5
        
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

30 inodes used (0.12%)
2 non-contiguous files (6.7%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 9/4/0
15343 blocks used (15.92%)
0 bad blocks
0 large files

18 regular files
3 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
21 files
e2fsck 1.41.11 (14-Mar-2010)
grow partition from 94.10 MiB to 184.01 GiB  00:00:00    ( SUCCESS )
        
old start: 30716343
old end: 30909059
old size: 192717 (94.10 MiB)
new start: 30716343
new end: 416613644
new size: 385897302 (184.01 GiB)
check file system on /dev/sda5 for errors and (if possible) fix them  00:00:01    ( SUCCESS )
        
e2fsck -f -y -v /dev/sda5
        
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

30 inodes used (0.12%)
2 non-contiguous files (6.7%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 9/4/0
15343 blocks used (15.92%)
0 bad blocks
0 large files

18 regular files
3 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
21 files
e2fsck 1.41.11 (14-Mar-2010)
grow file system to fill the partition  00:07:23    ( SUCCESS )
        
resize2fs /dev/sda5
        
Resizing the filesystem on /dev/sda5 to 192948648 (1k) blocks.
The filesystem on /dev/sda5 is now 192948648 blocks long.

resize2fs 1.41.11 (14-Mar-2010)
========================================

Shrink /dev/sda5 from 184.01 GiB to 94.10 MiB  00:18:13    ( SUCCESS )
        
calibrate /dev/sda5  00:00:00    ( SUCCESS )
        
path: /dev/sda5
start: 30716343
end: 416613644
size: 385897302 (184.01 GiB)
check file system on /dev/sda5 for errors and (if possible) fix them  00:09:04    ( SUCCESS )
        
e2fsck -f -y -v /dev/sda5
        
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

30 inodes used (0.00%)
2 non-contiguous files (6.7%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 9/4/0
5986156 blocks used (3.10%)
0 bad blocks
0 large files

18 regular files
3 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
21 files
e2fsck 1.41.11 (14-Mar-2010)
shrink file system  00:09:07    ( SUCCESS )
        
resize2fs /dev/sda5 96358K
        
Resizing the filesystem on /dev/sda5 to 96358 (1k) blocks.
The filesystem on /dev/sda5 is now 96358 blocks long.

resize2fs 1.41.11 (14-Mar-2010)
shrink partition from 184.01 GiB to 94.10 MiB  00:00:01    ( SUCCESS )
        
old start: 30716343
old end: 416613644
old size: 385897302 (184.01 GiB)
new start: 30716343
new end: 30909059
new size: 192717 (94.10 MiB)
check file system on /dev/sda5 for errors and (if possible) fix them  00:00:01    ( SUCCESS )
        
e2fsck -f -y -v /dev/sda5
        
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

30 inodes used (0.12%)
2 non-contiguous files (6.7%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 9/4/0
13806 blocks used (14.33%)
0 bad blocks
0 large files

18 regular files
3 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
21 files
e2fsck 1.41.11 (14-Mar-2010)
grow file system to fill the partition  00:00:00    ( SUCCESS )
        
resize2fs /dev/sda5
        
Resizing the filesystem on /dev/sda5 to 96356 (1k) blocks.
The filesystem on /dev/sda5 is now 96356 blocks long.

resize2fs 1.41.11 (14-Mar-2010)
========================================

Move /dev/sda6 to the left and grow it from 27.94 GiB to 211.86 GiB  00:25:41    ( SUCCESS )
        
calibrate /dev/sda6  00:00:01    ( SUCCESS )
        
path: /dev/sda6
start: 416616460
end: 475205451
size: 58588992 (27.94 GiB)
calculate new size and position of /dev/sda6  00:00:00    ( SUCCESS )
        
requested start: 30909123
requested end: 475202699
requested size: 444293577 (211.86 GiB)
new start: 30909123
new end: 475202699
new size: 444293577 (211.86 GiB)
check file system on /dev/sda6 for errors and (if possible) fix them  00:00:06    ( SUCCESS )
        
e2fsck -f -y -v /dev/sda6
        
Superblock last mount time is in the future.
(by less than a day, probably due to the hardware clock being incorrectly set) Fix? yes

Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

archroot: ***** FILE SYSTEM WAS MODIFIED *****

213801 inodes used (11.67%)
150 non-contiguous files (0.1%)
184 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 177710/43
1639606 blocks used (22.39%)
0 bad blocks
1 large file

159321 regular files
18043 directories
10 character device files
1 block device file
0 fifos
2384 links
36398 symbolic links (36008 fast symbolic links)
19 sockets
--------
216176 files
e2fsck 1.41.11 (14-Mar-2010)
move partition to the left  00:00:01    ( SUCCESS )
        
old start: 416616460
old end: 475205451
old size: 58588992 (27.94 GiB)
new start: 30909123
new end: 89498114
new size: 58588992 (27.94 GiB)
move file system to the left  00:24:20    ( SUCCESS )
        
using internal algorithm
copy 58588992 sectors
finding optimal blocksize
        
copy 65536 sectors using a blocksize of 64 sectors  00:00:03    ( SUCCESS )
        
65536 of 65536 copied
3.6146 seconds
copy 65536 sectors using a blocksize of 128 sectors  00:00:04    ( SUCCESS )
        
65536 of 65536 copied
3.39622 seconds
copy 65536 sectors using a blocksize of 256 sectors  00:00:02    ( SUCCESS )
        
65536 of 65536 copied
2.29948 seconds
copy 65536 sectors using a blocksize of 512 sectors  00:00:02    ( SUCCESS )
        
65536 of 65536 copied
2.33374 seconds
copy 65536 sectors using a blocksize of 1024 sectors  00:00:03    ( SUCCESS )
        
65536 of 65536 copied
2.51322 seconds
copy 65536 sectors using a blocksize of 2048 sectors  00:00:02    ( SUCCESS )
        
65536 of 65536 copied
2.26038 seconds
copy 65536 sectors using a blocksize of 4096 sectors  00:00:02    ( SUCCESS )
        
65536 of 65536 copied
2.00566 seconds
copy 65536 sectors using a blocksize of 8192 sectors  00:00:02    ( SUCCESS )
        
65536 of 65536 copied
1.70663 seconds
copy 65536 sectors using a blocksize of 16384 sectors  00:00:01    ( SUCCESS )
        
65536 of 65536 copied
1.50888 seconds
copy 65536 sectors using a blocksize of 32768 sectors  00:00:02    ( SUCCESS )
        
65536 of 65536 copied
1.47924 seconds
copy 65536 sectors using a blocksize of 65536 sectors  00:00:01    ( SUCCESS )
        
65536 of 65536 copied
1.4729 seconds
optimal blocksize is 65536 sectors (32.00 MiB)
copy 57868096 sectors using a blocksize of 65536 sectors  00:23:56    ( SUCCESS )
        
57868096 of 57868096 copied
58588992 sectors copied
check file system on /dev/sda6 for errors and (if possible) fix them  00:00:06    ( SUCCESS )
        
e2fsck -f -y -v /dev/sda6
        
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

213801 inodes used (11.67%)
150 non-contiguous files (0.1%)
184 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 177710/43
1639606 blocks used (22.39%)
0 bad blocks
1 large file

159321 regular files
18043 directories
10 character device files
1 block device file
0 fifos
2384 links
36398 symbolic links (36008 fast symbolic links)
19 sockets
--------
216176 files
e2fsck 1.41.11 (14-Mar-2010)
grow file system to fill the partition  00:00:00    ( SUCCESS )
        
resize2fs /dev/sda6
        
resize2fs 1.41.11 (14-Mar-2010)
The filesystem is already 7323624 blocks long. Nothing to do!

calculate new size and position of /dev/sda6  00:00:01    ( SUCCESS )
        
requested start: 30909123
requested end: 475202699
requested size: 444293577 (211.86 GiB)
new start: 30909123
new end: 475202699
new size: 444293577 (211.86 GiB)
check file system on /dev/sda6 for errors and (if possible) fix them  00:00:05    ( SUCCESS )
        
e2fsck -f -y -v /dev/sda6
        
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

213801 inodes used (11.67%)
150 non-contiguous files (0.1%)
184 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 177710/43
1639606 blocks used (22.39%)
0 bad blocks
1 large file

159321 regular files
18043 directories
10 character device files
1 block device file
0 fifos
2384 links
36398 symbolic links (36008 fast symbolic links)
19 sockets
--------
216176 files
e2fsck 1.41.11 (14-Mar-2010)
grow partition from 27.94 GiB to 211.86 GiB  00:00:01    ( SUCCESS )
        
old start: 30909123
old end: 89498114
old size: 58588992 (27.94 GiB)
new start: 30909123
new end: 475202699
new size: 444293577 (211.86 GiB)
check file system on /dev/sda6 for errors and (if possible) fix them  00:00:06    ( SUCCESS )
        
e2fsck -f -y -v /dev/sda6
        
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

213801 inodes used (11.67%)
150 non-contiguous files (0.1%)
184 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 177710/43
1639606 blocks used (22.39%)
0 bad blocks
1 large file

159321 regular files
18043 directories
10 character device files
1 block device file
0 fifos
2384 links
36398 symbolic links (36008 fast symbolic links)
19 sockets
--------
216176 files
e2fsck 1.41.11 (14-Mar-2010)
grow file system to fill the partition  00:00:54    ( SUCCESS )
        
resize2fs /dev/sda6
        
Resizing the filesystem on /dev/sda6 to 55536697 (4k) blocks.
The filesystem on /dev/sda6 is now 55536697 blocks long.

resize2fs 1.41.11 (14-Mar-2010)
========================================

Shrink /dev/sda6 from 211.86 GiB to 39.06 GiB  00:00:27    ( SUCCESS )
        
calibrate /dev/sda6  00:00:00    ( SUCCESS )
        
path: /dev/sda6
start: 30909123
end: 475202699
size: 444293577 (211.86 GiB)
check file system on /dev/sda6 for errors and (if possible) fix them  00:00:14    ( SUCCESS )
        
e2fsck -f -y -v /dev/sda6
        
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

213801 inodes used (1.54%)
150 non-contiguous files (0.1%)
184 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 177710/43
2398329 blocks used (4.32%)
0 bad blocks
1 large file

159321 regular files
18043 directories
10 character device files
1 block device file
0 fifos
2384 links
36398 symbolic links (36008 fast symbolic links)
19 sockets
--------
216176 files
e2fsck 1.41.11 (14-Mar-2010)
shrink file system  00:00:05    ( SUCCESS )
        
resize2fs /dev/sda6 40957685K
        
Resizing the filesystem on /dev/sda6 to 10239421 (4k) blocks.
The filesystem on /dev/sda6 is now 10239421 blocks long.

resize2fs 1.41.11 (14-Mar-2010)
shrink partition from 211.86 GiB to 39.06 GiB  00:00:01    ( SUCCESS )
        
old start: 30909123
old end: 475202699
old size: 444293577 (211.86 GiB)
new start: 30909123
new end: 112824494
new size: 81915372 (39.06 GiB)
check file system on /dev/sda6 for errors and (if possible) fix them  00:00:07    ( SUCCESS )
        
e2fsck -f -y -v /dev/sda6
        
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

213801 inodes used (8.35%)
150 non-contiguous files (0.1%)
184 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 177710/43
1686288 blocks used (16.47%)
0 bad blocks
1 large file

159321 regular files
18043 directories
10 character device files
1 block device file
0 fifos
2384 links
36398 symbolic links (36008 fast symbolic links)
19 sockets
--------
216176 files
e2fsck 1.41.11 (14-Mar-2010)
grow file system to fill the partition  00:00:00    ( SUCCESS )
        
resize2fs /dev/sda6
        
resize2fs 1.41.11 (14-Mar-2010)
The filesystem is already 10239421 blocks long. Nothing to do!

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

Move /dev/sda7 to the left and grow it from 67.68 GiB to 240.47 GiB  01:08:09    ( SUCCESS )
        
calibrate /dev/sda7  00:00:00    ( SUCCESS )
        
path: /dev/sda7
start: 475205515
end: 617136974
size: 141931460 (67.68 GiB)
calculate new size and position of /dev/sda7  00:00:00    ( SUCCESS )
        
requested start: 112824558
requested end: 617136974
requested size: 504312417 (240.47 GiB)
new start: 112824558
new end: 617136974
new size: 504312417 (240.47 GiB)
check file system on /dev/sda7 for errors and (if possible) fix them  00:00:05    ( SUCCESS )
        
e2fsck -f -y -v /dev/sda7
        
Superblock last mount time is in the future.
(by less than a day, probably due to the hardware clock being incorrectly set) Fix? yes

Superblock last write time is in the future.
(by less than a day, probably due to the hardware clock being incorrectly set). Fix? yes

Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

archhome: ***** FILE SYSTEM WAS MODIFIED *****

17375 inodes used (0.39%)
45 non-contiguous files (0.3%)
9 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 17340/20
14450824 blocks used (81.45%)
0 bad blocks
2 large files

15710 regular files
1651 directories
0 character device files
0 block device files
0 fifos
2 links
3 symbolic links (3 fast symbolic links)
2 sockets
--------
17368 files
e2fsck 1.41.11 (14-Mar-2010)
move partition to the left  00:00:01    ( SUCCESS )
        
old start: 475205515
old end: 617136974
old size: 141931460 (67.68 GiB)
new start: 112824558
new end: 254756017
new size: 141931460 (67.68 GiB)
move file system to the left  01:06:48    ( SUCCESS )
        
using internal algorithm
copy 141931460 sectors
finding optimal blocksize
        
copy 65536 sectors using a blocksize of 64 sectors  00:00:03    ( SUCCESS )
        
65536 of 65536 copied
3.31868 seconds
copy 65536 sectors using a blocksize of 128 sectors  00:00:03    ( SUCCESS )
        
65536 of 65536 copied
2.47129 seconds
copy 65536 sectors using a blocksize of 256 sectors  00:00:02    ( SUCCESS )
        
65536 of 65536 copied
2.38136 seconds
copy 65536 sectors using a blocksize of 512 sectors  00:00:02    ( SUCCESS )
        
65536 of 65536 copied
2.36665 seconds
copy 65536 sectors using a blocksize of 1024 sectors  00:00:03    ( SUCCESS )
        
65536 of 65536 copied
2.60633 seconds
copy 65536 sectors using a blocksize of 2048 sectors  00:00:02    ( SUCCESS )
        
65536 of 65536 copied
2.33836 seconds
copy 65536 sectors using a blocksize of 4096 sectors  00:00:02    ( SUCCESS )
        
65536 of 65536 copied
2.17669 seconds
copy 65536 sectors using a blocksize of 8192 sectors  00:00:02    ( SUCCESS )
        
65536 of 65536 copied
1.71828 seconds
copy 65536 sectors using a blocksize of 16384 sectors  00:00:02    ( SUCCESS )
        
65536 of 65536 copied
1.56909 seconds
copy 65536 sectors using a blocksize of 32768 sectors  00:00:01    ( SUCCESS )
        
65536 of 65536 copied
1.49093 seconds
copy 65536 sectors using a blocksize of 65536 sectors  00:00:02    ( SUCCESS )
        
65536 of 65536 copied
1.4784 seconds
optimal blocksize is 65536 sectors (32.00 MiB)
copy 141210564 sectors using a blocksize of 65536 sectors  01:06:24    ( SUCCESS )
        
141210564 of 141210564 copied
141931460 sectors copied
check file system on /dev/sda7 for errors and (if possible) fix them  00:00:04    ( SUCCESS )
        
e2fsck -f -y -v /dev/sda7
        
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

17375 inodes used (0.39%)
45 non-contiguous files (0.3%)
9 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 17340/20
14450824 blocks used (81.45%)
0 bad blocks
2 large files

15710 regular files
1651 directories
0 character device files
0 block device files
0 fifos
2 links
3 symbolic links (3 fast symbolic links)
2 sockets
--------
17368 files
e2fsck 1.41.11 (14-Mar-2010)
grow file system to fill the partition  00:00:00    ( SUCCESS )
        
resize2fs /dev/sda7
        
resize2fs 1.41.11 (14-Mar-2010)
The filesystem is already 17741432 blocks long. Nothing to do!

calculate new size and position of /dev/sda7  00:00:00    ( SUCCESS )
        
requested start: 112824558
requested end: 617136974
requested size: 504312417 (240.47 GiB)
new start: 112824558
new end: 617136974
new size: 504312417 (240.47 GiB)
check file system on /dev/sda7 for errors and (if possible) fix them  00:00:05    ( SUCCESS )
        
e2fsck -f -y -v /dev/sda7
        
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

17375 inodes used (0.39%)
45 non-contiguous files (0.3%)
9 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 17340/20
14450824 blocks used (81.45%)
0 bad blocks
2 large files

15710 regular files
1651 directories
0 character device files
0 block device files
0 fifos
2 links
3 symbolic links (3 fast symbolic links)
2 sockets
--------
17368 files
e2fsck 1.41.11 (14-Mar-2010)
grow partition from 67.68 GiB to 240.47 GiB  00:00:00    ( SUCCESS )
        
old start: 112824558
old end: 254756017
old size: 141931460 (67.68 GiB)
new start: 112824558
new end: 617136974
new size: 504312417 (240.47 GiB)
check file system on /dev/sda7 for errors and (if possible) fix them  00:00:05    ( SUCCESS )
        
e2fsck -f -y -v /dev/sda7
        
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

17375 inodes used (0.39%)
45 non-contiguous files (0.3%)
9 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 17340/20
14450824 blocks used (81.45%)
0 bad blocks
2 large files

15710 regular files
1651 directories
0 character device files
0 block device files
0 fifos
2 links
3 symbolic links (3 fast symbolic links)
2 sockets
--------
17368 files
e2fsck 1.41.11 (14-Mar-2010)
grow file system to fill the partition  00:01:01    ( SUCCESS )
        
resize2fs /dev/sda7
        
Resizing the filesystem on /dev/sda7 to 63039052 (4k) blocks.
The filesystem on /dev/sda7 is now 63039052 blocks long.

resize2fs 1.41.11 (14-Mar-2010)
========================================

Linux user #498977
With microsoft you get windows and gates, with linux you get the whole house!
My Blog about ArchLinux and other stuff

Offline

#19 2010-08-19 11:54:41

gazj
Member
From: /home/gazj -> /uk/cambs
Registered: 2007-02-09
Posts: 681
Website

Re: [SOLVED] Cant use unallocated space after removing windows partitions

I am an electrician.  There are so many variables with chargers.  Even if the plug fits the following must always be correct

Output voltage of charger must be the same as input voltage needed by laptop
The output voltage type must be the same as the voltage type required by the laptop.  ie AC or DC
If DC the polarity of the charger must match the polarity needed by the laptop
The charger must be able to supply the current needed by the laptop.  Measured in mA (milliamps)

The chances of everthing being right are slim.  If you don't know don't plug it in!

Last edited by gazj (2010-08-19 11:58:44)

Offline

#20 2010-08-19 11:58:34

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: [SOLVED] Cant use unallocated space after removing windows partitions

gazj wrote:

I am an electrician.

<gobble gobble>

The chances of everthing being right are slim.  If you don't know don't plug it in!

That's the takeaway for me :-)
Did you notice the last line rhymes?

Offline

#21 2010-08-19 12:00:31

gazj
Member
From: /home/gazj -> /uk/cambs
Registered: 2007-02-09
Posts: 681
Website

Re: [SOLVED] Cant use unallocated space after removing windows partitions

karol wrote:
gazj wrote:

I am an electrician.

<gobble gobble>

The chances of everthing being right are slim.  If you don't know don't plug it in!

That's the takeaway for me :-)
Did you notice the last line rhymes?

I didn't notice, but that could be a little phrase when someone asks me in the future wink

Offline

#22 2010-10-07 00:49:52

655321
Member
From: Costa Rica
Registered: 2009-12-08
Posts: 412
Website

Re: [SOLVED] Cant use unallocated space after removing windows partitions

Sorry, forgot to mark it as solved, thanks all for the help


Linux user #498977
With microsoft you get windows and gates, with linux you get the whole house!
My Blog about ArchLinux and other stuff

Offline

Board footer

Powered by FluxBB