Can't mount ext4 logical vol under new kernel

[philrigby]

Hi everyone. I'm new to Fedora, but not new to Linux.

I have 250Gb, 500Gb and 1Tb drives concatenated together as one volume group (span) with a logical volume (spanvol). Under kernel 2.6.31.5-127.fc12.x86_64 it mounts totally fine. However, under 2.6.31.6-145.fc12.x86_64, I get this:-

[root@undertaker ~]# mount -t ext4 /dev/mapper/span-spanvol /home
mount: wrong fs type, bad option, bad superblock on /dev/mapper/span-spanvol,
missing codepage or helper program, or other error
(could this be the IDE device where you in fact use
ide-scsi so that sr0 or sda or so is needed?)
In some cases useful info is found in syslog - try
dmesg | tail or so

[root@undertaker ~]# uname -a
Linux undertaker.rigbyfam.net 2.6.31.6-145.fc12.x86_64 #1 SMP Sat Nov 21 15:57:45 EST 2009 x86_64 x86_64 x86_64 GNU/Linux


Boot up with the older kernel, and no problems mounting. I update the kernel with yum command line (NOT yumex, I believe there's some issues with that) - and I've removed and reinstalled the kernel a couple of times, not made any difference.

Any help would be appreciated... thanks!

[SlowJet]

From the koji kernel log 145 seems like a broken test.
http://koji.fedoraproject.org/koji/b...buildID=144550
Try the latest 163, if it does not work then you need some special stratup parms or your computer drives were wired wrong due to a bug in your bios, the previous kernels, and so on.

If 163 works, then run it. if not drop down the list to 137, .. fine the version that breaks it and go read the patch on kernel org.

SJ

[philrigby]

Thanks for that - help me out with something though, how do I get that installed via yum? Is there a repo it's in someplace?

[SlowJet]

You download the rpm that you have on your computer.
su -c ' rpm -qa kerne*;rpm -qa perf'
will list all the kernel pieces installed
on the koji list click on the download link next to each rpm in the noarch that you need, scroll down to x86_64 section, download kernel pieces needed.

in a root term update all the pieces except kernel, kernel must be installed.
su -
cd /home/useryou/Downloads
ls
rpm -Uvh perf.rpm kernel-firmware.rpm kerenl-devel.rpm kernel-headers.rpm --test
if ok
rpm -Uvh perf.rpm kernel-firmware.rpm kernel-devel.rpm kernel-headers.rpm

rpm -ivh kernel.rpm --test
if ok
rpm -ivh kernel.rpm

SJ

[philrigby]

Tried your steps SJ, but it didn't make any difference - same issue. Still won't mount the ext4 logical volume.

[SlowJet]

Just for a double check could you try mounting like this

su -
lvs
/mount /dev/mapper/span-spanvol /home

LVM is supposed to allow for drive renumbering by the uuid
lvs (lvscan) checks the new dev's
mapper uses LVM to find the specs of the LV and f/s type

SJ

[philrigby]

Under the working kernel, I get this:-
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
spanvol span -wi-ao 1.59T


Under the other kernel -
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
spanvol span -wi-d- 1.59T


Using the mount statement fails (I guess the leading / was a typo)

[SlowJet]

Yes the slash on mount was a typo.
The -wi-d is clearly not a happy healthy VG.

Refer to this thread, post#2.
http://forums.fedoraforum.org/showthread.php?t=141817

The idea is to see if a partial will activate the others.
Then an e2fsck can be run after finding a good superblock.

Also, search for bugs, file a bug in bugzill.redhat.com and ask for help in the devel-list.

SJ

[philrigby]

I'll check that out. Strange though that it mounts fine under the previous kernel.

[philrigby]

Ok, success. I did fdisk -l | grep sd and it listed 250gb, 1tb and 500gb in that order. That's not the way around I want it to be, so I switched the cables on 500gb and 1tb. Then under the new kernel, the logical volume now mounts. So that's good.

Next piece of oddness, is that according to fdisk, the 500gb has no partition/filesystem on it all (which is impossible) and the 250gb drive is marked as having a Linux partition, not a linux lvm partition - weird. I'm going to move all the data someplace else, destroy the logical volume and rebuild it - it's a bit unstable for my liking at the moment.

Thanks for the help, SJ. Much appreciated.