On Fri, 2010-01-22 at 09:24 +0300, Lev Shamardin wrote:
Some later thoughts go below.
On 01/21/2010 01:50 AM, Phil Schaffner wrote:
1. The user should be instructed to start rescue mode with networking in
order to be able to retrieve the patch for mkinitrd.
The mkinitrd instructions
On Fri, 2010-01-22 at 08:57 +0300, Lev Shamardin wrote:
On 01/21/2010 01:50 AM, Phil Schaffner wrote:
4. It is not necessary to change LABEL=... to /dev/md_d0... in
/etc/fstab and /boot/grub/grub.conf.
Have you tested this? I'm not quite sure, but it seems to me that this did not
work at
Phil Schaffner ha scritto:
2. The command to create /etc/mdadm.conf will result in an extra line
spares=1 while the array is still syncing. Adding | head -1 to
the command to create it fixes the problem.
May I suggest to add | grep -v spares or | grep ARRAY instead? If the
command is
Lorenzo Quatrini wrote on 01/21/2010 06:26 AM:
Phil Schaffner ha scritto:
2. The command to create /etc/mdadm.conf will result in an extra line
spares=1 while the array is still syncing. Adding | head -1 to
the command to create it fixes the problem.
May I suggest to add | grep -v
Some later thoughts go below.
On 01/21/2010 01:50 AM, Phil Schaffner wrote:
1. The user should be instructed to start rescue mode with networking in
order to be able to retrieve the patch for mkinitrd.
The mkinitrd instructions should be moved to the beginning of the guide.
Networking
