Moveing SuSE 9.2 from IDE to SCSI
Hello guys... I got already SuSE 9.3 installed at /dev/hda but I need to move it to /dev/scd I know that I can move them by using dd, but, what else do I may need to change ? 1) Grub ? Which config files ? Should I do any other stuff rather than modify the new path at the Config files ? 2) FSTAB ? 3) Others ? Thanks --ed He who fights with monsters might take care lest he thereby become a monster. And if you gaze for long into an abyss, the abyss gazes also into you .Friedrich Nietzsche, Beyond Good and Evil, Aphorism 146
On Thursday 30 June 2005 9:06 am, Eduardo J. Vega A wrote:
Hello guys... I got already SuSE 9.3 installed at /dev/hda but I need to move it to /dev/scd
I know that I can move them by using dd, but, what else do I may need to change ?
1) Grub ? Which config files ? Should I do any other stuff rather than modify the new path at the Config files ? 2) FSTAB ? 3) Others ? First, dd may not be the right tool because it does an image copy. You can use the cp command with the -R flag, or rsync. You should also do this either from single user mode or by booting a standalone Linux or Rescue disk.
1) Grub
While you will need to change the specs in /boot/grub/menu.lst (or
grub.conf), you will also need to change the MBR to point to the
appropriate GRUB stage 2. This can be done via YaST or from the command
line. GRUB is well documented via the info command:
info grub
Other than the boot loader and fstab, most of the other configuration files
are based on file system locations.
Also, /dev/scd is generally a CD. Did you mean /dev/sda or /dev/sdc?
--
Jerry Feldman
On Thursday 30 June 2005 09:26 am, Jerry Feldman wrote:
On Thursday 30 June 2005 9:06 am, Eduardo J. Vega A wrote:
Hello guys... I got already SuSE 9.3 installed at /dev/hda but I need to move it to /dev/scd
I know that I can move them by using dd, but, what else do I may need to change ?
1) Grub ? Which config files ? Should I do any other stuff rather than modify the new path at the Config files ? 2) FSTAB ? 3) Others ?
First, dd may not be the right tool because it does an image copy. You can use the cp command with the -R flag, or rsync. You should also do this either from single user mode or by booting a standalone Linux or Rescue disk.
1) Grub While you will need to change the specs in /boot/grub/menu.lst (or grub.conf), you will also need to change the MBR to point to the appropriate GRUB stage 2. This can be done via YaST or from the command line. GRUB is well documented via the info command: info grub
Other than the boot loader and fstab, most of the other configuration files are based on file system locations. Also, /dev/scd is generally a CD. Did you mean /dev/sda or /dev/sdc?
Additionally you will need to include the module that drives the scsi controller (aic7xxx is one of them) in the initrd file so that the module is available at boot time.
right now I can see the hard disk when I boot from the IDE one, so the SCSI Modules are already loaded... should I need to modify the initrd file ? or it already contains what I need ? Thanks --ed
On Thursday 30 June 2005 09:26 am, Jerry Feldman wrote:
On Thursday 30 June 2005 9:06 am, Eduardo J. Vega A wrote:
Hello guys... I got already SuSE 9.3 installed at /dev/hda but I need to move it to /dev/scd
I know that I can move them by using dd, but, what else do I may need to change ?
1) Grub ? Which config files ? Should I do any other stuff rather than modify the new path at the Config files ? 2) FSTAB ? 3) Others ?
First, dd may not be the right tool because it does an image copy. You can use the cp command with the -R flag, or rsync. You should also do this either from single user mode or by booting a standalone Linux or Rescue disk.
1) Grub While you will need to change the specs in /boot/grub/menu.lst (or grub.conf), you will also need to change the MBR to point to the appropriate GRUB stage 2. This can be done via YaST or from the command line. GRUB is well documented via the info command: info grub
Other than the boot loader and fstab, most of the other configuration files are based on file system locations. Also, /dev/scd is generally a CD. Did you mean /dev/sda or /dev/sdc?
Additionally you will need to include the module that drives the scsi controller (aic7xxx is one of them) in the initrd file so that the module is available at boot time.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
--ed He who fights with monsters might take care lest he thereby become a monster. And if you gaze for long into an abyss, the abyss gazes also into you .Friedrich Nietzsche, Beyond Good and Evil, Aphorism 146
On Thursday 30 June 2005 10:53 am, Eduardo J. Vega A wrote:
right now I can see the hard disk when I boot from the IDE one, so the SCSI Modules are already loaded... should I need to modify the initrd file ? or it already contains what I need ?
Most likely (without any other info) you *will* need to change initrd. You are seeing the scsi drive because you have booted from your current IDE system and you have a running kernel, which can load whatever modules it needs. When you boot from the scsi drive, you will need that scsi module in your initrd so that the root drive can be accessed while the kernel is booting.
Thanks
--ed
On Thursday 30 June 2005 09:26 am, Jerry Feldman wrote:
On Thursday 30 June 2005 9:06 am, Eduardo J. Vega A wrote:
Hello guys... I got already SuSE 9.3 installed at /dev/hda but I need to move it to /dev/scd
I know that I can move them by using dd, but, what else do I may need to change ?
1) Grub ? Which config files ? Should I do any other stuff rather than modify the new path at the Config files ? 2) FSTAB ? 3) Others ?
First, dd may not be the right tool because it does an image copy. You can use the cp command with the -R flag, or rsync. You should also do this either from single user mode or by booting a standalone Linux or Rescue disk.
1) Grub While you will need to change the specs in /boot/grub/menu.lst (or grub.conf), you will also need to change the MBR to point to the appropriate GRUB stage 2. This can be done via YaST or from the command line. GRUB is well documented via the info command: info grub
Other than the boot loader and fstab, most of the other configuration files are based on file system locations. Also, /dev/scd is generally a CD. Did you mean /dev/sda or /dev/sdc?
Additionally you will need to include the module that drives the scsi controller (aic7xxx is one of them) in the initrd file so that the module is available at boot time.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
--ed
He who fights with monsters might take care lest he thereby become a monster. And if you gaze for long into an abyss, the abyss gazes also into you .Friedrich Nietzsche, Beyond Good and Evil, Aphorism 146
Jerry, Eduardo, On Thursday 30 June 2005 06:26, Jerry Feldman wrote:
...
First, dd may not be the right tool because it does an image copy. You can use the cp command with the -R flag, or rsync. You should also do this either from single user mode or by booting a standalone Linux or Rescue disk.
Beware. The "-R" / "-r" option to "cp" only triggers the recursive copying behavior. You absolutely, positively must also preserve all file attributes, so you really want "-a", which is a shorthand for "-dpR". -d same as --no-dereference --preserve=link -p same as --preserve=mode,ownership,timestamps -R, -r, --recursive copy directories recursively
...
-- Jerry Feldman
Randall Schulz
On Thursday 30 June 2005 10:16 am, Randall R Schulz wrote:
Jerry, Eduardo,
On Thursday 30 June 2005 06:26, Jerry Feldman wrote:
...
First, dd may not be the right tool because it does an image copy. You can use the cp command with the -R flag, or rsync. You should also do this either from single user mode or by booting a standalone Linux or Rescue disk.
Beware. The "-R" / "-r" option to "cp" only triggers the recursive copying behavior. You absolutely, positively must also preserve all file attributes, so you really want "-a", which is a shorthand for "-dpR".
-d same as --no-dereference --preserve=link -p same as --preserve=mode,ownership,timestamps -R, -r, --recursive copy directories recursively I certainly agree here. I was just in a bit of a rush. -d is the default on Linux when -R is used, but it is always better to be specific.
--
Jerry Feldman
Jerry Feldman wrote:
On Thursday 30 June 2005 10:16 am, Randall R Schulz wrote:
Jerry, Eduardo,
On Thursday 30 June 2005 06:26, Jerry Feldman wrote:
...
First, dd may not be the right tool because it does an image copy. You can use the cp command with the -R flag, or rsync. You should also do this either from single user mode or by booting a standalone Linux or Rescue disk. Beware. The "-R" / "-r" option to "cp" only triggers the recursive copying behavior. You absolutely, positively must also preserve all file attributes, so you really want "-a", which is a shorthand for "-dpR".
-d same as --no-dereference --preserve=link -p same as --preserve=mode,ownership,timestamps -R, -r, --recursive copy directories recursively I certainly agree here. I was just in a bit of a rush. -d is the default on Linux when -R is used, but it is always better to be specific.
I thought "cp -a" was the appropriate command. It copies everything, maintains permissions and access times and doesn't follow links.
participants (5)
-
Bruce Marshall -
Eduardo J. Vega A -
James Knott -
Jerry Feldman -
Randall R Schulz