Need to rescue working files after Kubunt 18.04.2 surprise release. 18.04.1 won't boot into desktop, so used...
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I verified /home/user directory and copied possibly relevant files to a backup directory. Changed owners to user. Made an empty USB to receive the backup file. So far, I'm frustrated. I may not be able to recover my bookmarks, either.
Somehow I need to copy the backup directory to a mounted 18.04.2 partition or USB stick, one way or another. There is only Kubuntu on this drive.
-- Additional information copied from comments
I made an update of 18.04.1 late Sunday the 10th or early Monday the 11th. Just an update, not an upgrade. I was tired and went to bed. At first I was confused what had happened when 18.04.1 wouldn't boot. I made a boot USB and that didn't help. I tried my old 18.04.1 install dvd, but that would only install 18.04.2. So, I put another, 18.04.2 partition on the drive, trying to preserve the 18.04.1 partition. Checking, 18.04.2 wasn't supposed to be released before Thursday, February 14. I'm not certain that 18.04.2 did in 18.04.1, but it's certainly complicated the process of rescue. I tried various things in KDE partition manager and GParted from the mounted 18.04.2 partition. I think I removed the 18.04.1 "bootable" label, in hopes that I could mount the partition as just a data partition. Removing the label didn't seem to make any difference. Anything, nothing seemed harmed.
I tried a lot of things, including making an empty ext4 USB stick, but couldn't get it to mount in 18.04.1. Anyway, I have this directory in the 18.04.1 partition that I need to transfer somewhere that it it can be saved more or less permanently, for reuse. I thought I did pretty well getting as far as I have, I will probably lose my list of installed packages, but who knows. In short, I did an awful lot of work that I would lack to save, as far as is reasonable. I'm willing to try some things, but I need help.
I first tried selecting each earlier kernel in turn, but the best I can do is get a root prompt. running "startx," but the result was disappointing. Perhaps I wasn't systematic with "startx" on each earlier kernel. I do know that no mount is listed on that partition. Should there be one, or would I just make more trouble for myself? I haven't been able to reapply the tag "bootable" on 18.04.1.
boot partitioning backup
edited Feb 13 at 8:10
guiverc
5,19921723
asked Feb 13 at 6:36
Byron HaleByron Hale
1
|
show 5 more comments
I verified /home/user directory and copied possibly relevant files to a backup directory. Changed owners to user. Made an empty USB to receive the backup file. So far, I'm frustrated. I may not be able to recover my bookmarks, either.
Somehow I need to copy the backup directory to a mounted 18.04.2 partition or USB stick, one way or another. There is only Kubuntu on this drive.
-- Additional information copied from comments
I made an update of 18.04.1 late Sunday the 10th or early Monday the 11th. Just an update, not an upgrade. I was tired and went to bed. At first I was confused what had happened when 18.04.1 wouldn't boot. I made a boot USB and that didn't help. I tried my old 18.04.1 install dvd, but that would only install 18.04.2. So, I put another, 18.04.2 partition on the drive, trying to preserve the 18.04.1 partition. Checking, 18.04.2 wasn't supposed to be released before Thursday, February 14. I'm not certain that 18.04.2 did in 18.04.1, but it's certainly complicated the process of rescue. I tried various things in KDE partition manager and GParted from the mounted 18.04.2 partition. I think I removed the 18.04.1 "bootable" label, in hopes that I could mount the partition as just a data partition. Removing the label didn't seem to make any difference. Anything, nothing seemed harmed.
I tried a lot of things, including making an empty ext4 USB stick, but couldn't get it to mount in 18.04.1. Anyway, I have this directory in the 18.04.1 partition that I need to transfer somewhere that it it can be saved more or less permanently, for reuse. I thought I did pretty well getting as far as I have, I will probably lose my list of installed packages, but who knows. In short, I did an awful lot of work that I would lack to save, as far as is reasonable. I'm willing to try some things, but I need help.
I first tried selecting each earlier kernel in turn, but the best I can do is get a root prompt. running "startx," but the result was disappointing. Perhaps I wasn't systematic with "startx" on each earlier kernel. I do know that no mount is listed on that partition. Should there be one, or would I just make more trouble for myself? I haven't been able to reapply the tag "bootable" on 18.04.1.
boot partitioning backup
edited Feb 13 at 8:10
guiverc
5,19921723
asked Feb 13 at 6:36
Byron HaleByron Hale
1
I meant to omit "There is no" and just say that I need to transfer the bacdkup folder to a working partition or USB stick.
– Byron Hale
Feb 13 at 6:42
I'm sorry but I don't understand your issue. What caused the issue? Why was 18.04.2 a surprise? Verified it how? You may need to clarify what your problem is. Also you should be able to edit your own questions, which is preferable to putting corrections in comments
– guiverc
Feb 13 at 6:50
Thanks for the edit, guiverc! I made an update of 18.04.1 late Sunday the 10th or early Monday the 11th. Just an update, not an upgrade. I was tired and went to bed. At first I was confused what had happened when 18.04.1 wouldn't boot. I made a boot USB and that didn't help. I tried my old 18.04.1 install dvd, but that
– Byron Hale
Feb 13 at 6:58
would only install 18.04.2. So, I put another, 18.04.2 partition on the drive, trying to preserve the 18.04.1 partition. Checking, 18.04.2 wasn't supposed to be released before Thursday, February 14. I'm not certain that 18.04.2 did in 18.04.1, but it's certainly complicated the process of rescue. I tried various things in KDE partition manager and GParted from the mounted 18.04.2 partition. I think I removed the 18.04.1 "bootable" label, in hopes that I could mount the partition as just a data partition. Removing the label didn't seem to make any difference. Anything, nothing seemed harmed.
– Byron Hale
Feb 13 at 7:17
I tried a lot of things, including making an empty ext4 USB stick, but couldn't get it to mount in 18.04.1. Anyway, I have this directory in the 18.04.1 partition that I need to transfer somewhere that it it can be saved more or less permanently, for reuse. I thought I did pretty well getting as far as I have, I will probably lose my list of installed packages, but who knows. In short, I did an awful lot of work that I would lack to save, as far as is reasonable. I'm willing to try some things, but I need help.
– Byron Hale
Feb 13 at 7:26
|
show 5 more comments
I verified /home/user directory and copied possibly relevant files to a backup directory. Changed owners to user. Made an empty USB to receive the backup file. So far, I'm frustrated. I may not be able to recover my bookmarks, either.
Somehow I need to copy the backup directory to a mounted 18.04.2 partition or USB stick, one way or another. There is only Kubuntu on this drive.
-- Additional information copied from comments
I made an update of 18.04.1 late Sunday the 10th or early Monday the 11th. Just an update, not an upgrade. I was tired and went to bed. At first I was confused what had happened when 18.04.1 wouldn't boot. I made a boot USB and that didn't help. I tried my old 18.04.1 install dvd, but that would only install 18.04.2. So, I put another, 18.04.2 partition on the drive, trying to preserve the 18.04.1 partition. Checking, 18.04.2 wasn't supposed to be released before Thursday, February 14. I'm not certain that 18.04.2 did in 18.04.1, but it's certainly complicated the process of rescue. I tried various things in KDE partition manager and GParted from the mounted 18.04.2 partition. I think I removed the 18.04.1 "bootable" label, in hopes that I could mount the partition as just a data partition. Removing the label didn't seem to make any difference. Anything, nothing seemed harmed.
I tried a lot of things, including making an empty ext4 USB stick, but couldn't get it to mount in 18.04.1. Anyway, I have this directory in the 18.04.1 partition that I need to transfer somewhere that it it can be saved more or less permanently, for reuse. I thought I did pretty well getting as far as I have, I will probably lose my list of installed packages, but who knows. In short, I did an awful lot of work that I would lack to save, as far as is reasonable. I'm willing to try some things, but I need help.
I first tried selecting each earlier kernel in turn, but the best I can do is get a root prompt. running "startx," but the result was disappointing. Perhaps I wasn't systematic with "startx" on each earlier kernel. I do know that no mount is listed on that partition. Should there be one, or would I just make more trouble for myself? I haven't been able to reapply the tag "bootable" on 18.04.1.
boot partitioning backup
edited Feb 13 at 8:10
guiverc
5,19921723
asked Feb 13 at 6:36
Byron HaleByron Hale
1
I verified /home/user directory and copied possibly relevant files to a backup directory. Changed owners to user. Made an empty USB to receive the backup file. So far, I'm frustrated. I may not be able to recover my bookmarks, either.
Somehow I need to copy the backup directory to a mounted 18.04.2 partition or USB stick, one way or another. There is only Kubuntu on this drive.
-- Additional information copied from comments
I made an update of 18.04.1 late Sunday the 10th or early Monday the 11th. Just an update, not an upgrade. I was tired and went to bed. At first I was confused what had happened when 18.04.1 wouldn't boot. I made a boot USB and that didn't help. I tried my old 18.04.1 install dvd, but that would only install 18.04.2. So, I put another, 18.04.2 partition on the drive, trying to preserve the 18.04.1 partition. Checking, 18.04.2 wasn't supposed to be released before Thursday, February 14. I'm not certain that 18.04.2 did in 18.04.1, but it's certainly complicated the process of rescue. I tried various things in KDE partition manager and GParted from the mounted 18.04.2 partition. I think I removed the 18.04.1 "bootable" label, in hopes that I could mount the partition as just a data partition. Removing the label didn't seem to make any difference. Anything, nothing seemed harmed.
I tried a lot of things, including making an empty ext4 USB stick, but couldn't get it to mount in 18.04.1. Anyway, I have this directory in the 18.04.1 partition that I need to transfer somewhere that it it can be saved more or less permanently, for reuse. I thought I did pretty well getting as far as I have, I will probably lose my list of installed packages, but who knows. In short, I did an awful lot of work that I would lack to save, as far as is reasonable. I'm willing to try some things, but I need help.
I first tried selecting each earlier kernel in turn, but the best I can do is get a root prompt. running "startx," but the result was disappointing. Perhaps I wasn't systematic with "startx" on each earlier kernel. I do know that no mount is listed on that partition. Should there be one, or would I just make more trouble for myself? I haven't been able to reapply the tag "bootable" on 18.04.1.
boot partitioning backup
boot partitioning backup
edited Feb 13 at 8:10
guiverc
5,19921723
asked Feb 13 at 6:36
Byron HaleByron Hale
1
edited Feb 13 at 8:10
guiverc
5,19921723
asked Feb 13 at 6:36
Byron HaleByron Hale
1
edited Feb 13 at 8:10
guiverc
5,19921723
edited Feb 13 at 8:10
guiverc
5,19921723
edited Feb 13 at 8:10
guiverc
5,19921723
5,19921723
asked Feb 13 at 6:36
Byron HaleByron Hale
1
asked Feb 13 at 6:36
Byron HaleByron Hale
1
asked Feb 13 at 6:36
Byron HaleByron Hale
1
1
I meant to omit "There is no" and just say that I need to transfer the bacdkup folder to a working partition or USB stick.
– Byron Hale
Feb 13 at 6:42
I'm sorry but I don't understand your issue. What caused the issue? Why was 18.04.2 a surprise? Verified it how? You may need to clarify what your problem is. Also you should be able to edit your own questions, which is preferable to putting corrections in comments
– guiverc
Feb 13 at 6:50
Thanks for the edit, guiverc! I made an update of 18.04.1 late Sunday the 10th or early Monday the 11th. Just an update, not an upgrade. I was tired and went to bed. At first I was confused what had happened when 18.04.1 wouldn't boot. I made a boot USB and that didn't help. I tried my old 18.04.1 install dvd, but that
– Byron Hale
Feb 13 at 6:58
would only install 18.04.2. So, I put another, 18.04.2 partition on the drive, trying to preserve the 18.04.1 partition. Checking, 18.04.2 wasn't supposed to be released before Thursday, February 14. I'm not certain that 18.04.2 did in 18.04.1, but it's certainly complicated the process of rescue. I tried various things in KDE partition manager and GParted from the mounted 18.04.2 partition. I think I removed the 18.04.1 "bootable" label, in hopes that I could mount the partition as just a data partition. Removing the label didn't seem to make any difference. Anything, nothing seemed harmed.
– Byron Hale
Feb 13 at 7:17
I tried a lot of things, including making an empty ext4 USB stick, but couldn't get it to mount in 18.04.1. Anyway, I have this directory in the 18.04.1 partition that I need to transfer somewhere that it it can be saved more or less permanently, for reuse. I thought I did pretty well getting as far as I have, I will probably lose my list of installed packages, but who knows. In short, I did an awful lot of work that I would lack to save, as far as is reasonable. I'm willing to try some things, but I need help.
– Byron Hale
Feb 13 at 7:26
|
show 5 more comments
I meant to omit "There is no" and just say that I need to transfer the bacdkup folder to a working partition or USB stick.
– Byron Hale
Feb 13 at 6:42
I'm sorry but I don't understand your issue. What caused the issue? Why was 18.04.2 a surprise? Verified it how? You may need to clarify what your problem is. Also you should be able to edit your own questions, which is preferable to putting corrections in comments
– guiverc
Feb 13 at 6:50
Thanks for the edit, guiverc! I made an update of 18.04.1 late Sunday the 10th or early Monday the 11th. Just an update, not an upgrade. I was tired and went to bed. At first I was confused what had happened when 18.04.1 wouldn't boot. I made a boot USB and that didn't help. I tried my old 18.04.1 install dvd, but that
– Byron Hale
Feb 13 at 6:58
would only install 18.04.2. So, I put another, 18.04.2 partition on the drive, trying to preserve the 18.04.1 partition. Checking, 18.04.2 wasn't supposed to be released before Thursday, February 14. I'm not certain that 18.04.2 did in 18.04.1, but it's certainly complicated the process of rescue. I tried various things in KDE partition manager and GParted from the mounted 18.04.2 partition. I think I removed the 18.04.1 "bootable" label, in hopes that I could mount the partition as just a data partition. Removing the label didn't seem to make any difference. Anything, nothing seemed harmed.
– Byron Hale
Feb 13 at 7:17
I tried a lot of things, including making an empty ext4 USB stick, but couldn't get it to mount in 18.04.1. Anyway, I have this directory in the 18.04.1 partition that I need to transfer somewhere that it it can be saved more or less permanently, for reuse. I thought I did pretty well getting as far as I have, I will probably lose my list of installed packages, but who knows. In short, I did an awful lot of work that I would lack to save, as far as is reasonable. I'm willing to try some things, but I need help.
– Byron Hale
Feb 13 at 7:26
I meant to omit "There is no" and just say that I need to transfer the bacdkup folder to a working partition or USB stick.
– Byron Hale
Feb 13 at 6:42
I meant to omit "There is no" and just say that I need to transfer the bacdkup folder to a working partition or USB stick.
– Byron Hale
Feb 13 at 6:42
I'm sorry but I don't understand your issue. What caused the issue? Why was 18.04.2 a surprise? Verified it how? You may need to clarify what your problem is. Also you should be able to edit your own questions, which is preferable to putting corrections in comments
– guiverc
Feb 13 at 6:50
I'm sorry but I don't understand your issue. What caused the issue? Why was 18.04.2 a surprise? Verified it how? You may need to clarify what your problem is. Also you should be able to edit your own questions, which is preferable to putting corrections in comments
– guiverc
Feb 13 at 6:50
Thanks for the edit, guiverc! I made an update of 18.04.1 late Sunday the 10th or early Monday the 11th. Just an update, not an upgrade. I was tired and went to bed. At first I was confused what had happened when 18.04.1 wouldn't boot. I made a boot USB and that didn't help. I tried my old 18.04.1 install dvd, but that
– Byron Hale
Feb 13 at 6:58
Thanks for the edit, guiverc! I made an update of 18.04.1 late Sunday the 10th or early Monday the 11th. Just an update, not an upgrade. I was tired and went to bed. At first I was confused what had happened when 18.04.1 wouldn't boot. I made a boot USB and that didn't help. I tried my old 18.04.1 install dvd, but that
– Byron Hale
Feb 13 at 6:58
would only install 18.04.2. So, I put another, 18.04.2 partition on the drive, trying to preserve the 18.04.1 partition. Checking, 18.04.2 wasn't supposed to be released before Thursday, February 14. I'm not certain that 18.04.2 did in 18.04.1, but it's certainly complicated the process of rescue. I tried various things in KDE partition manager and GParted from the mounted 18.04.2 partition. I think I removed the 18.04.1 "bootable" label, in hopes that I could mount the partition as just a data partition. Removing the label didn't seem to make any difference. Anything, nothing seemed harmed.
– Byron Hale
Feb 13 at 7:17
would only install 18.04.2. So, I put another, 18.04.2 partition on the drive, trying to preserve the 18.04.1 partition. Checking, 18.04.2 wasn't supposed to be released before Thursday, February 14. I'm not certain that 18.04.2 did in 18.04.1, but it's certainly complicated the process of rescue. I tried various things in KDE partition manager and GParted from the mounted 18.04.2 partition. I think I removed the 18.04.1 "bootable" label, in hopes that I could mount the partition as just a data partition. Removing the label didn't seem to make any difference. Anything, nothing seemed harmed.
– Byron Hale
Feb 13 at 7:17
I tried a lot of things, including making an empty ext4 USB stick, but couldn't get it to mount in 18.04.1. Anyway, I have this directory in the 18.04.1 partition that I need to transfer somewhere that it it can be saved more or less permanently, for reuse. I thought I did pretty well getting as far as I have, I will probably lose my list of installed packages, but who knows. In short, I did an awful lot of work that I would lack to save, as far as is reasonable. I'm willing to try some things, but I need help.
– Byron Hale
Feb 13 at 7:26
I tried a lot of things, including making an empty ext4 USB stick, but couldn't get it to mount in 18.04.1. Anyway, I have this directory in the 18.04.1 partition that I need to transfer somewhere that it it can be saved more or less permanently, for reuse. I thought I did pretty well getting as far as I have, I will probably lose my list of installed packages, but who knows. In short, I did an awful lot of work that I would lack to save, as far as is reasonable. I'm willing to try some things, but I need help.
– Byron Hale
Feb 13 at 7:26
|
show 5 more comments
0
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',
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%2f1117844%2fneed-to-rescue-working-files-after-kubunt-18-04-2-surprise-release-18-04-1-won%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
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.
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%2f1117844%2fneed-to-rescue-working-files-after-kubunt-18-04-2-surprise-release-18-04-1-won%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
I meant to omit "There is no" and just say that I need to transfer the bacdkup folder to a working partition or USB stick.
– Byron Hale
Feb 13 at 6:42
I'm sorry but I don't understand your issue. What caused the issue? Why was 18.04.2 a surprise? Verified it how? You may need to clarify what your problem is. Also you should be able to edit your own questions, which is preferable to putting corrections in comments
– guiverc
Feb 13 at 6:50
Thanks for the edit, guiverc! I made an update of 18.04.1 late Sunday the 10th or early Monday the 11th. Just an update, not an upgrade. I was tired and went to bed. At first I was confused what had happened when 18.04.1 wouldn't boot. I made a boot USB and that didn't help. I tried my old 18.04.1 install dvd, but that
– Byron Hale
Feb 13 at 6:58
would only install 18.04.2. So, I put another, 18.04.2 partition on the drive, trying to preserve the 18.04.1 partition. Checking, 18.04.2 wasn't supposed to be released before Thursday, February 14. I'm not certain that 18.04.2 did in 18.04.1, but it's certainly complicated the process of rescue. I tried various things in KDE partition manager and GParted from the mounted 18.04.2 partition. I think I removed the 18.04.1 "bootable" label, in hopes that I could mount the partition as just a data partition. Removing the label didn't seem to make any difference. Anything, nothing seemed harmed.
– Byron Hale
Feb 13 at 7:17
I tried a lot of things, including making an empty ext4 USB stick, but couldn't get it to mount in 18.04.1. Anyway, I have this directory in the 18.04.1 partition that I need to transfer somewhere that it it can be saved more or less permanently, for reuse. I thought I did pretty well getting as far as I have, I will probably lose my list of installed packages, but who knows. In short, I did an awful lot of work that I would lack to save, as far as is reasonable. I'm willing to try some things, but I need help.
– Byron Hale
Feb 13 at 7:26