Liberating to a USB disk

From BCCD 3.0

(Difference between revisions)
Jump to: navigation, search
(notes from #785)
m
 
Line 6: Line 6:
# /boot/grub/{menu.lst,devices.map} have accurate info and re-run grub-install if necessary. devices.map will contains /dev/disk/by-id references that will have useful information about the drive type.
# /boot/grub/{menu.lst,devices.map} have accurate info and re-run grub-install if necessary. devices.map will contains /dev/disk/by-id references that will have useful information about the drive type.
-
# /etc/fstab have accurate info. If the drive order will change on boot, make sure device-specific entries are changed.
+
# /etc/fstab has accurate info. If the drive order will change on boot, make sure device-specific entries are changed.
# LVM volumes become active quickly enough. Adding rootdelay=9 to /etc/grub.d/10_linux will ensure this.
# LVM volumes become active quickly enough. Adding rootdelay=9 to /etc/grub.d/10_linux will ensure this.

Latest revision as of 03:23, 24 May 2013

NOTE: These instructions are experimental and incomplete

These are notes from solving #785.

Steve Spicklemire wanted to know if BCCD could be liberated onto a USB disk rather than a SATA/IDE disk. In the past this worked, but in testing it no longer did. After some investigation, I discovered that whether this works or not is dependent on a number of factors:

  1. /boot/grub/{menu.lst,devices.map} have accurate info and re-run grub-install if necessary. devices.map will contains /dev/disk/by-id references that will have useful information about the drive type.
  2. /etc/fstab has accurate info. If the drive order will change on boot, make sure device-specific entries are changed.
  3. LVM volumes become active quickly enough. Adding rootdelay=9 to /etc/grub.d/10_linux will ensure this.
Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox