LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   put hd with slackware-current multilib installed on another machine (http://www.linuxquestions.org/questions/slackware-14/put-hd-with-slackware-current-multilib-installed-on-another-machine-4175444894/)

afreitascs 01-09-2013 08:46 PM

put hd with slackware-current multilib installed on another machine
 
My pc has defect.

I can remove the hd and put it in another machine?
Or must reinstall slackware, that other machine?

pc defective motherboard ---> asus M4A78LT-M LE (Phenom 910)

motherboard where want to put the hd ---> Gigabyte GA-MA78GM-sh2 (athlon 64 x2 5200 +)

many thanks

zrdc28 01-09-2013 09:08 PM

I have done that exact thing several times and it worked ok. You might have to do a little reconfiguring.

afreitascs 01-09-2013 09:12 PM

Quote:

Originally Posted by zrdc28 (Post 4866632)
I have done that exact thing several times and it worked ok. You might have to do a little reconfiguring.

thank you very much :)

afreitascs 01-10-2013 07:46 AM

Quote:

Originally Posted by zrdc28 (Post 4866632)
I have done that exact thing several times and it worked ok. You might have to do a little reconfiguring.

I got kernel panic!!!

Please which reconfigurations ???

thanks

tuxbg 01-10-2013 08:08 AM

Quote:

Originally Posted by afreitascs (Post 4867009)
I got kernel panic!!!

Please which reconfigurations ???

thanks

Look in lilo.conf what is a root=/dev/sd?
Do you have another hdd on the other computer.

afreitascs 01-10-2013 10:01 AM

well ... The slackware up! The cause of the "kernel panic" was an installation of windows I have in another partition. I edited the lilo.config and resolved!

but I can not I connect to internet!!

My network card was eth0, but now it is [as the eth1!

any idea

thanks

phenixia2003 01-10-2013 10:13 AM

Hello,

Quote:

Originally Posted by afreitascs (Post 4867125)
but I can not I connect to internet!!

My network card was eth0, but now it is [as the eth1!

any idea

thanks

1- edit /etc/udev/rules.d/70-persistent-net.rules
or
2- delete /etc/udev/rules.d/70-persistent-net.rules and restart udev (or reboot).

--
Seb

Woodsman 01-10-2013 10:15 AM

I move hard drives from one machine to another. I don't know your hardware, but the following files might need attention when moving the hard drive. I emphasize "might" because only you can determine which changes are needed. :)

BIOS
Many people connect SATA devices to any port. When the port order differs from the connection order, the BIOS will search in the SATA port order. A good policy is to connect the first SATA device to SATA port 1, the second SATA device to SATA port 2, etc. One way around this is to use UUIDs in fstab. Use the /sbin/blkid command to learn the UUID of a device.

Boot loader (grub, lilo, etc.)
Make sure the boot loader references the correct hard drive root partition and if necessary, initrd file path and name.

fstab
If there is more than one hard drive in the machine then fstab might need to be edited.

Those first three items are critical to booting. The remainder in this list affect performance but will not prohibit booting.

udev rules (always do this)
rm -f /etc/udev/rules.d/70-persistent*.rules

xorg.conf
When using an xorg.conf, the file might need to be edited.

Sound card settings
/etc/modprobe.d/sound.conf
/var/lib/alsa/asound.state or /etc/asound.state

modprobe.d
The blacklist used for one system might not be appropriate for another system.

conkyrc

When moving a hard drive back and forth between different machines, the best approach is to retain different copies of the affected files. Write a simple shell script to copy the appropriate version before moving the drive.

Regarding a kernel panic, look at the boot loader or fstab. Verify the root partition is correct.

afreitascs 01-10-2013 11:16 AM

Quote:

Originally Posted by phenixia2003 (Post 4867135)
Hello,



1- edit /etc/udev/rules.d/70-persistent-net.rules
or
2- delete /etc/udev/rules.d/70-persistent-net.rules and restart udev (or reboot).

--
Seb

Ok! resolved. I am free again :)

thanks

----------------------

Quote:

Woodsman

I move hard drives from one machine to another. I don't know your hardware, but the following files might need attention when moving the hard drive. I emphasize "might" because only you can determine which changes are needed.

BIOS
Many people connect SATA devices to any port. When the port order differs from the connection order, the BIOS will search in the SATA port order. A good policy is to connect the first SATA device to SATA port 1, the second SATA device to SATA port 2, etc. One way around this is to use UUIDs in fstab. Use the /sbin/blkid command to learn the UUID of a device.

Boot loader (grub, lilo, etc.)
Make sure the boot loader references the correct hard drive root partition and if necessary, initrd file path and name.

fstab
If there is more than one hard drive in the machine then fstab might need to be edited.

Those first three items are critical to booting. The remainder in this list affect performance but will not prohibit booting.

udev rules (always do this)
rm -f /etc/udev/rules.d/70-persistent*.rules

xorg.conf
When using an xorg.conf, the file might need to be edited.

Sound card settings
/etc/modprobe.d/sound.conf
/var/lib/alsa/asound.state or /etc/asound.state

modprobe.d
The blacklist used for one system might not be appropriate for another system.

conkyrc

When moving a hard drive back and forth between different machines, the best approach is to retain different copies of the affected files. Write a simple shell script to copy the appropriate version before moving the drive.

Regarding a kernel panic, look at the boot loader or fstab. Verify the root partition is correct.


Thanks for warnings :)


All times are GMT -5. The time now is 06:08 AM.