Hi All,

Maybe you're missing my desired outcome.

Maybe I've been using the phrase "master disk" incorrectly. too.

Maybe you're all working in a heavily networked environment, with many 
hard disks on-line to manage simultaneously -- while I'm just a 
standalone desktop user, running on a single HDD, and never hot swapping.

I DON'T want to =uniquely= identify each disk (using UUID, serial 
number, nor label) during the boot-up process -- but definitely when 
running the backup script which uses rsync (and then by using the device 
name (?) e.g.  /dev/sda  /dev/sdb ).

When my "master disk" (the only hard disk I use on a day to day basis, 
with all my OS, apps, and data on it) faults on me:  I want to take a 
recently backed-up/mirrored disk, physically replace my "master disk" 
with it, and have it boot up (taking over the role of being my "master 
disk" from then on).

This scheme has been working =perfectly= for me for at least 10 years 
now (including a fair few "restores" this way).  I have no motivation to 
alter it in any way.

I'm only asking LUV-list for assist in editing those boot-up scripts 
(below) because a couple things seem to have changed in Ubuntu since my 
current 10.4 version (and I'm using SATA drives for the first time).

Maybe a better approach:  Could anyone just point me to the specific 
forum where the Ubuntu boot process contributors focus their attention?

Thanks very much,

Carl
Bayswater

= = = = = =  O R I G I N A L   Q U E S T I O N  = = = = = =

> New system is Gigabyte MB, IntelCore i5 CPU, SATA HDD, dual booting on 64-bit 
> Windoze plus just-released Trusty 64-bit Desktop.
>
> Here's what I =would= do...
>
> (1)  Edit  /etc/default/grub  to remove the # at the start of line...
>    #GRUB_DISABLE_LINUX_UUID="true"
>
> (2)  Edit  /usr/share/grub/grub-mkconfig_lib  to comment out the 3 lines 
> starting...
>    if FS_UUID= (etc.)
> ... but that line doesn't exist in that file in the Trusty version of Ubuntu.
>
> (3)  Edit  /etc/fstab  and change very instance of UUID= (etc.) into the 
> corresponding drive and partition e.g. /dev/sda2
>
> (4)  Edit  /etc/initramfs-tools/conf.d/resume  and change UUID=RESUME= (etc.) 
> into the corresponding drive and partition e.g. /dev/sda2
>
> (5)  Run  update-grub
>
> (6)  Then re-do all the above each time I do a kernel upgrade.
_______________________________________________
luv-main mailing list
[email protected]
http://lists.luv.asn.au/listinfo/luv-main

Reply via email to