Comment 30 for bug 1475166

Hey Bryan

modprobe megaraid_sas max_sectors=2048

Doesn¹t seem to help either.

Same error.

Thanks
Adi

On 8/24/15, 2:53 PM, "Bryan Quigley" <email address hidden> wrote:

>All that patch appears to do is to remove an artificial limit for all
>devices to 1024. I haven't been able to reproduce the option reset on
>my systems, so here is what I would try:
>
>Try setting the controller option and see if that sticks [1]:
>rmmod megaraid_sas
>modprobe megaraid_sas max_sectors=2048
>
>It may also be possible to do this while booting as a kernel command
>option like: megaraid_sas.max_sectors=2048
>(2048 does actually mean 1024 for the other options).
>
>Otherwise, I'd recommend switching to a Live CD and see if the option
>works there.
>
>If not, a last option would be to try using sysfs on the livecd to see if
>that will help ensure it:
>sudo add-apt-repository universe
>sudo apt update
>edit /etc/sysfs.ctl adding block/xxx/queue/max_sectors_kb = 1024
>sudo apt install sysfsutils
>sudo service sysfsutils restart
>
>[1] http://fendertech.blogspot.com/2013/04/how-to-increase-maxsectorskb-
>for.html
>
>--
>You received this bug notification because you are subscribed to the bug
>report.
>https://bugs.launchpad.net/bugs/1475166
>
>Title:
> Ubuntu 15.04 Install Error with Avago Controller
>
>Status in linux package in Ubuntu:
> Triaged
>
>Bug description:
> Hello Canonical Team
>
> We are running to an issue installing ubuntu PPC64LE 15.04 full blown
> image on our servers (with RAID controller). Installation hangs
> around 70% of progress.
>
> An important part of our configuration is Avago RAID controller:
> 9361-8i Firmware version we used is 4.300.00-4429, and the package is
> 24.10.0-0002.
>
> IMPORTANT: It has to be noted that with same hardware configuration
> 14.10 full blown image installs fine.
>
> Dmesg logs are attached:
>
> Looking at dmesg logs point out that:
> LSI (avago) driver loads fine
> During further interaction with raid volume during the installation
>process, firmware errors are seen
> [ 196.991417] megasas: FW status 0x3
>
> [ 196.999376] megasas: FW status 0x3
>
> [ 197.007376] megasas: FW status 0x3
> Further down the process I/O errors are thrown
> [ 217.438664] Buffer I/O error on device sda2, logical block 22052864
>
> [ 217.438671] Buffer I/O error on device sda2, logical block 22052865
>
> [ 217.438678] Buffer I/O error on device sda2, logical block 22052866
>
> [ 217.438686] Buffer I/O error on device sda2, logical block 22052867
>
> Full dmesg log is attached. Snippet is pasted below highlighting:
>
> It can be noted that there¹s a Mellanox Connectx 3 pro card with some
>test Firmware on our setup.
> We can Ignore any diagnostic messages from that card in dmesg logs for
>the purpose of this bug.
>
> Thanks
> Adi Gangidi
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475166/+subscription
>s