Dear Wizards, We are running CentOS 6.2 on a cluster with HP SL360s G7 nodes. I have a question regarding assignment of device names during nermal boot versus installation.
The nodes run HP's iLO3 (integrated Lights Out), so we can (optionally) mount a virtual CD drive on a node. This drive is detected by the OS (as "Attached SCSI removable disk"). My problem is that on normal boot (standard CentOS kernel and initrd=initramfs), the (virtual) CD is given /dev/sda, and the internal HDD is /dev/sdb. This is reflected in fstab and grub.conf. The dmesg shows the following: [root@dn003 ~]# dmesg | grep 0:0:0 scsi 0:0:0:0: Direct-Access KVM vmDisk 0.01 PQ: 0 ANSI: 0 scsi 1:0:0:0: Direct-Access ATA GB0160EAPRR HPG2 PQ: 0 ANSI: 5 sd 1:0:0:0: [sdb] 312581808 512-byte logical blocks: (160 GB/149 GiB) sd 1:0:0:0: [sdb] Write Protect is off sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA sd 0:0:0:0: [sda] Attached SCSI removable disk sd 1:0:0:0: [sdb] Attached SCSI disk sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 1:0:0:0: Attached scsi generic sg1 type 0 So CD = "sd 0:0:0:0" = sg0 = sda and HDD = "sd 1:0:0:0" = sg1 = sdb However, when I install a node (with UYOK and modules from the node) I get something slightly different (the following is written by hand from a console, so there _cloud_ be typos): /scripts/pre-install # dmesg | grep 0:0:0 scsi 1:0:0:0: Direct-Access ATA GB0160EAPRR HPG2 PQ: 0 ANSI: 5 sd 1:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB) sd 1:0:0:0: [sda] Write Protect is off sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 1:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA sd 1:0:0:0: [sda] Attached SCSI disk sd 1:0:0:0: Attached scsi generic sg0 type 0 scsi 0:0:0:0: Direct-Access KVM vmDisk 0.01 PQ: 0 ANSI: 0 sd 0:0:0:0: Attached scsi generic sg1 type 0 sd 0:0:0:0: [sdb] Attached SCSI removable disk Here HDD is again 1:0:0:0, but it is now given sg0 and sda, while the CD ends up as sdb. The result is that the install script, which wants to format /dev/sdb fails: there is no media in the (virtual) CD drive. I find it curious that the line "scsi 0:0:0:0: Direct-Access ..." is very late in the installation case. That could mean that the HDD is already given device name before the CD is detected? Is there any way to fix the device naming, such that scsi 1:0:0:0 is sdb also when I install? All help/hints is much appreciated. Thanks. Bjarne ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
