New 64-bit Fedora Will Not Mount Similar 32-bit Filesystem

[Alan Feuerbacher]

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 at 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 at 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 at alan-fedora alan]# ls -l /mnt
total 4
drwxr-xr-x. 2 root root 4096 Nov  4 11:02 fedora32
[root at 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