On 04/04/2008, John <[EMAIL PROTECTED]> wrote:
>
> That would be ""touch ./autolable"".
touch /.autorelabel followed by a reboot and a long wait (depending upon the
size of your filesystem and the spped of your drives).
Alan.
___
CentOS mailing list
Ce
On Fri, 2008-04-04 at 00:54 -0500, Les Mikesell wrote:
> Sam Beam wrote:
> > On Wednesday 02 April 2008 01:07, Les Mikesell wrote:
> >> First cut - in your recovery shell, comment out /home from /etc/fstab
> >> and see if you can come up without it (log in as root, of course). That
> >> will at le
Sam Beam wrote:
On Wednesday 02 April 2008 01:07, Les Mikesell wrote:
First cut - in your recovery shell, comment out /home from /etc/fstab
and see if you can come up without it (log in as root, of course). That
will at least give you a fairly normal environment to try to figure out
why the md1
On Wednesday 02 April 2008 01:07, Les Mikesell wrote:
> First cut - in your recovery shell, comment out /home from /etc/fstab
> and see if you can come up without it (log in as root, of course). That
> will at least give you a fairly normal environment to try to figure out
> why the md1 device is
Sam Beam wrote:
I hope...
If you are booting a kernel that can't find your root partition, the
initrd might be the problem. There are several other things that also
have to be right. You should be able to boot your install cd/dvd with
"linux rescue" at the boot prompt to fix any of them, so
On Tuesday 01 April 2008 15:03, Les Mikesell wrote:
> > maybe that is why the system won't boot anymore after I synced the root
> > partition? ;)
> >
> > I hope...
>
> If you are booting a kernel that can't find your root partition, the
> initrd might be the problem. There are several other thing
Sam Beam wrote on Tue, 1 Apr 2008 14:43:51 -0400:
> So you don't run it at all
> after creating the md arrays?
I don't do any changes to initrd. I create the mirrored raid and I install
grub on the second disk, so that it works for booting on both disks.
The /boot partition needs to be on its o
Sam Beam wrote:
On Tuesday 01 April 2008 05:31, Kai Schaetzl wrote:
Sam Beam wrote on Tue, 1 Apr 2008 01:45:28 -0400:
OK sorry to hammer the list but one more question - having almost got the
drives mirrored and happy - since I have created a custom initrd that has
the raid1 drivers in it, do I
On Tuesday 01 April 2008 05:31, Kai Schaetzl wrote:
> Sam Beam wrote on Tue, 1 Apr 2008 01:45:28 -0400:
> > OK sorry to hammer the list but one more question - having almost got the
> > drives mirrored and happy - since I have created a custom initrd that has
> > the raid1 drivers in it, do I now h
Sam Beam wrote on Tue, 1 Apr 2008 01:45:28 -0400:
> OK sorry to hammer the list but one more question - having almost got the
> drives mirrored and happy - since I have created a custom initrd that has the
> raid1 drivers in it, do I now have to tell yum to ignore kernel updates? Will
> the sto
OK sorry to hammer the list but one more question - having almost got the
drives mirrored and happy - since I have created a custom initrd that has the
raid1 drivers in it, do I now have to tell yum to ignore kernel updates? Will
the stock kernel render me unbootable?
Actually I am not 100% sur
11 matches
Mail list logo
