Differences between version 6 and previous revision of EPIA-Grub.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 6 | Last edited on Monday, February 27, 2006 3:35:07 am | by MattCollins | Revert |
| Older page: | version 5 | Last edited on Monday, February 27, 2006 3:29:57 am | by MattCollins | Revert |
@@ -1,7 +1,7 @@
First draft:
-!!Using Grub to boot EPIA with > 130gb drive on secondary channel
+!
!!Using Grub to boot EPIA with > 130gb drive on secondary channel
This document is primarily written as an alternative for those experiencing the lilo 'L 99' error found under [LiloNotes].
@@ -53,9 +53,9 @@
</pre>
will install the basic grub bootloader without a menu. In the above example 'hd0' indicates our first hard drive (the cdrom is not included in that scan), '1' indicates our 2nd partition listed under fdisk (hdb2).
-Note: grub starts counting partitions from , rather than 1, so fdisk hdb1 is grub partition (hd0,), hdb2 is (hd0,1), etc. Grub also ignores extended partitions, so if you are using any you will need to subtract an additional 1 from the count.
+__
Note__
: grub starts counting partitions from , rather than 1, so fdisk hdb1 is grub partition (hd0,), hdb2 is (hd0,1), etc. Grub also ignores extended partitions, so if you are using any you will need to subtract an additional 1 from the count.
!! Further changes
So far, so good - but what if the partitions you wish to boot are above the 136gb mark? At this point grub will give you 'Error 18', the bios does not support the cylinder that partition is present on.
@@ -73,9 +73,9 @@
<pre>
/dev/hdb3 /boot ext3 defaults 0 1
</pre>
-Note: 'hdb3' will only be correct if you created your new boot space as partition three during the fdisk operations.
+__
Note__
: 'hdb3' will only be correct if you created your new boot space as partition three during the fdisk operations.
# Copy boot files over:
<pre>
mount /dev/hdb3 /mnt
@@ -102,9 +102,9 @@
</pre>
This line will provide a grub menu option titled 'test, kernel 2.6.13.2-chw-3' located on our new boot partition (hd0,2) (hard disk 0, fdisk partition , which we just created). Once located the kernel will be loaded with the line 'root=/dev/hdb2', telling it to find the rest of the operating system under linux hard disk hdb2. If you wish to create subsequent OS images to test other distros, os's or builds on, the kernel is simply loaded with a different root= argument.
-!!!
Fdisk example:
+__
Fdisk example__
:
The commands for fdisk are shown below:
<pre>
fdisk /dev/hdb
@@ -163,9 +163,9 @@
!! Final words:
But... other distros? Our whole disk is eaten by hdb2. Well, ext2 and ext3 filesystems can be resized without losing data. To do so use the 'resize2fs' command; if your partition is ext3 you will need to disable journaling with the 'tune2fs -O ^has_journal /dev/hdX' command first, use resize2fs to shrink your disk spanning drive, then re-enable it once done using 'tune2fs -j /dev/hdX'.
-Note that
this MUST be done with the drive unmount
- once again, boot off your cd or floppy, and work on the drive unmounted.
+__
Note__:
this MUST be done with the drive unmounted
- once again, boot off your cd or floppy, and work on the drive unmounted.
With your boot partition in the first 1023 cylinders as outlined above it is perfectly possible to place your subsequent OS layouts in extended partitions anywhere on the disk.
Create a new extended partition as partition 4, then divide up the space amongst as many drives as you like. I made two 5gb partitions for a 'stable' and 'test' OS image, while keeping /dev/hdb2 simply as a 'data' partition for my home directories and PVR recordings.
