grub on debian wheezy doesn't recognise mdraidDebian boot problemsCreating a partitioned raid1 array for...
PTIJ: Why can't I sing about soda on certain days?
Split a number into equal parts given the number of parts
School performs periodic password audits. Is my password compromised?
How does insurance birth control work?
Correct physics behind the colors on CD (compact disc)?
Rationale to prefer local variables over instance variables?
What is a term for a function that when called repeatedly, has the same effect as calling once?
I encountered my boss during an on-site interview at another company. Should I bring it up when seeing him next time?
Ahoy, Ye Traveler!
Quitting employee has privileged access to critical information
It doesn't matter the side you see it
How do I deal with being envious of my own players?
Where is the fallacy here?
Can an earth elemental drown/bury its opponent underground using earth glide?
How to mitigate "bandwagon attacking" from players?
The Ohm's law calculations of the parts do not agree with the whole
Can a space-faring robot still function over a billion years?
Difference between 'stomach' and 'uterus'
Why would the IRS ask for birth certificates or even audit a small tax return?
A bug in Excel? Conditional formatting for marking duplicates also highlights unique value
Should I use HTTPS on a domain that will only be used for redirection?
PTIJ: What dummy is the Gemara referring to?
What is better: yes / no radio, or simple checkbox?
Why doesn't "adolescent" take any articles in "listen to adolescent agonising"?
grub on debian wheezy doesn't recognise mdraid
Debian boot problemsCreating a partitioned raid1 array for booting a debian squeeze systemBuild and migrated to software raid (mdadm) on GPT disk, now can't assemble arrayRAID6 mdraid -> LVM -> EXT4 root with GRUB2?Debian Wheezy hangs before GRUB menu after successful install on Dell C-Series ServerDebian server does not get to grub on boot (possible raid issue)Cannot install grub, segmentation fault, unable to identify filesystem, superfluous RAID member, found two disks with same index — Debian 7Replaced SATA controller, software RAID (mdadm) stopped booting: grub rescue> no such diskIs it possible and wise to put the grub bios partition on a software raid?How to setup bootable RAID 0 on remote server
We're having a really strange problem when trying to boot from an mdraid on Debian Wheezy. All references online that I can find tell me that grub 1.99 (which is part of Debian Wheezy) should have no trouble booting from an mdraid volume. We're keep getting a grub rescue prompt, however.
We verified that grub can work with the disks, since booting from a non-raid ext4 formatted partition works without problem. As soon as we put /boot on a RAID array we created with mdadm, grub no longer recognises it.
Although we started out with a RAID5 array with LVM on top, while testing we've moved back to a simply /boot on a 4-disk RAID1 array. These are 4TB disks, so we're using GPT. We installed grub on all disks with the following command:
grub-install --no-floppy --modules="raid mdraid09 mdraid1x" /dev/sda
And for sdb, sdc and sdd, of course.
Grub keeps throwing us to grub rescue. An ls at this time only shows disks and gpt partitions, no md partitions. We've tried recreating the RAID1 with --metadata=0.9, but that didn't change the behaviour at all.
The hardware is a Dell PowerEdge R520 with the PERC 710i RAID controller. We've create RAID0s in the RAID controller for each disk and this seems to work as expected.
No obvious errors are thrown at installation time, either the OS or grub complain.
A reinstall of the grub-pc package doesn't solve the problem either.
We have no further idea what to try and are hoping for some input!
EDIT
We have indeed installed grub to every disk. We are getting a grub prompt, it just cannot read the mdraid. If we add a 'normal' ext4 partition to the machine to boot from, it works.
mdadm grub debian-wheezy
asked Jan 16 '14 at 11:37
Tim StoopTim Stoop
497313
bumped to the homepage by Community♦ 16 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
We're having a really strange problem when trying to boot from an mdraid on Debian Wheezy. All references online that I can find tell me that grub 1.99 (which is part of Debian Wheezy) should have no trouble booting from an mdraid volume. We're keep getting a grub rescue prompt, however.
We verified that grub can work with the disks, since booting from a non-raid ext4 formatted partition works without problem. As soon as we put /boot on a RAID array we created with mdadm, grub no longer recognises it.
Although we started out with a RAID5 array with LVM on top, while testing we've moved back to a simply /boot on a 4-disk RAID1 array. These are 4TB disks, so we're using GPT. We installed grub on all disks with the following command:
grub-install --no-floppy --modules="raid mdraid09 mdraid1x" /dev/sda
And for sdb, sdc and sdd, of course.
Grub keeps throwing us to grub rescue. An ls at this time only shows disks and gpt partitions, no md partitions. We've tried recreating the RAID1 with --metadata=0.9, but that didn't change the behaviour at all.
The hardware is a Dell PowerEdge R520 with the PERC 710i RAID controller. We've create RAID0s in the RAID controller for each disk and this seems to work as expected.
No obvious errors are thrown at installation time, either the OS or grub complain.
A reinstall of the grub-pc package doesn't solve the problem either.
We have no further idea what to try and are hoping for some input!
EDIT
We have indeed installed grub to every disk. We are getting a grub prompt, it just cannot read the mdraid. If we add a 'normal' ext4 partition to the machine to boot from, it works.
mdadm grub debian-wheezy
asked Jan 16 '14 at 11:37
Tim StoopTim Stoop
497313
bumped to the homepage by Community♦ 16 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Often, what the bios thinks is sd0 is not what grub thinks is sd0. Worse, sometimes linux doesn't agree, or grub when run from linux may disagree with grub run from bios. It is a PITA. I usually boot a KNOPPIX CD and install grub to every disk in the array. Also - I think /boot must be raid1, never raid5.
– Dan Garthwaite
Jan 16 '14 at 17:13
I've also seen a distro's rescue CD order drives differently than the same installed distro.
– Dan Garthwaite
Jan 16 '14 at 17:14
Yes, already tried that as well :S The server boots fine if we use a normal ext4 /boot partition. It's just that we'd prefer to have that partition on a RAID.
– Tim Stoop
Jan 17 '14 at 15:22
Sorry, a four disc RAID-1? I'm not quite sure how, unless it's RAID-1+0, which isn't RAID-1. Have you tried using a pukka RAID-1, ie two discs?
– MadHatter
Jan 17 '14 at 16:04
Yes, four disk RAID1. Just keep adding them.
– Dan Garthwaite
Jan 17 '14 at 18:04
add a comment |
We're having a really strange problem when trying to boot from an mdraid on Debian Wheezy. All references online that I can find tell me that grub 1.99 (which is part of Debian Wheezy) should have no trouble booting from an mdraid volume. We're keep getting a grub rescue prompt, however.
We verified that grub can work with the disks, since booting from a non-raid ext4 formatted partition works without problem. As soon as we put /boot on a RAID array we created with mdadm, grub no longer recognises it.
Although we started out with a RAID5 array with LVM on top, while testing we've moved back to a simply /boot on a 4-disk RAID1 array. These are 4TB disks, so we're using GPT. We installed grub on all disks with the following command:
grub-install --no-floppy --modules="raid mdraid09 mdraid1x" /dev/sda
And for sdb, sdc and sdd, of course.
Grub keeps throwing us to grub rescue. An ls at this time only shows disks and gpt partitions, no md partitions. We've tried recreating the RAID1 with --metadata=0.9, but that didn't change the behaviour at all.
The hardware is a Dell PowerEdge R520 with the PERC 710i RAID controller. We've create RAID0s in the RAID controller for each disk and this seems to work as expected.
No obvious errors are thrown at installation time, either the OS or grub complain.
A reinstall of the grub-pc package doesn't solve the problem either.
We have no further idea what to try and are hoping for some input!
EDIT
We have indeed installed grub to every disk. We are getting a grub prompt, it just cannot read the mdraid. If we add a 'normal' ext4 partition to the machine to boot from, it works.
mdadm grub debian-wheezy
asked Jan 16 '14 at 11:37
Tim StoopTim Stoop
497313
We're having a really strange problem when trying to boot from an mdraid on Debian Wheezy. All references online that I can find tell me that grub 1.99 (which is part of Debian Wheezy) should have no trouble booting from an mdraid volume. We're keep getting a grub rescue prompt, however.
We verified that grub can work with the disks, since booting from a non-raid ext4 formatted partition works without problem. As soon as we put /boot on a RAID array we created with mdadm, grub no longer recognises it.
Although we started out with a RAID5 array with LVM on top, while testing we've moved back to a simply /boot on a 4-disk RAID1 array. These are 4TB disks, so we're using GPT. We installed grub on all disks with the following command:
grub-install --no-floppy --modules="raid mdraid09 mdraid1x" /dev/sda
And for sdb, sdc and sdd, of course.
Grub keeps throwing us to grub rescue. An ls at this time only shows disks and gpt partitions, no md partitions. We've tried recreating the RAID1 with --metadata=0.9, but that didn't change the behaviour at all.
The hardware is a Dell PowerEdge R520 with the PERC 710i RAID controller. We've create RAID0s in the RAID controller for each disk and this seems to work as expected.
No obvious errors are thrown at installation time, either the OS or grub complain.
A reinstall of the grub-pc package doesn't solve the problem either.
We have no further idea what to try and are hoping for some input!
EDIT
We have indeed installed grub to every disk. We are getting a grub prompt, it just cannot read the mdraid. If we add a 'normal' ext4 partition to the machine to boot from, it works.
mdadm grub debian-wheezy
mdadm grub debian-wheezy
asked Jan 16 '14 at 11:37
Tim StoopTim Stoop
497313
asked Jan 16 '14 at 11:37
Tim StoopTim Stoop
497313
edited Jan 17 '14 at 15:20
Tim Stoop
asked Jan 16 '14 at 11:37
Tim StoopTim Stoop
497313
asked Jan 16 '14 at 11:37
Tim StoopTim Stoop
497313
asked Jan 16 '14 at 11:37
Tim StoopTim Stoop
497313
497313
bumped to the homepage by Community♦ 16 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 16 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Often, what the bios thinks is sd0 is not what grub thinks is sd0. Worse, sometimes linux doesn't agree, or grub when run from linux may disagree with grub run from bios. It is a PITA. I usually boot a KNOPPIX CD and install grub to every disk in the array. Also - I think /boot must be raid1, never raid5.
– Dan Garthwaite
Jan 16 '14 at 17:13
I've also seen a distro's rescue CD order drives differently than the same installed distro.
– Dan Garthwaite
Jan 16 '14 at 17:14
Yes, already tried that as well :S The server boots fine if we use a normal ext4 /boot partition. It's just that we'd prefer to have that partition on a RAID.
– Tim Stoop
Jan 17 '14 at 15:22
Sorry, a four disc RAID-1? I'm not quite sure how, unless it's RAID-1+0, which isn't RAID-1. Have you tried using a pukka RAID-1, ie two discs?
– MadHatter
Jan 17 '14 at 16:04
Yes, four disk RAID1. Just keep adding them.
– Dan Garthwaite
Jan 17 '14 at 18:04
add a comment |
Often, what the bios thinks is sd0 is not what grub thinks is sd0. Worse, sometimes linux doesn't agree, or grub when run from linux may disagree with grub run from bios. It is a PITA. I usually boot a KNOPPIX CD and install grub to every disk in the array. Also - I think /boot must be raid1, never raid5.
– Dan Garthwaite
Jan 16 '14 at 17:13
I've also seen a distro's rescue CD order drives differently than the same installed distro.
– Dan Garthwaite
Jan 16 '14 at 17:14
Yes, already tried that as well :S The server boots fine if we use a normal ext4 /boot partition. It's just that we'd prefer to have that partition on a RAID.
– Tim Stoop
Jan 17 '14 at 15:22
Sorry, a four disc RAID-1? I'm not quite sure how, unless it's RAID-1+0, which isn't RAID-1. Have you tried using a pukka RAID-1, ie two discs?
– MadHatter
Jan 17 '14 at 16:04
Yes, four disk RAID1. Just keep adding them.
– Dan Garthwaite
Jan 17 '14 at 18:04
Often, what the bios thinks is sd0 is not what grub thinks is sd0. Worse, sometimes linux doesn't agree, or grub when run from linux may disagree with grub run from bios. It is a PITA. I usually boot a KNOPPIX CD and install grub to every disk in the array. Also - I think /boot must be raid1, never raid5.
– Dan Garthwaite
Jan 16 '14 at 17:13
Often, what the bios thinks is sd0 is not what grub thinks is sd0. Worse, sometimes linux doesn't agree, or grub when run from linux may disagree with grub run from bios. It is a PITA. I usually boot a KNOPPIX CD and install grub to every disk in the array. Also - I think /boot must be raid1, never raid5.
– Dan Garthwaite
Jan 16 '14 at 17:13
I've also seen a distro's rescue CD order drives differently than the same installed distro.
– Dan Garthwaite
Jan 16 '14 at 17:14
I've also seen a distro's rescue CD order drives differently than the same installed distro.
– Dan Garthwaite
Jan 16 '14 at 17:14
Yes, already tried that as well :S The server boots fine if we use a normal ext4 /boot partition. It's just that we'd prefer to have that partition on a RAID.
– Tim Stoop
Jan 17 '14 at 15:22
Yes, already tried that as well :S The server boots fine if we use a normal ext4 /boot partition. It's just that we'd prefer to have that partition on a RAID.
– Tim Stoop
Jan 17 '14 at 15:22
Sorry, a four disc RAID-1? I'm not quite sure how, unless it's RAID-1+0, which isn't RAID-1. Have you tried using a pukka RAID-1, ie two discs?
– MadHatter
Jan 17 '14 at 16:04
Sorry, a four disc RAID-1? I'm not quite sure how, unless it's RAID-1+0, which isn't RAID-1. Have you tried using a pukka RAID-1, ie two discs?
– MadHatter
Jan 17 '14 at 16:04
Yes, four disk RAID1. Just keep adding them.
– Dan Garthwaite
Jan 17 '14 at 18:04
Yes, four disk RAID1. Just keep adding them.
– Dan Garthwaite
Jan 17 '14 at 18:04
add a comment |
1 Answer
1
active
oldest
votes
From my limited knowledge of grub with raid, I have concluded that it is important that the /boot raid array is indeed mounted to /boot when running grub-install, or specified with the boot= option.
How does your /boot/grub/grub.cfg file look like when issuing grub-install?
"set" is also interesting to view from the grub rescue console.
edited Jan 16 '16 at 11:48
Jakuje
6,85522534
answered Jan 16 '16 at 9:29
HestbenHestben
217
Heh, we eventually switched to PXE booting, which offered us more options and resilience for the exact problem we were fixing. Thanks for your interest, however!
– Tim Stoop
Jan 18 '16 at 13:48
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
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%2fserverfault.com%2fquestions%2f567671%2fgrub-on-debian-wheezy-doesnt-recognise-mdraid%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
From my limited knowledge of grub with raid, I have concluded that it is important that the /boot raid array is indeed mounted to /boot when running grub-install, or specified with the boot= option.
How does your /boot/grub/grub.cfg file look like when issuing grub-install?
"set" is also interesting to view from the grub rescue console.
edited Jan 16 '16 at 11:48
Jakuje
6,85522534
answered Jan 16 '16 at 9:29
HestbenHestben
217
Heh, we eventually switched to PXE booting, which offered us more options and resilience for the exact problem we were fixing. Thanks for your interest, however!
– Tim Stoop
Jan 18 '16 at 13:48
add a comment |
From my limited knowledge of grub with raid, I have concluded that it is important that the /boot raid array is indeed mounted to /boot when running grub-install, or specified with the boot= option.
How does your /boot/grub/grub.cfg file look like when issuing grub-install?
"set" is also interesting to view from the grub rescue console.
edited Jan 16 '16 at 11:48
Jakuje
6,85522534
answered Jan 16 '16 at 9:29
HestbenHestben
217
Heh, we eventually switched to PXE booting, which offered us more options and resilience for the exact problem we were fixing. Thanks for your interest, however!
– Tim Stoop
Jan 18 '16 at 13:48
add a comment |
From my limited knowledge of grub with raid, I have concluded that it is important that the /boot raid array is indeed mounted to /boot when running grub-install, or specified with the boot= option.
How does your /boot/grub/grub.cfg file look like when issuing grub-install?
"set" is also interesting to view from the grub rescue console.
edited Jan 16 '16 at 11:48
Jakuje
6,85522534
answered Jan 16 '16 at 9:29
HestbenHestben
217
From my limited knowledge of grub with raid, I have concluded that it is important that the /boot raid array is indeed mounted to /boot when running grub-install, or specified with the boot= option.
How does your /boot/grub/grub.cfg file look like when issuing grub-install?
"set" is also interesting to view from the grub rescue console.
edited Jan 16 '16 at 11:48
Jakuje
6,85522534
answered Jan 16 '16 at 9:29
HestbenHestben
217
edited Jan 16 '16 at 11:48
Jakuje
6,85522534
edited Jan 16 '16 at 11:48
Jakuje
6,85522534
edited Jan 16 '16 at 11:48
Jakuje
6,85522534
6,85522534
answered Jan 16 '16 at 9:29
HestbenHestben
217
answered Jan 16 '16 at 9:29
HestbenHestben
217
answered Jan 16 '16 at 9:29
HestbenHestben
217
217
Heh, we eventually switched to PXE booting, which offered us more options and resilience for the exact problem we were fixing. Thanks for your interest, however!
– Tim Stoop
Jan 18 '16 at 13:48
add a comment |
Heh, we eventually switched to PXE booting, which offered us more options and resilience for the exact problem we were fixing. Thanks for your interest, however!
– Tim Stoop
Jan 18 '16 at 13:48
Heh, we eventually switched to PXE booting, which offered us more options and resilience for the exact problem we were fixing. Thanks for your interest, however!
– Tim Stoop
Jan 18 '16 at 13:48
Heh, we eventually switched to PXE booting, which offered us more options and resilience for the exact problem we were fixing. Thanks for your interest, however!
– Tim Stoop
Jan 18 '16 at 13:48
add a comment |
Thanks for contributing an answer to Server Fault!
- 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%2fserverfault.com%2fquestions%2f567671%2fgrub-on-debian-wheezy-doesnt-recognise-mdraid%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
Often, what the bios thinks is sd0 is not what grub thinks is sd0. Worse, sometimes linux doesn't agree, or grub when run from linux may disagree with grub run from bios. It is a PITA. I usually boot a KNOPPIX CD and install grub to every disk in the array. Also - I think /boot must be raid1, never raid5.
– Dan Garthwaite
Jan 16 '14 at 17:13
I've also seen a distro's rescue CD order drives differently than the same installed distro.
– Dan Garthwaite
Jan 16 '14 at 17:14
Yes, already tried that as well :S The server boots fine if we use a normal ext4 /boot partition. It's just that we'd prefer to have that partition on a RAID.
– Tim Stoop
Jan 17 '14 at 15:22
Sorry, a four disc RAID-1? I'm not quite sure how, unless it's RAID-1+0, which isn't RAID-1. Have you tried using a pukka RAID-1, ie two discs?
– MadHatter
Jan 17 '14 at 16:04
Yes, four disk RAID1. Just keep adding them.
– Dan Garthwaite
Jan 17 '14 at 18:04