Hi,
This is my first post on this list, so please bear with me.
I've been trying to get a new 64-bit Fedora 17 installation to recognize an older disk that contains a 32-bit installation. I had installed the 32-bit version on my older Intel-based machine, but recently decided to replace the motherboard and CPU with 64-bit stuff, and get a new hard disk for the 64-bit system. I have many files on the 32-bit disk that I'd like to be able to access on the new 64-bit system, but so far I have not been able to mount the old disk. I've tried various "mount" commands with no success. I don't really understand the error messages when I try to mount the old disk.
Any help will be greatly appreciated.
Below is some information from the 64-bit installation that I think is relevant.
Here I'm trying to mount the old system: ########### [root@alan-fedora alan]# mount /dev/sdc /mnt/fedora32 mount: wrong fs type, bad option, bad superblock on /dev/sdc, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so [root@alan-fedora alan]# mount -t auto /dev/sdc /mnt/fedora32 mount: wrong fs type, bad option, bad superblock on /dev/sdc, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so
I've already created the /mnt/fedora32 mount point: ########### [root@alan-fedora alan]# ls -l /mnt total 4 drwxr-xr-x. 2 root root 4096 Nov 4 11:02 fedora32 [root@alan-fedora alan]# fdisk -l ###########
Here's what "fdisk -l" shows. /dev/sda is not used yet. /dev/sdc is the old 32-bit installation disk. /dev/sdb contains the new 64-bit installation. ########### Disk /dev/sda: 256.1 GB, 256060514304 bytes 255 heads, 63 sectors/track, 31130 cylinders, total 500118192 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000479af
Device Boot Start End Blocks Id System
WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000
Device Boot Start End Blocks Id System /dev/sdb1 * 1 4294967295 2147483647+ ee GPT Partition 1 does not start on physical sector boundary.
Disk /dev/sdc: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders, total 2930277168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x0006e27f
Device Boot Start End Blocks Id System /dev/sdc1 * 2048 206847 102400 83 Linux /dev/sdc2 1026048 2930276351 1464625152 8e Linux LVM
Disk /dev/mapper/vg_alan--fedora-lv_swap: 18.7 GB, 18656264192 bytes 255 heads, 63 sectors/track, 2268 cylinders, total 36438016 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/mapper/vg_alan--fedora-lv_root: 53.7 GB, 53687091200 bytes 255 heads, 63 sectors/track, 6527 cylinders, total 104857600 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/mapper/vg_alan--fedora-lv_home: 2927.7 GB, 2927691300864 bytes 255 heads, 63 sectors/track, 355938 cylinders, total 5718147072 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes ###########
I think that one thing that's happening is that the LVM software is getting confused by the fact that both the 32-bit and 64-bit installations have the same names for the LVM volumes (or whatever the proper terminology is). But I don't know what to do to straighten out the confusion.
Thanks, Alan
Am 04.11.2012 18:46, schrieb Alan Feuerbacher:
I have many files on the 32-bit disk that I'd like to be able to access on the new 64-bit system, but so far I have not been able to mount the old disk. I've tried various "mount" commands with no success. I don't really understand the error messages when I try to mount the old disk.
first: there is no difference in the filesystem between i686/x86_64
[root@alan-fedora alan]# mount /dev/sdc /mnt/fedora32 mount: wrong fs type, bad option, bad superblock on /dev/sdc, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so
/dev/sdc != /dev/sdc1
why do you try to mount the whole disk instead a partitionwith a filesystem on it?
I think that one thing that's happening is that the LVM software is getting confused by the fact that both the 32-bit and 64-bit installations have the same names for the LVM volumes (or whatever the proper terminology is). But I don't know what to do to straighten out the confusion
that may be, but above you do NOT try to access any LVM you try to mount the whole disk
On 4 November 2012 17:46, Alan Feuerbacher alanf00@comcast.net wrote:
[root@alan-fedora alan]# mount /dev/sdc /mnt/fedora32
Wrong. /dev/sdc1 or /dev/sdc2. Also you can do a pvscan and then check out what logical volumes you have and mount the volumes.
Allegedly, on or about 04 November 2012, Alan Feuerbacher sent:
Here I'm trying to mount the old system: ########### [root@alan-fedora alan]# mount /dev/sdc /mnt/fedora32 mount: wrong fs type, bad option, bad superblock on /dev/sdc, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so
[root@alan-fedora alan]# mount -t auto /dev/sdc /mnt/fedora32
Firstly, it was already doing "auto," as far as I'm aware, so that's pretty much redundant. What's really missing is *which* partition to try and mount on sdc.
Device Boot Start End Blocks Id System /dev/sdc1 * 2048 206847 102400 83 Linux /dev/sdc2 1026048 2930276351 1464625152 8e Linux LVM
The small sdc1 is, most likely, a boot partition, which you can ignore. You want to be trying to mount sdc2.
However, that's LVM, not a plain partition, and I'm fairly certain that you want to use the LVM tools to mount it. And, I'm very certain that you're going to have problems if it uses the same volume names as your new drive that you're running from. The simplest solution will probably be to rename your old volumes before you attempt to mount them.
So, look into managing LVM volumes, then get back to the list when you get stuck again. (It's ages since I've tried anything with LVM, it's probably changed since then, and I've probably forgotten what I did.)
Future hint: Next time you create LVM volumes and partitions, put something unique into their names. A date, a name, or a number...
But if you never intend to try and span across several discs, which brings about its own set of hazards (one failure on any disc, and all of them becomes wrecked), I'd advise to completely avoid LVM on your next installation.
On 11/4/2012 1:07 PM, Hakan Koseoglu wrote:
[root@alan-fedora alan]# mount /dev/sdc /mnt/fedora32
Wrong. /dev/sdc1 or /dev/sdc2. Also you can do a pvscan and then check out what logical volumes you have and mount the volumes.
Thank you! I was able to mount /dev/sdc1 and look at the files there. This corresponds to /boot.
I did a pvscan and it came up with this:
######### PV /dev/sdb3 VG vg_alan-fedora lvm2 [2.73 TiB / 0 free] Total: 1 [2.73 TiB] in use: 1 [2.73 TiB] / in no VG: 0 [0 ] #########
Why is /dev/sdc not displayed? Even when fdisk shows it as an LVM volume?
I'm really confused by this.
Alan
Try with lsblk -f
2012/11/4 Alan Feuerbacher alanf00@comcast.net
On 11/4/2012 1:07 PM, Hakan Koseoglu wrote:
[root@alan-fedora alan]# mount /dev/sdc /mnt/fedora32
Wrong. /dev/sdc1 or /dev/sdc2. Also you can do a pvscan and then check out what logical volumes you have and mount the volumes.
Thank you! I was able to mount /dev/sdc1 and look at the files there. This corresponds to /boot.
I did a pvscan and it came up with this:
######### PV /dev/sdb3 VG vg_alan-fedora lvm2 [2.73 TiB / 0 free] Total: 1 [2.73 TiB] in use: 1 [2.73 TiB] / in no VG: 0 [0 ] #########
Why is /dev/sdc not displayed? Even when fdisk shows it as an LVM volume?
I'm really confused by this.
Alan
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.**org/mailman/listinfo/usershttps://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/**Mailing_list_guidelineshttp://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On 11/4/2012 1:33 PM, Alchemist wrote:
Try with lsblk -f
I did a pvscan and it came up with this: ######### PV /dev/sdb3 VG vg_alan-fedora lvm2 [2.73 TiB / 0 free] Total: 1 [2.73 TiB] in use: 1 [2.73 TiB] / in no VG: 0 [0 ] ######### Why is /dev/sdc not displayed? Even when fdisk shows it as an LVM volume?
Here's the output:
############### [root@alan-fedora lvmdump.dump1]# lsblk -f NAME FSTYPE LABEL UUID MOUNTPOINT sda
sdb
├─sdb1
├─sdb2 ext4 f3ef71bf-f58d-4312-abcb-7dd514aab661 /boot └─sdb3 LVM2_member z00IIw-k1Ie-y8Uy-9ovN-pqZz-k2GR-kDItHD ├─vg_alan--fedora-lv_swap (dm-0) swap b4c7d2e0-cafd-4527-8e69-b9c883e579e9 [SWAP] ├─vg_alan--fedora-lv_root (dm-1) ext4 _Fedora-17-x86_6 423b85c7-4a96-4699-8ff0-4a0b5c643d26 / └─vg_alan--fedora-lv_home (dm-2) ext4 05aa4b62-5c63-4ee3-aa7c-f742c7d971cb /home sdc
├─sdc1 ext4 1878d5d2-9135-470d-bc57-634fe7f979e8 /mnt/fedora32 └─sdc2
sr0 ###############
As you can see, lsblk displays information about /dev/sdc, and shows the mount that I did earlier ("mount /dev/sdc1 /mnt/fedora32"), and shows sdc1 as an ext4 filesystem, but shows nothing about sdc2 other than that it exists. Any suggestions?
Alan
Am 04.11.2012 20:02, schrieb Alan Feuerbacher:
On 11/4/2012 1:33 PM, Alchemist wrote:
Try with lsblk -f
I did a pvscan and it came up with this: ######### PV /dev/sdb3 VG vg_alan-fedora lvm2 [2.73 TiB / 0 free] Total: 1 [2.73 TiB] in use: 1 [2.73 TiB] / in no VG: 0 [0 ] ######### Why is /dev/sdc not displayed? Even when fdisk shows it as an LVM volume?Here's the output:
############### [root@alan-fedora lvmdump.dump1]# lsblk -f NAME FSTYPE LABEL UUID MOUNTPOINT sda sdb ├─sdb1 ├─sdb2 ext4 f3ef71bf-f58d-4312-abcb-7dd514aab661 /boot └─sdb3 LVM2_member z00IIw-k1Ie-y8Uy-9ovN-pqZz-k2GR-kDItHD ├─vg_alan--fedora-lv_swap (dm-0) swap b4c7d2e0-cafd-4527-8e69-b9c883e579e9 [SWAP] ├─vg_alan--fedora-lv_root (dm-1) ext4 _Fedora-17-x86_6 423b85c7-4a96-4699-8ff0-4a0b5c643d26 / └─vg_alan--fedora-lv_home (dm-2) ext4 05aa4b62-5c63-4ee3-aa7c-f742c7d971cb /home sdc ├─sdc1 ext4 1878d5d2-9135-470d-bc57-634fe7f979e8 /mnt/fedora32 └─sdc2 sr0 ###############
As you can see, lsblk displays information about /dev/sdc, and shows the mount that I did earlier ("mount /dev/sdc1 /mnt/fedora32"), and shows sdc1 as an ext4 filesystem, but shows nothing about sdc2 other than that it exists. Any suggestions?
so are you sure that the old setup used LVM at all? you said "/dev/sdc1" looks like /boot of the old install so i bet /dev/sdc2 is the system-disk and if you did not have a seperated /home what else do you search?
On 11/4/2012 1:10 PM, Tim wrote:
Firstly, it was already doing "auto," as far as I'm aware, so that's pretty much redundant. What's really missing is *which* partition to try and mount on sdc.
Device Boot Start End Blocks Id System/dev/sdc1 * 2048 206847 102400 83 Linux /dev/sdc2 1026048 2930276351 1464625152 8e Linux LVM
The small sdc1 is, most likely, a boot partition, which you can ignore.
That's right. sdc2 contains the data I want to retrieve.
You want to be trying to mount sdc2.
However, that's LVM, not a plain partition, and I'm fairly certain that you want to use the LVM tools to mount it. And, I'm very certain that you're going to have problems if it uses the same volume names as your new drive that you're running from. The simplest solution will probably be to rename your old volumes before you attempt to mount them.
That sounds very reasonable. Unfortunately, after looking at the man page for lvm and its associated sub-programs, and trying a number of them, I can't find anything that looks like it might work.
The basic problem is that the lvm tools don't seem to recognize sdc2 as an LVM partition. I don't understand why, because that disk was formatted by the Fedora installer. It was a completely vanilla installation, so far as I know. I'm still at a loss here.
So, look into managing LVM volumes, then get back to the list when you get stuck again. (It's ages since I've tried anything with LVM, it's probably changed since then, and I've probably forgotten what I did.)
Anything you can remember could be very helpful.
Future hint: Next time you create LVM volumes and partitions, put something unique into their names. A date, a name, or a number...
Well, whatever is there was chosen by the Fedora installer when I installed the 32-bit system some days ago.
But if you never intend to try and span across several discs, which brings about its own set of hazards (one failure on any disc, and all of them becomes wrecked), I'd advise to completely avoid LVM on your next installation.
I more or less tried that on my old 32-bit system. I installed a new disk and installed Fedora on a non-LVM partition. It could not see the LVM partition on the older disk -- same problem as I have now.
Thanks for your help.
Alan
On 4 Nov 2012 at 14:02, Alan Feuerbacher wrote:
Date sent: Sun, 04 Nov 2012 14:02:55 -0500 From: Alan Feuerbacher alanf00@comcast.net To: users@lists.fedoraproject.org Subject: Re: New 64-bit Fedora Will Not Mount Similar 32-bit Filesystem
On 11/4/2012 1:33 PM, Alchemist wrote:
Try with lsblk -f
I did a pvscan and it came up with this: ######### PV /dev/sdb3 VG vg_alan-fedora lvm2 [2.73 TiB / 0 free] Total: 1 [2.73 TiB] in use: 1 [2.73 TiB] / in no VG: 0 [0 ] ######### Why is /dev/sdc not displayed? Even when fdisk shows it as an LVM volume?Here's the output:
############### [root@alan-fedora lvmdump.dump1]# lsblk -f NAME FSTYPE LABEL UUID MOUNTPOINT sda
sdb
├─sdb1
├─sdb2 ext4 f3ef71bf-f58d-4312-abcb-7dd514aab661 /boot └─sdb3 LVM2_member z00IIw-k1Ie-y8Uy-9ovN-pqZz-k2GR-kDItHD ├─vg_alan--fedora-lv_swap (dm-0) swap b4c7d2e0-cafd-4527-8e69-b9c883e579e9 [SWAP] ├─vg_alan--fedora-lv_root (dm-1) ext4 _Fedora-17-x86_6 423b85c7-4a96-4699-8ff0-4a0b5c643d26 / └─vg_alan--fedora-lv_home (dm-2) ext4 05aa4b62-5c63-4ee3-aa7c-f742c7d971cb /home sdc
├─sdc1 ext4 1878d5d2-9135-470d-bc57-634fe7f979e8 /mnt/fedora32 └─sdc2
sr0 ###############
As you can see, lsblk displays information about /dev/sdc, and shows the mount that I did earlier ("mount /dev/sdc1 /mnt/fedora32"), and shows sdc1 as an ext4 filesystem, but shows nothing about sdc2 other than that it exists. Any suggestions?
Alan
Since the sdc2 is an lvm partition, you don't mount it via the mount command. You need to mount the lvm partitions within it.
What does cat /proc/partitions show.
On my system I get this. major minor #blocks name
8 0 488386584 sda 8 1 204800 sda1 8 2 32696288 sda2 8 3 455482912 sda3 253 0 27123712 dm-0 253 1 5570560 dm-1
sda is the disk sda1 is the boot partition sda2 is the lvm partition sda3 os another partition dm-0 is the root partition of the LVM dm-1 is the swap partition
sfdisk -l will report on the disk
Another command that shows info.
blkid
/dev/sda1: UUID="4cf2b9e4-4c23-4060-be46-811b4a62c4a5" SEC_TYPE="ext2" TYPE="ext3" /dev/sda2: UUID="Vcje2C-yBVj-BucG-979I-aVYF-sKMt-rvEi4X" TYPE="LVM2_member" /dev/dm-0: UUID="77b3e1ee-3302-4a1d-83c1-7fd84399bf2f" TYPE="ext4" /dev/dm-1: TYPE="swap" UUID="55dba510-1d21-4c4d-b80c-878d709c3192" /dev/mapper/vg_setzco-lv_swap: TYPE="swap" UUID="55dba510-1d21-4c4d-b80c-878d709c3192" /dev/mapper/vg_setzco-lv_root: UUID="77b3e1ee-3302-4a1d-83c1-7fd84399bf2f" TYPE="ext4" /dev/sda3: UUID="5e369c30-713b-4d7a-9bce-10ddaefb41f5" SEC_TYPE="ext2" TYPE="ext3" /dev/root: UUID="77b3e1ee-3302-4a1d-83c1-7fd84399bf2f" TYPE="ext4"
You might be able to mount the partition by doing something like. mount /dev/dm-0 /mnt/mountpoint
There may be an issue if both lvm partitions have the same names as you current systems. I don't think it will allow that, you have to jump thru some hops to make the names different. On my newer systems I don't use LVM.
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
+----------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor Guam Community College Computer Center mailto:mikes@kuentos.guam.net mailto:msetzerii@gmail.com http://www.guam.net/home/mikes Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ +----------------------------------------------------------+
http://setiathome.berkeley.edu (Original) Number of Seti Units Returned: 19,471 Processing time: 32 years, 290 days, 12 hours, 58 minutes (Total Hours: 287,489)
BOINC@HOME CREDITS SETI 13222158.441100 | EINSTEIN 8998518.969852 ROSETTA 5280097.220867 | ABC 15413680.757493
On 11/4/2012 2:07 PM, Reindl Harald wrote:
As you can see, lsblk displays information about /dev/sdc, and shows the mount that I did earlier ("mount /dev/sdc1 /mnt/fedora32"), and shows sdc1 as an ext4 filesystem, but shows nothing about sdc2 other than that it exists. Any suggestions?
so are you sure that the old setup used LVM at all?
Absolutely. I didn't mention this, but during the last several days I've tried a lot of different things to be able to look at the files on /dev/sdc, and there were plenty of confirmations of that. Furthermore, after the 32-bit installation was done, I often looked at the output of fdisk, and it ALWAYS showed LVM information -- pretty much the same information as fdisk now shows about the 64-bit installation, except for differences in the physical attibutes of the hard disks.
you said "/dev/sdc1" looks like /boot of the old install so i bet /dev/sdc2 is the system-disk and if you did not have a seperated /home what else do you search?
I don't really understand your question. But when I did fdisk on the 32-bit system (when it was up and running; it's disassembled now), /dev/sdc1 was always listed as /boot. And /dev/sdc2 was always broken up into the logical volumes /, swap and /home -- just like the new 64-bit installation is.
Alan
On 11/04/2012 02:22 PM, Alan Feuerbacher wrote:
On 11/4/2012 2:07 PM, Reindl Harald wrote:
As you can see, lsblk displays information about /dev/sdc, and shows the mount that I did earlier ("mount /dev/sdc1 /mnt/fedora32"), and shows sdc1 as an ext4 filesystem, but shows nothing about sdc2 other than that it exists. Any suggestions?
so are you sure that the old setup used LVM at all?
Absolutely. I didn't mention this, but during the last several days I've tried a lot of different things to be able to look at the files on /dev/sdc, and there were plenty of confirmations of that. Furthermore, after the 32-bit installation was done, I often looked at the output of fdisk, and it ALWAYS showed LVM information -- pretty much the same information as fdisk now shows about the 64-bit installation, except for differences in the physical attibutes of the hard disks.
you said "/dev/sdc1" looks like /boot of the old install so i bet /dev/sdc2 is the system-disk and if you did not have a seperated /home what else do you search?
I don't really understand your question. But when I did fdisk on the 32-bit system (when it was up and running; it's disassembled now), /dev/sdc1 was always listed as /boot. And /dev/sdc2 was always broken up into the logical volumes /, swap and /home -- just like the new 64-bit installation is.
Alan
For what it's worth, I switched from 32-bit F14 to 64-bit F17. I retained the same LVM and physical-volume setup from before. I kept my /home partition (actually a logical volume) and reformatted everything else. I had no problems at all. Of course, I used Anaconda on a KDE Live Spin to do the up-conversion. But I'm not sure why I should succeed where the OP failed.
Temlakos
2012/11/4 Alan Feuerbacher alanf00@comcast.net
On 11/4/2012 1:10 PM, Tim wrote:
Firstly, it was already doing "auto," as far as I'm aware, so that's
pretty much redundant. What's really missing is *which* partition to try and mount on sdc.
Device Boot Start End Blocks Id System/dev/sdc1 * 2048 206847 102400 83 Linux /dev/sdc2 1026048 2930276351 1464625152 8e Linux LVM
The small sdc1 is, most likely, a boot partition, which you can ignore.
That's right. sdc2 contains the data I want to retrieve.
You want to be trying to mount sdc2.
However, that's LVM, not a plain partition, and I'm fairly certain that you want to use the LVM tools to mount it. And, I'm very certain that you're going to have problems if it uses the same volume names as your new drive that you're running from. The simplest solution will probably be to rename your old volumes before you attempt to mount them.
That sounds very reasonable. Unfortunately, after looking at the man page for lvm and its associated sub-programs, and trying a number of them, I can't find anything that looks like it might work.
The basic problem is that the lvm tools don't seem to recognize sdc2 as an LVM partition. I don't understand why, because that disk was formatted by the Fedora installer. It was a completely vanilla installation, so far as I know. I'm still at a loss here.
So, look into managing LVM volumes, then get back to the list when you
get stuck again. (It's ages since I've tried anything with LVM, it's probably changed since then, and I've probably forgotten what I did.)
Anything you can remember could be very helpful.
Future hint: Next time you create LVM volumes and partitions, put
something unique into their names. A date, a name, or a number...
Well, whatever is there was chosen by the Fedora installer when I installed the 32-bit system some days ago.
But if you never intend to try and span across several discs, which
brings about its own set of hazards (one failure on any disc, and all of them becomes wrecked), I'd advise to completely avoid LVM on your next installation.
I more or less tried that on my old 32-bit system. I installed a new disk and installed Fedora on a non-LVM partition. It could not see the LVM partition on the older disk -- same problem as I have now.
Thanks for your help.
Ok lets try
shell# pvs
you must see line /dev/sdc2 and its VG name
shell# vgscan shell# vgchange -a y "VG name from pvs output" shell# lvscan here goes your ACTIVE "/dev/***" output shell# mnt "/dev/***" /mnt/fedora32
Alan
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.**org/mailman/listinfo/usershttps://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/**Mailing_list_guidelineshttp://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On 11/4/2012 2:20 PM, Michael D. Setzer II wrote:
That's very useful input. Here's a lot of output based on it:
############## [root@alan-fedora ~]# cat /proc/partitions major minor #blocks name
8 0 250059096 sda 8 16 2930266584 sdb 8 17 1024 sdb1 8 18 512000 sdb2 8 19 2929752064 sdb3 8 32 1465138584 sdc 8 33 102400 sdc1 8 34 1464625152 sdc2 11 0 1048575 sr0 253 0 18219008 dm-0 253 1 52428800 dm-1 253 2 2859073536 dm-2 ##############
The last three lines correspond to /dev/sdb which is where the new 64-bit Fedora is.
############## [root@alan-fedora ~]# sfdisk -l
Disk /dev/sda: 31130 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System /dev/sda1 0 - 0 0 0 Empty /dev/sda2 0 - 0 0 0 Empty /dev/sda3 0 - 0 0 0 Empty /dev/sda4 0 - 0 0 0 Empty
WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util sfdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sdb: 364801 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System /dev/sdb1 * 0+ 267349- 267350- 2147483647+ ee GPT sfdisk: start: (c,h,s) expected (0,0,2) found (0,0,1)
/dev/sdb2 0 - 0 0 0 Empty /dev/sdb3 0 - 0 0 0 Empty /dev/sdb4 0 - 0 0 0 Empty
Disk /dev/sdc: 182401 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System /dev/sdc1 * 0+ 12- 13- 102400 83 Linux /dev/sdc2 63+ 182401- 182338- 1464625152 8e Linux LVM /dev/sdc3 0 - 0 0 0 Empty /dev/sdc4 0 - 0 0 0 Empty
Disk /dev/mapper/vg_alan--fedora-lv_swap: 2268 cylinders, 255 heads, 63 sectors/track
sfdisk: ERROR: sector 0 does not have an msdos signature sfdisk: /dev/mapper/vg_alan--fedora-lv_swap: unrecognized partition table type
sfdisk: No partitions found
Disk /dev/mapper/vg_alan--fedora-lv_root: 6527 cylinders, 255 heads, 63 sectors/track
sfdisk: ERROR: sector 0 does not have an msdos signature sfdisk: /dev/mapper/vg_alan--fedora-lv_root: unrecognized partition table typesfdisk: No partitions found
Disk /dev/mapper/vg_alan--fedora-lv_root: 6527 cylinders, 255 heads, 63 sectors/track
sfdisk: ERROR: sector 0 does not have an msdos signature sfdisk: /dev/mapper/vg_alan--fedora-lv_root: unrecognized partition table type
sfdisk: No partitions found
Disk /dev/mapper/vg_alan--fedora-lv_home: 355938 cylinders, 255 heads, 63 sectors/track
sfdisk: ERROR: sector 0 does not have an msdos signature sfdisk: /dev/mapper/vg_alan--fedora-lv_home: unrecognized partition table type
sfdisk: No partitions found ##############
I'm not sure what to make of the above, but sfdisk says to use GNU parted, so:
Here's what GNU parted gives: ############## [root@alan-fedora ~]# parted -l Model: ATA SAMSUNG SSD 830 (scsi) Disk /dev/sda: 256GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags:
Number Start End Size Type File system Flags
Model: ATA WDC WD30EZRX-00M (scsi) Disk /dev/sdb: 3001GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Disk Flags: pmbr_boot
Number Start End Size File system Name Flags 1 1049kB 2097kB 1049kB bios_grub 2 2097kB 526MB 524MB ext4 3 526MB 3001GB 3000GB lvm
Model: ATA WDC WD15EARX-00P (scsi) Disk /dev/sdc: 1500GB Sector size (logical/physical): 512B/4096B Partition Table: msdos Disk Flags:
Number Start End Size Type File system Flags 1 1049kB 106MB 105MB primary ext4 boot 2 525MB 1500GB 1500GB primary lvm
Model: Linux device-mapper (linear) (dm) Disk /dev/mapper/vg_alan--fedora-lv_home: 2928GB Sector size (logical/physical): 512B/4096B Partition Table: loop Disk Flags:
Number Start End Size File system Flags 1 0.00B 2928GB 2928GB ext4
Model: Linux device-mapper (linear) (dm) Disk /dev/mapper/vg_alan--fedora-lv_root: 53.7GB Sector size (logical/physical): 512B/4096B Partition Table: loop Disk Flags:
Number Start End Size File system Flags 1 0.00B 53.7GB 53.7GB ext4
Model: Linux device-mapper (linear) (dm) Disk /dev/mapper/vg_alan--fedora-lv_swap: 18.7GB Sector size (logical/physical): 512B/4096B Partition Table: loop Disk Flags:
Number Start End Size File system Flags 1 0.00B 18.7GB 18.7GB linux-swap(v1) ##############
Here's another command you suggested: ############## [root@alan-fedora ~]# blkid /dev/sdb2: UUID="f3ef71bf-f58d-4312-abcb-7dd514aab661" TYPE="ext4" /dev/sdb3: UUID="z00IIw-k1Ie-y8Uy-9ovN-pqZz-k2GR-kDItHD" TYPE="LVM2_member" /dev/sdc1: UUID="1878d5d2-9135-470d-bc57-634fe7f979e8" TYPE="ext4" /dev/mapper/vg_alan--fedora-lv_swap: UUID="b4c7d2e0-cafd-4527-8e69-b9c883e579e9" TYPE="swap" /dev/mapper/vg_alan--fedora-lv_root: LABEL="_Fedora-17-x86_6" UUID="423b85c7-4a96-4699-8ff0-4a0b5c643d26" TYPE="ext4" /dev/mapper/vg_alan--fedora-lv_home: UUID="05aa4b62-5c63-4ee3-aa7c-f742c7d971cb" TYPE="ext4" ##############
To be complete, here's the contents of /etc/fstab: ############## [root@alan-fedora ~]# cat /etc/fstab
# # /etc/fstab # Created by anaconda on Sun Nov 4 05:47:26 2012 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # /dev/mapper/vg_alan--fedora-lv_root / ext4 defaults 1 1 UUID=f3ef71bf-f58d-4312-abcb-7dd514aab661 /boot ext4 defaults 1 2 /dev/mapper/vg_alan--fedora-lv_home /home ext4 defaults 1 2 /dev/mapper/vg_alan--fedora-lv_swap swap swap defaults 0 0 ##############
And here's what mount gives: ############## [root@alan-fedora ~]# mount -l proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime,seclabel) devtmpfs on /dev type devtmpfs (rw,nosuid,seclabel,size=8051124k,nr_inodes=2012781,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,seclabel,gid=5,mode=620,ptmxmode=000) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,seclabel) tmpfs on /run type tmpfs (rw,nosuid,nodev,seclabel,mode=755) /dev/mapper/vg_alan--fedora-lv_root on / type ext4 (rw,relatime,seclabel,data=ordered) [_Fedora-17-x86_6] securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime) tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,seclabel,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=26,pgrp=1,timeout=300,minproto=5,maxproto=5,direct) configfs on /sys/kernel/config type configfs (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,seclabel) tmpfs on /media type tmpfs (rw,nosuid,nodev,noexec,relatime,seclabel,mode=755) mqueue on /dev/mqueue type mqueue (rw,relatime,seclabel) /dev/sdb2 on /boot type ext4 (rw,relatime,seclabel,stripe=4,data=ordered) /dev/mapper/vg_alan--fedora-lv_home on /home type ext4 (rw,relatime,seclabel,data=ordered) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) gvfs-fuse-daemon on /run/user/alan/gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000) /dev/sdc1 on /mnt/fedora32 type ext4 (rw,relatime,seclabel,stripe=4,data=ordered) ##############
The comments in /etc/fstab suggested looking at /dev/disk, so: ############## [alan@alan-fedora Building]$ man findfs [alan@alan-fedora Building]$ cd /dev/disk [alan@alan-fedora disk]$ ls by-id by-label by-partuuid by-uuid [alan@alan-fedora disk]$ ls -l total 0 drwxr-xr-x. 2 root root 500 Nov 4 11:29 by-id drwxr-xr-x. 2 root root 60 Nov 4 11:29 by-label drwxr-xr-x. 2 root root 100 Nov 4 11:29 by-partuuid drwxr-xr-x. 2 root root 140 Nov 4 11:29 by-uuid [alan@alan-fedora disk]$ cd by-uuid [alan@alan-fedora by-uuid]$ ls 05aa4b62-5c63-4ee3-aa7c-f742c7d971cb 423b85c7-4a96-4699-8ff0-4a0b5c643d26 f3ef71bf-f58d-4312-abcb-7dd514aab661 1878d5d2-9135-470d-bc57-634fe7f979e8 b4c7d2e0-cafd-4527-8e69-b9c883e579e9 [alan@alan-fedora by-uuid]$ ls -l total 0 lrwxrwxrwx. 1 root root 10 Nov 4 14:39 05aa4b62-5c63-4ee3-aa7c-f742c7d971cb -> ../../dm-2 lrwxrwxrwx. 1 root root 10 Nov 4 11:29 1878d5d2-9135-470d-bc57-634fe7f979e8 -> ../../sdc1 lrwxrwxrwx. 1 root root 10 Nov 4 14:39 423b85c7-4a96-4699-8ff0-4a0b5c643d26 -> ../../dm-1 lrwxrwxrwx. 1 root root 10 Nov 4 14:39 b4c7d2e0-cafd-4527-8e69-b9c883e579e9 -> ../../dm-0 lrwxrwxrwx. 1 root root 10 Nov 4 11:29 f3ef71bf-f58d-4312-abcb-7dd514aab661 -> ../../sdb2 [alan@alan-fedora by-uuid]$ cd ../by-id [alan@alan-fedora by-id]$ ls -l total 0 lrwxrwxrwx. 1 root root 9 Nov 4 11:29 ata-HL-DT-ST_BD-RE_BH14NS40_8KC3T51A20_3 -> ../../sr0 lrwxrwxrwx. 1 root root 9 Nov 4 14:39 ata-SAMSUNG_SSD_830_Series_S0Z4NEAC923324 -> ../../sda lrwxrwxrwx. 1 root root 9 Nov 4 14:39 ata-WDC_WD15EARX-00PASB0_WD-WCAZAE820424 -> ../../sdc lrwxrwxrwx. 1 root root 10 Nov 4 11:29 ata-WDC_WD15EARX-00PASB0_WD-WCAZAE820424-part1 -> ../../sdc1 lrwxrwxrwx. 1 root root 10 Nov 4 11:29 ata-WDC_WD15EARX-00PASB0_WD-WCAZAE820424-part2 -> ../../sdc2 lrwxrwxrwx. 1 root root 9 Nov 4 14:39 ata-WDC_WD30EZRX-00MMMB0_WD-WCAWZ2754564 -> ../../sdb lrwxrwxrwx. 1 root root 10 Nov 4 11:29 ata-WDC_WD30EZRX-00MMMB0_WD-WCAWZ2754564-part1 -> ../../sdb1 lrwxrwxrwx. 1 root root 10 Nov 4 11:29 ata-WDC_WD30EZRX-00MMMB0_WD-WCAWZ2754564-part2 -> ../../sdb2 lrwxrwxrwx. 1 root root 10 Nov 4 11:29 ata-WDC_WD30EZRX-00MMMB0_WD-WCAWZ2754564-part3 -> ../../sdb3 lrwxrwxrwx. 1 root root 10 Nov 4 14:39 dm-name-vg_alan--fedora-lv_home -> ../../dm-2 lrwxrwxrwx. 1 root root 10 Nov 4 14:39 dm-name-vg_alan--fedora-lv_root -> ../../dm-1 lrwxrwxrwx. 1 root root 10 Nov 4 14:39 dm-name-vg_alan--fedora-lv_swap -> ../../dm-0 lrwxrwxrwx. 1 root root 10 Nov 4 14:39 dm-uuid-LVM-kWHwWQB21WYM0ENMcjDCPfU3TMrAScH2DQUoiBbNoyp9kb29fq1N67pNLMVQa4FE -> ../../dm-2 lrwxrwxrwx. 1 root root 10 Nov 4 14:39 dm-uuid-LVM-kWHwWQB21WYM0ENMcjDCPfU3TMrAScH2OjnAJ50moS9cVczfZM5rdtEMFe1xVXAC -> ../../dm-0 lrwxrwxrwx. 1 root root 10 Nov 4 14:39 dm-uuid-LVM-kWHwWQB21WYM0ENMcjDCPfU3TMrAScH2ZvETulE7sMVYvfz68sSl0MEOg6cLaYGh -> ../../dm-1 lrwxrwxrwx. 1 root root 9 Nov 4 14:39 wwn-0x50014ee2b1cbd34d -> ../../sdc lrwxrwxrwx. 1 root root 10 Nov 4 11:29 wwn-0x50014ee2b1cbd34d-part1 -> ../../sdc1 lrwxrwxrwx. 1 root root 10 Nov 4 11:29 wwn-0x50014ee2b1cbd34d-part2 -> ../../sdc2 lrwxrwxrwx. 1 root root 9 Nov 4 14:39 wwn-0x50014ee2b1e723eb -> ../../sdb lrwxrwxrwx. 1 root root 10 Nov 4 11:29 wwn-0x50014ee2b1e723eb-part1 -> ../../sdb1 lrwxrwxrwx. 1 root root 10 Nov 4 11:29 wwn-0x50014ee2b1e723eb-part2 -> ../../sdb2 lrwxrwxrwx. 1 root root 10 Nov 4 11:29 wwn-0x50014ee2b1e723eb-part3 -> ../../sdb3 lrwxrwxrwx. 1 root root 9 Nov 4 14:39 wwn-0x5002538043584d30 -> ../../sda [alan@alan-fedora by-id]$ cd ../by-label [alan@alan-fedora by-label]$ ls -l total 0 lrwxrwxrwx. 1 root root 10 Nov 4 14:39 _Fedora-17-x86_6 -> ../../dm-1 [alan@alan-fedora by-label]$ cd ../by-partuuid [alan@alan-fedora by-partuuid]$ ls -l total 0 lrwxrwxrwx. 1 root root 10 Nov 4 11:29 9b1a4186-705f-469d-945a-77be5834d8af -> ../../sdb3 lrwxrwxrwx. 1 root root 10 Nov 4 11:29 b5d37f66-2567-4986-8596-6b1927c4bdd2 -> ../../sdb2 lrwxrwxrwx. 1 root root 10 Nov 4 11:29 efae6c78-9f2d-4bce-8df7-5a757a9f724e -> ../../sdb1 ##############
The above clearly shows that there is SOME kind of LVM information in /dev/sdc, but again I don't know why the system doesn't seem to deal with it as I would expect.
You might be able to mount the partition by doing something like. mount /dev/dm-0 /mnt/mountpoint
Given all the above information, there does not seem to be anything like /dev/dm-0 that corresponds to /dev/sdc. Again I'm at a loss.
There may be an issue if both lvm partitions have the same names as you current systems. I don't think it will allow that, you have to jump thru some hops to make the names different. On my newer systems I don't use LVM.
I suspect you're right, but I don't know how to do any of that.
Alan
On 11/4/2012 2:34 PM, Alchemist wrote:
I more or less tried that on my old 32-bit system. I installed a new disk and installed Fedora on a non-LVM partition. It could not see the LVM partition on the older disk -- same problem as I have now.
Ok lets try
shell# pvs
you must see line /dev/sdc2 and its VG name
shell# vgscan shell# vgchange -a y "VG name from pvs output" shell# lvscan here goes your ACTIVE "/dev/***" output shell# mnt "/dev/***" /mnt/fedora32
Here's what I get doing some of that:
################# [root@alan-fedora ~]# pvs PV VG Fmt Attr PSize PFree /dev/sdb3 vg_alan-fedora lvm2 a-- 2.73t 0
[root@alan-fedora ~]# vgscan Reading all physical volumes. This may take a while... Found volume group "vg_alan-fedora" using metadata type lvm2
[root@alan-fedora ~]# lvscan ACTIVE '/dev/vg_alan-fedora/lv_swap' [17.38 GiB] inherit ACTIVE '/dev/vg_alan-fedora/lv_home' [2.66 TiB] inherit ACTIVE '/dev/vg_alan-fedora/lv_root' [50.00 GiB] inherit #################
I don't see a VG name for /dev/sdc2.
I'm confused about what vgchange is supposed to do. The man page does not say what it does with the line you suggested. Specifically, the command takes an INPUT volume name, and the implication is that that name will be changed, but changed to what?
Alan
2012/11/4 Alan Feuerbacher alanf00@comcast.net
On 11/4/2012 2:34 PM, Alchemist wrote:
I more or less tried that on my old 32-bit system. I installed a newdisk and installed Fedora on a non-LVM partition. It could not see the LVM partition on the older disk -- same problem as I have now.Ok lets try
shell# pvs
you must see line /dev/sdc2 and its VG name
shell# vgscan shell# vgchange -a y "VG name from pvs output" shell# lvscan here goes your ACTIVE "/dev/***" output shell# mnt "/dev/***" /mnt/fedora32
Here's what I get doing some of that:
################# [root@alan-fedora ~]# pvs PV VG Fmt Attr PSize PFree /dev/sdb3 vg_alan-fedora lvm2 a-- 2.73t 0
[root@alan-fedora ~]# vgscan Reading all physical volumes. This may take a while... Found volume group "vg_alan-fedora" using metadata type lvm2
[root@alan-fedora ~]# lvscan ACTIVE '/dev/vg_alan-fedora/lv_swap' [17.38 GiB] inherit ACTIVE '/dev/vg_alan-fedora/lv_home' [2.66 TiB] inherit ACTIVE '/dev/vg_alan-fedora/lv_root' [50.00 GiB] inherit #################
I don't see a VG name for /dev/sdc2.
I'm confused about what vgchange is supposed to do. The man page does not say what it does with the line you suggested. Specifically, the command takes an INPUT volume name, and the implication is that that name will be changed, but changed to what?
Alan
That line makes volume group active. But not in this case. If both volumes are made by Anaconda and both have name "vg_alan-fedora" (as hostname) it may cause misunderstanding, for pvscanning, but as far as i know, pvs shows all VG even with same labels. Do you use Gnome? You check it with palimpsest, or all this is console releated only? Next, you can power off pc, disconnect/disable your master hdd(new), enable only old and boot from LiveCD(Fedora or any that supports LVM) and rename your old hdd VG vg_alan-fedora to f.e. vg_alan_old, so if there is a problem with naming, you now will have twoo different VG labels. Then connect/enable back your master drive, and boot as now. Then try again to pvscan. In any case be careful, do not damage your data!!!
how to rename>>> livecd# pvs livecd# vgscan livecd# vgchange -a n livecd# vgrename vg_alan-fedora vg_alan-old
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.**org/mailman/listinfo/usershttps://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/**Mailing_list_guidelineshttp://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Given the output you've shared of pvs and other LVM tools, it sort of looks like your older drive's LVM is in some way broken.
If I were you, I'd start by rebooting the system with the old drive disconnected. This should help ensure that nothing is in an odd state due to running more or less random LVM commands.
I'm mostly assuming that you're using an external connection. If not, don't worry about connecting and disconnecting the drive.
Before you connect the drive, open a terminal and run "tail -f /var/log/messages" as the root user. The information printed as you run commands may be useful.
Next, connect the hard drive to the system. The messages file should indicate that the drive was detected and the device name assigned to it.
Use "pvck" to see if there's anything wrong with the LVM partition. This LVM partition on a USB-attached hard drive is fine: [root@vagabond ~]# pvck /dev/sdb2 Found label on /dev/sdb2, sector 1, type=LVM2 001 Found text metadata area: offset=4096, size=1044480
On a Fedora system, if the partition is not damaged, it'll be detected but not activated automatically. At this point, you should see it in the volume group list (trimmed for brevity): [root@vagabond ~]# vgdisplay --- Volume group --- VG Name vg_vagabond VG Size 283.41 GiB VG UUID B78GaD-Sr7W-qiVD-Yyj9-HUh2-R2KN-BSziek
--- Volume group --- VG Name vg_vagabond VG Size 118.22 GiB VG UUID MswsDc-uBqi-U7cU-uF3T-lNtP-H9fx-aY2Enb
I now have two groups attached with the same name, which is problematic. There isn't an indication of which physical volume is part of each volume group (I'm not sure where such information might be available), but I can definitely tell which volume is on my external disk based on the size of the group. I'd want to rename the group on the external drive in order to use it on this system: [root@vagabond ~]# vgrename B78GaD-Sr7W-qiVD-Yyj9-HUh2-R2KN-BSziek vg_vagabond_old Volume group "vg_vagabond" successfully renamed to "vg_vagabond_old"
Note that renaming the group will probably make that hard drive unbootable, since its configuration no longer matches the volume group's name.
Now that the group has a unique name, it is safe to activate it. The activation process creates the device files needed to interact with the volume group and logical volumes. [root@vagabond ~]# vgchange -a y vg_vagabond_old 3 logical volume(s) in volume group "vg_vagabond_old" now active
[root@vagabond ~]# ls /dev/mapper/ vg_vagabond_old-lv_root vg_vagabond_old-lv_home vg_vagabond_old-lv_swap
[root@vagabond ~]# ls /dev/vg_vagabond_old/ lv_home lv_root lv_swap
You can mount either of those device nodes to access the files they contain: # mount /dev/vg_vagabond_old-lv_home /mnt
When you're done: [root@vagabond ~]# umount /mnt [root@vagabond ~]# vgchange -a n vg_vagabond_old 0 logical volume(s) in volume group "vg_vagabond_old" now active [root@vagabond ~]# eject /dev/sdb
-
Alan Feuerbacher -
Alchemist -
Gordon Messmer -
Hakan Koseoglu -
Michael D. Setzer II -
Reindl Harald -
Temlakos -
Tim