Comment 27 for bug 1475166

Thanks for the bisect results! We can confirm that this fixes the issue by manually specifying the max_sectors_kb and seeing if that fixes the issue.
1. Boot the server installation and stop at the partitioning screen (this way we make sure it has detected everything)
2. Switch to another VT (Ctrl-Alt-F2)
3. Confirm and post the values of cat /sys/block/xxx/queue/max_sectors_kb and max_hw_sectors_kb (where xxx is the block device for the Avago controller)
4. Execute - echo 1024 > /sys/block/vda/queue/max_sectors_kb
5. Confirm it was really changed with cat
6. Proceed with the installation

Now, if you want to use this as a more permanent workaround you need to specify the 1024 value in sysfs on the installed system as well. Once confirmed, we would want to get from Avago (or at least some manual testing) what the real hw maximum of this value should be and add it the driver (as described in the commit message).