On Mon, 2010-07-19 at 04:16 -0400, Felix Miata wrote:
On 2010/07/19 09:58 (GMT+0200) Roger Oberholtzer composed:
I am trying to move a hard disk to a different computer. I have moved disks before and not experienced the type of problem I am experiencing now.
The disk is an 11.0 openSUSE install. On it's original system it is:
# lsscsi [0:0:0:0] disk ATA Maxtor 6L250R0 BAJ4 /dev/sda
In /etc/fstab it is:
/dev/disk/by-id/scsi-SATA_Maxtor_6L250R0_L59ST7RH-part3
When I put the disk in the new system, grub starts ok, and the kernel boots. At some point it says it is waiting for /dev/disk/by-id/scsi-SATA_Maxtor_6L250R0_L59ST7RH-part3 to come on line. It never does. I get a command prompt, and very few commands.
I tried changing /dev/disk/by-id/scsi-SATA_Maxtor_6L250R0_L59ST7RH-part3 in /etc/fstab to be /dev/sda3, thinking that the by-id name is different in the new computer. But I got the same message about /dev/disk/by-id/scsi-SATA_Maxtor_6L250R0_L59ST7RH-part3. Which leads me to think it is something in the initrd.
I am not sure where to proceed. Any suggestions?
(I am migrating a subversion/trac system to a new machine and then from openSUSE 11.0 to 11.3. I want to do the new machine now, and the 11.0 to 11.3 upgrade in a month or so.)
The old machine and new machine most likely use HD interfaces that use different drivers. Put the HD back in the old machine and rebuild the initrd to include the driver for the new machine, then try again. Alternatively, recompile the kernel to include required controller drivers so that an initrd isn't required.
I guess this must be it. Still, I would have thought it was a generic ATA interface driver. I will have to see what the new machine is using. To make matters less obvious, the new machine has a ATA and a SATA interface. There is a Linux install on the new machine on the SATA connector. I am needing to connect this disk to the ATA connector. I wonder which driver that will be (that is different than in the other machine). I guess the easiest way is to add the driver to the list of modules in Yast, and let yast rebuild it (keeping a copy jic...) I forgot to add that when I get the prompt, /dev has no disk entries at all. I had hoped to find the 'new' name of the disk drive. Of course, sdaX should have been there. But, if the driver did not find anything, then nothing would be there. If I could update the software at the same time, I would just do a new install now. But, due to a host of reasons, the update has to wait a bit. The trac environment on the old machine (11.0) needs to be re-created in 11.3. That must be completed before the move to 11.3 is done. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org