Hi all-

I am a FC3 user, with a problem seeing my second drive. I would appreciate any insights.

I recently needed to get a bigger hard drive. I opted to remove the old drive (working just fine), and replace it with a new drive and do a new install of FC3 onto the new drive. This way I could go back to the old drive if I ever needed to (this gives me a safe backup with no extra work). All is well - the new drive boots fine, works fine.

I would like to hook my old drive up now in order to transfer some archived/original files from it to the new drive. I must be missing fundamental point - I cannot seem to be able to read the partition I want to. Here is what I did:
* New big drive is master in 1st ide slot
* Old small drive is slave in 1st ide slot
* jumpers are correct for both drives defining master and slave

Power up

On boot, FC3 reported a duplicate partition name on the slave drive (/boot). Yes, since the slave was the real boot drive before, the boot partition name now conflicts with the new drives partition called /boot. I used
tune2fs -L /xboot /dev/hdb1
in order to remove the contention. Reboot shows no contention problem.

I cannot mount the 2nd partition - where I think all of the data is on the old, smaller drive.

Here are the facts:

---------------------------
# more /proc/partitions
major minor #blocks name

3 0 245117376 hda
3 1 104391 hda1
3 2 245007315 hda2
3 64 78150744 hdb <------
3 65 104391 hdb1 <------
3 66 78043770 hdb2 <------ this is what I want to copy from (I think)
253 0 242778112 dm-0
253 1 2031616 dm-1
8 0 58615704 sda
8 1 58613121 sda1
----------------------------

# fdisk -l

Disk /dev/hda: 251.0 GB, 251000193024 bytes
255 heads, 63 sectors/track, 30515 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 14 30515 245007315 8e Linux LVM

Disk /dev/hdb: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdb1 * 1 13 104391 83 Linux
/dev/hdb2 14 9729 78043770 8e Linux LVM

Disk /dev/sda: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 7297 58613121 c W95 FAT32 (LBA)
------------------

With this setup, I can do a:
mount /dev/hdb1 /media/drive2 -t ext3

and it will show me the contents of the boot partition on the old drive just fine.

After doing a umount, if I try to do a:
mount /dev/hdb2 /media/drive2 -t ext3

I get:
mount: wrong fs type, bad option, bad superblock on /dev/hdb2,
or too many mounted file systems

What am I missing?


Much thanks,
DC

This may have something to do with it. Have you tried mounting with either no filesystem type specified, or using Resierfs ?

Cheers,

mj

Hi,
1)I created a Linux LVM partition of 75 GB using fdisk.
2) reboot
3) mkfs -t ext3 /dev/hdaxx
4) mount /dev/hdaxx /tmp ### please, don't use the -t option!!!

It worked fine. If you have the problems, like before, do reset the partition
before calling mkfs using "dd if=/dev/zero of=/dev/hdb2 bs=163840"
Regards
Andreas Huppert

Stop! fdisk and mkfs would delete the data.

I'd rather suggest you find out whether LVM is properly supported and set up on your machine (i.e. were physical volumes, volume groups, logical volumes created etc?)...

See also
http://www.sistina.com/products_lvm.htm
and search for documentation there or look at
http://tldp.org/HOWTO/LVM-HOWTO/
http://www.suse.de/de/whitepapers/lvm/index.html

P.S.: Was this an LVM-partition on your original set up, or has something gone awry?

Since you have data that you have backed up on the second drive I would proceed with caution.

It appears that you have LVM on /dev/hdb2 and that is what you can't mount. You can only mount the logical volumes on the volume group that is hosted by that physical drive. I assume that you set up logical volumes on that drive.

Before disconnecting such a drive you need to do a vgexport to "detach" the pv from the system. But all is not lost.

Here's what I would suggest you do:
1. vgscan - you shouldn't get any errors at this step.
2. pvscan - you should see both /dev/hda2 and /dev/hdb2
3. vgimport /dev/vgxx - whatever it was called. But the problem may exist if you used the same name for the new volume group
4. vgchange -a y /dev/vgxx
5. vgdisplay -v /dev/vgxx - should show details of logical volumes

If this doesn't make sense, you might want to check the documentation for LVM2.

Let us know what you find, etc.

Good Luck

Hi DocFabian and JZL240I-U-

Thank you for your helpful leads (and warnings). I will need to do some reading on LVM2 just to get familiar with the commands that DocFabian has provided. I will post more as soon as I know it. LVM looks like it can be very powerful over the old way of doing things (with simple fstab entries), at the cost of having to fdo a bit more study.

Thanks!
DC