after copying partition, how to deal with fstab when it references by UUID ?
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Distribution: Hardy (Gnome on Ubuntu 8.04) on Compaq N600c laptop
Posts: 323
Rep:
after copying partition, how to deal with fstab when it references by UUID ?
I'm completely confused:
I duplicated all partitions (yes, I kept types, size and position the same) from /dev/sdb to /dev/sda. (/dev/sdb is the original, working linux-only drive). Don't know if it's relevant, but the old is a SATA, the new a PATA.
I then went through the mystifying process of installing grub onto /dev/sda. That seemed to work, as specify that drive in the bios boot menu does startup linux.
But then, if sdb is left enabled (in bios), the machine does boot; all looks normal, but /dev/sdb1 is mounted on "/", and sda isn't even mounted.
I checked /etc/fstab (yes, the one in sda), and it referenced by UUID. So I tried to change that entry to use "/dev/sda" in place of the UUID, changing nothing else on said line. And it did exactly that: changed nothing. It still boots using /dev/sdb1 for "/".
If I disable the sdb drive in bios, the boot just hangs at"Loading, please wait".
Distribution: Hardy (Gnome on Ubuntu 8.04) on Compaq N600c laptop
Posts: 323
Original Poster
Rep:
Thanks for the tip.
I'll give that a try, but my goal is to get rid of the original drive, and also to understand why the new drive doesn't load (or somehow mounts the old drive).
I then went through the mystifying process of installing grub onto /dev/sda. That seemed to work, as specify that drive in the bios boot menu does startup linux.
Again how - precisely. Your supposition isn't supported by the following evidence.
Quote:
But then, if sdb is left enabled (in bios), the machine does boot; all looks normal, but /dev/sdb1 is mounted on "/", and sda isn't even mounted.
...
If I disable the sdb drive in bios, the boot just hangs at"Loading, please wait".
Looks like you haven't updated grub to use the correct disk. If it was me I'd pull the old disk out, and fix things from a liveCD. Tell us what you did, we can suggest fix(s).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.