• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 216
  • Last Modified:

SCSI Drives Taking Red Hat OS's boot device

I have asked this question previously, but unfortunately have not gotten a solution.  I am still having problems and need help.  Thanks for any help you can provide!!

http://www.experts-exchange.com/Operating_Systems/Linux/Q_21833674.html


When I connect a StorEdge 3320 array of disks (in a JBOD configuration - no RAID, the OS just sees them as disks) to a RHEL 4.3 system, linux will assign /dev devices to it.  The only problem is that it assigns the /dev/sda1 device (the root partition) to a disk in the array, instead of the internal disk.

I found that Sun knows about this issue and says the following:
1.During boot up, press 'e' at the grub kernel selection screen.
2.Go to the line that points to the kernel and press 'e' again to edit the line:
kernel /vmlinux-2.4.9-3.24 ro root=/dev/sda3
3.If one drive was added to the system, change /dev/sda3 to /dev/sdb3. For two new drives, change it to /dev/sdc3.

I'm sure this would work, except that I am using Linux LVM for all partitions, besides /boot of course.  Any ideas?  Is there a way to statically map LVM partitions?  Thanks.
0
barthalamu
Asked:
barthalamu
1 Solution
 
cjl7freelance for hireCommented:
Hi, (again)

LVM should work anyway, since it isn't using physical disks but scans them for volume groups...
(from initrd.img)
echo Scanning logical volumes
lvm vgscan --ignorelockingfailure
echo Activating logical volumes
lvm vgchange -ay --ignorelockingfailure vg00


Is your kernel line really configured like that? In RHEL 4 it should use LVM for it's root device and should say something like

kernel /vmlinuz-2.6.16.11 ro root=/dev/vg00/rootvol rhgb quiet

Could you post your /etc/grub.conf?


You say you are still having problems, what is the problem?
Is your box not booting when you connect the fiber-disks?

//jonas
0
 
barthalamuAuthor Commented:
Sorry for the late reply.

I really never found the exact problem.  I found that a combination of moving the controller card and reboots seemed to fix it.  Thanks for your help.  I appreciate it.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now