hello experts,

I have been using Fedora 16 for quite a time and yes, I am facing a big problem..may be because of a a bug in Fedora 16..
I hope you people will make it clear..

the condition is::
I have two harddisks both are having Fedora 16 installed occupying the full space on both of them, say hdd-A and hdd-B.

The problem comes when i boot my system with both the harddisks plugged in. First I select which hdd to boot from bios then the selected one starts to boot up, GRUB appears and loads the selected kernel but after the booting process is done.
what I am getting is a mixed File System.!!!! i.e. I get the /home directory of other hard disk!!!!
and this is the case when I boot any of the harddisk A or B,
I always face the cross mount problem??

Rather, if I boot with single hdd,(other one plugged off) it boots as normal!!!

Is anyone facing this problem??

Any help or discussion is appreciated..

Regards!!!!

can you show us how did you configure mounts?

Did you clone one disk from the other?
Check the uuid of the disks. Your symptoms sound to me like they have the same uuid, which is a symptom of a cloned disc.

Cheers,
Terry

@pan64
Sir, can you please be specific about what you said, I didn`t get you..
btw,

$mount results in this..
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,relatime,size=2053028k,nr_inodes=207565,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,relatime)
/dev/mapper/VolGroup-lv_root on / type ext4 (rw,relatime,data=ordered)
tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/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=23,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
securityfs on /sys/kernel/security type securityfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
tmpfs on /media type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755)
mqueue on /dev/mqueue type mqueue (rw,relatime)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
/dev/sda2 on /boot type ext4 (rw,relatime,data=ordered)
/dev/mapper/VolGroup-lv_home on /home type ext4 (rw,relatime,data=ordered)
gvfs-fuse-daemon on /home/beyond/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)



@terry-duel
I didn`t cloned the disks, I did a seperate install on both the disks, guess a month`s difference is there betweeen the install in both . One disk is of 80gb(IDE) and other is of 250gb(Sata)..

this is the /etc/fstab file and maybe the automounter involved. Also you have logical volumes, how the VolumeGroups configured?

@pan64,

$vgdisplay

--- Volume group ---
VG Name VolGroup
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 4
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 3
Open LV 3
Max PV 0
Cur PV 1
Act PV 1
VG Size 232.38 GiB
PE Size 32.00 MiB
Total PE 7436
Alloc PE / Size 7436 / 232.38 GiB
Free PE / Size 0 / 0
VG UUID C1qV69-tbaP-LIs7-LxDB-ou1o-lcPM-0RlhI6


pvdisplay
--- Physical volume ---
PV Name /dev/sda3
VG Name VolGroup
PV Size 232.40 GiB / not usable 21.00 MiB
Allocatable yes (but full)
PE Size 32.00 MiB
Total PE 7436
Free PE 0
Allocated PE 7436
PV UUID 2yNdss-70jN-qDX4-vnzG-Jp3k-0dGc-G4Dbww



lvdisplay
--- Logical volume ---
LV Name /dev/VolGroup/lv_swap
VG Name VolGroup
LV UUID 71DV2W-USaQ-EHVO-1mQN-LsJ2-8zif-SknDXi
LV Write Access read/write
LV Status available
# open 2
LV Size 5.19 GiB
Current LE 166
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0

--- Logical volume ---
LV Name /dev/VolGroup/lv_home
VG Name VolGroup
LV UUID r3AxGJ-Sp60-ftCw-wc2E-FS1O-7mtT-5FoLi5
LV Write Access read/write
LV Status available
# open 1
LV Size 177.19 GiB
Current LE 5670
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:2

--- Logical volume ---
LV Name /dev/VolGroup/lv_root
VG Name VolGroup
LV UUID hpuRWT-9003-SzRi-D1cz-avQv-CBcU-0pm5eZ
LV Write Access read/write
LV Status available
# open 1
LV Size 50.00 GiB
Current LE 1600
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1

If you did default installs, you will have the same named vg's and lv's - you can confirm that by booting each disk alone. Effectively the same as cloned disks as suggested above.
LVM can't mount the second copy, and is apparently finding the "other" copy first when both disks are mounted.

Can be ugly to rectify.

@syg00-yes, you are right!!!

Yes, I did the default install
and as we can see that the LV names are same....

This is the display when I searched for the volume groups in my Second harddisk (IDE) with 80gb space


sh-4.2# lvdisplay
--- Logical volume ---
LV Name /dev/VolGroup/lv_swap
VG Name VolGroup
LV UUID r9Bc5b-P3bB-C6BO-8BU6-gkef-rYaS-M3pc4d
LV Write Access read/write
LV Status available
# open 2
LV Size 5.19 GiB
Current LE 166
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0

--- Logical volume ---
LV Name /dev/VolGroup/lv_home
VG Name VolGroup
LV UUID gLxf3q-3WF5-Cmj0-AqZw-5Z2P-our3-ffPXKW
LV Write Access read/write
LV Status available
# open 1
LV Size 22.94 GiB
Current LE 734
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:2

--- Logical volume ---
LV Name /dev/VolGroup/lv_root
VG Name VolGroup
LV UUID Eexxkk-oa9j-WW64-B1IN-9SQg-SRWE-TX0zHn
LV Write Access read/write
LV Status available
# open 1
LV Size 45.91 GiB
Current LE 1469
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1



sh-4.2# pvdisplay
--- Physical volume ---
PV Name /dev/sda3
VG Name VolGroup
PV Size 74.04 GiB / not usable 9.00 MiB
Allocatable yes (but full)
PE Size 32.00 MiB
Total PE 2369
Free PE 0
Allocated PE 2369
PV UUID 3Zx5xw-EnZo-wkKA-2YEu-qP7b-D1Em-3jWuzD


sh-4.2# vgdisplay
--- Volume group ---
VG Name VolGroup
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 4
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 3
Open LV 3
Max PV 0
Cur PV 1
Act PV 1
VG Size 74.03 GiB
PE Size 32.00 MiB
Total PE 2369
Alloc PE / Size 2369 / 74.03 GiB
Free PE / Size 0 / 0
VG UUID vRLXzb-0d2b-g2VB-pmbc-gKoQ-FhFg-njUD0d


But One thing that I am still not able to figure out is that
when I have selected a particular harddisk to boot from BIOS, then during the boot process, (assuming 1st hard disk is selected) the other one is only seen as a device, it is not mounted up, right??? So, how can it find the name from the other device??
I mean if sda is selected then how can it do mounts from sdb???

Plese do make me correct!!

They don't need to be mounted - pvscan and vgscan would probably be run in your initrd. Why you get something from the "other" disk I have no idea.