-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 21 Feb 2006 at 15:31, Paul Howarth wrote: Date sent: Tue, 21 Feb 2006 15:31:49 +0000 From: Paul Howarth <paul@xxxxxxxxxxxx> To: For users of Fedora Core releases <fedora-list@xxxxxxxxxx> Subject: Re: Moving LVM partition from /dev/hda2 to /dev/sda2 Send reply to: For users of Fedora Core releases <fedora-list@xxxxxxxxxx> <mailto:fedora-list-request@xxxxxxxxxx?subject=unsubscribe> <mailto:fedora-list-request@xxxxxxxxxx?subject=subscribe> > 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@xxxxxxxxxxxxxxxx> > > Organization: Infinity Ltd. > > To: For users of Fedora Core releases <fedora-list@xxxxxxxxxx> > > Subject: Re: Moving LVM partition from /dev/hda2 to /dev/sda2 > > Send reply to: For users of Fedora Core releases <fedora-list@xxxxxxxxxx> > > <mailto:fedora-list-request@xxxxxxxxxx?subject=unsubscribe> > > <mailto:fedora-list-request@xxxxxxxxxx?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. That seems to have done it. I mounted the /boot partition of the SATA drive as /boot2 , and rename the init of the latest kernel, and then make a new one with the mkinitrd. Then disconnected the HDA drive, and it then booted up fine. Did notice that the smartd failed to load, but will have to check on that. Thanks > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > +----------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor Guam Community College Computer Center mailto:mikes@xxxxxxxxxxxxxxxx mailto:msetzerii@xxxxxxxxx http://www.guam.net/home/mikes Guam - Where America's Day Begins +----------------------------------------------------------+ http://setiathome.berkeley.edu Number of Seti Units Returned: 19,471 Processing time: 32 years, 290 days, 12 hours, 58 minutes (Total Hours: 287,489) BOINC Seti@Home Total Credits 450570.865971 -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.8 -- QDPGP 2.61c Comment: http://community.wow.net/grt/qdpgp.html iQA/AwUBQ/q68SzGQcr/2AKZEQL1TgCgvPRWqn8Oa9ONp8spdg0YR1oMApcAnA5r I6aaFNukC99jRBQ89PuKzR8J =ryLk -----END PGP SIGNATURE-----
