Penguin
Diff: MigratingDisksExample
EditPageHistoryDiffInfoLikePages

Differences between version 2 and predecessor to the previous major change of MigratingDisksExample.

Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History

Newer page: version 2 Last edited on Tuesday, March 1, 2005 5:47:04 pm by DanielLawson Revert
Older page: version 1 Last edited on Monday, March 29, 2004 7:40:26 pm by DanielLawson Revert
@@ -1,5 +1,4 @@
-  
 If you've ever been in the situation where you are doing a full upgrade of the disks in a server, you'll face the problem of getting the data from one set of disks to the other, without wanting to reinstall from scratch. 
  
 Here's how I'd do it: 
  
@@ -33,10 +32,9 @@
  chroot /mnt/root /bin/bash 
  
 * Make sure everything looks like its ok. 
  
-* Reinstall your bootloader. if you are in the chroot as described above. Note that <new boot device> is just that! if you are booting off  
- a SCSI RAID array, it'll possibly be /dev/md0. If it's an IDE disk that will eventually be on /dev/hda but is currently on /dev/hde, try /dev/hde - but I can't guarantee that'll work. You might want to make a bootdisk so you can boot off that when you yank the old disks. 
+* Reinstall your bootloader. if you are in the chroot as described above. Note that <new boot device> is just that! if you are booting off a SCSI RAID array, it'll possibly be /dev/md0. If it's an IDE disk that will eventually be on /dev/hda but is currently on /dev/hde, try /dev/hde - but I can't guarantee that'll work. You might want to make a bootdisk so you can boot off that when you yank the old disks. 
  
  lilo -b <new boot device> 
  
 ** If you aren't in the chroot, specify the config file