General

Symptom: We are trying to install Tamdhu on UCS 220, but it fails, because UCS 220 hard disk cannot be discovered by Tamdhu RC9. It shows that it cannot find any harddisk during installation. Condition: Tamdhu RC9 installation on UCS 220. Workaround: No. Details for debugging: Failed to discover UCS 220 hard disk in Tamdhu RC9 [host:~]$ lspci | grep -i raid 82:00.0 RAID bus controller: LSI Logic / Symbios Logic Device 005b (rev 03) [host:~]$ lspci -n | grep 82:00 82:00.0 0104: 1000:005b (rev 03) [host:~]$ fdisk -l [host:~]$ grep -i 005b /lib/modules/2.6.34.10-131/modules.pcimap aic7xxx 0x00009005 0x0000005b 0xffffffff 0xffffffff 0x00010000 0x00ffff00 0x0 radeonfb 0x00001002 0x00005b60 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0 radeonfb 0x00001002 0x00005b62 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0 radeonfb 0x00001002 0x00005b63 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0 radeonfb 0x00001002 0x00005b64 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0 radeonfb 0x00001002 0x00005b65 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0 dmesg output: /ws/ansli-ott/RC9.dmesg Succeeded with RC8 [host:~]$ lspci | grep -i RAID 82:00.0 RAID bus controller: LSI Logic / Symbios Logic Device 005b (rev 03) [host:~]$ lspci -n | grep 82:00 82:00.0 0104: 1000:005b (rev 03) [host:~]$ grep -i 005b /lib/modules/2.6.32-131/modules.pcimap aic7xxx 0x00009005 0x0000005b 0xffffffff 0xffffffff 0x00010000 0x00ffff00 0x0 radeonfb 0x00001002 0x00005b60 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0 radeonfb 0x00001002 0x00005b62 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0 radeonfb 0x00001002 0x00005b63 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0 radeonfb 0x00001002 0x00005b64 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0 radeonfb 0x00001002 0x00005b65 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0 [host:~]$ fdisk -l Disk /dev/sda: 897.0 GB, 896998047744 bytes 255 heads, 62 sectors/track, 110812 cylinders Units = cylinders of 15810 * 512 = 8094720 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x454c564c Device Boot Start End Blocks Id System /dev/sda1 * 1 260 2055269 83 Linux /dev/sda2 261 517 2031585 83 Linux /dev/sda3 518 3109 20489760 83 Linux /dev/sda4 3110 110812 851392215 5 Extended /dev/sda5 3110 3240 1035524 83 Linux /dev/sda6 3241 3306 521699 83 Linux Disk /dev/dm-0: 3145 MB, 3145728000 bytes 255 heads, 62 sectors/track, 388 cylinders Units = cylinders of 15810 * 512 = 8094720 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x7f3ddc81 Device Boot Start End Blocks Id System /dev/dm-0p1 * 1 388 3067109 83 Linux Disk /dev/dm-1: 2097 MB, 2097152000 bytes 255 heads, 62 sectors/track, 259 cylinders Units = cylinders of 15810 * 512 = 8094720 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x06f8f99b Device Boot Start End Blocks Id System /dev/dm-1p1 1 66 521699 83 Linux /dev/dm-1p2 67 132 521730 83 Linux /dev/dm-1p3 133 259 1003935 83 Linux dmesg output: /ws/ansli-ott/RC8.dmesg CEL 5.03 & CEL 5.5 There is no entry for 1000:005b in CEL 5.03 picmap. For 5.5, there is an entry: megaraid_sas 0x00001000 0x0000005b 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0 Previous RAID in UCS220/210 Previous RAID in UCS220/210 is 1000:0079. Same to 1000:005b, there is no entry for it on RC8/RC9/CEL 5.03; but CEL 5.5 has one entry: megaraid_sas 0x00001000 0x00000079 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0 However, this RAID has no problem for RC9, CEL 5.03 installation.