All sorted.
The problem was that the initrd image from the SGI XFS boot CD was in ext2
format so it was trying to mount the root filesystem in ext2/3 aswell.
If the grub parameter was added to specify the boot file system as XFS it
tried loading the initrd as XFS which is where the superblock errors came
from.
Can you specify a root file system type and a different initrd file system
type?
We cured it by recompiling the kernel with all the drivers we needed at boot
time compiled in so that we didn't need to use initrd and therefore could
specify the root fs as XFS without problems.
> -----Original Message-----
> From: Seth Mos [mailto:knuffie@xxxxxxxxx]
> Sent: Wednesday, April 23, 2003 14:10
> To: Gareth Blades; linux-xfs@xxxxxxxxxxx
> Cc: Kai Leibrandt
> Subject: RE: Redhat 9 - grub wont boot with XFS root fs after migration
>
>
> At 14:04 23-4-2003 +0100, Gareth Blades wrote:
> >Yes I did install grub in (hd0) which is the MBR. I did try installing it
> >into (hd0,0) later but I have since run xfs_repair so if there were any
> >problems it should have fixed it.
>
> Did GRUB install the bootloader in both disks in the raid 1 set?
>
> I still use lilo with my raid 1 configs and are unfamiliar with GRUB. It
> doesn't sound like you are doing anything wrong.
>
> The difference is that with LILO you specify that boot=/dev/md0
> and it will
> then install the bootloader in the mbr of both disks.
>
> If the bootloader ends up in the wrong place you will notice this as a
> corrupt superblock on the XFS filesystem since they both want to go into
> block 0 of the partition/drive.
>
> Cheers
> --
> Seth
> It might just be your lucky day, if you only knew.
>
>
>
|