Hi,
I recently upgraded my desktop system with a much larger hard drive. The old hard drive is now in an external hard drive enclosure (the kind made by Metal Gear Box) and is plugged in to a USB port. The old drive has these partitions
Microsoft Windows XP -- 30 Gb Fedora Core 4 -- 30 Gb
My problem is, I can see the /boot partition on the drive, but I cannot see the / (root) partition, and I'm want to get at my former home directory because I have some files there I forgot to back up. I'm wondering if that partition was named something like: '/dev/VolGroup00/LogVol00' and mounted on /.
Thanks for any help!
Bob Cochran
On Sat, Dec 31, 2005 at 09:50:12AM -0500, Robert L Cochran wrote:
Hi,
I recently upgraded my desktop system with a much larger hard drive. The old hard drive is now in an external hard drive enclosure (the kind made by Metal Gear Box) and is plugged in to a USB port. The old drive has these partitions
Microsoft Windows XP -- 30 Gb Fedora Core 4 -- 30 Gb
My problem is, I can see the /boot partition on the drive, but I cannot see the / (root) partition, and I'm want to get at my former home directory because I have some files there I forgot to back up. I'm wondering if that partition was named something like: '/dev/VolGroup00/LogVol00' and mounted on /.
Odd. If you can see one partition you ought to be able to see them all. What happens if you (as root) run "fdisk -l /dev/..." against the external drive? And are the appropriate device files being created, e.g. /dev/sda1, /dev/sda2, etc.
Is your system using the swap partition on the external drive ("cat /proc/swaps")? If so you may wish to prevent it, as it is a hot-plugable drive.
I do a similar operation annually. What I do is mount my old /dev/hda as /dev/hdc, and leave it in place for a year. I set all the partitions on the old drive to ro in /etc/fstab, e.g.:
/dev/hdc3 /mnt/oldsys ext3 owner,ro 1 2
The main gotcha is you must be careful with the partition labels so that you don't get duplicates, e.g. two /home partitions.
Robert L Cochran wrote:
Hi,
I recently upgraded my desktop system with a much larger hard drive. The old hard drive is now in an external hard drive enclosure (the kind made by Metal Gear Box) and is plugged in to a USB port. The old drive has these partitions
Microsoft Windows XP -- 30 Gb Fedora Core 4 -- 30 Gb
My problem is, I can see the /boot partition on the drive, but I cannot see the / (root) partition, and I'm want to get at my former home directory because I have some files there I forgot to back up. I'm wondering if that partition was named something like: '/dev/VolGroup00/LogVol00' and mounted on /.
Thanks for any help!
Bob Cochran
You are right that the / partition is contained in the LVM. I believe you need to run lvm and make the partition active, assign a mountpoint for the lvm, then mount the lvm. The label that the old hard drive is using is probably / which is the label most likely used on your newly installed system. I recovered my previous installation using a USB enclosure and activating the LVM. It was a long time back and useful information on activating the LVM was upplied by someone on this list. Adding USB enclosure - LVM to subject.
Jim
Jim Cornette wrote:
Robert L Cochran wrote:
Hi,
I recently upgraded my desktop system with a much larger hard drive. The old hard drive is now in an external hard drive enclosure (the kind made by Metal Gear Box) and is plugged in to a USB port. The old drive has these partitions
Microsoft Windows XP -- 30 Gb Fedora Core 4 -- 30 Gb
My problem is, I can see the /boot partition on the drive, but I cannot see the / (root) partition, and I'm want to get at my former home directory because I have some files there I forgot to back up. I'm wondering if that partition was named something like: '/dev/VolGroup00/LogVol00' and mounted on /.
Thanks for any help!
Bob Cochran
You are right that the / partition is contained in the LVM. I believe you need to run lvm and make the partition active, assign a mountpoint for the lvm, then mount the lvm. The label that the old hard drive is using is probably / which is the label most likely used on your newly installed system. I recovered my previous installation using a USB enclosure and activating the LVM. It was a long time back and useful information on activating the LVM was upplied by someone on this list. Adding USB enclosure - LVM to subject.
Jim
Thanks for the insight. This led me to give 'man lvm' a fast glance, then I Googled on lvm and found a how-to in the LDP, part of which is this:
http://www.tldp.org/HOWTO/LVM-HOWTO/recipemovevgtonewsys.html
I'd better explain that in my old system, I had two (2) physical hard drives. The first is a 60 Gb drive and this is the drive we are discussing below, which is installed in a Metal Gear USB hard drive enclosure.
The second drive is a 120 Gb drive which actually represents a former Fedora Core system (whether FC2 or FC3, I can't remember.) I built a new computer more than a year ago. I bought the 60 Gb drive, divided that into a partition for Windows XP and left the rest as unallocated free space. I installed Windows, then installed Fedora Core 3. At the time I installed FC 3, I decided to plug in the 120 Gb drive as a second hard drive. I just thought of it as a way of giving myself access to the data on my former system. This was mounted on a directory named /mnt/any and seemed to work fine for a long while under FC3. The only odd thing is that I couldn't do any compiles with gcc from the directories on that drive. I'd get messages about not having permission. The directories were named similarly to my current home directory. I use /home/rlc on this system, and the old system also had /home/rlc when that was active. I then ran FC3 for a long time on this system. I upgraded this 2-hard drive system to Fedora Core 4. I've only been running FC4 for a few months now.
Now I've done yet a makeover of my hardware. I took out the 60 and 120 Gb drives and in their place I put in a 400 Gb drive. The old motherboard and processor have been replaced too.
Now I realize that my backup DVD doesn't have some files I really need. I've quickly put the 60 Gb drive in the drive enclosure and plugged it in.
But I'm still confused by my own attempts to bring back my old partitions and access those directories. I plugged in the USB cable with this result:
Dec 31 18:37:16 bobcp4 fstab-sync[21919]: added mount point /media/usbdisk for /dev/sdb1 Dec 31 18:37:17 bobcp4 fstab-sync[21925]: added mount point /media/usbdisk1 for /dev/sdb2
Then I did a 'pvscan' to see if I could find the volume group:
[root@bobcp4 ~]# pvscan PV /dev/sda2 VG VolGroup00 lvm2 [372.50 GB / 32.00 MB free] Total: 1 [372.50 GB] / in use: 1 [372.50 GB] / in no VG: 0 [0 ]
What we see above is my current active lvm partition. I wonder why the swap volume group isn't shown? And there is nothing from sdb...puzzling, that.
So on the hard drive I mounted via USB, I would expect to see 4 partitions when I think about it:
an NTFS partition for Windows XP;
a swap partition;
a /boot partition for FC4;
and a / partition for everything else.
/ and swap seems to be missing.
Here is what's in /media/usbdisk. I suspect it is probably Windows XP, the NTFS partition:
[root@bobcp4 ~]# ls -al /media/usbdisk total 12 drwxr-xr-x 2 root root 4096 Dec 31 18:37 . drwxr-xr-x 6 root root 4096 Dec 31 18:37 ..
/media/usbdisk1 looks like /boot:
[root@bobcp4 ~]# ls -al /media/usbdisk1 total 28262 drwxr-xr-x 4 root root 4096 Dec 14 05:53 . drwxr-xr-x 6 root root 4096 Dec 31 18:37 .. -rw-r--r-- 1 root root 50848 Jun 2 2005 config-2.6.11-1.1369_FC4 -rw-r--r-- 1 root root 52480 Sep 28 19:24 config-2.6.13-1.1526_FC4 -rw-r--r-- 1 root root 52514 Oct 20 01:38 config-2.6.13-1.1532_FC4 -rw-r--r-- 1 root root 54391 Nov 9 19:16 config-2.6.14-1.1637_FC4 -rw-r--r-- 1 root root 54413 Nov 27 03:34 config-2.6.14-1.1644_FC4 -rw-r--r-- 1 root root 54399 Dec 13 21:46 config-2.6.14-1.1653_FC4 drwxr-xr-x 2 root root 1024 Dec 14 05:53 grub -rw-r--r-- 1 root root 1948129 Oct 9 12:32 initrd-2.6.11-1.1369_FC4.img -rw-r--r-- 1 root root 1954696 Oct 9 15:20 initrd-2.6.13-1.1526_FC4.img -rw-r--r-- 1 root root 1955846 Oct 20 20:47 initrd-2.6.13-1.1532_FC4.img -rw-r--r-- 1 root root 1917983 Nov 10 16:45 initrd-2.6.14-1.1637_FC4.img -rw-r--r-- 1 root root 1917986 Nov 28 21:12 initrd-2.6.14-1.1644_FC4.img -rw-r--r-- 1 root root 1917769 Dec 14 05:53 initrd-2.6.14-1.1653_FC4.img drwx------ 2 root root 12288 Nov 10 2004 lost+found -rw-r--r-- 1 root root 916318 Jun 2 2005 System.map-2.6.11-1.1369_FC4 -rw-r--r-- 1 root root 941697 Sep 28 19:24 System.map-2.6.13-1.1526_FC4 -rw-r--r-- 1 root root 942036 Oct 20 01:38 System.map-2.6.13-1.1532_FC4 -rw-r--r-- 1 root root 958081 Nov 9 19:16 System.map-2.6.14-1.1637_FC4 -rw-r--r-- 1 root root 958383 Nov 27 03:34 System.map-2.6.14-1.1644_FC4 -rw-r--r-- 1 root root 958892 Dec 13 21:46 System.map-2.6.14-1.1653_FC4 -rw-r--r-- 1 root root 1951836 Jun 2 2005 vmlinuz-2.6.11-1.1369_FC4 -rw-r--r-- 1 root root 2020745 Sep 28 19:24 vmlinuz-2.6.13-1.1526_FC4 -rw-r--r-- 1 root root 2021093 Oct 20 01:38 vmlinuz-2.6.13-1.1532_FC4 -rw-r--r-- 1 root root 1718117 Nov 9 19:16 vmlinuz-2.6.14-1.1637_FC4 -rw-r--r-- 1 root root 1717815 Nov 27 03:34 vmlinuz-2.6.14-1.1644_FC4 -rw-r--r-- 1 root root 1713442 Dec 13 21:46 vmlinuz-2.6.14-1.1653_FC4
So, where is everything else?
Thanks for any help.
Bob Cochran
On 12/31/05, Robert L Cochran cochranb@speakeasy.net wrote:
Jim Cornette wrote:
Robert L Cochran wrote:
My problem is, I can see the /boot partition on the drive, but I cannot see the / (root) partition, and I'm want to get at my former home directory because I have some files there I forgot to back up. I'm wondering if that partition was named something like: '/dev/VolGroup00/LogVol00' and mounted on /.
I recently ran into this very thing and wondered what the solution was. I was dry-running a system rescue using Knoppix live and Systemrescuecd (another live distro), and I could mount everything but the LVM partitions on the Fedora 4 machine under test. (And, of course, that's where the vast majority of my files of interest are.) What it taught me is that I won't be using LVM anymore, because it's not conducive to rescue efforts. When Fedora 5 is released in a few months, I intend to rebuild partitions from scratch, without LVM.
I didn't try the Fedora 4 rescue CD. Using it might have met with more success.
Jay
Robert L Cochran wrote:
Jim Cornette wrote:
Robert L Cochran wrote:
Hi,
I recently upgraded my desktop system with a much larger hard drive. The old hard drive is now in an external hard drive enclosure (the kind made by Metal Gear Box) and is plugged in to a USB port. The old drive has these partitions
Microsoft Windows XP -- 30 Gb Fedora Core 4 -- 30 Gb
My problem is, I can see the /boot partition on the drive, but I cannot see the / (root) partition, and I'm want to get at my former home directory because I have some files there I forgot to back up. I'm wondering if that partition was named something like: '/dev/VolGroup00/LogVol00' and mounted on /.
Thanks for any help!
Bob Cochran
You are right that the / partition is contained in the LVM. I believe you need to run lvm and make the partition active, assign a mountpoint for the lvm, then mount the lvm. The label that the old hard drive is using is probably / which is the label most likely used on your newly installed system. I recovered my previous installation using a USB enclosure and activating the LVM. It was a long time back and useful information on activating the LVM was upplied by someone on this list. Adding USB enclosure - LVM to subject.
Jim
Thanks for the insight. This led me to give 'man lvm' a fast glance, then I Googled on lvm and found a how-to in the LDP, part of which is this:
http://www.tldp.org/HOWTO/LVM-HOWTO/recipemovevgtonewsys.html
I'd better explain that in my old system, I had two (2) physical hard drives. The first is a 60 Gb drive and this is the drive we are discussing below, which is installed in a Metal Gear USB hard drive enclosure.
The second drive is a 120 Gb drive which actually represents a former Fedora Core system (whether FC2 or FC3, I can't remember.) I built a new computer more than a year ago. I bought the 60 Gb drive, divided that into a partition for Windows XP and left the rest as unallocated free space. I installed Windows, then installed Fedora Core 3. At the time I installed FC 3, I decided to plug in the 120 Gb drive as a second hard drive. I just thought of it as a way of giving myself access to the data on my former system. This was mounted on a directory named /mnt/any and seemed to work fine for a long while under FC3. The only odd thing is that I couldn't do any compiles with gcc from the directories on that drive. I'd get messages about not having permission. The directories were named similarly to my current home directory. I use /home/rlc on this system, and the old system also had /home/rlc when that was active. I then ran FC3 for a long time on this system. I upgraded this 2-hard drive system to Fedora Core 4. I've only been running FC4 for a few months now.
Now I've done yet a makeover of my hardware. I took out the 60 and 120 Gb drives and in their place I put in a 400 Gb drive. The old motherboard and processor have been replaced too.
Now I realize that my backup DVD doesn't have some files I really need. I've quickly put the 60 Gb drive in the drive enclosure and plugged it in.
But I'm still confused by my own attempts to bring back my old partitions and access those directories. I plugged in the USB cable with this result:
Dec 31 18:37:16 bobcp4 fstab-sync[21919]: added mount point /media/usbdisk for /dev/sdb1 Dec 31 18:37:17 bobcp4 fstab-sync[21925]: added mount point /media/usbdisk1 for /dev/sdb2
Then I did a 'pvscan' to see if I could find the volume group:
[root@bobcp4 ~]# pvscan PV /dev/sda2 VG VolGroup00 lvm2 [372.50 GB / 32.00 MB free] Total: 1 [372.50 GB] / in use: 1 [372.50 GB] / in no VG: 0 [0 ]
What we see above is my current active lvm partition. I wonder why the swap volume group isn't shown? And there is nothing from sdb...puzzling, that.
So on the hard drive I mounted via USB, I would expect to see 4 partitions when I think about it:
an NTFS partition for Windows XP;
a swap partition;
a /boot partition for FC4;
and a / partition for everything else.
/ and swap seems to be missing.
Here is what's in /media/usbdisk. I suspect it is probably Windows XP, the NTFS partition:
[root@bobcp4 ~]# ls -al /media/usbdisk total 12 drwxr-xr-x 2 root root 4096 Dec 31 18:37 . drwxr-xr-x 6 root root 4096 Dec 31 18:37 ..
/media/usbdisk1 looks like /boot:
[root@bobcp4 ~]# ls -al /media/usbdisk1 total 28262 drwxr-xr-x 4 root root 4096 Dec 14 05:53 . drwxr-xr-x 6 root root 4096 Dec 31 18:37 .. -rw-r--r-- 1 root root 50848 Jun 2 2005 config-2.6.11-1.1369_FC4 -rw-r--r-- 1 root root 52480 Sep 28 19:24 config-2.6.13-1.1526_FC4 -rw-r--r-- 1 root root 52514 Oct 20 01:38 config-2.6.13-1.1532_FC4 -rw-r--r-- 1 root root 54391 Nov 9 19:16 config-2.6.14-1.1637_FC4 -rw-r--r-- 1 root root 54413 Nov 27 03:34 config-2.6.14-1.1644_FC4 -rw-r--r-- 1 root root 54399 Dec 13 21:46 config-2.6.14-1.1653_FC4 drwxr-xr-x 2 root root 1024 Dec 14 05:53 grub -rw-r--r-- 1 root root 1948129 Oct 9 12:32 initrd-2.6.11-1.1369_FC4.img -rw-r--r-- 1 root root 1954696 Oct 9 15:20 initrd-2.6.13-1.1526_FC4.img -rw-r--r-- 1 root root 1955846 Oct 20 20:47 initrd-2.6.13-1.1532_FC4.img -rw-r--r-- 1 root root 1917983 Nov 10 16:45 initrd-2.6.14-1.1637_FC4.img -rw-r--r-- 1 root root 1917986 Nov 28 21:12 initrd-2.6.14-1.1644_FC4.img -rw-r--r-- 1 root root 1917769 Dec 14 05:53 initrd-2.6.14-1.1653_FC4.img drwx------ 2 root root 12288 Nov 10 2004 lost+found -rw-r--r-- 1 root root 916318 Jun 2 2005 System.map-2.6.11-1.1369_FC4 -rw-r--r-- 1 root root 941697 Sep 28 19:24 System.map-2.6.13-1.1526_FC4 -rw-r--r-- 1 root root 942036 Oct 20 01:38 System.map-2.6.13-1.1532_FC4 -rw-r--r-- 1 root root 958081 Nov 9 19:16 System.map-2.6.14-1.1637_FC4 -rw-r--r-- 1 root root 958383 Nov 27 03:34 System.map-2.6.14-1.1644_FC4 -rw-r--r-- 1 root root 958892 Dec 13 21:46 System.map-2.6.14-1.1653_FC4 -rw-r--r-- 1 root root 1951836 Jun 2 2005 vmlinuz-2.6.11-1.1369_FC4 -rw-r--r-- 1 root root 2020745 Sep 28 19:24 vmlinuz-2.6.13-1.1526_FC4 -rw-r--r-- 1 root root 2021093 Oct 20 01:38 vmlinuz-2.6.13-1.1532_FC4 -rw-r--r-- 1 root root 1718117 Nov 9 19:16 vmlinuz-2.6.14-1.1637_FC4 -rw-r--r-- 1 root root 1717815 Nov 27 03:34 vmlinuz-2.6.14-1.1644_FC4 -rw-r--r-- 1 root root 1713442 Dec 13 21:46 vmlinuz-2.6.14-1.1653_FC4
So, where is everything else?
Thanks for any help.
Bob Cochran
I searched the archives for whatever I had to do in order to get the lvm activated. Here is one posting that I made:
https://www.redhat.com/archives/fedora-list/2005-April/msg01943.html
From an earlier posting someone suggested to run the following commands to activate and later deactivate LVM volumes in rescue mode. I used these commands on an external USB drive to get at data from a previous installation and it worked. You might be able to get at your data in this way. Jim
Excerpt from earlier help. Once booted into text-mode rescue, invoke the following commands:
lvm lvscan lvm vgchange -ay
This will scan for all LVM volumes and then will make them active and accessible.
lvm vgchange -an
will deactivate them all. end Excerpt:
Basically, the LVM volumes on the hard drive from an earlier install was labeled / for the main partition and this label being the same as my non-lvm clean install was also labeled /. When the kernel booted and the saw the same label, it ignored the LVM which contained the / and swap lvm content. To access the partition, I ran the lvscan and vgchange commands. I then had to make a mountpoint under /mnt to mount the LVM partition. I believe I got the information as /dev-mapper/volgroup00/<whatever> --- Sorry, I forgot what it is called, I no longer use LVM. I took that information of where the volume was and used mount /dev-mapper/volgroup00/<whatever> /mnt/olddrive and was able to access all the content from the LVM after mounting it. I transferred all of my desired information from the drive and never used it since.
There might be discussions in march of this year or close to that time frame in the archives. The helpful person has not posted recently to my knowledge but knew a lot about dealing with LVMs.
All of your swap partitions and other filesystem dvisions are all contained in the LVM. The only partitions you should have are the one for windows, the /boot partition and the third partition should be where all of the LVM "partitions" or slices are kept. If you ran fdisk on the /dev/sdb device, you should have three partitions. Without dev-mapper, it does not show.
Good luck! It is possible, I just cannot remember the exact method that I used to get at the LVM.
Jim
I searched the archives for whatever I had to do in order to get the lvm activated. Here is one posting that I made:
https://www.redhat.com/archives/fedora-list/2005-April/msg01943.html
From an earlier posting someone suggested to run the following commands to activate and later deactivate LVM volumes in rescue mode. I used these commands on an external USB drive to get at data from a previous installation and it worked. You might be able to get at your data in this way. Jim
Excerpt from earlier help. Once booted into text-mode rescue, invoke the following commands:
lvm lvscan lvm vgchange -ay
This will scan for all LVM volumes and then will make them active and accessible.
lvm vgchange -an
will deactivate them all. end Excerpt:
Basically, the LVM volumes on the hard drive from an earlier install was labeled / for the main partition and this label being the same as my non-lvm clean install was also labeled /. When the kernel booted and the saw the same label, it ignored the LVM which contained the / and swap lvm content. To access the partition, I ran the lvscan and vgchange commands. I then had to make a mountpoint under /mnt to mount the LVM partition. I believe I got the information as /dev-mapper/volgroup00/<whatever> --- Sorry, I forgot what it is called, I no longer use LVM. I took that information of where the volume was and used mount /dev-mapper/volgroup00/<whatever> /mnt/olddrive and was able to access all the content from the LVM after mounting it. I transferred all of my desired information from the drive and never used it since.
There might be discussions in march of this year or close to that time frame in the archives. The helpful person has not posted recently to my knowledge but knew a lot about dealing with LVMs.
All of your swap partitions and other filesystem dvisions are all contained in the LVM. The only partitions you should have are the one for windows, the /boot partition and the third partition should be where all of the LVM "partitions" or slices are kept. If you ran fdisk on the /dev/sdb device, you should have three partitions. Without dev-mapper, it does not show.
Good luck! It is possible, I just cannot remember the exact method that I used to get at the LVM.
Jim
Thanks for the detailed help, Jim! I'll give this a try later this morning after I recover from the New Year's party.
Bob
Robert L Cochran wrote:
I searched the archives for whatever I had to do in order to get the lvm activated. Here is one posting that I made:
https://www.redhat.com/archives/fedora-list/2005-April/msg01943.html
From an earlier posting someone suggested to run the following commands to activate and later deactivate LVM volumes in rescue mode. I used these commands on an external USB drive to get at data from a previous installation and it worked. You might be able to get at your data in this way. Jim
Excerpt from earlier help. Once booted into text-mode rescue, invoke the following commands:
lvm lvscan lvm vgchange -ay
This will scan for all LVM volumes and then will make them active and accessible.
lvm vgchange -an
will deactivate them all. end Excerpt:
Basically, the LVM volumes on the hard drive from an earlier install was labeled / for the main partition and this label being the same as my non-lvm clean install was also labeled /. When the kernel booted and the saw the same label, it ignored the LVM which contained the / and swap lvm content. To access the partition, I ran the lvscan and vgchange commands. I then had to make a mountpoint under /mnt to mount the LVM partition. I believe I got the information as /dev-mapper/volgroup00/<whatever> --- Sorry, I forgot what it is called, I no longer use LVM. I took that information of where the volume was and used mount /dev-mapper/volgroup00/<whatever> /mnt/olddrive and was able to access all the content from the LVM after mounting it. I transferred all of my desired information from the drive and never used it since.
There might be discussions in march of this year or close to that time frame in the archives. The helpful person has not posted recently to my knowledge but knew a lot about dealing with LVMs.
All of your swap partitions and other filesystem dvisions are all contained in the LVM. The only partitions you should have are the one for windows, the /boot partition and the third partition should be where all of the LVM "partitions" or slices are kept. If you ran fdisk on the /dev/sdb device, you should have three partitions. Without dev-mapper, it does not show.
Good luck! It is possible, I just cannot remember the exact method that I used to get at the LVM.
Jim
Thanks for the detailed help, Jim! I'll give this a try later this morning after I recover from the New Year's party.
Bob
It would probably be safer to wait until then. I hande over the computer to Linux tots for the evening and they stayed occupied with ppracer, neverball, super tux and the like. None of them were interested in accessing files on a drive configured with LVM.
Better luck in 2006
Jim
Jim Cornette wrote:
Robert L Cochran wrote:
I searched the archives for whatever I had to do in order to get the lvm activated. Here is one posting that I made:
https://www.redhat.com/archives/fedora-list/2005-April/msg01943.html
From an earlier posting someone suggested to run the following commands to activate and later deactivate LVM volumes in rescue mode. I used these commands on an external USB drive to get at data from a previous installation and it worked. You might be able to get at your data in this way. Jim
Excerpt from earlier help. Once booted into text-mode rescue, invoke the following commands:
lvm lvscan lvm vgchange -ay
This will scan for all LVM volumes and then will make them active and accessible.
lvm vgchange -an
will deactivate them all. end Excerpt:
Basically, the LVM volumes on the hard drive from an earlier install was labeled / for the main partition and this label being the same as my non-lvm clean install was also labeled /. When the kernel booted and the saw the same label, it ignored the LVM which contained the / and swap lvm content. To access the partition, I ran the lvscan and vgchange commands. I then had to make a mountpoint under /mnt to mount the LVM partition. I believe I got the information as /dev-mapper/volgroup00/<whatever> --- Sorry, I forgot what it is called, I no longer use LVM. I took that information of where the volume was and used mount /dev-mapper/volgroup00/<whatever> /mnt/olddrive and was able to access all the content from the LVM after mounting it. I transferred all of my desired information from the drive and never used it since.
There might be discussions in march of this year or close to that time frame in the archives. The helpful person has not posted recently to my knowledge but knew a lot about dealing with LVMs.
All of your swap partitions and other filesystem dvisions are all contained in the LVM. The only partitions you should have are the one for windows, the /boot partition and the third partition should be where all of the LVM "partitions" or slices are kept. If you ran fdisk on the /dev/sdb device, you should have three partitions. Without dev-mapper, it does not show.
Good luck! It is possible, I just cannot remember the exact method that I used to get at the LVM.
Jim
Thanks for the detailed help, Jim! I'll give this a try later this morning after I recover from the New Year's party.
Bob
It would probably be safer to wait until then. I hande over the computer to Linux tots for the evening and they stayed occupied with ppracer, neverball, super tux and the like. None of them were interested in accessing files on a drive configured with LVM.
Better luck in 2006
Jim
I'd like to follow up on this. Here is what I did.
1. Booted machine in rescue mode, using my install DVD, with the external USB drive containing my other FC4 system plugged in. 2. Executed 'chroot /mnt/sysimage'. 3. Ran 'lvm lvscan' as suggested. I got this output.
ACTIVE 'dev/VolGroup00/LogVol00' [370.53 GB] inherit ACTIVE 'dev/VolGroup00/LogVol01' [1.94 GB] inherit
The above logical volumes seem to reference my 400 Gb hard drive in my new, upgraded system, not the 60 Gb drive which is connected by USB.
I then unplugged the USB cable for my 60 Gb drive and re-plugged it in. Executing 'lvm lvscan' then got me this output:
/dev/sdb1: open failed: no such device or address /dev/sdb2: open failed: no such device or address /dev/sdb3: open failed: no such device or address
ACTIVE 'dev/VolGroup00/LogVol00' [370.53 GB] inherit ACTIVE 'dev/VolGroup00/LogVol01' [1.94 GB] inherit
Question: should I have manually mounted the partitions before issuing 'lvm lvscan'?
************ (Removed rescue CD, boot back into Fedora Core 4 on new system) ************
I then read the entire LVM how-to for lvm2 on tldp.org. It doesn't offer practical advice for this situation -- rescuing data from an older lvm-based system.
I also read 'man lvm', with no better results.
I then checked Bugzilla. There are 124 (or is it 125?) bugs listed for LVM.
It is looking more and more like I'll need to take out my 400 Gb drive and substitute my 60 Gb drive/120 Gb drive, and boot into that system, all to recover a little more data. Perhaps I need to quit using LVM.
Thanks
Bob Cochran
Robert L Cochran wrote:
Jim Cornette wrote:
Robert L Cochran wrote:
https://www.redhat.com/archives/fedora-list/2005-April/msg01943.html
From an earlier posting someone suggested to run the following commands to activate and later deactivate LVM volumes in rescue mode. I used these commands on an external USB drive to get at data from a previous installation and it worked. You might be able to get at your data in this way. Jim
lvm lvscan lvm vgchange -ay
I'd like to follow up on this. Here is what I did.
- Booted machine in rescue mode, using my install DVD, with the
external USB drive containing my other FC4 system plugged in.
I booted into my regular installation. I then ran 'lvm vgchange -ay' to activate the lvm volumes. I think that I did a pvscan to get the information about the available lvms.
- Executed 'chroot /mnt/sysimage'.
This would simple activate your system without all of the normally loaded tools. This is good information for if you needed to mount your system in rescue mode in the future.
- Ran 'lvm lvscan' as suggested. I got this output.
ACTIVE 'dev/VolGroup00/LogVol00' [370.53 GB] inherit ACTIVE 'dev/VolGroup00/LogVol01' [1.94 GB] inherit
The above logical volumes seem to reference my 400 Gb hard drive in my new, upgraded system, not the 60 Gb drive which is connected by USB.
The 'vgchange -ay' command might be needed to add additional volumes that might have labelling which conflict with your newly mounted system. lvscan might then recognize the volumes on the USB enclosure drive.
I then unplugged the USB cable for my 60 Gb drive and re-plugged it in. Executing 'lvm lvscan' then got me this output:
/dev/sdb1: open failed: no such device or address /dev/sdb2: open failed: no such device or address /dev/sdb3: open failed: no such device or address
/dev/sdb3 seems to be where your LVM is located.
ACTIVE 'dev/VolGroup00/LogVol00' [370.53 GB] inherit ACTIVE 'dev/VolGroup00/LogVol01' [1.94 GB] inherit
Question: should I have manually mounted the partitions before issuing 'lvm lvscan'?
I am not sure if it is possible to mount a partition with lvm volumes on it. I would imagine that filesystem is not correct would result from attempting to mount /dev/sdb3.
************ (Removed rescue CD, boot back into Fedora Core 4 on new system) ************
I then read the entire LVM how-to for lvm2 on tldp.org. It doesn't offer practical advice for this situation -- rescuing data from an older lvm-based system.
Go figure, real life situations never seem to match intended use for systm designs.
I also read 'man lvm', with no better results.
I then checked Bugzilla. There are 124 (or is it 125?) bugs listed for LVM.
It is looking more and more like I'll need to take out my 400 Gb drive and substitute my 60 Gb drive/120 Gb drive, and boot into that system, all to recover a little more data. Perhaps I need to quit using LVM.
Not adding a detour to those that use LVM, but adding a "me too" to LVM usage. If you do have to take drastic measures and re-install the drive from the USB enclosure, add this fact to the list. I did get this to work for once and recovered data from the drive contained in the USB enclosure. I really don't recall the exact steps that I took to get at the drive. It mounted and I did retrieve the information from the drive.
Since you have LVMs on your new system also, probably the dev/VolGroup00/LogVol00 identity is the same for both disks. It might have worked for me because I had no new LVMs on the running system.
Give system-config-lvm a try and see if you can manipulate the USB drive on a running system. If not, you may be out of luck and need to swap the drive out and backup your desired information onto a DVD or other media.
I'm sure the information is on the LVM, but in what format, I don't know. (dev/VolGroup00/LogVol00 also or different)
Jim
Thanks
Bob Cochran
Jim Cornette wrote:
Robert L Cochran wrote:
Jim Cornette wrote:
Robert L Cochran wrote:
https://www.redhat.com/archives/fedora-list/2005-April/msg01943.html
From an earlier posting someone suggested to run the following commands to activate and later deactivate LVM volumes in rescue mode. I used these commands on an external USB drive to get at data from a previous installation and it worked. You might be able to get at your data in this way. Jim
lvm lvscan lvm vgchange -ay
I'd like to follow up on this. Here is what I did.
- Booted machine in rescue mode, using my install DVD, with the
external USB drive containing my other FC4 system plugged in.
I booted into my regular installation. I then ran 'lvm vgchange -ay' to activate the lvm volumes. I think that I did a pvscan to get the information about the available lvms.
- Executed 'chroot /mnt/sysimage'.
This would simple activate your system without all of the normally loaded tools. This is good information for if you needed to mount your system in rescue mode in the future.
- Ran 'lvm lvscan' as suggested. I got this output.
ACTIVE 'dev/VolGroup00/LogVol00' [370.53 GB] inherit ACTIVE 'dev/VolGroup00/LogVol01' [1.94 GB] inherit
The above logical volumes seem to reference my 400 Gb hard drive in my new, upgraded system, not the 60 Gb drive which is connected by USB.
The 'vgchange -ay' command might be needed to add additional volumes that might have labelling which conflict with your newly mounted system. lvscan might then recognize the volumes on the USB enclosure drive.
I then unplugged the USB cable for my 60 Gb drive and re-plugged it in. Executing 'lvm lvscan' then got me this output:
/dev/sdb1: open failed: no such device or address /dev/sdb2: open failed: no such device or address /dev/sdb3: open failed: no such device or address
/dev/sdb3 seems to be where your LVM is located.
ACTIVE 'dev/VolGroup00/LogVol00' [370.53 GB] inherit ACTIVE 'dev/VolGroup00/LogVol01' [1.94 GB] inherit
Question: should I have manually mounted the partitions before issuing 'lvm lvscan'?
I am not sure if it is possible to mount a partition with lvm volumes on it. I would imagine that filesystem is not correct would result from attempting to mount /dev/sdb3.
************ (Removed rescue CD, boot back into Fedora Core 4 on new system) ************
I then read the entire LVM how-to for lvm2 on tldp.org. It doesn't offer practical advice for this situation -- rescuing data from an older lvm-based system.
Go figure, real life situations never seem to match intended use for systm designs.
I also read 'man lvm', with no better results.
I then checked Bugzilla. There are 124 (or is it 125?) bugs listed for LVM.
It is looking more and more like I'll need to take out my 400 Gb drive and substitute my 60 Gb drive/120 Gb drive, and boot into that system, all to recover a little more data. Perhaps I need to quit using LVM.
Not adding a detour to those that use LVM, but adding a "me too" to LVM usage. If you do have to take drastic measures and re-install the drive from the USB enclosure, add this fact to the list. I did get this to work for once and recovered data from the drive contained in the USB enclosure. I really don't recall the exact steps that I took to get at the drive. It mounted and I did retrieve the information from the drive.
Since you have LVMs on your new system also, probably the dev/VolGroup00/LogVol00 identity is the same for both disks. It might have worked for me because I had no new LVMs on the running system.
Give system-config-lvm a try and see if you can manipulate the USB drive on a running system. If not, you may be out of luck and need to swap the drive out and backup your desired information onto a DVD or other media.
I'm sure the information is on the LVM, but in what format, I don't know. (dev/VolGroup00/LogVol00 also or different)
Jim
Thanks
Bob Cochran
To continue the saga, I took my machine apart to investigate this and spent part of the evening swapping drives in and out. I really feel like I'm paying big for not understanding how LVM works -- and remaining in blissful ignorance for a couple of years, too.
My Asrock motherboard has an option for booting from USB, so I tried to boot my 60 Gb drive from USB (in order to avoid taking it out of the external enclosure.) This gave me a black screen with these letters:
LI
I have some memory that this is the word LINUX and how many letters of the word are spelled out on the screen indicate something about the nature of the boot problem. No doubt, to boot from USB, I need code that can speak USB-ese. So much for this option.
I took the drive out of the enclosure, and connected it to the motherboard's SATA connector (There are 3, and I used the one numbered SATA1.) I When I turned on the power, the exprected GRUB screen came up, and when I booted the 1653 kernel, a kernel panic resulted. I got this message:
Unable to find volume group "VolGroup00"
So now I'm confused. It looks to me like Grub is installed on my 60 Gb drive (that's why I got the nice splash screen) but the actual volume group is defined on my 120 Gb drive? This 120 Gb physical drive is (or was) really an older system. I thought I had one system installed on each of two different drives. I thought the 60 Gb drive was devoted to Fedora Core 4 and the 120 Gb drive was an older release, Fedora Core 3.
Bob Cochran
On 1/2/06, Robert L Cochran cochranb@speakeasy.net wrote:
Jim Cornette wrote:
My Asrock motherboard has an option for booting from USB, so I tried to boot my 60 Gb drive from USB (in order to avoid taking it out of the external enclosure.) This gave me a black screen with these letters:
LI
I have some memory that this is the word LINUX and how many letters of the word are spelled out on the screen indicate something about the nature of the boot problem.
If memory serves, the LI is part of the word LILO, the old LInux LOader that has been largely supplanted by GRUB. I wish I had more information to provide in helping solve your problem, but alas, I don't. I'm watching this thread with interest, though, but thus far it's only cementing my decision to abandon LVM in the future.
On January 2, 2006 21:54, Robert L Cochran wrote:
LI
I have some memory that this is the word LINUX and how many letters of the word are spelled out on the screen indicate something about the nature of the boot problem.
Hi Robert,
For the lilo prompt descriptions, I happen to have something on that:
Prompt Description L<nn> represents one of 16 disk-error codes. LI The second-stage boot loader loaded, but could not run. LIL? The descriptor table could not be read. LIL The second-stage boot loader loaded at an incorrect address. LIL- LILO found a corrupt descriptor table. LILO LILO ran successfully.
Hope this helps,
Phil
Phil Savoie wrote:
On January 2, 2006 21:54, Robert L Cochran wrote:
LI
I have some memory that this is the word LINUX and how many letters of the word are spelled out on the screen indicate something about the nature of the boot problem.
Hi Robert,
For the lilo prompt descriptions, I happen to have something on that:
Prompt Description L<nn> represents one of 16 disk-error codes. LI The second-stage boot loader loaded, but could not run. LIL? The descriptor table could not be read. LIL The second-stage boot loader loaded at an incorrect address. LIL- LILO found a corrupt descriptor table. LILO LILO ran successfully.
Hope this helps,
Phil
Thanks a lot. I'm quite puzzled because I haven't used LILO in years. I use Grub and have done so since it was first released -- in Redhat 8 or 9, I think.
Bob
Robert L Cochran wrote:
Jim Cornette wrote:
Robert L Cochran wrote:
Jim Cornette wrote:
Robert L Cochran wrote:
https://www.redhat.com/archives/fedora-list/2005-April/msg01943.html
From an earlier posting someone suggested to run the following commands to activate and later deactivate LVM volumes in rescue mode. I used these commands on an external USB drive to get at data from a previous installation and it worked. You might be able to get at your data in this way. Jim
lvm lvscan lvm vgchange -ay
I'd like to follow up on this. Here is what I did.
- Booted machine in rescue mode, using my install DVD, with the
external USB drive containing my other FC4 system plugged in.
I booted into my regular installation. I then ran 'lvm vgchange -ay' to activate the lvm volumes. I think that I did a pvscan to get the information about the available lvms.
- Executed 'chroot /mnt/sysimage'.
This would simple activate your system without all of the normally loaded tools. This is good information for if you needed to mount your system in rescue mode in the future.
- Ran 'lvm lvscan' as suggested. I got this output.
ACTIVE 'dev/VolGroup00/LogVol00' [370.53 GB] inherit ACTIVE 'dev/VolGroup00/LogVol01' [1.94 GB] inherit
The above logical volumes seem to reference my 400 Gb hard drive in my new, upgraded system, not the 60 Gb drive which is connected by USB.
The 'vgchange -ay' command might be needed to add additional volumes that might have labelling which conflict with your newly mounted system. lvscan might then recognize the volumes on the USB enclosure drive.
I then unplugged the USB cable for my 60 Gb drive and re-plugged it in. Executing 'lvm lvscan' then got me this output:
/dev/sdb1: open failed: no such device or address /dev/sdb2: open failed: no such device or address /dev/sdb3: open failed: no such device or address
/dev/sdb3 seems to be where your LVM is located.
ACTIVE 'dev/VolGroup00/LogVol00' [370.53 GB] inherit ACTIVE 'dev/VolGroup00/LogVol01' [1.94 GB] inherit
Question: should I have manually mounted the partitions before issuing 'lvm lvscan'?
I am not sure if it is possible to mount a partition with lvm volumes on it. I would imagine that filesystem is not correct would result from attempting to mount /dev/sdb3.
************ (Removed rescue CD, boot back into Fedora Core 4 on new system) ************
I then read the entire LVM how-to for lvm2 on tldp.org. It doesn't offer practical advice for this situation -- rescuing data from an older lvm-based system.
Go figure, real life situations never seem to match intended use for systm designs.
I also read 'man lvm', with no better results.
I then checked Bugzilla. There are 124 (or is it 125?) bugs listed for LVM.
It is looking more and more like I'll need to take out my 400 Gb drive and substitute my 60 Gb drive/120 Gb drive, and boot into that system, all to recover a little more data. Perhaps I need to quit using LVM.
Not adding a detour to those that use LVM, but adding a "me too" to LVM usage. If you do have to take drastic measures and re-install the drive from the USB enclosure, add this fact to the list. I did get this to work for once and recovered data from the drive contained in the USB enclosure. I really don't recall the exact steps that I took to get at the drive. It mounted and I did retrieve the information from the drive.
Since you have LVMs on your new system also, probably the dev/VolGroup00/LogVol00 identity is the same for both disks. It might have worked for me because I had no new LVMs on the running system.
Give system-config-lvm a try and see if you can manipulate the USB drive on a running system. If not, you may be out of luck and need to swap the drive out and backup your desired information onto a DVD or other media.
I'm sure the information is on the LVM, but in what format, I don't know. (dev/VolGroup00/LogVol00 also or different)
Jim
Thanks
Bob Cochran
To continue the saga, I took my machine apart to investigate this and spent part of the evening swapping drives in and out. I really feel like I'm paying big for not understanding how LVM works -- and remaining in blissful ignorance for a couple of years, too.
My Asrock motherboard has an option for booting from USB, so I tried to boot my 60 Gb drive from USB (in order to avoid taking it out of the external enclosure.) This gave me a black screen with these letters:
LI
I have some memory that this is the word LINUX and how many letters of the word are spelled out on the screen indicate something about the nature of the boot problem. No doubt, to boot from USB, I need code that can speak USB-ese. So much for this option.
I took the drive out of the enclosure, and connected it to the motherboard's SATA connector (There are 3, and I used the one numbered SATA1.) I When I turned on the power, the exprected GRUB screen came up, and when I booted the 1653 kernel, a kernel panic resulted. I got this message:
Unable to find volume group "VolGroup00"
So now I'm confused. It looks to me like Grub is installed on my 60 Gb drive (that's why I got the nice splash screen) but the actual volume group is defined on my 120 Gb drive? This 120 Gb physical drive is (or was) really an older system. I thought I had one system installed on each of two different drives. I thought the 60 Gb drive was devoted to Fedora Core 4 and the 120 Gb drive was an older release, Fedora Core 3.
Bob Cochran
I can't remember when I got this idea of adding a 60 Gb drive to my former system. But the drive was probably new at the time and had no data on it. The 120 Gb drive had a Fedora Core 3 system on it -- and maybe it was earlier than that, Fedora Core 2? My idea was to preserve everything on the 120 Gb drive and install a new Windows XP plus Fedora Core 3 system on the 60 Gb drive.
Maybe what happened is that the 120 Gb drive already had an LVM volume group on it, and when I added the 60 Gb drive the unpartitioned free space in it was being seen as an extension to that volume group. So it simply gobbled up the new physical volume. (I simply let the installer do what it wanted.) But LVM still let me treat the 60 Gb drive as if it were a separate physical volume. So to really see my home directory at last, I need to have both physical drives installed in my system. What interfaces I use (SATA or PATA) doesn't matter, but both drives are needed for me to see the /home directories. Does this make sense?
Bob Cochran
Robert L Cochran wrote:
I can't remember when I got this idea of adding a 60 Gb drive to my former system. But the drive was probably new at the time and had no data on it. The 120 Gb drive had a Fedora Core 3 system on it -- and maybe it was earlier than that, Fedora Core 2? My idea was to preserve everything on the 120 Gb drive and install a new Windows XP plus Fedora Core 3 system on the 60 Gb drive.
Maybe what happened is that the 120 Gb drive already had an LVM volume group on it, and when I added the 60 Gb drive the unpartitioned free space in it was being seen as an extension to that volume group. So it simply gobbled up the new physical volume. (I simply let the installer do what it wanted.) But LVM still let me treat the 60 Gb drive as if it were a separate physical volume. So to really see my home directory at last, I need to have both physical drives installed in my system. What interfaces I use (SATA or PATA) doesn't matter, but both drives are needed for me to see the /home directories. Does this make sense?
Bob Cochran
I believe that when you allow the installer to do as it pleases, it could come up with some scheme similar to your assumption. I however could not say for certain if one super LVM would be generated.
Jim
Robert L Cochran wrote:
Jim Cornette wrote:
Robert L Cochran wrote:
Jim Cornette wrote:
Robert L Cochran wrote:
https://www.redhat.com/archives/fedora-list/2005-April/msg01943.html
From an earlier posting someone suggested to run the following commands to activate and later deactivate LVM volumes in rescue mode. I used these commands on an external USB drive to get at data from a previous installation and it worked. You might be able to get at your data in this way. Jim
lvm lvscan lvm vgchange -ay
I'd like to follow up on this. Here is what I did.
- Booted machine in rescue mode, using my install DVD, with the
external USB drive containing my other FC4 system plugged in.
I booted into my regular installation. I then ran 'lvm vgchange -ay' to activate the lvm volumes. I think that I did a pvscan to get the information about the available lvms.
- Executed 'chroot /mnt/sysimage'.
This would simple activate your system without all of the normally loaded tools. This is good information for if you needed to mount your system in rescue mode in the future.
- Ran 'lvm lvscan' as suggested. I got this output.
ACTIVE 'dev/VolGroup00/LogVol00' [370.53 GB] inherit ACTIVE 'dev/VolGroup00/LogVol01' [1.94 GB] inherit
The above logical volumes seem to reference my 400 Gb hard drive in my new, upgraded system, not the 60 Gb drive which is connected by USB.
The 'vgchange -ay' command might be needed to add additional volumes that might have labelling which conflict with your newly mounted system. lvscan might then recognize the volumes on the USB enclosure drive.
I then unplugged the USB cable for my 60 Gb drive and re-plugged it in. Executing 'lvm lvscan' then got me this output:
/dev/sdb1: open failed: no such device or address /dev/sdb2: open failed: no such device or address /dev/sdb3: open failed: no such device or address
/dev/sdb3 seems to be where your LVM is located.
ACTIVE 'dev/VolGroup00/LogVol00' [370.53 GB] inherit ACTIVE 'dev/VolGroup00/LogVol01' [1.94 GB] inherit
Question: should I have manually mounted the partitions before issuing 'lvm lvscan'?
I am not sure if it is possible to mount a partition with lvm volumes on it. I would imagine that filesystem is not correct would result from attempting to mount /dev/sdb3.
************ (Removed rescue CD, boot back into Fedora Core 4 on new system) ************
I then read the entire LVM how-to for lvm2 on tldp.org. It doesn't offer practical advice for this situation -- rescuing data from an older lvm-based system.
Go figure, real life situations never seem to match intended use for systm designs.
I also read 'man lvm', with no better results.
I then checked Bugzilla. There are 124 (or is it 125?) bugs listed for LVM.
It is looking more and more like I'll need to take out my 400 Gb drive and substitute my 60 Gb drive/120 Gb drive, and boot into that system, all to recover a little more data. Perhaps I need to quit using LVM.
Not adding a detour to those that use LVM, but adding a "me too" to LVM usage. If you do have to take drastic measures and re-install the drive from the USB enclosure, add this fact to the list. I did get this to work for once and recovered data from the drive contained in the USB enclosure. I really don't recall the exact steps that I took to get at the drive. It mounted and I did retrieve the information from the drive.
Since you have LVMs on your new system also, probably the dev/VolGroup00/LogVol00 identity is the same for both disks. It might have worked for me because I had no new LVMs on the running system.
Give system-config-lvm a try and see if you can manipulate the USB drive on a running system. If not, you may be out of luck and need to swap the drive out and backup your desired information onto a DVD or other media.
I'm sure the information is on the LVM, but in what format, I don't know. (dev/VolGroup00/LogVol00 also or different)
Jim
Thanks
Bob Cochran
To continue the saga, I took my machine apart to investigate this and spent part of the evening swapping drives in and out. I really feel like I'm paying big for not understanding how LVM works -- and remaining in blissful ignorance for a couple of years, too.
Too bad Filipe is not active on the list. He seemed to know pretty much about it. I should become more familiar with the workings of LVM also. However, I deserted the concept and went with traditional partitioning.
My Asrock motherboard has an option for booting from USB, so I tried to boot my 60 Gb drive from USB (in order to avoid taking it out of the external enclosure.) This gave me a black screen with these letters:
LI
USB support for drives was not setup in Fedora/Redhat yet. There has to be USB drivers added to the initrd before it will boot. With USB support in BIOS, you are OK until the kernel takes over from BIOS. After the kernel starts to search for drives, no drives are found because of the chicken or egg syndrome. USB devices are needed before the USB drives are detected.
I have some memory that this is the word LINUX and how many letters of the word are spelled out on the screen indicate something about the nature of the boot problem. No doubt, to boot from USB, I need code that can speak USB-ese. So much for this option.
I took the drive out of the enclosure, and connected it to the motherboard's SATA connector (There are 3, and I used the one numbered SATA1.) I When I turned on the power, the exprected GRUB screen came up, and when I booted the 1653 kernel, a kernel panic resulted. I got this message:
Unable to find volume group "VolGroup00"
Do you have all the drives in the computer, the new system and the drive from the USB enclosure? I am not sure what your actual setup is.
Rescue discs are starting to sound appropriate now.
So now I'm confused. It looks to me like Grub is installed on my 60 Gb drive (that's why I got the nice splash screen) but the actual volume group is defined on my 120 Gb drive? This 120 Gb physical drive is (or was) really an older system. I thought I had one system installed on each of two different drives. I thought the 60 Gb drive was devoted to Fedora Core 4 and the 120 Gb drive was an older release, Fedora Core 3.
With the LABEL and the way different BIOS versions work, it is easy to become confused on what device is the actual booting device.
Bob Cochran
I just remembered that there is a tool called system-config-lvm which launched fine when I launched it. The tool looks intuitive and might be an easier way to get at the lvm on the USB device.
give it a try.
Jim
-
Charles Curley -
J. K. Cliburn -
Jim Cornette -
Phil Savoie -
Robert L Cochran