Re: LABEL in grub.conf

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Monday 03 January 2005 18:44, Bill Matthews wrote:
> That was my problem.  In order to prepare for a restore, I start with
> a blank disk, and format it to match my old drive.  But in doing that,
> I don't think volume labels ever got set. "e2label /dev/sda1" returns
> /boot but "e2label /dev/sdb"1 returns nothing. .
how do you partition /prepare your disk?
if you do the trad "fdisk followed by mke2fs" routine you can create the 
labels when you create the filesystems - 
mke2fs -L /boot -j /dev/sdb1 etc etc

> So in order for grub.conf to boot the new drive, I have to assign
> partition labels, or change grub.conf to use physical device names?
In short, yes. The labels are more flexible as they don't care where the 
filesystem actually is, so you could plug your disk in anywhere you'd like 
to. 
<gotcha>as long as there are no other filesystems with the same label on any 
of your disks.</gotcha>
If there are it gets a bit stroppy.

Stuart
-- 
Stuart Sears RHCE, RHCX
Early to bed and early to rise and you'll be groggy when everyone else is
wide awake.

-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

[Index of Archives]     [CentOS]     [Kernel Development]     [PAM]     [Fedora Users]     [Red Hat Development]     [Big List of Linux Books]     [Linux Admin]     [Gimp]     [Asterisk PBX]     [Yosemite News]     [Red Hat Crash Utility]


  Powered by Linux