Combine Beginning Unallocated Space with Ending Ubuntu Partition

Clash Royale CLAN TAG#URR8PPP up vote
2
down vote
favorite
I couldn't find an example anywhere of what I'm trying to accomplish.
Below is what my hard drive looks like right now.
I want to either:
- Combine the unallocated space at the beginning of the drive with my kubuntu install on sda3
- Or at least make the unallocated space available to use as extra storage for my kubuntu OS

I'm afraid that if I resize sda3 to take up the unallocated space, it will screw up my linux mount point, resulting in frustrating problems. Perhaps I just need to reassign the mount point after resizing?
I would also settle for just being able to use that unallocated space to store documents and other files.
Any help is greatly appreciated!
14.04 partitioning kubuntu gparted mountpoint
add a comment |Â
up vote
2
down vote
favorite
I couldn't find an example anywhere of what I'm trying to accomplish.
Below is what my hard drive looks like right now.
I want to either:
- Combine the unallocated space at the beginning of the drive with my kubuntu install on sda3
- Or at least make the unallocated space available to use as extra storage for my kubuntu OS

I'm afraid that if I resize sda3 to take up the unallocated space, it will screw up my linux mount point, resulting in frustrating problems. Perhaps I just need to reassign the mount point after resizing?
I would also settle for just being able to use that unallocated space to store documents and other files.
Any help is greatly appreciated!
14.04 partitioning kubuntu gparted mountpoint
Why would resizing sda3 mess up the mount point?
â dsstorefile1
Apr 20 at 0:11
I'd just grow sda3 using the unallocated space before it, and ignore the unallocated at the end of the drive. If you have sda3 mounted (ie. running)gpartedwill no doubt complain (you need to umount first), so I'd just use a 'live' system (eg. Ubuntu install media) to do the resize. At worst you'll lose the pointer from grub stage1 (mbr) that points to where in sda3 the /boot (grub stage1.5) is, but its easily fixed (and most likely won't be an issue anyway)
â guiverc
Apr 20 at 0:32
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I couldn't find an example anywhere of what I'm trying to accomplish.
Below is what my hard drive looks like right now.
I want to either:
- Combine the unallocated space at the beginning of the drive with my kubuntu install on sda3
- Or at least make the unallocated space available to use as extra storage for my kubuntu OS

I'm afraid that if I resize sda3 to take up the unallocated space, it will screw up my linux mount point, resulting in frustrating problems. Perhaps I just need to reassign the mount point after resizing?
I would also settle for just being able to use that unallocated space to store documents and other files.
Any help is greatly appreciated!
14.04 partitioning kubuntu gparted mountpoint
I couldn't find an example anywhere of what I'm trying to accomplish.
Below is what my hard drive looks like right now.
I want to either:
- Combine the unallocated space at the beginning of the drive with my kubuntu install on sda3
- Or at least make the unallocated space available to use as extra storage for my kubuntu OS

I'm afraid that if I resize sda3 to take up the unallocated space, it will screw up my linux mount point, resulting in frustrating problems. Perhaps I just need to reassign the mount point after resizing?
I would also settle for just being able to use that unallocated space to store documents and other files.
Any help is greatly appreciated!
14.04 partitioning kubuntu gparted mountpoint
edited Apr 20 at 2:15
stumblebee
2,3083922
2,3083922
asked Apr 20 at 0:08
Shey
111
111
Why would resizing sda3 mess up the mount point?
â dsstorefile1
Apr 20 at 0:11
I'd just grow sda3 using the unallocated space before it, and ignore the unallocated at the end of the drive. If you have sda3 mounted (ie. running)gpartedwill no doubt complain (you need to umount first), so I'd just use a 'live' system (eg. Ubuntu install media) to do the resize. At worst you'll lose the pointer from grub stage1 (mbr) that points to where in sda3 the /boot (grub stage1.5) is, but its easily fixed (and most likely won't be an issue anyway)
â guiverc
Apr 20 at 0:32
add a comment |Â
Why would resizing sda3 mess up the mount point?
â dsstorefile1
Apr 20 at 0:11
I'd just grow sda3 using the unallocated space before it, and ignore the unallocated at the end of the drive. If you have sda3 mounted (ie. running)gpartedwill no doubt complain (you need to umount first), so I'd just use a 'live' system (eg. Ubuntu install media) to do the resize. At worst you'll lose the pointer from grub stage1 (mbr) that points to where in sda3 the /boot (grub stage1.5) is, but its easily fixed (and most likely won't be an issue anyway)
â guiverc
Apr 20 at 0:32
Why would resizing sda3 mess up the mount point?
â dsstorefile1
Apr 20 at 0:11
Why would resizing sda3 mess up the mount point?
â dsstorefile1
Apr 20 at 0:11
I'd just grow sda3 using the unallocated space before it, and ignore the unallocated at the end of the drive. If you have sda3 mounted (ie. running)
gparted will no doubt complain (you need to umount first), so I'd just use a 'live' system (eg. Ubuntu install media) to do the resize. At worst you'll lose the pointer from grub stage1 (mbr) that points to where in sda3 the /boot (grub stage1.5) is, but its easily fixed (and most likely won't be an issue anyway)â guiverc
Apr 20 at 0:32
I'd just grow sda3 using the unallocated space before it, and ignore the unallocated at the end of the drive. If you have sda3 mounted (ie. running)
gparted will no doubt complain (you need to umount first), so I'd just use a 'live' system (eg. Ubuntu install media) to do the resize. At worst you'll lose the pointer from grub stage1 (mbr) that points to where in sda3 the /boot (grub stage1.5) is, but its easily fixed (and most likely won't be an issue anyway)â guiverc
Apr 20 at 0:32
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
No, you can just do it. The partition table will still list the expanded one as Partition 3, and you will have no Partition 1. I have done this myself.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
No, you can just do it. The partition table will still list the expanded one as Partition 3, and you will have no Partition 1. I have done this myself.
add a comment |Â
up vote
0
down vote
No, you can just do it. The partition table will still list the expanded one as Partition 3, and you will have no Partition 1. I have done this myself.
add a comment |Â
up vote
0
down vote
up vote
0
down vote
No, you can just do it. The partition table will still list the expanded one as Partition 3, and you will have no Partition 1. I have done this myself.
No, you can just do it. The partition table will still list the expanded one as Partition 3, and you will have no Partition 1. I have done this myself.
answered Apr 20 at 0:24
Martin W
73238
73238
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1026553%2fcombine-beginning-unallocated-space-with-ending-ubuntu-partition%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Why would resizing sda3 mess up the mount point?
â dsstorefile1
Apr 20 at 0:11
I'd just grow sda3 using the unallocated space before it, and ignore the unallocated at the end of the drive. If you have sda3 mounted (ie. running)
gpartedwill no doubt complain (you need to umount first), so I'd just use a 'live' system (eg. Ubuntu install media) to do the resize. At worst you'll lose the pointer from grub stage1 (mbr) that points to where in sda3 the /boot (grub stage1.5) is, but its easily fixed (and most likely won't be an issue anyway)â guiverc
Apr 20 at 0:32