Moving LVM partition from /dev/hda2 to /dev/sda2
Paul Howarth
paul at city-fan.org
Tue Feb 21 15:31:49 UTC 2006
Michael D. Setzer II wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 20 Feb 2006 at 22:21, Mikkel L. Ellertson wrote:
>
> Date sent: Mon, 20 Feb 2006 22:21:25 -0600
> From: "Mikkel L. Ellertson" <mikkel at infinity-ltd.com>
> Organization: Infinity Ltd.
> To: For users of Fedora Core releases <fedora-list at redhat.com>
> Subject: Re: Moving LVM partition from /dev/hda2 to /dev/sda2
> Send reply to: For users of Fedora Core releases <fedora-list at redhat.com>
> <mailto:fedora-list-request at redhat.com?subject=unsubscribe>
> <mailto:fedora-list-request at redhat.com?subject=subscribe>
>
>>Michael D. Setzer II wrote:
>>
>>>On 20 Feb 2006 at 23:33, Paul Howarth wrote:
>>>
>>>
>>>>>Does your SATA drive need some driver module to be loaded?
>>>>>This might come from the ramdisk in rescue mode (and hence work), whilst
>>>>>not being present in the ramdisk created at kernel install time for the
>>>>>regular IDE drive (and hence not work). A possibility perhaps.
>>>>>
>>>
>>>
>>>I can mount the other partitions from old drive. So, I don't think it needs any
>>>special driver. I can mount /dev/sda1 to /boot2, which is the boot partition,
>>>and I formated the extra space on the drive as /dev/sda3 as /data.
>>>
>>>When I remove the old drive, and boot from the SATA drive it gets to the
>>>grub menu, and seems to load the kernel, but then doesn't find the LVM
>>>partition.
>>>
>>>When I run lvm command after booting from the old drive, one of the
>>>commands will list the duplicate volumes found, and also that the one is
>>>using /dev/sda2 instead of /dev/hda2.
>>>
>>>One comment I got said it might be using something other than hd0 for the
>>>SATA drive, but it also might be that the LVM volumn has something in it
>>>that links it to /dev/hda2.
>>>
>>>Thanks for the info.
>>>
>>
>>That is a good indication that the initrd.img on the SATA drive does
>>not have the correct modules for the SATA drive in it. Because it
>>can not access the SATA drive, it can not load the modules needed to
>>access it. This is not a problem with the IDE drive, because the
>>modules are in the initrd.img. After the root file system is
>>mounted, the kernel can load the module for the SATA drive, and
>>mount the LVM partition from the SATA drive. So you will need to
>>build a new initrd.img for the SATA drive.
>>
>
> That might be it. I find that lsmod lists the following when booted from the
> regular drive.
> sata_sis 8261 0
> libata 56653 1 sata_sis
>
> Question is how does on do the update to add this. I tried doing an upgrade
> from the DVD to the SATA drive, but it said something about no kernel
> installed, so it didn't update the grub or anything else, and the reboot did the
> same thing. Perhaps removing the kernels from the boot would cause it to
> update the kernel and other files.
>
>
> Here is the last part of the boot process before the error, so it can load the
> /boot from the sata drive, and load the kernel from it.
>
> Uncompressing Linux... OK, booting the kernel.
> Red Hat nash version 4.2.15 starting
> Reading all physical volumes. This may take a while...
> No volume groups found
> unable to find volume group "VolGroup00"
> ERROR: /bin/lvm exiting abnormally with value 5 !(pid 480)
Try making a new initrd and use the "--with=sata_sis" option to mkinitrd.
Or try adding:
alias scsi_hostadapter sata_sis
to /etc/modprobe.conf and rebuild your initrd.
Paul.
More information about the fedora-list
mailing list