Author Topic: Grub does not load kernel after installation on SAS drive  (Read 2269 times)

regist forsoft

  • Zen Apprentice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Grub does not load kernel after installation on SAS drive
« on: February 03, 2013, 05:44:08 pm »
Hello all,

I try to get zentyal 3.0 installed on a SAS Array of two drives attached to an Dell SAS 6i Controller. The installation (64bit) found and installed on the virtual drive, but after reboot, it failes to boot via grub.

Ok, seems a problem with the Dell SAS 6ir Raid Controller. I get such output on failsafe

[   20.175104] scsi6 : ioc0: LSISAS1068E B3, FwRev=00192f00h, Ports=1, MaxQ=266, IRQ=16
[   20.212421] mptsas: ioc0: attaching sata device: fw_channel 0, fw_id 8, phy 0, sas_addr 0x1221000000000000
[   20.224982] scsi 6:0:0:0: Direct-Access     ATA     DRIVE 1 Descriptor ....
[   20.228523] mptsas: ioc0: attaching sata device: fw_channel 0, fw_id 1, phy 1, sas_addr 0x1221000001000000
[   20.241088] scsi 6:0:1:0: Direct-Access     ATA      DRIVE 2 Descriptor ....
[   20.244875] mptsas: ioc0: attaching raid volume, channel 1, id 0
[   20.245914] scsi 6:1:0:0: Direct-Access     Dell     VIRTUAL DISK     1028 PQ: 0 ANSI: 5
[   20.258408] sd 6:1:0:0: [sda] logical drive parameter here .....
[   20.259166] sd 6:1:0:0: [sda] Write Protect is off
[   20.259172] sd 6:1:0:0: [sda] Mode Sense: 03 00 00 08
[   20.259434] sd 6:1:0:0: [sda] Got wrong page
[   20.259494] sd 6:1:0:0: [sda] Assuming drive cache: write through
[   20.260950] sd 6:1:0:0: [sda] Got wrong page
[   20.261009] sd 6:1:0:0: [sda] Assuming drive cache: write through
[   20.302918]  sda: sda1 .... < sda5 >
[   20.305534] sd 6:1:0:0: [sda] Got wrong page
[   20.305593] sd 6:1:0:0: [sda] Assuming drive cache: write through
[   20.305654] sd 6:1:0:0: [sda] Attached SCSI disk

The lvm with / is on sda5. Seems a driver/timing problem. Cannot get access to the attached volume for some reason. Is this unique to the SAS 6ir Raid Controller or a common issue ?

Ok, a workaround is to apply a rootdelay. But the same hardware did boot on 10.04 LTS without any problem. If you have a similar issue with your Raid Controller, how did you fix it ?
« Last Edit: February 04, 2013, 07:20:59 am by regist forsoft »