On Wed, Feb 23, 2011 at 8:11 AM, Panayiotis Karabassis wrote:
> On 02/23/2011 03:10 PM, Tom H wrote:
>> On Wed, Feb 23, 2011 at 8:01 AM, Panayiotis Karabassis
>> wrote:
>>>
>>> BTW, could someone explain the difference between
>>> GRUB_CMDLINE_LINUX_DEFAULT
>>> and GRUB_CMDLINE_LINUX in /etc/defa
On 02/23/2011 03:10 PM, Tom H wrote:
On Wed, Feb 23, 2011 at 8:01 AM, Panayiotis Karabassis wrote:
BTW, could someone explain the difference between GRUB_CMDLINE_LINUX_DEFAULT
and GRUB_CMDLINE_LINUX in /etc/default/grub?
For every vmlinuz... in /boot, GRUB_CMDLINE_LINUX_DEFAULT appli
On Wed, Feb 23, 2011 at 8:01 AM, Panayiotis Karabassis wrote:
>
> BTW, could someone explain the difference between GRUB_CMDLINE_LINUX_DEFAULT
> and GRUB_CMDLINE_LINUX in /etc/default/grub?
For every vmlinuz... in /boot, GRUB_CMDLINE_LINUX_DEFAULT applies to
the runlevel 2 entry and GRUB_CMDLINE_
On 02/23/2011 02:22 PM, martin f krafft wrote:
also sprach Panayiotis Karabassis [2011.02.23.1029 +0100]:
I had solved this in lenny by using the following
/usr/share/initramfs-tools/scripts/local-top/mdadm script:
Set rootdelay=30 on the kernel command line.
Your solution seem
also sprach Panayiotis Karabassis [2011.02.23.1029 +0100]:
> I had solved this in lenny by using the following
> /usr/share/initramfs-tools/scripts/local-top/mdadm script:
Set rootdelay=30 on the kernel command line.
> My solution is broken after the upgrade to squeeze and the problem
> has regr
Hi!
To simplify things a little: I have an external USB disk (/dev/sdc1)
that is part of an MD array (/dev/md0).
During boot, I experienced the following problem: /dev/md0 was assembled
with only 1 drive out of 2 (the internal one). This was due to /dev/sdc1
taking some time to be detected,
6 matches
Mail list logo
