So what is the fault there? Why does one need to unmount and remount, and more
important, when does one have to do so?
There have been reports with people upgrading their rpm (xfs enabled) kernels
and crashing the GRUB second load stage. At the first sight this looks like
the same bug the installer sees (these people have obviously installed the new
kernel and rebooted a short while after, like the installer does).
Maybe xfs root (or boot) filesystems don't write dirty buffers back, and
(as a workaround) should always be remounted before shutting them down?
On Tue, Apr 15, 2003 at 02:38:41PM +0200, Mogens Kjaer wrote:
> Mogens Kjaer wrote:
> ...
> >Hm, there must be a better way of doing this (tm). Remounting
> >the installation partition?
> ...
>
> Success! It turned out to be easier than I thought:
>
> I couldn't umount /mnt/sysimage, it was busy because
> /mnt/sysimage/proc and /mnt/sysimage/dev/pts were
> also mounted.
>
> To umount everything, and mount it again,
> one has to add these two lines to
> /usr/lib/booty/bootloaderInfo.py in stage2.img,
> near line 806, (inbetween the calls
> of /sbin/grub-install and /sbin/grub):
>
> fsset.umountFilesystems(instRoot)
> fsset.mountFilesystems(instRoot)
>
> - maybe the upgradeGrub function needs to
> be changed as well...
>
> It works both if the /boot directory
> is a part of the root directory, and if
> /boot is on an XFS partition of its own.
>
> Mogens
>
--
Axel.Thimm@xxxxxxxxxxxxxxxxxxx
|