Re: grub-pc mdadm root (really Resolved)
15/01/2012 00:16, Marc Auslander wrote: From /etc/defaults/mdadm # INITRDSTART: # list of arrays (or 'all') to start automatically when the initial ramdisk # loads. This list *must* include the array holding your root filesystem. Use # 'none' to prevent any array from being started from the initial ramdisk. INITRDSTART='none' Changing this to all (or just the root device, but I put in all) is the correct fix. How did I miss that for so long. Sigh. Thanks to all. Just for the records, when installing on raid from the Debian installer (from my experience with wheezy), this option is set to all automatically, and AUTOSTART to true. Good you solved it. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f12a8fd.5090...@googlemail.com
Re: grub-pc mdadm root
On Sat, Jan 14, 2012 at 6:00 PM, Marc Auslander marca...@gmail.com wrote: Tom H tomh0...@gmail.com writes: Can you unpack your initrd and check whether you have an mdadm script in the scripts directory, an mdadm rule in the udev directory, and an /etc/mdadm/mdadm.conf? (I can't access a Debian box at the moment or I would've given you exact paths to the first two; sorry.) I looked in initrd. There is both an mdadm script and my kludge script in local-top. There is an mdadm.conf. There is no udev or dev in the archive at all. I think one problem is that /conf/conf.d/md in initrd has MD_DEVS=none but where does that come from? Both MD_DEVS=none and the non-existence /lib/udev/rules.d/64-md-raid-rules in your initrd are from /usr/share/initramfs-tools/hooks/mdadm which sources /etc/default/mdadm - in which you have non-default values. Rather than stay with your manual addition of a script to your initrd, I'd adjust the values in /etc/default/mdadm and regenerate the initrd. If you don't, the next time that it's regenerated, you'll eventually reboot into an initramfs shell. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=SyrfsWHgHdqNgV2LeX8=9vedbopeulicva_pbqfdvk...@mail.gmail.com
Re: grub-pc mdadm root
On Fri, Jan 13, 2012 at 4:08 PM, Marc Auslander marca...@gmail.com wrote:
I'm still having no luck booting an mdadm 1.2 root.
grub2 works - I get into the boot kernel and initram. But when it
comes to mount the real kernel, I fall into initramfs shell with a
message that the kernel can't be found. And it can't, because the
raid root device hasn't been assembled. (No raid devices exist in
/dev).
I can assemble it in initramfs shell using mdadm, so all the stuff is there.
So I really need to see any grub.cfg stanza that actually works -
mostly to see what vmlinuz parameters are needed.
It think that it's your initrd that needs some attention...
Anyway, from a wheezy install:
menuentry 'Debian GNU/Linux, with Linux 3.1.0-1-686-pae' --class
debian --class gnu-linux --class gnu --class os {
insmod gzio
insmod raid
insmod mdraid1x
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(mduuid/ea8a8cde873a9900f6e13b3742a475ca)'
search --no-floppy --fs-uuid --set=root
e201fc61-91dd-4657-a703-0f7802df62c7
echo'Loading Linux 3.1.0-1-686-pae ...'
linux /boot/vmlinuz-3.1.0-1-686-pae
root=UUID=e201fc61-91dd-4657-a703-0f7802df62c7 ro
echo'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.1.0-1-686-pae
}
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAOdo=szqy7kdnmj+p6s8uzk3rhqzzoaf9cuknwmos85zcvv...@mail.gmail.com
Re: grub-pc mdadm root
Tom H tomh0...@gmail.com writes: On Fri, Jan 13, 2012 at 4:08 PM, Marc Auslander marca...@gmail.com wrote: I'm still having no luck booting an mdadm 1.2 root. grub2 works - I get into the boot kernel and initram. But when it comes to mount the real kernel, I fall into initramfs shell with a message that the kernel can't be found. And it can't, because the raid root device hasn't been assembled. (No raid devices exist in /dev). I can assemble it in initramfs shell using mdadm, so all the stuff is there. So I really need to see any grub.cfg stanza that actually works - mostly to see what vmlinuz parameters are needed. It think that it's your initrd that needs some attention... Anyway, from a wheezy install: Thanks for the help. That's essentially what my grub stanza does. I've run update-initramfs. So I don't know what attention my initrd needs at this point. As I reported - all the code and mdadm.conf are in it. In the initrd shell, if I assemble my root raid disk and exit, the boot completes normally. This is squeeze - is it possible that the newer kernel has code to assemble early? Is there some other option or setting which causes it to assemble early? Also, are you using md version 1.2 raid. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87lipaf56h@aptiva.optonline.net
Re: grub-pc mdadm root (Resolved?)
Marc Auslander marca...@gmail.com writes: As I reported - all the code and mdadm.conf are in it. In the initrd shell, if I assemble my root raid disk and exit, the boot completes normally. I stumbled on the initramfs scripts, held my breath and added a local-top script which assembled my root array. Now I boot! So it works - but is this the right way to do it? In an case, thanks for the help. Knowing it could work kept me flailing. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87ehv2818d.fsf...@aptiva.optonline.net
Re: grub-pc mdadm root
On Sat, Jan 14, 2012 at 2:35 PM, Marc Auslander marca...@gmail.com wrote: Tom H tomh0...@gmail.com writes: On Fri, Jan 13, 2012 at 4:08 PM, Marc Auslander marca...@gmail.com wrote: I'm still having no luck booting an mdadm 1.2 root. grub2 works - I get into the boot kernel and initram. But when it comes to mount the real kernel, I fall into initramfs shell with a message that the kernel can't be found. And it can't, because the raid root device hasn't been assembled. (No raid devices exist in /dev). I can assemble it in initramfs shell using mdadm, so all the stuff is there. So I really need to see any grub.cfg stanza that actually works - mostly to see what vmlinuz parameters are needed. It think that it's your initrd that needs some attention... Anyway, from a wheezy install: Thanks for the help. That's essentially what my grub stanza does. I've run update-initramfs. So I don't know what attention my initrd needs at this point. This is squeeze - is it possible that the newer kernel has code to assemble early? I've got servers running squeeze with grub2 and mdadm. Is there some other option or setting which causes it to assemble early? Can you unpack your initrd and check whether you have an mdadm script in the scripts directory, an mdadm rule in the udev directory, and an /etc/mdadm/mdadm.conf? (I can't access a Debian box at the moment or I would've given you exact paths to the first two; sorry.) Also, are you using md version 1.2 raid. Yes; it's the d-i default for squeeze and wheezy. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=sw-mbaplc8q_9uezmrcepajrhjc7ycvru_6rftceua...@mail.gmail.com
Re: grub-pc mdadm root (Resolved?)
14/01/2012 21:42, Marc Auslander wrote: Marc Auslandermarca...@gmail.com writes: As I reported - all the code and mdadm.conf are in it. In the initrd shell, if I assemble my root raid disk and exit, the boot completes normally. I stumbled on the initramfs scripts, held my breath and added a local-top script which assembled my root array. Now I boot! So it works - but is this the right way to do it? In an case, thanks for the help. Knowing it could work kept me flailing. You mean like one of those: $ find /etc/initramfs-tools/ -name mdadm /etc/initramfs-tools/hooks/mdadm /etc/initramfs-tools/scripts/local-top/mdadm They are coming from /usr/share/initramfs-tools/(hooks|scripts)* It should have been picked up by update-initramfs. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f1201c9.1040...@googlemail.com
Re: grub-pc mdadm root (Resolved?)
Should have been picked up and installation went ahead without it. Debian reminds me of those Mars Rovers, they're not supposed to be able to work but they get into a hostile environment and surprise everybody by working any way.On Sat, 14 Jan 2012, tv.deb...@googlemail.com wrote: 14/01/2012 21:42, Marc Auslander wrote: Marc Auslandermarca...@gmail.com writes: As I reported - all the code and mdadm.conf are in it. In the initrd shell, if I assemble my root raid disk and exit, the boot completes normally. I stumbled on the initramfs scripts, held my breath and added a local-top script which assembled my root array. Now I boot! So it works - but is this the right way to do it? In an case, thanks for the help. Knowing it could work kept me flailing. You mean like one of those: $ find /etc/initramfs-tools/ -name mdadm /etc/initramfs-tools/hooks/mdadm /etc/initramfs-tools/scripts/local-top/mdadm They are coming from /usr/share/initramfs-tools/(hooks|scripts)* It should have been picked up by update-initramfs. Jude jdashiel-at-shellworld-dot-net http://www.shellworld.net/~jdashiel/nj.html -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.bsf.2.01.1201141739350.82...@freire1.furyyjbeyq.arg
Re: grub-pc mdadm root (really Resolved)
From /etc/defaults/mdadm # INITRDSTART: # list of arrays (or 'all') to start automatically when the initial ramdisk # loads. This list *must* include the array holding your root filesystem. Use # 'none' to prevent any array from being started from the initial ramdisk. INITRDSTART='none' Changing this to all (or just the root device, but I put in all) is the correct fix. How did I miss that for so long. Sigh. Thanks to all. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87y5t9dged.fsf...@aptiva.optonline.net
Re: grub-pc mdadm root
I'm still having no luck booting an mdadm 1.2 root. grub2 works - I get into the boot kernel and initram. But when it comes to mount the real kernel, I fall into initramfs shell with a message that the kernel can't be found. And it can't, because the raid root device hasn't been assembled. (No raid devices exist in /dev). I can assemble it in initramfs shell using mdadm, so all the stuff is there. So I really need to see any grub.cfg stanza that actually works - mostly to see what vmlinuz parameters are needed. Any help will be appreciated. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/877h0vwbrq@aptiva.optonline.net
Re: grub-pc mdadm root
10/01/2012 00:13, Marc Auslander wrote: Is it possible to boot a raid root file system. I'm having trouble finding up to date documentation. Some searchs talk about a separate /boot partition - I don't understand why that is needed or relevant. I'm assuming I'd make a mdadm v 1.2 raid 1 partition for root. Can someone either tell me if this is workable, or point me at documentation. (the current grub-pc info is silent about mdadm). google search lead to various bug reports. Hi, I can't point to any documentation right now, but I can confirm it just works since I have machines running this kind of config. I only use a separate /boot for RAID + LUKS, but raid1 alone can work without it. Having said that, I am not surprised about the bug reports, I have filled some myself. There was a problem when grub-pc 1.99 came out, but the mduuid patch solved that, it's now fixed thanks to: 2011-04-17 Vladimir Serbinenko phco...@gmail.com Identify RAID by its UUID rather than (guessed) name. * grub-core/disk/raid.c (ascii2hex): New function. (grub_raid_open): Accept mduuid/%s specification. * grub-core/kern/emu/getroot.c (get_mdadm_name): Revamped into ... (get_mdadm_uuid): ... this. (grub_util_get_grub_dev): Use mduuid/%s if UUID is available. Squeeze version (1.98) is OK, this problem only occurred in wheezy/testing and up. If you find a specific bug report that worries you, maybe you can point to it ? Anyway, it should work, have fun. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f0bfabc.1050...@googlemail.com
Re: grub-pc mdadm root
10/01/2012 00:13, Marc Auslander: Is it possible to boot a raid root file system. I'm having trouble finding up to date documentation. Some searchs talk about a separate /boot partition - I don't understand why that is needed or relevant. I'm assuming I'd make a mdadm v 1.2 raid 1 partition for root. [snip] I forgot that part, yes, 1.2, fill in mdadm.conf AND rebuild initrd afterward if your are setting up things manually (as opposed to a new install). No need to change file-system ID to fd, that was for 0.90 type metadata. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f0bfb78.4010...@googlemail.com
Re: grub-pc mdadm root
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10.01.2012 00:13, Marc Auslander wrote: Is it possible to boot a raid root file system. I'm having trouble finding up to date documentation. Some searchs talk about a separate /boot partition - I don't understand why that is needed or relevant. I'm assuming I'd make a mdadm v 1.2 raid 1 partition for root. Can someone either tell me if this is workable, or point me at documentation. (the current grub-pc info is silent about mdadm). google search lead to various bug reports. Hi, - From my experience it works with grub2 out of the box. Iirc, you do not need to do anything special, just setup the raid in the installer, install the system and let the installer setup grub2. The stuff about /boot is for users with grub1 or other bootloaders not capable to boot directly from mdadm-volumes (or lvm or whatever). Another situation where you have to think about /boot is if your going to encrypt your root using cryptsetup. Afaik you even should even be able to use LVM on raid without much trouble, but i never actually tried to do that. Greetings HP -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8MJZ4ACgkQjLvx8ViUjYL91wCeOFbj9F/CKwl5C4KW2jjWITKZ 39IAnRhrlv5CMjw70oN1QvFNCH3UdDCD =V5lH -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f0c25bf.3030...@spahan.ch
Re: grub-pc mdadm root
Some searchs talk about a separate /boot partition - I don't understand why that is needed or relevant. I'm assuming I'd make a mdadm v 1.2 raid 1 partition for root. Your /boot must be in a regular partition or in a raid1 volume. It may either have it's own filesystem (I typically use one that's 512mb in size) or in the root filesystem. If it's in the root filesystem, then that means that root should be in a regular partition or in a raid1 volume. I typically put /boot in raid1 then create a raid5/6 volume, then I create lvm volumes that use the raid5/6 volumes.
Re: grub-pc mdadm root
also sprach Justin Jereza justinjer...@gmail.com [2012.01.10.1523 +0100]: Your /boot must be in a regular partition or in a raid1 volume. It may either have it's own filesystem (I typically use one that's 512mb in size) or in the root filesystem. If it's in the root filesystem, then that means that root should be in a regular partition or in a raid1 volume. With grub2, your /boot can be an LV on a RAID6 if you want it to be. The only thing that does not work is /boot on dmcrypt. Having /boot on a separate RAID1, however, might be easier for recovery, especially if you are not so familiar yet. Later, however, it doesn't matter, i.e. Debian installer rescue mode or grml can easily give you access to a system, and Super Grub Disk can boot such a system too, should you ever need it. -- .''`. martin f. krafft madduck@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems computer science is no more about computers than astronomy is about telescopes. -- edsgar w. dijkstra digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Re: grub-pc mdadm root
With grub2, your /boot can be an LV on a RAID6 if you want it to be. The only thing that does not work is /boot on dmcrypt. I forgot about grub2. It's only recently that I've built it and seen how big of a monster it is. All the modules it comes with is quite useful though. Having /boot on a separate RAID1, however, might be easier for recovery, That's true.
