I've got a machine with three hard-drives in it. two sata and one ide. I've a fedora 10 (upgraded from 9) on the first sata drive, and I've installed fedora 11 on the second sata drive. The machine boots off the first of these drives and the ide one contains windows. I copied the lines out of grub.conf on the f11 disk, and copied them to the grub.conf of the
first disk,
andreinstalled. However, f10 boots fine, f11 doesn't boot. and grub gives me an error 17.
why did you reinstall ? If I am not mistaken , that will generate a new different UUID and then the old stanza willl fail.
HTH Jack
ok, I've got to reinstall my system due to new hardware (32-64 bit) and wanted to see what F11 was like, whilst being able to keep on using my slightly broken f10 installtion in the mean time.. I don't really understand why it's using the UUID, I've just got two versions of fedora on two drives and would just like them to boot.
The F11 isn't a reinstall, it's a first time install on a clean drive.
Thanks, Jim
2009/9/18 jackson byers byersjab@gmail.com
I've got a machine with three hard-drives in it. two sata and one ide.
I've a fedora 10 (upgraded
from 9) on the first sata drive, and I've installed fedora 11 on the
second sata drive. The machine
boots off the first of these drives and the ide one contains windows. I
copied the lines out of
grub.conf on the f11 disk, and copied them to the grub.conf of the
first disk,
andreinstalled. However, f10 boots fine, f11 doesn't boot. and grub gives me an error 17.
why did you reinstall ? If I am not mistaken , that will generate a new different UUID and then the old stanza willl fail.
HTH Jack
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
On 09-09-19 07:57:03, James Allsopp wrote:
... I don't really understand why it's using the UUID, ...
Because the GRUB stanza you copied to boot F11 says:
root=UUID=7ba6f364-68c2-4dad-a54e-18c3464b0eb5
That is, it says root is identified by its UUID.
So is there some sort of conversion in the initrd converting from the UUId to something conventional like /dev/sdb2, and if so why doesn't just substituting /dev/sdb2 not work.
2009/9/19 Tony Nelson tonynelson@georgeanelson.com
On 09-09-19 07:57:03, James Allsopp wrote:
... I don't really understand why it's using the UUID, ...
Because the GRUB stanza you copied to boot F11 says:
root=UUID=7ba6f364-68c2-4dad-a54e-18c3464b0eb5
That is, it says root is identified by its UUID.
-- ____________________________________________________________________ TonyN.:' mailto:tonynelson@georgeanelson.com ' http://www.georgeanelson.com/
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
On Sat, Sep 19, 2009 at 7:05 PM, James Allsopp <jamesaallsopp@googlemail.com
wrote:
So is there some sort of conversion in the initrd converting from the UUId to something conventional like /dev/sdb2, and if so why doesn't just substituting /dev/sdb2 not work.
Because, as Tony stated, the root partition is identified by its UUID.
2009/9/19 Tony Nelson tonynelson@georgeanelson.com
On 09-09-19 07:57:03, James Allsopp wrote:
... I don't really understand why it's using the UUID, ...
Because the GRUB stanza you copied to boot F11 says:
root=UUID=7ba6f364-68c2-4dad-a54e-18c3464b0eb5
That is, it says root is identified by its UUID.
-- ____________________________________________________________________ TonyN.:' mailto:tonynelson@georgeanelson.com ' http://www.georgeanelson.com/
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
but why isn't idenitfied by /dev/sda2 like partitions normally are? I'm not understanding why a UUID is necessary, as opposed to a standard /dev/sd pointer to the root partition.
Basically how can I get this to work? Jim
2009/9/19 Aioanei Rares schaiba@gmail.com
On Sat, Sep 19, 2009 at 7:05 PM, James Allsopp < jamesaallsopp@googlemail.com> wrote:
So is there some sort of conversion in the initrd converting from the UUId to something conventional like /dev/sdb2, and if so why doesn't just substituting /dev/sdb2 not work.
Because, as Tony stated, the root partition is identified by its UUID.
2009/9/19 Tony Nelson tonynelson@georgeanelson.com
On 09-09-19 07:57:03, James Allsopp wrote:
... I don't really understand why it's using the UUID, ...
Because the GRUB stanza you copied to boot F11 says:
root=UUID=7ba6f364-68c2-4dad-a54e-18c3464b0eb5
That is, it says root is identified by its UUID.
-- ____________________________________________________________________ TonyN.:' mailto:tonynelson@georgeanelson.com ' http://www.georgeanelson.com/
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
-- Aioanei Rares schaiba@fedoraproject.org "China is a big country, inhabited by many Chinese." --Charles de Gaulle
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
On Sat, Sep 19, 2009 at 18:19:05 +0100, James Allsopp jamesaallsopp@googlemail.com wrote:
but why isn't idenitfied by /dev/sda2 like partitions normally are? I'm not understanding why a UUID is necessary, as opposed to a standard /dev/sd pointer to the root partition.
Things are moving more toward using UUIDs. UUIDs are more stable in identifying file systems, raid arrays than using generic names. That makes them better fitted for the job.
On 09/19/2009 01:19 PM, James Allsopp wrote:
but why isn't idenitfied by /dev/sda2 like partitions normally are? I'm not understanding why a UUID is necessary, as opposed to a standard /dev/sd pointer to the root partition.
Jim, look at it this way. You have a system with 4 different disk cables, which can support up to 6 different disk devices. You have a working system using /dev/sda and /dev/sdb. You add a new disk drive. All of a sudden, your system devices are /dev/sda (your *new* drive), /dev/sdb (your old /dev/sda) and /dev/sdc (your old /dev/sdb). Now, even if you *can* find your old root partition, it has names which reference partitions on the wrong disks. Your system is broken.
With UUIDs, once you can locate the correct root disk partition, it also references your old disks via UUID and can find them regardless of their new device names in the new setup. All you have to do is reference your new disk partitions via their UUIDs.
Its the same with, well, suppose your motherboard dies and you replace it with a new one. If you are not careful cabling your disks in the new setup, you'll have the same problems as above, whereas if you use UUIDs, everything will get found, regardless of where it ends up (once you have your boot disk identified correctly and booting).
Basically how can I get this to work?
Use the UUIDs.
Jim
On 09/19/2009 10:39 AM, Bruno Wolff III wrote:
On Sat, Sep 19, 2009 at 18:19:05 +0100, James Allsopp jamesaallsopp@googlemail.com wrote:
but why isn't idenitfied by /dev/sda2 like partitions normally are? I'm not understanding why a UUID is necessary, as opposed to a standard /dev/sd pointer to the root partition.
Things are moving more toward using UUIDs. UUIDs are more stable in identifying file systems, raid arrays than using generic names. That makes them better fitted for the job.
Yes, somewhat true. But I still use carefully managed labels instead of hard to remember UUIDs and it you lose it, its a pain to recover. It's easier for me to see: f11-boot, f11-root, f-App1, u9-boot, u9-root, ..., w2kPro, w2kSvr, VistaH, XpPro, and so on. I have many different OSes dispersed over many HDs.
As for grub itself, I use a grub "tree-structure" and the primary boot grub so happens to be based on F8-grub and on the drive's 1st partition, followed with whatever grubs each OS supports and each in it's own boot/root partitions per drive and usually all in the extended partition. All of my OS SATA drives uses the maximum of 15 partitions, so that the tables are always preserved, I learned this the hard way.
All in all, it works very well.
The point is, labels and/or UUID are not a requirement, but a perhaps convention? This could change though, but I hope not.
FWIW Dan
On 09-09-19 12:05:20, James Allsopp wrote:
So is there some sort of conversion in the initrd converting from the UUId to something conventional like /dev/sdb2,
No, the UUID is just looked at for each volume until a match is found (or not). Try the `blkid` command; see `man blkid`.
and if so why doesn't just substituting /dev/sdb2 not work.
Perhaps that is not the correct name, or your "root" line is wrong. It is also possible that the UUID was changed when you reinstalled (though it should not change unless you reformatted the drive).
2009/9/19 Tony Nelson tonynelson@georgeanelson.com
On 09-09-19 07:57:03, James Allsopp wrote:
... I don't really understand why it's using the UUID, ...
Because the GRUB stanza you copied to boot F11 says:
root=UUID=7ba6f364-68c2-4dad-a54e-18c3464b0eb5
That is, it says root is identified by its UUID.
On Sat, 2009-09-19 at 17:05 +0100, James Allsopp wrote:
So is there some sort of conversion in the initrd converting from the UUId to something conventional like /dev/sdb2, and if so
There's several ways to map one to another. The "blkid" command will list the drive partitions for you, detailing device names and related UUIDs.
why doesn't just substituting /dev/sdb2 not work.
Perhaps, because when you boot differently, the drives are numbered differently. e.g. One system sees that partition as sdb2, another sees it as sdc2.