xfs
[Top] [All Lists]

Re: Problem with SGI XFS for Red Hat 7.0 Installer on SGI 1200

To: Ken Murchison <ken@xxxxxxxxxx>
Subject: Re: Problem with SGI XFS for Red Hat 7.0 Installer on SGI 1200
From: Eric Sandeen <sandeen@xxxxxxxx>
Date: 20 Feb 2001 14:59:41 -0600
Cc: Tom Duffy <tduffy@xxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <3A92CE3E.95D70C32@xxxxxxxxxx>
References: <Pine.LNX.4.30.0102201158210.25923-100000@xxxxxxxxxxxxxxxxxx> <3A92CE3E.95D70C32@xxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
On 20 Feb 2001 15:06:22 -0500, Ken Murchison wrote:

> Tom Duffy wrote:

> > 
> > this is most likely a problem with the initrd.  probably did not complete
> > or that it could not find the appropriate module to use for scsi
> > controller.


I agree that the initrd is the likely culprit...

Have you tried the recovery method on the installer caveats page?
(http://216.32.174.192/projects/xfs/installcavs.html)

==============
Some systems with particular ide chip sets are known to have problems at
install time that prevent the initial ram disk from being generated. The
fix for this problem is to reboot the system into rescue mode from the
install CD by typing "linux rescue" at the boot prompt, and then
executing the following commands. (If your / and /boot are on the same
partition, simply ignore the lines pertaining to /boot.)


cd /tmp
mknod hda<partition # of root fs> b 3 <partition number>
mknod hda<partition # of /boot fs> b 3 <partition number>
mount -t xfs hda<part#> /mnt/A
mount -t xfs hda<part#> /mnt/A/boot
chroot /mnt/A
/sbin/mkinitrd /boot/initrd-2.4.0-SGI_XFS_PR.img  2.4.0-SGI_XFS_PR
vi /etc/lilo.conf
add to the correct kernel entry:
initrd=/boot/initrd-2.4.0-SGI_XFS_PR.img
/sbin/lilo -v
exit (out of chrooted shell)
umount /mnt/A/boot
umount /mnt/A

Reboot the system.



<Prev in Thread] Current Thread [Next in Thread>