How to get access to the hdd's free space
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
I have 500 Gb HDD disk that was divided in two parts during the Ubuntu installation process. Ubuntu was installed on it's own partitions. So how can I get access to the remaining free space?
sudo fdisk -l /dev/sda
[sudo] password for nick_name:
Disk /dev/sda: 465,8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xe7e4bdad
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 10000383 9998336 4,8G 82 Linux swap / Solaris
/dev/sda2 10002430 440625151 430622722 205,3G 5 Extended
/dev/sda5 10002432 49999871 39997440 19,1G 83 Linux
/dev/sda6 50001920 440625151 390623232 186,3G 83 Linux
Partition 2 does not start on physical sector boundary.
sudo mount | grep '^/dev/S+'
[sudo] password for nick_name:
/dev/sda5 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
/dev/sda6 on /home type ext4 (rw,relatime,data=ordered)
sudo lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 4,9M 1 loop /snap/canonical-livepatch/41
loop1 7:1 0 86,6M 1 loop /snap/core/4650
loop2 7:2 0 21M 1 loop /snap/gnome-logs/25
loop3 7:3 0 21,6M 1 loop /snap/gnome-logs/31
loop4 7:4 0 12,2M 1 loop /snap/gnome-characters/69
loop5 7:5 0 3,3M 1 loop /snap/gnome-system-monitor/36
loop6 7:6 0 140M 1 loop /snap/gnome-3-26-1604/59
loop7 7:7 0 86,6M 1 loop /snap/core/4486
loop8 7:8 0 3,7M 1 loop /snap/gnome-system-monitor/39
loop9 7:9 0 1,6M 1 loop /snap/gnome-calculator/154
loop10 7:10 0 139,5M 1 loop /snap/gnome-3-26-1604/64
loop11 7:11 0 13M 1 loop /snap/gnome-characters/86
loop12 7:12 0 2,3M 1 loop /snap/gnome-calculator/167
sda 8:0 0 465,8G 0 disk
├─sda1 8:1 0 4,8G 0 part [SWAP]
├─sda2 8:2 0 1K 0 part
├─sda5 8:5 0 19,1G 0 part /
└─sda6 8:6 0 186,3G 0 part /home
18.04 disk
asked May 28 at 8:30
Alex Stelmakh
815
add a comment |Â
up vote
0
down vote
favorite
I have 500 Gb HDD disk that was divided in two parts during the Ubuntu installation process. Ubuntu was installed on it's own partitions. So how can I get access to the remaining free space?
sudo fdisk -l /dev/sda
[sudo] password for nick_name:
Disk /dev/sda: 465,8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xe7e4bdad
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 10000383 9998336 4,8G 82 Linux swap / Solaris
/dev/sda2 10002430 440625151 430622722 205,3G 5 Extended
/dev/sda5 10002432 49999871 39997440 19,1G 83 Linux
/dev/sda6 50001920 440625151 390623232 186,3G 83 Linux
Partition 2 does not start on physical sector boundary.
sudo mount | grep '^/dev/S+'
[sudo] password for nick_name:
/dev/sda5 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
/dev/sda6 on /home type ext4 (rw,relatime,data=ordered)
sudo lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 4,9M 1 loop /snap/canonical-livepatch/41
loop1 7:1 0 86,6M 1 loop /snap/core/4650
loop2 7:2 0 21M 1 loop /snap/gnome-logs/25
loop3 7:3 0 21,6M 1 loop /snap/gnome-logs/31
loop4 7:4 0 12,2M 1 loop /snap/gnome-characters/69
loop5 7:5 0 3,3M 1 loop /snap/gnome-system-monitor/36
loop6 7:6 0 140M 1 loop /snap/gnome-3-26-1604/59
loop7 7:7 0 86,6M 1 loop /snap/core/4486
loop8 7:8 0 3,7M 1 loop /snap/gnome-system-monitor/39
loop9 7:9 0 1,6M 1 loop /snap/gnome-calculator/154
loop10 7:10 0 139,5M 1 loop /snap/gnome-3-26-1604/64
loop11 7:11 0 13M 1 loop /snap/gnome-characters/86
loop12 7:12 0 2,3M 1 loop /snap/gnome-calculator/167
sda 8:0 0 465,8G 0 disk
├─sda1 8:1 0 4,8G 0 part [SWAP]
├─sda2 8:2 0 1K 0 part
├─sda5 8:5 0 19,1G 0 part /
└─sda6 8:6 0 186,3G 0 part /home
18.04 disk
asked May 28 at 8:30
Alex Stelmakh
815
2
In various ways. How can we help if you don't show us the actual configuration? Please edit the question and include at least the output ofsudo fdisk -l /dev/sda,sudo mount | grep '^/dev/S+'andsudo lsblk.
– AlexP
May 28 at 8:34
I feel absolutely dummy about these linux tricks. Could these commands cause injury to my system in some way?
– Alex Stelmakh
May 28 at 10:57
1
Don't worry, these commands are only getting information and will not change anything to your configuration. You can read about these commands (and all others) withman <command>.
– muclux
May 28 at 11:02
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have 500 Gb HDD disk that was divided in two parts during the Ubuntu installation process. Ubuntu was installed on it's own partitions. So how can I get access to the remaining free space?
sudo fdisk -l /dev/sda
[sudo] password for nick_name:
Disk /dev/sda: 465,8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xe7e4bdad
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 10000383 9998336 4,8G 82 Linux swap / Solaris
/dev/sda2 10002430 440625151 430622722 205,3G 5 Extended
/dev/sda5 10002432 49999871 39997440 19,1G 83 Linux
/dev/sda6 50001920 440625151 390623232 186,3G 83 Linux
Partition 2 does not start on physical sector boundary.
sudo mount | grep '^/dev/S+'
[sudo] password for nick_name:
/dev/sda5 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
/dev/sda6 on /home type ext4 (rw,relatime,data=ordered)
sudo lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 4,9M 1 loop /snap/canonical-livepatch/41
loop1 7:1 0 86,6M 1 loop /snap/core/4650
loop2 7:2 0 21M 1 loop /snap/gnome-logs/25
loop3 7:3 0 21,6M 1 loop /snap/gnome-logs/31
loop4 7:4 0 12,2M 1 loop /snap/gnome-characters/69
loop5 7:5 0 3,3M 1 loop /snap/gnome-system-monitor/36
loop6 7:6 0 140M 1 loop /snap/gnome-3-26-1604/59
loop7 7:7 0 86,6M 1 loop /snap/core/4486
loop8 7:8 0 3,7M 1 loop /snap/gnome-system-monitor/39
loop9 7:9 0 1,6M 1 loop /snap/gnome-calculator/154
loop10 7:10 0 139,5M 1 loop /snap/gnome-3-26-1604/64
loop11 7:11 0 13M 1 loop /snap/gnome-characters/86
loop12 7:12 0 2,3M 1 loop /snap/gnome-calculator/167
sda 8:0 0 465,8G 0 disk
├─sda1 8:1 0 4,8G 0 part [SWAP]
├─sda2 8:2 0 1K 0 part
├─sda5 8:5 0 19,1G 0 part /
└─sda6 8:6 0 186,3G 0 part /home
18.04 disk
asked May 28 at 8:30
Alex Stelmakh
815
I have 500 Gb HDD disk that was divided in two parts during the Ubuntu installation process. Ubuntu was installed on it's own partitions. So how can I get access to the remaining free space?
sudo fdisk -l /dev/sda
[sudo] password for nick_name:
Disk /dev/sda: 465,8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xe7e4bdad
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 10000383 9998336 4,8G 82 Linux swap / Solaris
/dev/sda2 10002430 440625151 430622722 205,3G 5 Extended
/dev/sda5 10002432 49999871 39997440 19,1G 83 Linux
/dev/sda6 50001920 440625151 390623232 186,3G 83 Linux
Partition 2 does not start on physical sector boundary.
sudo mount | grep '^/dev/S+'
[sudo] password for nick_name:
/dev/sda5 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
/dev/sda6 on /home type ext4 (rw,relatime,data=ordered)
sudo lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 4,9M 1 loop /snap/canonical-livepatch/41
loop1 7:1 0 86,6M 1 loop /snap/core/4650
loop2 7:2 0 21M 1 loop /snap/gnome-logs/25
loop3 7:3 0 21,6M 1 loop /snap/gnome-logs/31
loop4 7:4 0 12,2M 1 loop /snap/gnome-characters/69
loop5 7:5 0 3,3M 1 loop /snap/gnome-system-monitor/36
loop6 7:6 0 140M 1 loop /snap/gnome-3-26-1604/59
loop7 7:7 0 86,6M 1 loop /snap/core/4486
loop8 7:8 0 3,7M 1 loop /snap/gnome-system-monitor/39
loop9 7:9 0 1,6M 1 loop /snap/gnome-calculator/154
loop10 7:10 0 139,5M 1 loop /snap/gnome-3-26-1604/64
loop11 7:11 0 13M 1 loop /snap/gnome-characters/86
loop12 7:12 0 2,3M 1 loop /snap/gnome-calculator/167
sda 8:0 0 465,8G 0 disk
├─sda1 8:1 0 4,8G 0 part [SWAP]
├─sda2 8:2 0 1K 0 part
├─sda5 8:5 0 19,1G 0 part /
└─sda6 8:6 0 186,3G 0 part /home
18.04 disk
asked May 28 at 8:30
Alex Stelmakh
815
edited May 28 at 12:56
asked May 28 at 8:30
Alex Stelmakh
815
asked May 28 at 8:30
Alex Stelmakh
815
asked May 28 at 8:30
Alex Stelmakh
815
815
2
In various ways. How can we help if you don't show us the actual configuration? Please edit the question and include at least the output ofsudo fdisk -l /dev/sda,sudo mount | grep '^/dev/S+'andsudo lsblk.
– AlexP
May 28 at 8:34
I feel absolutely dummy about these linux tricks. Could these commands cause injury to my system in some way?
– Alex Stelmakh
May 28 at 10:57
1
Don't worry, these commands are only getting information and will not change anything to your configuration. You can read about these commands (and all others) withman <command>.
– muclux
May 28 at 11:02
add a comment |Â
2
In various ways. How can we help if you don't show us the actual configuration? Please edit the question and include at least the output ofsudo fdisk -l /dev/sda,sudo mount | grep '^/dev/S+'andsudo lsblk.
– AlexP
May 28 at 8:34
I feel absolutely dummy about these linux tricks. Could these commands cause injury to my system in some way?
– Alex Stelmakh
May 28 at 10:57
1
Don't worry, these commands are only getting information and will not change anything to your configuration. You can read about these commands (and all others) withman <command>.
– muclux
May 28 at 11:02
2
2
In various ways. How can we help if you don't show us the actual configuration? Please edit the question and include at least the output of
sudo fdisk -l /dev/sda, sudo mount | grep '^/dev/S+' and sudo lsblk.– AlexP
May 28 at 8:34
In various ways. How can we help if you don't show us the actual configuration? Please edit the question and include at least the output of
sudo fdisk -l /dev/sda, sudo mount | grep '^/dev/S+' and sudo lsblk.– AlexP
May 28 at 8:34
I feel absolutely dummy about these linux tricks. Could these commands cause injury to my system in some way?
– Alex Stelmakh
May 28 at 10:57
I feel absolutely dummy about these linux tricks. Could these commands cause injury to my system in some way?
– Alex Stelmakh
May 28 at 10:57
1
1
Don't worry, these commands are only getting information and will not change anything to your configuration. You can read about these commands (and all others) with
man <command>.– muclux
May 28 at 11:02
Don't worry, these commands are only getting information and will not change anything to your configuration. You can read about these commands (and all others) with
man <command>.– muclux
May 28 at 11:02
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Â
draft saved
draft discarded
Â
draft saved
draft discarded
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%2f1041123%2fhow-to-get-access-to-the-hdds-free-space%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
2
In various ways. How can we help if you don't show us the actual configuration? Please edit the question and include at least the output of
sudo fdisk -l /dev/sda,sudo mount | grep '^/dev/S+'andsudo lsblk.– AlexP
May 28 at 8:34
I feel absolutely dummy about these linux tricks. Could these commands cause injury to my system in some way?
– Alex Stelmakh
May 28 at 10:57
1
Don't worry, these commands are only getting information and will not change anything to your configuration. You can read about these commands (and all others) with
man <command>.– muclux
May 28 at 11:02