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
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
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
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
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
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
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
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
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'
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
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
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
-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
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
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
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
16 matches
Mail list logo
