Hi All,
Wondering if anyone can comment on an easy way to get grub to update all
components in a raid1 array. I have a raid1 /boot with a raid10 /root and
have previously used lilo with the raid-extra-boot option to install to boot
sectors of all component devices. With grub it appears that
Hi All,
Wondering if anyone can comment on an easy way to get grub to update all
components in a raid1 array. I have a raid1 /boot with a raid10 /root and
have previously used lilo with the raid-extra-boot option to install to boot
sectors of all component devices. With grub it appears that
On Saturday 04 February 2006 11:22 am, you wrote:
On Sat, 4 Feb 2006, Lewis Shobbrook wrote:
Is there any way to avoid this requirement for input, so that the system
skips the missing drive as the raid/initrd system did previously?
what boot errors are you getting before it drops you
On Friday 03 February 2006 2:02 pm, you wrote:
Hi Dean,
Thanks for the suggestions.
On Thu, 2 Feb 2006, dean gaudet wrote:
i've never looked at yaird in detail -- but you can probably use
initramfs-tools instead of yaird...
i take it all back... i just tried initramfs-tools and it failed
Hi All,
I'm trying to get my head around the way that the new debian initrd system
yaird and mdadm.conf interact.
While running raid5 with yaird, I've discovered that if I replace or remove a
healthy drive, without manually using mdadm --set-faulty, the system will not
reboot. I get startup
mdrun to start the root partition based on its UUID -- and so it should
work fine (to get root mounted) even without dorking around with
mdadm.conf.
but if you want to stick with yaird:
On Fri, 3 Feb 2006, Lewis Shobbrook wrote:
My mdadm.conf (I never needed to use at all previous
Hi All,
I have a problem attempting to boot a raid 1 system from lilo. I have
succeeded at this many times in the past, but am completely stumped as to
what the issue is in this instance. I have the boot and root partitions
seperate on /dev/md0 /dev/md1 respectively, both raid1.
The mdadm
On Thursday 25 August 2005 7:14 pm, you wrote:
Fdisk it and set partitions to Raid Autodetect (0xfd) possibly?
Tyler.
Nope already set fd
Lewis Shobbrook wrote:
Hi All,
I have a problem attempting to boot a raid 1 system from lilo. I have
succeeded at this many times in the past
device is mounted then all required modules are present.
H
Rui Santos
Lewis Shobbrook wrote:
Hi All,
I have a problem attempting to boot a raid 1 system from lilo. I have
succeeded at this many times in the past, but am completely stumped as to
what the issue is in this instance. I
/md1
mounts. Often these type of problems are associated with the initrd
modules, and result in kernel panic earlier in the boot process. I'd
expect that if one raid1 device is mounted then all required modules are
present.
H
Rui Santos
Lewis Shobbrook wrote:
Hi All,
I
10 matches
Mail list logo
