RAID fails to work after Ubuntu reinstall
So I have made a hardware raid in my motherboard bios that worked for Kubuntu 18.04 and mounted to my home folder. Due to issues with KDE and the Nvidia Drivers, I'm going back to Ubuntu (unity).
I try to use the same setup from my past RAID that has my home folders inside it. But when the system loads, it goes into emergency mode. The issue seems to be that /dev/mapper/isw__myraid has timed out. I had reinstalled twice and it has not fixed anything.
And this is what my installer sees
Gnome disk sees differently
boot partitioning raid
asked Jan 26 at 0:54
weezle1234weezle1234
85110
add a comment |
So I have made a hardware raid in my motherboard bios that worked for Kubuntu 18.04 and mounted to my home folder. Due to issues with KDE and the Nvidia Drivers, I'm going back to Ubuntu (unity).
I try to use the same setup from my past RAID that has my home folders inside it. But when the system loads, it goes into emergency mode. The issue seems to be that /dev/mapper/isw__myraid has timed out. I had reinstalled twice and it has not fixed anything.
And this is what my installer sees
Gnome disk sees differently
boot partitioning raid
asked Jan 26 at 0:54
weezle1234weezle1234
85110
In my experience, the machine does not generally see the 'raid' array if it's in hardware (unless you use purpose-tools to peek into hardware) so I'd guess you have made a hardware/bios change (ie. bios or setting change outside of Ubuntu) or your hardware raid has failed & no longer functions. This is outside of Ubuntu's control in my opinion.
– guiverc
Jan 26 at 1:12
Yea I actually fixed it on accident
– weezle1234
Jan 26 at 1:36
add a comment |
So I have made a hardware raid in my motherboard bios that worked for Kubuntu 18.04 and mounted to my home folder. Due to issues with KDE and the Nvidia Drivers, I'm going back to Ubuntu (unity).
I try to use the same setup from my past RAID that has my home folders inside it. But when the system loads, it goes into emergency mode. The issue seems to be that /dev/mapper/isw__myraid has timed out. I had reinstalled twice and it has not fixed anything.
And this is what my installer sees
Gnome disk sees differently
boot partitioning raid
asked Jan 26 at 0:54
weezle1234weezle1234
85110
So I have made a hardware raid in my motherboard bios that worked for Kubuntu 18.04 and mounted to my home folder. Due to issues with KDE and the Nvidia Drivers, I'm going back to Ubuntu (unity).
I try to use the same setup from my past RAID that has my home folders inside it. But when the system loads, it goes into emergency mode. The issue seems to be that /dev/mapper/isw__myraid has timed out. I had reinstalled twice and it has not fixed anything.
And this is what my installer sees
Gnome disk sees differently
boot partitioning raid
boot partitioning raid
asked Jan 26 at 0:54
weezle1234weezle1234
85110
asked Jan 26 at 0:54
weezle1234weezle1234
85110
asked Jan 26 at 0:54
weezle1234weezle1234
85110
asked Jan 26 at 0:54
weezle1234weezle1234
85110
asked Jan 26 at 0:54
weezle1234weezle1234
85110
85110
In my experience, the machine does not generally see the 'raid' array if it's in hardware (unless you use purpose-tools to peek into hardware) so I'd guess you have made a hardware/bios change (ie. bios or setting change outside of Ubuntu) or your hardware raid has failed & no longer functions. This is outside of Ubuntu's control in my opinion.
– guiverc
Jan 26 at 1:12
Yea I actually fixed it on accident
– weezle1234
Jan 26 at 1:36
add a comment |
In my experience, the machine does not generally see the 'raid' array if it's in hardware (unless you use purpose-tools to peek into hardware) so I'd guess you have made a hardware/bios change (ie. bios or setting change outside of Ubuntu) or your hardware raid has failed & no longer functions. This is outside of Ubuntu's control in my opinion.
– guiverc
Jan 26 at 1:12
Yea I actually fixed it on accident
– weezle1234
Jan 26 at 1:36
In my experience, the machine does not generally see the 'raid' array if it's in hardware (unless you use purpose-tools to peek into hardware) so I'd guess you have made a hardware/bios change (ie. bios or setting change outside of Ubuntu) or your hardware raid has failed & no longer functions. This is outside of Ubuntu's control in my opinion.
– guiverc
Jan 26 at 1:12
In my experience, the machine does not generally see the 'raid' array if it's in hardware (unless you use purpose-tools to peek into hardware) so I'd guess you have made a hardware/bios change (ie. bios or setting change outside of Ubuntu) or your hardware raid has failed & no longer functions. This is outside of Ubuntu's control in my opinion.
– guiverc
Jan 26 at 1:12
Yea I actually fixed it on accident
– weezle1234
Jan 26 at 1:36
Yea I actually fixed it on accident
– weezle1234
Jan 26 at 1:36
add a comment |
1 Answer
1
active
oldest
votes
So apparently the issue was my BIOS. My system has UEFI and boots from an M.2 SSD so the motherboard had some secure keys that needed to be deleted from the system in order to work.
Now it boots fine.
answered Jan 26 at 1:38
weezle1234weezle1234
85110
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%2f1112963%2fraid-fails-to-work-after-ubuntu-reinstall%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
So apparently the issue was my BIOS. My system has UEFI and boots from an M.2 SSD so the motherboard had some secure keys that needed to be deleted from the system in order to work.
Now it boots fine.
answered Jan 26 at 1:38
weezle1234weezle1234
85110
add a comment |
So apparently the issue was my BIOS. My system has UEFI and boots from an M.2 SSD so the motherboard had some secure keys that needed to be deleted from the system in order to work.
Now it boots fine.
answered Jan 26 at 1:38
weezle1234weezle1234
85110
add a comment |
So apparently the issue was my BIOS. My system has UEFI and boots from an M.2 SSD so the motherboard had some secure keys that needed to be deleted from the system in order to work.
Now it boots fine.
answered Jan 26 at 1:38
weezle1234weezle1234
85110
So apparently the issue was my BIOS. My system has UEFI and boots from an M.2 SSD so the motherboard had some secure keys that needed to be deleted from the system in order to work.
Now it boots fine.
answered Jan 26 at 1:38
weezle1234weezle1234
85110
answered Jan 26 at 1:38
weezle1234weezle1234
85110
answered Jan 26 at 1:38
weezle1234weezle1234
85110
answered Jan 26 at 1:38
weezle1234weezle1234
85110
85110
add a comment |
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.
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%2f1112963%2fraid-fails-to-work-after-ubuntu-reinstall%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
In my experience, the machine does not generally see the 'raid' array if it's in hardware (unless you use purpose-tools to peek into hardware) so I'd guess you have made a hardware/bios change (ie. bios or setting change outside of Ubuntu) or your hardware raid has failed & no longer functions. This is outside of Ubuntu's control in my opinion.
– guiverc
Jan 26 at 1:12
Yea I actually fixed it on accident
– weezle1234
Jan 26 at 1:36