[Bug 390804] New: Problem with installation of bootloader on a IBM QS21 Cell blade
https://bugzilla.novell.com/show_bug.cgi?id=390804 Summary: Problem with installation of bootloader on a IBM QS21 Cell blade Product: openSUSE 11.0 Version: Beta 1 Platform: PowerPC-64 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Booting AssignedTo: jsrain@novell.com ReportedBy: dominik.klein@de.ibm.com QAContact: jsrain@novell.com Found By: --- I tried to install openSUSE 11.0 Beta 1 on an Cell-based IBM QS21 blade with SAS-attached storage. Installation via Serial-over-LAN and VNC was painless. The installation of the bootloader however failed. To finish the insallation without errors, I chose not to install any bootloader. Then I booted from the DVD and chrooted into the installation to install the bootloader manually by creating a proper /etc/lilo.conf and running 'lilo'. That didn't work either: # lilo running on chrp ERROR: in config file, boot = /dev/sda1 is not a primary partition This is the /etc/lilo.conf I used: boot=/dev/sda1 timeout=100 default=linux image=/boot/vmlinux-2.6.25-rc9-17-default initrd=/boot/initrd-2.6.25-rc9-17-default.img label=linux append="console=ttyS0,19200 root=/dev/sda5 quiet sysrq=1" I guess this is related to the show_of_path.sh script. This is what I get when I call 'show_of_path.sh /dev/sda': ERROR: Could not find a known hard disk directory under '/proc/device-tree/axon@10000000000/plb5/plb4/pcix@4000004600000000/scsi@2' Same for 'ofpathname /dev/sda': ERROR: Could not find a known hard disk directory under '/proc/device-tree/axon@10000000000/plb5/plb4/pcix@4000004600000000/scsi@2' ofpathname: Could not retrieve Open Firmware device path for logical device "/dev/sda". These are the contents of '/proc/device-tree/axon@10000000000/plb5/plb4/pcix@4000004600000000/scsi@2': # ls -l total 0 -r--r--r-- 1 root root 4 2008-05-14 14:54 #address-cells -r--r--r-- 1 root root 80 2008-05-14 14:54 assigned-addresses -r--r--r-- 1 root root 4 2008-05-14 14:54 class-code -r--r--r-- 1 root root 4 2008-05-14 14:54 device-id -r--r--r-- 1 root root 5 2008-05-14 14:54 device_type -r--r--r-- 1 root root 4 2008-05-14 14:54 devsel-speed dr-xr-xr-x 2 root root 0 2008-05-14 14:54 disk@0,0,0 -r--r--r-- 1 root root 4 2008-05-14 14:54 interrupts -r--r--r-- 1 root root 4 2008-05-14 14:54 linux,phandle -r--r--r-- 1 root root 4 2008-05-14 14:54 max-latency -r--r--r-- 1 root root 4 2008-05-14 14:54 min-grant -r--r--r-- 1 root root 5 2008-05-14 14:54 name -r--r--r-- 1 root root 100 2008-05-14 14:54 reg -r--r--r-- 1 root root 4 2008-05-14 14:54 revision-id -r--r--r-- 1 root root 4 2008-05-14 14:54 #size-cells -r--r--r-- 1 root root 4 2008-05-14 14:54 subsystem-id -r--r--r-- 1 root root 4 2008-05-14 14:54 subsystem-vendor-id -r--r--r-- 1 root root 0 2008-05-14 14:54 udf-supported -r--r--r-- 1 root root 4 2008-05-14 14:54 vendor-id And here are the contents of the disk@0,0,0 subdirectory: # ls -l total 0 -r--r--r-- 1 root root 4 2008-05-15 15:53 block-size -r--r--r-- 1 root root 6 2008-05-15 15:53 device_type -r--r--r-- 1 root root 4 2008-05-15 15:53 linux,phandle -r--r--r-- 1 root root 4 2008-05-15 15:53 max-lba -r--r--r-- 1 root root 5 2008-05-15 15:53 name -r--r--r-- 1 root root 8 2008-05-15 15:53 sas-address show_of_path.sh seems to look for a file called 'disk' where on my system there's only one called 'disk@0,0,0'. On my RHEL5 based blade 'ofpathname' works fine, however: # ofpathname /dev/sda /axon@10000000000/plb5/plb4/pcix@4000004600000000/scsi@2/sd@0,0 The path I got directly from the SLOF prompt is this: /axon@10000000000/plb5/plb4/pcix@4000004600000000/scsi@2/disk@0,0,0 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=390804
User jsrain@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c1
Jiri Srain
https://bugzilla.novell.com/show_bug.cgi?id=390804
User pth@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c2
Philipp Thomas
https://bugzilla.novell.com/show_bug.cgi?id=390804
User olh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c3
Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=390804
User dominik.klein@de.ibm.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c4
--- Comment #4 from Dominik Klein
https://bugzilla.novell.com/show_bug.cgi?id=390804
User dominik.klein@de.ibm.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c5
--- Comment #5 from Dominik Klein
https://bugzilla.novell.com/show_bug.cgi?id=390804
User dominik.klein@de.ibm.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c6
Dominik Klein
https://bugzilla.novell.com/show_bug.cgi?id=390804
User olh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c7
Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=390804
User dominik.klein@de.ibm.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c8
Dominik Klein
https://bugzilla.novell.com/show_bug.cgi?id=390804
User olh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c9
--- Comment #9 from Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=390804
User olh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c10
Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=390804
User dominik.klein@de.ibm.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c11
--- Comment #11 from Dominik Klein
https://bugzilla.novell.com/show_bug.cgi?id=390804
User hannsj_uhl@de.ibm.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c12
Hanns-Joachim Uhl
https://bugzilla.novell.com/show_bug.cgi?id=390804
LTC BugProxy
https://bugzilla.novell.com/show_bug.cgi?id=390804
User olh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c13
Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=390804
LTC BugProxy
https://bugzilla.novell.com/show_bug.cgi?id=390804
User bugproxy@us.ibm.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c14
--- Comment #14 from LTC BugProxy
https://bugzilla.novell.com/show_bug.cgi?id=390804
User olh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c15
Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=390804
User olh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c16
--- Comment #16 from Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=390804
User bugproxy@us.ibm.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c17
--- Comment #17 from LTC BugProxy
https://bugzilla.novell.com/show_bug.cgi?id=390804
User olh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c18
--- Comment #18 from Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=390804
User bugproxy@us.ibm.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c19
--- Comment #19 from LTC BugProxy
https://bugzilla.novell.com/show_bug.cgi?id=390804
User olh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c20
--- Comment #20 from Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=390804
User olh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c21
--- Comment #21 from Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=390804
User olh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c22
--- Comment #22 from Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=390804
User bugproxy@us.ibm.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c23
--- Comment #23 from LTC BugProxy
https://bugzilla.novell.com/show_bug.cgi?id=390804
Hanns-Joachim Uhl
https://bugzilla.novell.com/show_bug.cgi?id=390804
User bugproxy@us.ibm.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c24
--- Comment #24 from LTC BugProxy
https://bugzilla.novell.com/show_bug.cgi?id=390804
User olh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c25
--- Comment #25 from Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=390804
User bugproxy@us.ibm.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c26
--- Comment #26 from LTC BugProxy
------- Comment From olh@novell.com 2008-07-02 08:11:43 MDT------- Sure, but it will not help much because the boot-device value can not be updated from Linux. So how do you boot from /dev/sdj (if there are so many disks configured)? The Webinterface offers only 4 harddisks, I think.
@Alexander, can you answer the 2nd part of Olafs question ? Thanks ! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=390804
User bugproxy@us.ibm.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c27
--- Comment #27 from LTC BugProxy
(In reply to comment #20)
------- Comment From olh@novell.com 2008-07-02 08:11:43 MDT------- Sure, but it will not help much because the boot-device value can not be updated from Linux. So how do you boot from /dev/sdj (if there are so many disks configured)? The Webinterface offers only 4 harddisks, I think.
@Alexander, can you answer the 2nd part of Olafs question ? Thanks !
Updating boot-device value would not help anyway. To set up a SAS device one have reboot to the SMS Menu and provide the device SAS address (WWID) and LUN: 9. Change SAS Boot Device -> 1. Change SAS Boot Device Address -> <enter SAS address> 2. Change SAS Boot Device LUN id -> <enter LUN value> You may find detailed description in the QS21 IUG. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=390804
User bugproxy@us.ibm.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c28
--- Comment #28 from LTC BugProxy
https://bugzilla.novell.com/show_bug.cgi?id=390804
User olh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c29
--- Comment #29 from Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=390804
User bugproxy@us.ibm.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c30
--- Comment #30 from LTC BugProxy
------- Comment From olh@novell.com 2008-07-03 07:36:26 MDT------- can the 'boot-device' part be automated? I mean, the installer does not show any details about the used disk. So how would one know the SAS address or LUN?
Please implement something that can be used from the Linux side. Preferably reuse the existing 'update firmware boot-device variable via nvsetenv or nvram tool' practice.
Olaf, we're looking into this now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=390804
User olh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=390804#c31
Olaf Hering
participants (1)
-
bugzilla_noreply@novell.com