/boot has run out of room and cannot be resized
up vote
1
down vote
favorite
I recognize this answer has been provided multiple times, but I guess I need a little more help than what I have read thus far.
I have a hardware RAID1 SSD set (AMD RAID) that I set up successfully on my ASUS (M4A785-M) motherboard. As per my previous post, I cloned my previous hard drive RAID1 set to the SSDs using Clonezilla. I had a few issues, but the migration was successful.
I just got a notification for an update to Ubuntu base. I tried the update but there was not enough space. I have deleted all older version and memtest and it still needs 697K more space. I have never had an issue before that couldn't be solved just by getting rid of older versions, but it appears more space is needed for this newer base version.
I tried to resize using a GParted startup disk, but have had no success. It appears that I cannot extend this partition. I thought I read somewhere that one could move the /boot partition to an unallocated partition and use that as a the new boot partition. If that is the case, I would appreciate knowing exactly how to do that.
If that is not the case, I have two mirrored SSDs with a working Ubuntu operating system that cannot be upgraded.
Any advice on how I can resolve this problem without having to reinstall everything I have from scratch would be appreciated. I have included my GParted output. As you can see, I have plenty of unallocated space on the drive.
boot partitioning resize
edited Dec 4 at 7:46
karel
56k11124142
asked Dec 4 at 6:10
user3147955
61
|
show 2 more comments
up vote
1
down vote
favorite
I recognize this answer has been provided multiple times, but I guess I need a little more help than what I have read thus far.
I have a hardware RAID1 SSD set (AMD RAID) that I set up successfully on my ASUS (M4A785-M) motherboard. As per my previous post, I cloned my previous hard drive RAID1 set to the SSDs using Clonezilla. I had a few issues, but the migration was successful.
I just got a notification for an update to Ubuntu base. I tried the update but there was not enough space. I have deleted all older version and memtest and it still needs 697K more space. I have never had an issue before that couldn't be solved just by getting rid of older versions, but it appears more space is needed for this newer base version.
I tried to resize using a GParted startup disk, but have had no success. It appears that I cannot extend this partition. I thought I read somewhere that one could move the /boot partition to an unallocated partition and use that as a the new boot partition. If that is the case, I would appreciate knowing exactly how to do that.
If that is not the case, I have two mirrored SSDs with a working Ubuntu operating system that cannot be upgraded.
Any advice on how I can resolve this problem without having to reinstall everything I have from scratch would be appreciated. I have included my GParted output. As you can see, I have plenty of unallocated space on the drive.
boot partitioning resize
edited Dec 4 at 7:46
karel
56k11124142
asked Dec 4 at 6:10
user3147955
61
Try creating a directory /boot2 place your files in that and soft link them into /boot.ln -s /boot2/any_file /boot/any_file
– rhubarbdog
Dec 4 at 6:32
Thanks, I will give it a try. Would I have to link all new Ubuntu versions that same way. Get the update into /boot and copy them over to /boot2 and do the link to keep ample space in /boot open?
– user3147955
Dec 4 at 7:14
yes. This may not work, but your next solution is probably back everything up, erase your partitions and start again
– rhubarbdog
Dec 4 at 8:18
Manual, temporary solution: APT keeps two kernels installed. When you have checked the newest installed one works correctly, manually remove the older one. This should give you the space to install another.
– Melebius
Dec 4 at 8:58
1
Ok, so I backed up my entire system using APTIK, wiped out my RAID1 pair and installed the latest LTS Ubuntu 18.04 version. Then I did a restore. Had to do a little tweaking here and there (a lot actually) to get it back to the same as it was prior to the reinstall but I got there, all in one day.I notice that now there is only one big partition for the entire file system so space for /boot will no longer be a concern. Thanks to all who gave me advice here. I think this was the most comprehensive solution I could do to resolve this issue.
– user3147955
Dec 6 at 4:37
|
show 2 more comments
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I recognize this answer has been provided multiple times, but I guess I need a little more help than what I have read thus far.
I have a hardware RAID1 SSD set (AMD RAID) that I set up successfully on my ASUS (M4A785-M) motherboard. As per my previous post, I cloned my previous hard drive RAID1 set to the SSDs using Clonezilla. I had a few issues, but the migration was successful.
I just got a notification for an update to Ubuntu base. I tried the update but there was not enough space. I have deleted all older version and memtest and it still needs 697K more space. I have never had an issue before that couldn't be solved just by getting rid of older versions, but it appears more space is needed for this newer base version.
I tried to resize using a GParted startup disk, but have had no success. It appears that I cannot extend this partition. I thought I read somewhere that one could move the /boot partition to an unallocated partition and use that as a the new boot partition. If that is the case, I would appreciate knowing exactly how to do that.
If that is not the case, I have two mirrored SSDs with a working Ubuntu operating system that cannot be upgraded.
Any advice on how I can resolve this problem without having to reinstall everything I have from scratch would be appreciated. I have included my GParted output. As you can see, I have plenty of unallocated space on the drive.
boot partitioning resize
edited Dec 4 at 7:46
karel
56k11124142
asked Dec 4 at 6:10
user3147955
61
I recognize this answer has been provided multiple times, but I guess I need a little more help than what I have read thus far.
I have a hardware RAID1 SSD set (AMD RAID) that I set up successfully on my ASUS (M4A785-M) motherboard. As per my previous post, I cloned my previous hard drive RAID1 set to the SSDs using Clonezilla. I had a few issues, but the migration was successful.
I just got a notification for an update to Ubuntu base. I tried the update but there was not enough space. I have deleted all older version and memtest and it still needs 697K more space. I have never had an issue before that couldn't be solved just by getting rid of older versions, but it appears more space is needed for this newer base version.
I tried to resize using a GParted startup disk, but have had no success. It appears that I cannot extend this partition. I thought I read somewhere that one could move the /boot partition to an unallocated partition and use that as a the new boot partition. If that is the case, I would appreciate knowing exactly how to do that.
If that is not the case, I have two mirrored SSDs with a working Ubuntu operating system that cannot be upgraded.
Any advice on how I can resolve this problem without having to reinstall everything I have from scratch would be appreciated. I have included my GParted output. As you can see, I have plenty of unallocated space on the drive.
boot partitioning resize
boot partitioning resize
edited Dec 4 at 7:46
karel
56k11124142
asked Dec 4 at 6:10
user3147955
61
edited Dec 4 at 7:46
karel
56k11124142
asked Dec 4 at 6:10
user3147955
61
edited Dec 4 at 7:46
karel
56k11124142
edited Dec 4 at 7:46
karel
56k11124142
edited Dec 4 at 7:46
karel
56k11124142
56k11124142
asked Dec 4 at 6:10
user3147955
61
asked Dec 4 at 6:10
user3147955
61
asked Dec 4 at 6:10
user3147955
61
61
Try creating a directory /boot2 place your files in that and soft link them into /boot.ln -s /boot2/any_file /boot/any_file
– rhubarbdog
Dec 4 at 6:32
Thanks, I will give it a try. Would I have to link all new Ubuntu versions that same way. Get the update into /boot and copy them over to /boot2 and do the link to keep ample space in /boot open?
– user3147955
Dec 4 at 7:14
yes. This may not work, but your next solution is probably back everything up, erase your partitions and start again
– rhubarbdog
Dec 4 at 8:18
Manual, temporary solution: APT keeps two kernels installed. When you have checked the newest installed one works correctly, manually remove the older one. This should give you the space to install another.
– Melebius
Dec 4 at 8:58
1
Ok, so I backed up my entire system using APTIK, wiped out my RAID1 pair and installed the latest LTS Ubuntu 18.04 version. Then I did a restore. Had to do a little tweaking here and there (a lot actually) to get it back to the same as it was prior to the reinstall but I got there, all in one day.I notice that now there is only one big partition for the entire file system so space for /boot will no longer be a concern. Thanks to all who gave me advice here. I think this was the most comprehensive solution I could do to resolve this issue.
– user3147955
Dec 6 at 4:37
|
show 2 more comments
Try creating a directory /boot2 place your files in that and soft link them into /boot.ln -s /boot2/any_file /boot/any_file
– rhubarbdog
Dec 4 at 6:32
Thanks, I will give it a try. Would I have to link all new Ubuntu versions that same way. Get the update into /boot and copy them over to /boot2 and do the link to keep ample space in /boot open?
– user3147955
Dec 4 at 7:14
yes. This may not work, but your next solution is probably back everything up, erase your partitions and start again
– rhubarbdog
Dec 4 at 8:18
Manual, temporary solution: APT keeps two kernels installed. When you have checked the newest installed one works correctly, manually remove the older one. This should give you the space to install another.
– Melebius
Dec 4 at 8:58
1
Ok, so I backed up my entire system using APTIK, wiped out my RAID1 pair and installed the latest LTS Ubuntu 18.04 version. Then I did a restore. Had to do a little tweaking here and there (a lot actually) to get it back to the same as it was prior to the reinstall but I got there, all in one day.I notice that now there is only one big partition for the entire file system so space for /boot will no longer be a concern. Thanks to all who gave me advice here. I think this was the most comprehensive solution I could do to resolve this issue.
– user3147955
Dec 6 at 4:37
Try creating a directory /boot2 place your files in that and soft link them into /boot.
ln -s /boot2/any_file /boot/any_file– rhubarbdog
Dec 4 at 6:32
Try creating a directory /boot2 place your files in that and soft link them into /boot.
ln -s /boot2/any_file /boot/any_file– rhubarbdog
Dec 4 at 6:32
Thanks, I will give it a try. Would I have to link all new Ubuntu versions that same way. Get the update into /boot and copy them over to /boot2 and do the link to keep ample space in /boot open?
– user3147955
Dec 4 at 7:14
Thanks, I will give it a try. Would I have to link all new Ubuntu versions that same way. Get the update into /boot and copy them over to /boot2 and do the link to keep ample space in /boot open?
– user3147955
Dec 4 at 7:14
yes. This may not work, but your next solution is probably back everything up, erase your partitions and start again
– rhubarbdog
Dec 4 at 8:18
yes. This may not work, but your next solution is probably back everything up, erase your partitions and start again
– rhubarbdog
Dec 4 at 8:18
Manual, temporary solution: APT keeps two kernels installed. When you have checked the newest installed one works correctly, manually remove the older one. This should give you the space to install another.
– Melebius
Dec 4 at 8:58
Manual, temporary solution: APT keeps two kernels installed. When you have checked the newest installed one works correctly, manually remove the older one. This should give you the space to install another.
– Melebius
Dec 4 at 8:58
1
1
Ok, so I backed up my entire system using APTIK, wiped out my RAID1 pair and installed the latest LTS Ubuntu 18.04 version. Then I did a restore. Had to do a little tweaking here and there (a lot actually) to get it back to the same as it was prior to the reinstall but I got there, all in one day.I notice that now there is only one big partition for the entire file system so space for /boot will no longer be a concern. Thanks to all who gave me advice here. I think this was the most comprehensive solution I could do to resolve this issue.
– user3147955
Dec 6 at 4:37
Ok, so I backed up my entire system using APTIK, wiped out my RAID1 pair and installed the latest LTS Ubuntu 18.04 version. Then I did a restore. Had to do a little tweaking here and there (a lot actually) to get it back to the same as it was prior to the reinstall but I got there, all in one day.I notice that now there is only one big partition for the entire file system so space for /boot will no longer be a concern. Thanks to all who gave me advice here. I think this was the most comprehensive solution I could do to resolve this issue.
– user3147955
Dec 6 at 4:37
|
show 2 more comments
active
oldest
votes
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',
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%2f1098301%2fboot-has-run-out-of-room-and-cannot-be-resized%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f1098301%2fboot-has-run-out-of-room-and-cannot-be-resized%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
Try creating a directory /boot2 place your files in that and soft link them into /boot.
ln -s /boot2/any_file /boot/any_file– rhubarbdog
Dec 4 at 6:32
Thanks, I will give it a try. Would I have to link all new Ubuntu versions that same way. Get the update into /boot and copy them over to /boot2 and do the link to keep ample space in /boot open?
– user3147955
Dec 4 at 7:14
yes. This may not work, but your next solution is probably back everything up, erase your partitions and start again
– rhubarbdog
Dec 4 at 8:18
Manual, temporary solution: APT keeps two kernels installed. When you have checked the newest installed one works correctly, manually remove the older one. This should give you the space to install another.
– Melebius
Dec 4 at 8:58
1
Ok, so I backed up my entire system using APTIK, wiped out my RAID1 pair and installed the latest LTS Ubuntu 18.04 version. Then I did a restore. Had to do a little tweaking here and there (a lot actually) to get it back to the same as it was prior to the reinstall but I got there, all in one day.I notice that now there is only one big partition for the entire file system so space for /boot will no longer be a concern. Thanks to all who gave me advice here. I think this was the most comprehensive solution I could do to resolve this issue.
– user3147955
Dec 6 at 4:37