Merge lp:~psusi/ubuntu/precise/installation-guide/partitions into lp:ubuntu/precise/installation-guide

Proposed by Phillip Susi
Status: Needs review
Proposed branch: lp:~psusi/ubuntu/precise/installation-guide/partitions
Merge into: lp:ubuntu/precise/installation-guide
Diff against target: 103 lines (+22/-51)
2 files modified
debian/changelog (+7/-0)
en/partitioning/partition/x86.xml (+15/-51)
To merge this branch: bzr merge lp:~psusi/ubuntu/precise/installation-guide/partitions
Reviewer Review Type Date Requested Status
Colin Watson Pending
Review via email: mp+92841@code.launchpad.net

This proposal supersedes a proposal from 2012-01-13.

Description of the change

How's that look?

To post a comment you must log in.
Revision history for this message
Colin Watson (cjwatson) wrote : Posted in a previous version of this proposal

I think this removes too much information. Although I don't have specific citations for you, I've unfortunately seen even quite recent systems that had trouble booting from later in the disk and required a /boot partition.

Could you keep most of the wording about /boot partitions, and just remove the obsolete bit about partition numbering?

review: Needs Fixing
Revision history for this message
Phillip Susi (psusi) wrote : Posted in a previous version of this proposal

The documentation itself already said it is only an issue for PCs from circa 1995-1998. Reading the installation guide as a lay person, I'm thinking who cares about PCs from 14 years ago?

By the way, doesn't grub now require lba mode anyhow? So if you did still have an old bios that only does CHS, a /boot partition wouldn't help.

How many recent systems have this kind of trouble? One in a million? Is that enough to justify a section in the installation guide?

Revision history for this message
Colin Watson (cjwatson) wrote : Posted in a previous version of this proposal

I'm not saying the documentation is correct in all respects, but you
can't just remove that big chunk of text. GRUB can handle CHS to some
extent; and in any case it isn't just CHS, there are other reasons why
you might need /boot to be near the start of the disk.

No, please don't exaggerate. If it were one in a million I very much
doubt I'd have seen multiple examples of this.

If you want a thoroughly modern example, >2TB disks are becoming common,
but in discussions with BIOS people nobody is able to tell me with any
confidence that the weakly-tested support for 64-bit reads using BIOS
calls actually works on a plurality of systems, and thus it's quite
possible that /boot needs to be in the first 2TB of the disk if you're
using GPT with BIOS (which otherwise ought to work fine in most cases)
in order to avoid lurking unreliability. While the reasoning is quite
different from that in the guide at the moment, the ultimate advice is
essentially the same.

Unmerged revisions

40. By Phillip Susi

* Remove outdated/incorrect partition information (LP: #704412)
* Add section on using GPT

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'debian/changelog'
2--- debian/changelog 2011-09-26 16:06:37 +0000
3+++ debian/changelog 2012-02-13 20:12:18 +0000
4@@ -1,3 +1,10 @@
5+installation-guide (20100518ubuntu6) precise; urgency=low
6+
7+ * Remove outdated/incorrect partition information (LP: #704412)
8+ * Add section on using GPT
9+
10+ -- Phillip Susi <psusi@ubuntu.com> Fri, 13 Jan 2012 15:01:07 -0500
11+
12 installation-guide (20100518ubuntu5) oneiric; urgency=low
13
14 * Bump kernelversion to 3.0.
15
16=== modified file 'en/partitioning/partition/x86.xml'
17--- en/partitioning/partition/x86.xml 2007-07-23 15:52:44 +0000
18+++ en/partitioning/partition/x86.xml 2012-02-13 20:12:18 +0000
19@@ -17,8 +17,8 @@
20
21 The PC BIOS generally adds additional constraints for disk
22 partitioning. There is a limit to how many <quote>primary</quote> and
23-<quote>logical</quote> partitions a drive can contain. Additionally, with pre
24-1994&ndash;98 BIOSes, there are limits to where on the drive the BIOS can boot
25+<quote>logical</quote> partitions a drive can contain. Additionally, with
26+very old or buggy BIOSes, there are limits to where on the drive the BIOS can boot
27 from. More information can be found in the
28 <ulink url="&url-partition-howto;">Linux Partition HOWTO</ulink> and the
29 <ulink url="&url-phoenix-bios-faq-large-disk;">Phoenix BIOS FAQ</ulink>, but
30@@ -36,60 +36,24 @@
31 drive.
32
33 </para><para>
34-
35-Linux limits the partitions per drive to 15 partitions for SCSI disks
36-(3 usable primary partitions, 12 logical partitions), and 63
37-partitions on an IDE drive (3 usable primary partitions, 60 logical
38-partitions). However the normal Ubuntu system provides
39-only 20 devices for partitions, so you may not install on partitions
40-higher than 20 unless you first manually create devices for those
41-partitions.
42-
43-</para><para>
44-
45-If you have a large IDE disk, and are using neither LBA addressing,
46-nor overlay drivers (sometimes provided by hard disk manufacturers),
47-then the boot partition (the partition containing your kernel image)
48-must be placed within the first 1024 cylinders of your hard drive
49-(usually around 524 megabytes, without BIOS translation).
50-
51-</para><para>
52-
53-This restriction doesn't apply if you have a BIOS newer than around
54-1995&ndash;98 (depending on the manufacturer) that supports the <quote>Enhanced
55-Disk Drive Support Specification</quote>. Both Lilo, the Linux loader, and
56-Ubuntu's alternative <command>mbr</command> must use the BIOS to read the
57-kernel from the disk into RAM. If the BIOS int 0x13 large disk access
58-extensions are found to be present, they will be utilized. Otherwise,
59-the legacy disk access interface is used as a fall-back, and it cannot
60-be used to address any location on the disk higher than the 1023rd
61-cylinder. Once Linux is booted, no matter what BIOS your computer
62-has, these restrictions no longer apply, since Linux does not use the
63-BIOS for disk access.
64-
65-</para><para>
66-
67-If you have a large disk, you might have to use cylinder translation
68-techniques, which you can set from your BIOS setup program, such as
69-LBA (Logical Block Addressing) or CHS translation mode (<quote>Large</quote>).
70-More information about issues with large disks can be found in the
71-<ulink url="&url-large-disk-howto;">Large Disk HOWTO</ulink>. If you
72-are using a cylinder translation scheme, and the BIOS does not support
73-the large disk access extensions, then your boot partition has to fit
74-within the <emphasis>translated</emphasis> representation of the
75-1024th cylinder.
76-
77-</para><para>
78-
79-The recommended way of accomplishing this is to create a small (25&ndash;50MB
80+The new <quote>GUID Parittion Table</quote> (GPT) can be used instead
81+of the <quote>msdos</quote> partition table. GPT has no extended or
82+logical partitions, and supports 128 primary partitions and disks larger
83+than 2TB. GPT was intended to be used on <quote>EFI</quote> based machines.
84+Some recent motherboards have an option to boot in EFI or BIOS mode.
85+When booting in EFI mode, you must create a small (100MB) boot partition.
86+This boot partition <emphasis>must</emphasis> be mounted on <filename>
87+/boot/efi</filename>. To boot in BIOS mode, you must create a tiny (1 MB)
88+<quote>bios_grub</quote> partition. Either should be at or near the start of the disk.
89+</para><para>
90+
91+If you have an old/buggy BIOS that can not access the whole disk,
92+the recommended way of dealing with this is to create a small (100MB
93 should suffice) partition at the beginning of the disk to be used as
94 the boot partition, and then create whatever other partitions you wish
95 to have, in the remaining area. This boot partition
96 <emphasis>must</emphasis> be mounted on <filename>/boot</filename>,
97 since that is the directory where the Linux kernel(s) will be stored.
98-This configuration will work on any system, regardless of whether LBA
99-or large disk CHS translation is used, and regardless of whether your
100-BIOS supports the large disk access extensions.
101
102 </para>
103 </sect2>

Subscribers

People subscribed via source and target branches

to all changes: