Account Links: Cart | Your Account | Logout

Skip to content

Red Hat Knowledgebase

Red Hat Knowledgebase Search:

Updated Within the Last:

New Solutions within the last day New Solutions within the last week New Solutions within the last month

Browse by topics:


Click to View a Topic
Red Hat Enterprise Linux > AS/ES/WS v. 3 > Issue <<  112 of 593 >>

Solution Tools:


Email a Solution Postcard Printer version Submit a comment on this answer Update notifications Request an answer Back

Article Reference

Article ID: 3514
Last update: 02-02-05
Issue:
How do I modify my modules.conf file so my external fiber channel disks stop showing up as /dev/sda and my internal drives as /dev/sdb?
Resolution:
Release Found: Red Hat Enterprise Linux 3, Red Hat Enterprise Linux 2.1

Symptom:
A QLogic fiber channel adapter was added to the server and connected to an external storage array. When the system was booted up, the internal disks on the server originally desginated as /dev/sda, were now designated /dev/sdb while the external disks on the fiber storage were now /dev/sda.

Solution: While examining the /etc/modules.conf file, it was noted that the module for the QLogic adapter was listed before the module for SCSI adapter connected to the server's internal disks:

 
#cat /etc/modules.conf

alias eth0e1000 
alias eth1 e1000 
alias scsi_hostadapter qla2300 
alias scsi_hostadapter1 mptbase 
alias scsi_hostadapter2 mptscsih 
alias usb-controller usb-ohci 
 


Since the QLogic module was being loaded before the internal SCSI adapter's modules, the operating system was picking up the disks attached to the fiber adapter as /dev/sda.

To prevent this from happening, the /etc/modules.conf file must be modified so the QLogic module loads after the internal SCSI modules. Example:

 
alias eth0 e1000 
alias eth1 e1000  
alias scsi_hostadapter mptbase 
alias scsi_hostadapter1 mptscsih 
alias scsi_hostadapter2 qla2300
alias usb-controller usb-ohci 
     


After making this modification and saving the file, you need to rebuild the initrd image.

WARNING: Make Sure you build this against the correct kernel (the kernel you want to run). It is recommend that if you are going to replace your existing initrd image with the new one, that you make a back-up copy first. The -f option will force or overwrite the existing initrd image file.
cp /boot/initrd-2.4.9-e.27smp.img /boot/initrd-2.4.9-e.27smp.img.bak
mkinitrd -f -v /boot/initrd-2.4.9-e.27smp.img 2.4.9-e.27smp
In order for the changes to take effect you will need to reboot your system to the kernel you rebuilt the initrd image for.


How well did this entry answer your question?


good wrong incomplete out of date
Red Hat Enterprise Linux > AS/ES/WS v. 3 > Issue <<   112  of  593  >>