This commit is contained in:
gferg 2002-09-04 13:34:30 +00:00
parent ff7b23bd27
commit fd2331c926
2 changed files with 53 additions and 3 deletions

View File

@ -1564,7 +1564,7 @@ install, configure, and use IPv6 applications on Linux machines.
Linux-Promise-RAID1-HOWTO</ULink>,
<CiteTitle>Linux Migration to Promise RAID Card HOWTO</CiteTitle>
</Para><Para>
<CiteTitle>Updated: August 2002</CiteTitle>.
<CiteTitle>Updated: September 2002</CiteTitle>.
Outlines the steps of how to migrate an existing (Red Hat) Linux
install onto a Promise TX2 Card for the purposes of RAID-1 Mirroring.
</Para>

View File

@ -12,7 +12,7 @@
<firstname>Benjamin</firstname>
<surname>Simkin</surname>
<affiliation>
<address><email>ben(at)empathy.com.au</email></address>
<address><email>ben (at) empathy.com.au</email></address>
</affiliation>
</author>
@ -22,6 +22,12 @@
<!-- Most recent revision goes at the top; list in descending order -->
<revhistory>
<revision>
<revnumber>1.3</revnumber>
<date>2002-09-04</date>
<authorinitials>bs</authorinitials>
<revremark>Added Troubleshooting section</revremark>
</revision>
<revision>
<revnumber>1.1</revnumber>
<date>2002-08-05</date>
<authorinitials>bs</authorinitials>
@ -323,9 +329,12 @@ After that is done, follow the instructions of the next section.
<para>
Choose "LinuxFromRaid" Option at LILO.
It should boot up without much of an error. It will, however
It should boot up without any errors. It will, however
complain about swap. Ignore that, as we will fix it in a moment.
You may receive an error about incorrect module version, or a kernel mismatch. Please see the
"troubleshooting" section about this.
After we have booted up on the new system, we must edit a few files:
</para>
@ -408,9 +417,50 @@ Drive -
3 : IC Secondary/Master 41174MB BASE(0xbc00) BM(0xc408) IRQ(11) UDMA5
</screen>
That is all.
</para>
</sect1>
<sect1><title>Troubleshooting</title>
<para>
You may get a kernel mismatch error message. This means that you don't have the correct version module for use with your kernel.
If you cannot get the correct module version for use with your kernel, choose the closest one, and follow these steps;
This may not work in some instances, so remember to have your boot disk handy.
<screen>
# cd /boot
# cat initrd-2.4.2-2.img |gunzip > /tmp/myimage
# mkdir /mnt/tmp
# mount /tmp/myimage /mnt/tmp -t ext2 -o loop=/dev/loop3
# cd /mnt/tmp
# vi linuxrc
</screen>
Now modify 'insmod ft' to 'insmod -f ft'.
This will force the sytem to load the module.
Save the file, and exit from vi (or emacs :))
<screen>
# umount /mnt/tmp
# gzip /tmp/myimage
# cp myimage.gz /boot/initrd-2.4.2-2.img
</screen>
You will obviously have to use the correct filename for your initrd file.
I am using 2.4.2-2 as example.
Now, reboot, and all should be well.
</para>
</sect1>
</article>