Unsolved
This post is more than 5 years old
1 Rookie
•
8 Posts
0
736
December 18th, 2008 14:00
LVM cannot be checked at startup (modules not loaded)
Hello,
I made a ext3 filesystem on LVM using a device provided by PowerPath (/dev/emcpowera1), it works fine but if (in the /etc/fstab) I activate the filesystem check at startup (e.g. /dev/vg1/lv1 /san ext3 defaults 0 2), RHEL 5.2 64bits fails to boot because "/dev/vg1/lv1" doesn't exists yet... because EMC modules aren't loaded yet.
If I use " /dev/vg1/lv1 /san ext3 defaults 0 0" everthing works fine but the filesystem isn't checked at startup.
I use the last version of the kernel ( 2.6.18-92.1.22.el5) and PowerPath ( 5.1 SP2 - build 21).
Note: It works fine with RHEL4.
The server is a Dell M600 blade and the SAN is an EMC Clariion CX3-10c.
I can provide screenshots of the error message and list of modules when it happends (lsmod) if it can helps.
Any idea how I could resolve this? In fact I need the emc modules to be loaded earlier but the PowerPath-way seems weird: a list of modules to load is included on-the-fly by the startup script to /etc/modules.conf. The issue is reproducible.
Regards,
I made a ext3 filesystem on LVM using a device provided by PowerPath (/dev/emcpowera1), it works fine but if (in the /etc/fstab) I activate the filesystem check at startup (e.g. /dev/vg1/lv1 /san ext3 defaults 0 2), RHEL 5.2 64bits fails to boot because "/dev/vg1/lv1" doesn't exists yet... because EMC modules aren't loaded yet.
If I use " /dev/vg1/lv1 /san ext3 defaults 0 0" everthing works fine but the filesystem isn't checked at startup.
I use the last version of the kernel ( 2.6.18-92.1.22.el5) and PowerPath ( 5.1 SP2 - build 21).
Note: It works fine with RHEL4.
The server is a Dell M600 blade and the SAN is an EMC Clariion CX3-10c.
I can provide screenshots of the error message and list of modules when it happends (lsmod) if it can helps.
Any idea how I could resolve this? In fact I need the emc modules to be loaded earlier but the PowerPath-way seems weird: a list of modules to load is included on-the-fly by the startup script to /etc/modules.conf. The issue is reproducible.
Regards,
0 events found
No Events found!
sigpedag
1 Rookie
•
8 Posts
0
December 18th, 2008 15:00
I also re-activated every possible service because I used to select the minimum and I have the same error...
So the real question is: "Is it possible to check a filesystem hosted on a PowerPath device at startup??"
SKT2
2 Intern
•
1.3K Posts
0
December 19th, 2008 07:00
with "defaults 0 0" ; did the FS get mounted even w/o checking/fsck?
also the fsck is done depnding on the policy/setting while creating the LV. Check "man tune2fs"
You have a new kernel. Not new PP.
Message was edited by:
santhosh theyyan
dynamox
9 Legend
•
20.4K Posts
1
December 19th, 2008 13:00
https://forums.emc.com/forums/thread.jspa?messageID=505822
sigpedag
1 Rookie
•
8 Posts
0
December 19th, 2008 15:00
Using the "_netdev" option in the fstab solved my problem, the PowerPath device can now be automatically checked at startup.
Too bad the RHEL4 and RHEL5 behavior aren't the same.
Thanks again.
sigpedag
1 Rookie
•
8 Posts
0
December 19th, 2008 15:00
imported/activated?
fsck.ext3: Not such file or directory while trying to open /dev/vg1/lv1
/dev/vg1/lv1:
The superblock could not be read or does not describe a correct ext2 filesystem...
This means that /dev/vg1/lv1 doesn't exist yet.
w/o checking/fsck?
Yes, no problem at all, the FS can be automatically mounted with no error.
while creating the LV. Check "man tune2fs"
tune2fs allows to configure the number of mounts or the time between two mounts before a full check, but in my case fsck fails whatever these options are.
Dos this means that there's a new version of PP? 5.1 SP2 is the newer I can download.
Maybe you mean that the kernel might be "too much" up-to-date and that I need to use an older kernel certified in the EMC matrix for PowerPath?