« previous next »
Pages: [1]   Go Down

Author Topic: UUID - SOLVED  (Read 2241 times)

Offline dangbert

  • Sr. Member
  • ****
  • Posts: 360
UUID - SOLVED
« on: February 05, 2010, 01:58:23 PM »
i was looking at another distro (loaded it into sda7)  and somehow the UUID on my primary PCLinuxOS (2009.2KDE) partition (sda1) got changed.  Any helpful hints on how to change it back?  I reinstalled PCLinuxOS but the original install (sda1) is much better and I would love to get it back.

Thanks

Deb
« Last Edit: February 06, 2010, 12:47:39 PM by dangbert »
Logged

Offline Was_Just19

  • Hero Member
  • *****
  • Posts: 6852
  • MLU
Re: UUID
« Reply #1 on: February 05, 2010, 02:05:21 PM »
Typing into a terminal

blkid         <enter>

will return details of your partitions including their UUIDs.

Is that what you were looking for?

Code: [Select]
/dev/sda5: UUID="4bfd54de-974f-473e-87af-050e9e99a7bb" TYPE="swap"
/dev/sda6: LABEL="Root" UUID="9dc6a34a-8a6f-4cd6-9ba0-46a24b2907fc" TYPE="ext3"
/dev/sda7: LABEL="Home" UUID="f0fc24db-f7ed-4c45-8456-8f27a84fe89d" TYPE="ext3"


regards.
« Last Edit: February 05, 2010, 02:06:53 PM by JohnBoy »
Logged

Online Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11593
  • ----IOFLU----
Re: UUID
« Reply #2 on: February 05, 2010, 02:17:53 PM »
Quote from: dangbert on February 05, 2010, 01:58:23 PM

i was looking at another distro (loaded it into sda7)  and somehow the UUID on my primary PCLinuxOS (2009.2KDE) partition (sda1) got changed.  Any helpful hints on how to change it back?  I reinstalled PCLinuxOS but the original install (sda1) is much better and I would love to get it back.

Thanks

Deb

When you format a partition, it's given a unique UUID number, as part of the process. If you reformat, the UUID number changes. Without reformatting I don't know how a UUID would change. The whole point of UUID numbers is to have a constant, unique, identification system for each partition; something that does not change, once the partition is formatted.

To determine what the actual UUID numbers of all partitions currently are, use the blkid command.

Example:

[root@fatman ~]# blkid
/dev/hda5: UUID="2be4fddf-f783-4449-bf36-2dff451c9ab9" SEC_TYPE="ext2" TYPE="ext3" LABEL="TV-1"
/dev/hda1: UUID="8dd1e8b5-1cc7-4a59-9cbe-844225b5a18c" SEC_TYPE="ext2" TYPE="ext3" LABEL="boot200"
/dev/hda2: TYPE="swap" UUID="859fbc30-88b0-48e5-9224-a6f74e0d38a5" LABEL="swap200"
/dev/hda3: UUID="3b7d8a95-2144-431c-ae9e-935a9e40b5f1" SEC_TYPE="ext2" TYPE="ext3" LABEL="TR5-2"
/dev/sda2: TYPE="swap" LABEL="swap1000" UUID="584a1d5d-668d-4435-8a90-589283eb3e8b"
/dev/sda3: LABEL="TR5" UUID="6ae6cf37-7fd2-4b9c-86dc-f037141745bb" TYPE="ext3" SEC_TYPE="ext2"
/dev/sda5: LABEL="TR5-Documents" UUID="9c1bbdf4-5f3c-4d70-b03a-983504da6c15" TYPE="ext3" SEC_TYPE="ext2"
/dev/sda7: UUID="36feb97d-2f61-4709-b6f5-8e8d8fee3370" TYPE="ext3" SEC_TYPE="ext2" LABEL="TR6"
/dev/sda6: UUID="dcf02721-aca8-494f-8182-cc8ab1df8430" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda1: LABEL="boot1000" UUID="10165aee-8b41-4c52-aa7e-c6b0d6d17eeb" TYPE="ext3" SEC_TYPE="ext2"
/dev/sda8: UUID="5361ae3c-128c-47b6-a23c-0b34e3c76057" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda9: UUID="003077db-2988-4dcf-9baa-58e1798a4a85" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda10: UUID="7b1f293e-8deb-49de-adbf-db9173fd2599" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdc1: LABEL="750boot" UUID="985efd35-13a4-4279-8129-0f9552d95ccb" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdc2: UUID="0ccd09b0-ebb4-4f78-8c73-632232adf438" TYPE="swap" LABEL="swap750"
/dev/sdc3: LABEL="750pclos" UUID="ace4498d-cd4b-458b-9b0c-853c0679fe70" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdc5: LABEL="Documents2" UUID="d9550e51-e2e6-4b48-b382-d491ab0bc1ea" TYPE="ext3"
/dev/sdc6: LABEL="share9" UUID="3abe7220-57d1-40c8-acb3-b8d13585577f" TYPE="ext3"
/dev/sdc7: LABEL="Documents" UUID="6c984560-d3bc-4ea9-b2ad-62586c662bcf" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdc8: LABEL="750mm" UUID="b512d57e-3c7a-4226-96ea-98ba93d5d486" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdc9: LABEL="movies" UUID="90ae3f6a-46b2-485a-886d-e4c203491907" TYPE="ext3"
/dev/sdc10: LABEL="120backup" UUID="3dff9abc-88c0-47dc-bd2c-f3f991acab69" TYPE="ext3" SEC_TYPE="ext2"
/dev/sdc11: LABEL="storage00" UUID="f0320f20-48d5-4ddb-89ed-9da4676aefa4" TYPE="ext3"
/dev/sda11: UUID="3d1692bb-afe0-4648-b5be-d30f1eca32e7" TYPE="ext3"
/dev/sda12: LABEL="movies2" UUID="fad35a11-5738-401e-88b6-56b78dfeb15a" SEC_TYPE="ext2" TYPE="ext3"
/dev/hdb1: LABEL="usb_boot" UUID="77ad8b9e-39cf-4ff6-88e4-6c4fe1cd33f9" TYPE="ext3"
/dev/hdb2: UUID="ee7bb52e-06f6-4d83-bd83-f0d25e791c3d" TYPE="swap"
/dev/hdb3: LABEL="usb_root" UUID="3d637e7e-0844-4edb-a85e-d5a9e45fd8cf" SEC_TYPE="ext2" TYPE="ext3"
/dev/hdb5: LABEL="usb_home" UUID="d4df1799-91e0-4946-9bd7-526ea1989f8f" SEC_TYPE="ext2" TYPE="ext3"
/dev/hdb6: LABEL="share7" UUID="ff1937e8-f0ba-4a33-a544-ddfb3fd7a269" TYPE="ext3"
/dev/hdb7: UUID="33fde9f7-aec2-44cc-8ae4-c32749414220" SEC_TYPE="ext2" TYPE="ext3"


To determine the UUID of a specific partition;

[root@fatman ~]# blkid /dev/sda3
/dev/sda3: LABEL="TR5" UUID="6ae6cf37-7fd2-4b9c-86dc-f037141745bb" TYPE="ext3" SEC_TYPE="ext2"

You do not need to issue the command as root, but you will need to be root to edit and modify any system files that refer to the UUID numbers, such as /etc/fstab. or /boot/grub/menu.lst.
Logged
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline dangbert

  • Sr. Member
  • ****
  • Posts: 360
Re: UUID
« Reply #3 on: February 05, 2010, 03:41:57 PM »

You are never too old to learn.  I looked in the /sda1/dev/fstab and had a deleted partition.  Got rid of it and could boot into /sda1 - sort of.  The "gfxmenu" cannot be found.  So I have to boot in fail safe, but I can at least get into it.

Question, what and where is the "gfxmenu," and how do I get it back?  Can I just delete the line entry with it in it from "menu.lst?"

Thanks

Deb

Update, I am up on the install in question, but it is a "load failsafe, exit, login as user"  But it works.  What does not work is the Bootloader.  I have updated the bootloader from this install and still no go.  As i said, it works in "faiilsafe" but not through the standard loader.  Any hints?

Thanks

Deb
« Last Edit: February 05, 2010, 05:32:08 PM by dangbert »
Logged

Online Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11593
  • ----IOFLU----
Re: UUID
« Reply #4 on: February 05, 2010, 08:02:45 PM »
Quote from: dangbert on February 05, 2010, 03:41:57 PM

You are never too old to learn.  I looked in the /sda1/dev/fstab and had a deleted partition.  Got rid of it and could boot into /sda1 - sort of.  The "gfxmenu" cannot be found.  So I have to boot in fail safe, but I can at least get into it.

Question, what and where is the "gfxmenu," and how do I get it back?  Can I just delete the line entry with it in it from "menu.lst?"

Thanks

Deb

Update, I am up on the install in question, but it is a "load failsafe, exit, login as user"  But it works.  What does not work is the Bootloader.  I have updated the bootloader from this install and still no go.  As i said, it works in "faiilsafe" but not through the standard loader.  Any hints?

Thanks

Deb

You really need to learn to understand the boot loader. It's the same boot loader, no matter which option you select at boot time. It looks for the the same kernel and initrd image with each option. What parameters are given to the kernel is what makes the difference. If the OS boots with any selection, the boot loader is working and doing it's job.

If the installation is fairly new, the gfxmenu is in the /boot directory of the / partition. In older installations it is at;

gfxmenu (hd0,n)/usr/share/gfxboot/themes/pclinuxos/boot/message

with n being the / partition.

To have a clear idea of what's happening with your installation, we need to see the results of;

[root@localhost ~]# fdisk -l          <Enter>    <-- That's a lower case L not a number 1.

And the contents of /boot/grub/menu.lst.

[root@localhost ~]# cat /boot/grub/menu.lst            <Enter>

From the running system, open a terminal, run those two commands, then post your results.
Logged
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline dangbert

  • Sr. Member
  • ****
  • Posts: 360
Re: UUID
« Reply #5 on: February 06, 2010, 07:50:44 AM »


Thanks, here is the requested info.  The thing I found interesting is I have two boot partitions.

Also, the error code is 23, if that helps.

fdisk -l resluts:

Disk /dev/sda: 500.1 GB, 500106780160 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x14cb14cb

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        9726    78124063+  83  Linux
/dev/sda2            9727       30966   170610300    5  Extended
/dev/sda5            9727       11225    12040686   82  Linux swap / Solaris
/dev/sda6   *       11226       21405    81770818+  83  Linux
/dev/sda7           21406       30966    76798701   83  Linux

cat /boot/grub/menu.lst results:

timeout 10                                                                 
color black/cyan yellow/cyan                                               
gfxmenu (sd0,0)/boot/gfxmenu                                               
default 0                                                                   

title PCLinuxOS_2009.2
kernel (sd0,0)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_2009.2 root=UUID=b5ca1f80-889c-4b47-8e51-2596142f77e1 acpi=on resume=UUID=317ef3d3-24f7-4a2b-81c0-3d39da6cb0a1 splash=silent vga=788                                                           
initrd (sd0,0)/boot/initrd.img                                                 

title linux-nonfb
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=b5ca1f80-889c-4b47-8e51-2596142f77e1 acpi=on resume=UUID=317ef3d3-24f7-4a2b-81c0-3d39da6cb0a1     
initrd (hd0,0)/boot/initrd.img                                                 

title failsafe
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=b5ca1f80-889c-4b47-8e51-2596142f77e1 failsafe acpi=on
initrd (hd0,0)/boot/initrd.img

title PCLinuxOS LDXE
root (hd0,5)
configfile /boot/grub/menu.lst

# This is a divider, added to separate the menu items below from the PCLINUXOS standard grub entries
title           Other operating systems:


# This entry automatically added by the PCLinuxOS redo-mbr for an existing
# linux installation on /dev/sda6.
title           PCLinuxOS 2009.4 (on /dev/sda6)
root            (hd0,5)
kernel          /boot/vmlinuz BOOT_IMAGE=PCLinuxOS_2009.4 root=UUID=49bc8486-007f-4520-a230-eb0ac184fdca acpi=on resume=UUID=317ef3d3-24f7-4a2b-81c0-3d39da6cb0a1 splash=silent vga=788
initrd          (hd0,5)/boot/initrd.img
savedefault
boot


# This entry automatically added by the PCLinuxOS redo-mbr for an existing
# linux installation on /dev/sda7.
title           PCLinuxOS_KDE4 (on /dev/sda7)
root            (hd0,6)
kernel          /boot/vmlinuz BOOT_IMAGE=PCLinuxOS_KDE4 root=UUID=807dc7b3-85a6-4069-9641-b993481fc076 acpi=on resume=UUID=317ef3d3-24f7-4a2b-81c0-3d39da6cb0a1 splash=silent vga=788
initrd          (hd0,6)/boot/initrd.img
savedefault


Thanks again.

Deb
Logged

Online Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11593
  • ----IOFLU----
Re: UUID
« Reply #6 on: February 06, 2010, 08:45:16 AM »
Quote from: dangbert on February 06, 2010, 07:50:44 AM


Thanks, here is the requested info.  The thing I found interesting is I have two boot partitions.

Also, the error code is 23, if that helps.

fdisk -l resluts:

Disk /dev/sda: 500.1 GB, 500106780160 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x14cb14cb

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        9726    78124063+  83  Linux
/dev/sda2            9727       30966   170610300    5  Extended
/dev/sda5            9727       11225    12040686   82  Linux swap / Solaris
/dev/sda6   *       11226       21405    81770818+  83  Linux
/dev/sda7           21406       30966    76798701   83  Linux

cat /boot/grub/menu.lst results:

timeout 10                                                                 
color black/cyan yellow/cyan                                               
gfxmenu (sd0,0)/boot/gfxmenu                                               
default 0                                                                   

title PCLinuxOS_2009.2
kernel (sd0,0)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_2009.2 root=UUID=b5ca1f80-889c-4b47-8e51-2596142f77e1 acpi=on resume=UUID=317ef3d3-24f7-4a2b-81c0-3d39da6cb0a1 splash=silent vga=788                                                           
initrd (sd0,0)/boot/initrd.img                                                 

title linux-nonfb
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=b5ca1f80-889c-4b47-8e51-2596142f77e1 acpi=on resume=UUID=317ef3d3-24f7-4a2b-81c0-3d39da6cb0a1     
initrd (hd0,0)/boot/initrd.img                                                 

title failsafe
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=b5ca1f80-889c-4b47-8e51-2596142f77e1 failsafe acpi=on
initrd (hd0,0)/boot/initrd.img

title PCLinuxOS LDXE
root (hd0,5)
configfile /boot/grub/menu.lst

# This is a divider, added to separate the menu items below from the PCLINUXOS standard grub entries
title           Other operating systems:


# This entry automatically added by the PCLinuxOS redo-mbr for an existing
# linux installation on /dev/sda6.
title           PCLinuxOS 2009.4 (on /dev/sda6)
root            (hd0,5)
kernel          /boot/vmlinuz BOOT_IMAGE=PCLinuxOS_2009.4 root=UUID=49bc8486-007f-4520-a230-eb0ac184fdca acpi=on resume=UUID=317ef3d3-24f7-4a2b-81c0-3d39da6cb0a1 splash=silent vga=788
initrd          (hd0,5)/boot/initrd.img
savedefault
boot


# This entry automatically added by the PCLinuxOS redo-mbr for an existing
# linux installation on /dev/sda7.
title           PCLinuxOS_KDE4 (on /dev/sda7)
root            (hd0,6)
kernel          /boot/vmlinuz BOOT_IMAGE=PCLinuxOS_KDE4 root=UUID=807dc7b3-85a6-4069-9641-b993481fc076 acpi=on resume=UUID=317ef3d3-24f7-4a2b-81c0-3d39da6cb0a1 splash=silent vga=788
initrd          (hd0,6)/boot/initrd.img
savedefault


Look at the lines above that I highlighted in blue. You have three instances of (sd0,0) which should be (hd0,0).

Grub has no idea what a (sd0,0) is, so throws an error 23.

 23 : Error while parsing number
      This error is returned if GRUB was expecting to read a number and
      encountered bad data.

To BIOS and grub, all hard drives are (hdn), with the n being the hard drive designation number. The counting for both starts at 0.

Correction:

You don't have any boot partitions, but you do appear to have three / partitions, two of which are tagged as active, which is of no consequence to Linux.

Windows needs a primary partition, tagged as active, in order to boot. Linux does not use the active tag for anything, as the booting instructions are in the boot loader stanzas, in this case, the stanzas in /boot/grub/menu.lst.

When troubleshooting booting problems, it is important to use the proper terminology when referring to various items, in order to give a clear and accurate description of your problem. Improper terminology can lead to misunderstandings and, in turn, improper repair instructions.

To fix the current problem, as root, open a terminal and enter;

[root@localhost ~]# kwrite /boot/grub/menu.lst          <Enter>

When menu.lst opens in kwrite, change each of the (sd0,0) to (hd0,0), then save the file.

On rebooting, the gfxmenu should be found, if it actually exists, and the first menu option should also work properly.

Post your results.
Logged
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline dangbert

  • Sr. Member
  • ****
  • Posts: 360
Re: UUID
« Reply #7 on: February 06, 2010, 12:46:55 PM »

What can I say, when you're good, you're good.

Something so simple and so easily over looked. 

Thanks, it worked like a charm.

Deb
Logged

Online Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11593
  • ----IOFLU----
Re: UUID
« Reply #8 on: February 06, 2010, 02:30:34 PM »
Quote from: dangbert on February 06, 2010, 12:46:55 PM

What can I say, when you're good, you're good.

Something so simple and so easily over looked. 

Thanks, it worked like a charm.

Deb

You're welcome. :D
Logged
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline Joble

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 6804
  • USA - Mountain Time
Re: UUID
« Reply #9 on: February 06, 2010, 04:37:02 PM »
Quote from: dangbert on February 06, 2010, 12:46:55 PM

What can I say, when you're good, you're good.

Something so simple and so easily over looked.  

Thanks, it worked like a charm.

Deb

Congratulations!  O-P is actually pretty good like that.

So Solved then?  If you add "Solved" to the subject line of the first post, others will find a solution when searching.   ;)
« Last Edit: February 06, 2010, 04:39:27 PM by Joble »
Logged
Search First.
Forum Rules
Hero means I talk a lot, nothing more, nothing less!
Have an Awesome Day!
Healthy System

Offline dangbert

  • Sr. Member
  • ****
  • Posts: 360
Re: UUID - SOLVED
« Reply #10 on: February 06, 2010, 04:44:15 PM »


Yes, It is solved. 

O-P was the one this time, but one of the things that makes this distro so vastly different from all the others is summed up in three things.  The level of help available(in this case demonstrated by O-P), the genuine interest (the fact you posted) and seeing the guy who is the driving force for the distro actually on line helping folks. 

A heart felt thanks to one and all for what you do.

Deb
Logged

Offline Joble

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 6804
  • USA - Mountain Time
Re: UUID - SOLVED
« Reply #11 on: February 06, 2010, 08:15:51 PM »
:)  I was watching this thread from the beginning.  I had UUID trouble before and was hoping for some insight, which I found here.  Thx for posting the question.
Logged
Search First.
Forum Rules
Hero means I talk a lot, nothing more, nothing less!
Have an Awesome Day!
Healthy System
Pages: [1]   Go Up
« previous next »