Mailinglist Archive: opensuse-bugs (4243 mails)

< Previous Next >
[Bug 1017731] New: [doc] [grub disk order]: Setting the Disk Order
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 02 Jan 2017 10:44:10 +0000
  • Message-id: <bug-1017731-21960@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=1017731


Bug ID: 1017731
Summary: [doc] [grub disk order]: Setting the Disk Order
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 42.2
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Documentation
Assignee: fs@xxxxxxxx
Reporter: richard.bos@xxxxxxxxx
QA Contact: fs@xxxxxxxx
Found By: ---
Blocker: ---

Procedure&nbsp;12.2: Setting the Disk Order

https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.grub2.html#pro.sec.grub2.yast2.config.order

Two remarks, opportunities for improvement:
1) The explanation states: "If your computer has more than one hard disk, you
can specify the boot sequence of the disks"

- What is the effect of this setting?
- Does it determine where e.g. the 'generic code for the MBR' is saved?
- What happens when the disk order in BIOS is: 1) sda, 2) sdb and in this
dialog the user puts it the other way around? Does it harm, becomes booting
slower or perhaps impossible?
- In case the system has a duplex disk setup (RAID-1), including swap; is it
possible with this option to save the bootloader at for example disk sda and
sdb separately (by running yast/bootloader twice?



2) The explanation states:
- Open the Boot Code Options tab.
- Click Boot Loader Installation Details --> This must be: 'edit disk boot
order', see screenshot above the explanation as well

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
This Thread
  • No further messages