On Sun, 5 Feb 2006 09:07:29 +1100 Lewis Shobbrook wrote:
Basically it just states waiting X seconds
Please post in public rather than to me privately.
If this debate is related to a bug already filed against the Debian
package of yaird then cc that bugreport: bug number@bugs.debian.org -
and
On Mon, 24 Apr 2006 17:13:42 +0200 Jonas Smedegaard wrote:
On Sun, 5 Feb 2006 09:07:29 +1100 Lewis Shobbrook wrote:
Basically it just states waiting X seconds
Please post in public rather than to me privately.
Uh, how embarrassing: I thought I was looking in my inbox, but instead
was
On Sun, 5 Feb 2006, Lewis Shobbrook wrote:
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This thread is all very relevant.
But please cc [EMAIL PROTECTED] rather than me
privately.
Regards,
- Jonas
- --
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
- Enden er nær:
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 to the
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
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 to the root password
prompt?
is it trying to fsck
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
i've never looked at yaird in detail -- but you can probably use
initramfs-tools instead of yaird... the deb 2.6.14 and later kernels will
use whichever one of those is installed. i know that initramfs-tools uses
mdrun to start the root partition based on its UUID -- and so it should
work
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 to boot
my system properly... whereas yaird almost got everything right.
the main
On Friday 03 February 2006 1:13 pm, you wrote:
Thanks Dean,
I'll try this out...
i've never looked at yaird in detail -- but you can probably use
initramfs-tools instead of yaird... the deb 2.6.14 and later kernels will
use whichever one of those is installed. i know that initramfs-tools uses
11 matches
Mail list logo
