Use any disk for /boot regardless of its size

Bug #1592358 reported by OpenStack Infra
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Won't Fix
Medium
Fuel Documentation Team

Bug Description

https://review.openstack.org/327179
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.

commit 8c118a477603e3c75e336c3a5cc9b36cc9edc05f
Author: Alexander Gordeev <email address hidden>
Date: Thu Jun 2 15:53:57 2016 +0300

    Use any disk for /boot regardless of its size

    Apparently, the disks which're bigger than 2T were excluded from list
    of bootable disks if possible. Just because in the past, those disks
    were unrecognized by BIOS (or UEFI under CSM).

    In fact, it was just misconfiguration of RAID controller or BIOS
    itself.

    GRUB uses BIOS INT13h in order to find all available disks.
    Therefore, unless particular disk is not configured as 'bootable',
    there's no change for GRUB to find it.

    One should configure hardware in the following way assuming that
    the first disk (hd0) is bootable and is used for operating system
    purposes.
    In case of hardware RAID, FC multipath or any other HBA, the disk
    (or lun, or whatever) which was configured as 'bootable' will be
    reported as hd0 via INT13h. So, GRUB will be able to boot from it.

    DocImpact
    Closes-Bug: #1588260

    Change-Id: I7bc729ffafa3b9d6bfe8521fa38599d36d02f7e1
    (cherry picked from commit e2a20044b23ece6627a90827f3fc235b24d3880a)
    (cherry picked from commit 7ffbf39caf5845bd82b8ce20a7766cf24aa803fb)

Dmitry Klenov (dklenov)
Changed in fuel:
milestone: none → 8.0-updates
assignee: nobody → Fuel Documentation Team (fuel-docs)
importance: Undecided → Medium
status: New → Confirmed
tags: added: area-docs
Revision history for this message
Michael Petersen (mpetason) wrote :

Adding Customer-Found.

Environment was 8.0.
Disks = Raid Array with 8x450TB disks in Raid 5, so 2.87 TB usable.

tags: added: customer-found
Revision history for this message
Oleksiy Molchanov (omolchanov) wrote :

We are not going to fix this bug.

Changed in fuel:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.