Re: [gentoo-user] Raid1 (continued) mdadm
On Friday 15 April 2011 20:46:47 Mark Shields wrote: On Fri, Apr 15, 2011 at 2:47 PM, Florian Philipp li...@binarywings.netwrote: Am 15.04.2011 16:56, schrieb James: Hello, New day, and a fresh approach to fixing the raid one install. Following this doc (no lvm no intramfs): http://www.gentoo.org/doc/en/gentoo-x86+raid+lvm2-quickinstall.xml The disk were all resync'd (end of last thread). Since this is a simple 3 partition 2 disk mirror (identical drives formatting) and I want to mirror all three (/boot, /, swap) I used these commands: mdadm --create /dev/md127 --level=1 --raid-devices=2 --metadata=0.90 /dev/sda1 /dev/sdb1 mdadm --create /dev/md125 --level=1 --raid-devices=2 --metadata=0.90 /dev/sda3 /dev/sdb3 mdadm --create /dev/md126 --level=1 --raid-devices=2 --metadata=0.90 /dev/sda2 /dev/sdb2 If my theory holds, it should be sufficient if /boot has metadata=0.90 because that's what grub has to access. So do I need to issue these commands? If so, are they correct? A little unclear on mknod livecd ~ # mknod /dev/md127 b 9 1 livecd ~ # mknod /dev/md125 b 9 3 or livecd ~ # mknod /dev/md127 b 9 127 livecd ~ # mknod /dev/md125 b 9 125 livecd ~ # mknod /dev/md126 b 9 126 ??? I doubt you need mknod. Udev should handle this. Maybe you should try it without and see whether udev really creates them. If so, you might still add them to the static /dev. Use something like this: mount --bind / /mnt mknod /mnt/dev/md127 b 9 1 This circumvents udev and writes directly to root. Of course, you have to replace / with whatever is the mount point of your root partition when you boot from a live-CD. Regards, Florian Philipp You need mknod during the creation process when booted from a minimal install disc; when you finish building the system and boot it the first time, udev handles it from there. I didn't need mknod when I did this last time. udev picked it up correctly from the start. And yes, you're right; only boot needs the --metadata=0.90. -- Joost
[gentoo-user] Raid1 (continued) mdadm
Hello, New day, and a fresh approach to fixing the raid one install. Following this doc (no lvm no intramfs): http://www.gentoo.org/doc/en/gentoo-x86+raid+lvm2-quickinstall.xml The disk were all resync'd (end of last thread). Since this is a simple 3 partition 2 disk mirror (identical drives formatting) and I want to mirror all three (/boot, /, swap) I used these commands: mdadm --create /dev/md127 --level=1 --raid-devices=2 --metadata=0.90 /dev/sda1 /dev/sdb1 mdadm --create /dev/md125 --level=1 --raid-devices=2 --metadata=0.90 /dev/sda3 /dev/sdb3 mdadm --create /dev/md126 --level=1 --raid-devices=2 --metadata=0.90 /dev/sda2 /dev/sdb2 So do I need to issue these commands? If so, are they correct? A little unclear on mknod livecd ~ # mknod /dev/md127 b 9 1 livecd ~ # mknod /dev/md125 b 9 3 or livecd ~ # mknod /dev/md127 b 9 127 livecd ~ # mknod /dev/md125 b 9 125 livecd ~ # mknod /dev/md126 b 9 126 ???
Re: [gentoo-user] Raid1 (continued) mdadm
Am 15.04.2011 16:56, schrieb James: Hello, New day, and a fresh approach to fixing the raid one install. Following this doc (no lvm no intramfs): http://www.gentoo.org/doc/en/gentoo-x86+raid+lvm2-quickinstall.xml The disk were all resync'd (end of last thread). Since this is a simple 3 partition 2 disk mirror (identical drives formatting) and I want to mirror all three (/boot, /, swap) I used these commands: mdadm --create /dev/md127 --level=1 --raid-devices=2 --metadata=0.90 /dev/sda1 /dev/sdb1 mdadm --create /dev/md125 --level=1 --raid-devices=2 --metadata=0.90 /dev/sda3 /dev/sdb3 mdadm --create /dev/md126 --level=1 --raid-devices=2 --metadata=0.90 /dev/sda2 /dev/sdb2 If my theory holds, it should be sufficient if /boot has metadata=0.90 because that's what grub has to access. So do I need to issue these commands? If so, are they correct? A little unclear on mknod livecd ~ # mknod /dev/md127 b 9 1 livecd ~ # mknod /dev/md125 b 9 3 or livecd ~ # mknod /dev/md127 b 9 127 livecd ~ # mknod /dev/md125 b 9 125 livecd ~ # mknod /dev/md126 b 9 126 ??? I doubt you need mknod. Udev should handle this. Maybe you should try it without and see whether udev really creates them. If so, you might still add them to the static /dev. Use something like this: mount --bind / /mnt mknod /mnt/dev/md127 b 9 1 This circumvents udev and writes directly to root. Of course, you have to replace / with whatever is the mount point of your root partition when you boot from a live-CD. Regards, Florian Philipp signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] Raid1 (continued) mdadm
On Fri, Apr 15, 2011 at 2:47 PM, Florian Philipp li...@binarywings.netwrote: Am 15.04.2011 16:56, schrieb James: Hello, New day, and a fresh approach to fixing the raid one install. Following this doc (no lvm no intramfs): http://www.gentoo.org/doc/en/gentoo-x86+raid+lvm2-quickinstall.xml The disk were all resync'd (end of last thread). Since this is a simple 3 partition 2 disk mirror (identical drives formatting) and I want to mirror all three (/boot, /, swap) I used these commands: mdadm --create /dev/md127 --level=1 --raid-devices=2 --metadata=0.90 /dev/sda1 /dev/sdb1 mdadm --create /dev/md125 --level=1 --raid-devices=2 --metadata=0.90 /dev/sda3 /dev/sdb3 mdadm --create /dev/md126 --level=1 --raid-devices=2 --metadata=0.90 /dev/sda2 /dev/sdb2 If my theory holds, it should be sufficient if /boot has metadata=0.90 because that's what grub has to access. So do I need to issue these commands? If so, are they correct? A little unclear on mknod livecd ~ # mknod /dev/md127 b 9 1 livecd ~ # mknod /dev/md125 b 9 3 or livecd ~ # mknod /dev/md127 b 9 127 livecd ~ # mknod /dev/md125 b 9 125 livecd ~ # mknod /dev/md126 b 9 126 ??? I doubt you need mknod. Udev should handle this. Maybe you should try it without and see whether udev really creates them. If so, you might still add them to the static /dev. Use something like this: mount --bind / /mnt mknod /mnt/dev/md127 b 9 1 This circumvents udev and writes directly to root. Of course, you have to replace / with whatever is the mount point of your root partition when you boot from a live-CD. Regards, Florian Philipp You need mknod during the creation process when booted from a minimal install disc; when you finish building the system and boot it the first time, udev handles it from there. And yes, you're right; only boot needs the --metadata=0.90.
