Increased encrypted partition size but Gnome Files still thinks it's small
I have an installation of Ubuntu Desktop 18.04.1 running in VirtualBox 5.2.20. When I first installed it, I made the mistake of giving the VDI a capacity of only 20 GB. That filled up fairly quickly, so I decided to enlarge the VDI and home partition.
The home partition is encrypted with LUKS. I used VBoxManager to increase the capacity of the VDI to 100 GB, then I booted the Ubuntu VM and installed GParted to enlarge the partition. It worked perfectly, the machine boots fine every time and Gnome Disks shows the partition scheme exactly as expected.
The problem now is that Files thinks the partition capacity is still 19.2 GB and still shows me constant warnings about low disk space. At this point the disk has 18.1 GB of data on it, so it's not "full" (according to Files) yet. I've been googling but haven't found a solution yet. Any ideas? Also, if the data on it goes over what Files thinks the capacity is, will that cause problems?
partitioning nautilus encryption
edited Dec 23 at 20:05
George Udosen
19.5k94266
asked Dec 23 at 19:37
Zero
13113
add a comment |
I have an installation of Ubuntu Desktop 18.04.1 running in VirtualBox 5.2.20. When I first installed it, I made the mistake of giving the VDI a capacity of only 20 GB. That filled up fairly quickly, so I decided to enlarge the VDI and home partition.
The home partition is encrypted with LUKS. I used VBoxManager to increase the capacity of the VDI to 100 GB, then I booted the Ubuntu VM and installed GParted to enlarge the partition. It worked perfectly, the machine boots fine every time and Gnome Disks shows the partition scheme exactly as expected.
The problem now is that Files thinks the partition capacity is still 19.2 GB and still shows me constant warnings about low disk space. At this point the disk has 18.1 GB of data on it, so it's not "full" (according to Files) yet. I've been googling but haven't found a solution yet. Any ideas? Also, if the data on it goes over what Files thinks the capacity is, will that cause problems?
partitioning nautilus encryption
edited Dec 23 at 20:05
George Udosen
19.5k94266
asked Dec 23 at 19:37
Zero
13113
The commandsudo cryptsetup resize --size <new-size> encrypted-volume. Let me check the entry for new-size!
– George Udosen
Dec 23 at 20:26
add a comment |
I have an installation of Ubuntu Desktop 18.04.1 running in VirtualBox 5.2.20. When I first installed it, I made the mistake of giving the VDI a capacity of only 20 GB. That filled up fairly quickly, so I decided to enlarge the VDI and home partition.
The home partition is encrypted with LUKS. I used VBoxManager to increase the capacity of the VDI to 100 GB, then I booted the Ubuntu VM and installed GParted to enlarge the partition. It worked perfectly, the machine boots fine every time and Gnome Disks shows the partition scheme exactly as expected.
The problem now is that Files thinks the partition capacity is still 19.2 GB and still shows me constant warnings about low disk space. At this point the disk has 18.1 GB of data on it, so it's not "full" (according to Files) yet. I've been googling but haven't found a solution yet. Any ideas? Also, if the data on it goes over what Files thinks the capacity is, will that cause problems?
partitioning nautilus encryption
edited Dec 23 at 20:05
George Udosen
19.5k94266
asked Dec 23 at 19:37
Zero
13113
I have an installation of Ubuntu Desktop 18.04.1 running in VirtualBox 5.2.20. When I first installed it, I made the mistake of giving the VDI a capacity of only 20 GB. That filled up fairly quickly, so I decided to enlarge the VDI and home partition.
The home partition is encrypted with LUKS. I used VBoxManager to increase the capacity of the VDI to 100 GB, then I booted the Ubuntu VM and installed GParted to enlarge the partition. It worked perfectly, the machine boots fine every time and Gnome Disks shows the partition scheme exactly as expected.
The problem now is that Files thinks the partition capacity is still 19.2 GB and still shows me constant warnings about low disk space. At this point the disk has 18.1 GB of data on it, so it's not "full" (according to Files) yet. I've been googling but haven't found a solution yet. Any ideas? Also, if the data on it goes over what Files thinks the capacity is, will that cause problems?
partitioning nautilus encryption
partitioning nautilus encryption
edited Dec 23 at 20:05
George Udosen
19.5k94266
asked Dec 23 at 19:37
Zero
13113
edited Dec 23 at 20:05
George Udosen
19.5k94266
asked Dec 23 at 19:37
Zero
13113
edited Dec 23 at 20:05
George Udosen
19.5k94266
edited Dec 23 at 20:05
George Udosen
19.5k94266
edited Dec 23 at 20:05
George Udosen
19.5k94266
19.5k94266
asked Dec 23 at 19:37
Zero
13113
asked Dec 23 at 19:37
Zero
13113
asked Dec 23 at 19:37
Zero
13113
13113
The commandsudo cryptsetup resize --size <new-size> encrypted-volume. Let me check the entry for new-size!
– George Udosen
Dec 23 at 20:26
add a comment |
The commandsudo cryptsetup resize --size <new-size> encrypted-volume. Let me check the entry for new-size!
– George Udosen
Dec 23 at 20:26
The command
sudo cryptsetup resize --size <new-size> encrypted-volume. Let me check the entry for new-size!– George Udosen
Dec 23 at 20:26
The command
sudo cryptsetup resize --size <new-size> encrypted-volume. Let me check the entry for new-size!– George Udosen
Dec 23 at 20:26
add a comment |
1 Answer
1
active
oldest
votes
I think you missed out on the LUKS resize part:
resize <name>
Resizes an active mapping <name>.
If --size (in sectors) is not specified, the size of the underlying block device is
used. Note that this does not change the raw device geometry, it just changes how
many sectors of the raw device are represented in the mapped device.
So the command sudo cryptsetup resize <encrypted-volume> should inform LUKS about the new size.
The basic steps are:
Boot the desktop, live CD. Use gparted (or any tool) to put unallocated space adjacent, and to the left of your Crypt partition.
Enlarge the Partition storing the crypt with fdisk.Reboot ~ You should always reboot after changing your partition table with fdisk.
Boot the desktop, live CD. Install & configure the tools (lvm2 and cryptsetup).
sudo apt update && sudo apt install lvm2 cryptsetupsudo modprobe dm-cryptsudo cryptsetup luksOpen /dev/sda5 crypt1
Enlarge the Crypt with cryptsetup.
sudo cryptsetup resize <encrypted-volume>
Note:
Steps 1 and 2 you have done already so you should be looking at step 3, but read through that link provided to understand what is going on.
Source:
https://help.ubuntu.com/community/ResizeEncryptedPartitions
answered Dec 23 at 20:35
George Udosen
19.5k94266
Exactly what I needed. Specifically, I followed the "Detailed resizing ~ Enlarging an encrypted partition" section in your link and it fixed the problem perfectly. Thank you.
– Zero
Dec 23 at 22:06
Your welcome and Happy holidays!
– George Udosen
Dec 23 at 22:07
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1104074%2fincreased-encrypted-partition-size-but-gnome-files-still-thinks-its-small%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I think you missed out on the LUKS resize part:
resize <name>
Resizes an active mapping <name>.
If --size (in sectors) is not specified, the size of the underlying block device is
used. Note that this does not change the raw device geometry, it just changes how
many sectors of the raw device are represented in the mapped device.
So the command sudo cryptsetup resize <encrypted-volume> should inform LUKS about the new size.
The basic steps are:
Boot the desktop, live CD. Use gparted (or any tool) to put unallocated space adjacent, and to the left of your Crypt partition.
Enlarge the Partition storing the crypt with fdisk.Reboot ~ You should always reboot after changing your partition table with fdisk.
Boot the desktop, live CD. Install & configure the tools (lvm2 and cryptsetup).
sudo apt update && sudo apt install lvm2 cryptsetupsudo modprobe dm-cryptsudo cryptsetup luksOpen /dev/sda5 crypt1
Enlarge the Crypt with cryptsetup.
sudo cryptsetup resize <encrypted-volume>
Note:
Steps 1 and 2 you have done already so you should be looking at step 3, but read through that link provided to understand what is going on.
Source:
https://help.ubuntu.com/community/ResizeEncryptedPartitions
answered Dec 23 at 20:35
George Udosen
19.5k94266
Exactly what I needed. Specifically, I followed the "Detailed resizing ~ Enlarging an encrypted partition" section in your link and it fixed the problem perfectly. Thank you.
– Zero
Dec 23 at 22:06
Your welcome and Happy holidays!
– George Udosen
Dec 23 at 22:07
add a comment |
I think you missed out on the LUKS resize part:
resize <name>
Resizes an active mapping <name>.
If --size (in sectors) is not specified, the size of the underlying block device is
used. Note that this does not change the raw device geometry, it just changes how
many sectors of the raw device are represented in the mapped device.
So the command sudo cryptsetup resize <encrypted-volume> should inform LUKS about the new size.
The basic steps are:
Boot the desktop, live CD. Use gparted (or any tool) to put unallocated space adjacent, and to the left of your Crypt partition.
Enlarge the Partition storing the crypt with fdisk.Reboot ~ You should always reboot after changing your partition table with fdisk.
Boot the desktop, live CD. Install & configure the tools (lvm2 and cryptsetup).
sudo apt update && sudo apt install lvm2 cryptsetupsudo modprobe dm-cryptsudo cryptsetup luksOpen /dev/sda5 crypt1
Enlarge the Crypt with cryptsetup.
sudo cryptsetup resize <encrypted-volume>
Note:
Steps 1 and 2 you have done already so you should be looking at step 3, but read through that link provided to understand what is going on.
Source:
https://help.ubuntu.com/community/ResizeEncryptedPartitions
answered Dec 23 at 20:35
George Udosen
19.5k94266
Exactly what I needed. Specifically, I followed the "Detailed resizing ~ Enlarging an encrypted partition" section in your link and it fixed the problem perfectly. Thank you.
– Zero
Dec 23 at 22:06
Your welcome and Happy holidays!
– George Udosen
Dec 23 at 22:07
add a comment |
I think you missed out on the LUKS resize part:
resize <name>
Resizes an active mapping <name>.
If --size (in sectors) is not specified, the size of the underlying block device is
used. Note that this does not change the raw device geometry, it just changes how
many sectors of the raw device are represented in the mapped device.
So the command sudo cryptsetup resize <encrypted-volume> should inform LUKS about the new size.
The basic steps are:
Boot the desktop, live CD. Use gparted (or any tool) to put unallocated space adjacent, and to the left of your Crypt partition.
Enlarge the Partition storing the crypt with fdisk.Reboot ~ You should always reboot after changing your partition table with fdisk.
Boot the desktop, live CD. Install & configure the tools (lvm2 and cryptsetup).
sudo apt update && sudo apt install lvm2 cryptsetupsudo modprobe dm-cryptsudo cryptsetup luksOpen /dev/sda5 crypt1
Enlarge the Crypt with cryptsetup.
sudo cryptsetup resize <encrypted-volume>
Note:
Steps 1 and 2 you have done already so you should be looking at step 3, but read through that link provided to understand what is going on.
Source:
https://help.ubuntu.com/community/ResizeEncryptedPartitions
answered Dec 23 at 20:35
George Udosen
19.5k94266
I think you missed out on the LUKS resize part:
resize <name>
Resizes an active mapping <name>.
If --size (in sectors) is not specified, the size of the underlying block device is
used. Note that this does not change the raw device geometry, it just changes how
many sectors of the raw device are represented in the mapped device.
So the command sudo cryptsetup resize <encrypted-volume> should inform LUKS about the new size.
The basic steps are:
Boot the desktop, live CD. Use gparted (or any tool) to put unallocated space adjacent, and to the left of your Crypt partition.
Enlarge the Partition storing the crypt with fdisk.Reboot ~ You should always reboot after changing your partition table with fdisk.
Boot the desktop, live CD. Install & configure the tools (lvm2 and cryptsetup).
sudo apt update && sudo apt install lvm2 cryptsetupsudo modprobe dm-cryptsudo cryptsetup luksOpen /dev/sda5 crypt1
Enlarge the Crypt with cryptsetup.
sudo cryptsetup resize <encrypted-volume>
Note:
Steps 1 and 2 you have done already so you should be looking at step 3, but read through that link provided to understand what is going on.
Source:
https://help.ubuntu.com/community/ResizeEncryptedPartitions
answered Dec 23 at 20:35
George Udosen
19.5k94266
edited Dec 23 at 21:07
answered Dec 23 at 20:35
George Udosen
19.5k94266
answered Dec 23 at 20:35
George Udosen
19.5k94266
answered Dec 23 at 20:35
George Udosen
19.5k94266
19.5k94266
Exactly what I needed. Specifically, I followed the "Detailed resizing ~ Enlarging an encrypted partition" section in your link and it fixed the problem perfectly. Thank you.
– Zero
Dec 23 at 22:06
Your welcome and Happy holidays!
– George Udosen
Dec 23 at 22:07
add a comment |
Exactly what I needed. Specifically, I followed the "Detailed resizing ~ Enlarging an encrypted partition" section in your link and it fixed the problem perfectly. Thank you.
– Zero
Dec 23 at 22:06
Your welcome and Happy holidays!
– George Udosen
Dec 23 at 22:07
Exactly what I needed. Specifically, I followed the "Detailed resizing ~ Enlarging an encrypted partition" section in your link and it fixed the problem perfectly. Thank you.
– Zero
Dec 23 at 22:06
Exactly what I needed. Specifically, I followed the "Detailed resizing ~ Enlarging an encrypted partition" section in your link and it fixed the problem perfectly. Thank you.
– Zero
Dec 23 at 22:06
Your welcome and Happy holidays!
– George Udosen
Dec 23 at 22:07
Your welcome and Happy holidays!
– George Udosen
Dec 23 at 22:07
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1104074%2fincreased-encrypted-partition-size-but-gnome-files-still-thinks-its-small%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The command
sudo cryptsetup resize --size <new-size> encrypted-volume. Let me check the entry for new-size!– George Udosen
Dec 23 at 20:26