Re: fsck.ext3: No such file or directory while trying to open/dev/datavg/optOracle

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,


# mkinitrd -f /boot/initrd-`uname -r`.img `uname -r`

Created the new mkinitrd ; still facing the same issue.  No luck.
We are using LUNs from EMC CLARiiON frame.  Since we are not SAN booting; I
guess all that I have to do is install powerpath, discover the LUN allocated
and put it to use with regular lvm commands.

I am not sure what SAN drivers needs to be loaded before automount and if
they have to be included in initrd-2.6.18-238.el5.img.

We use emulex fibre adapters.  I am also not sure if this has anything to do
with the settings for HBA.

# powermt display dev=all
Pseudo name=emcpowera
CLARiiON ID=APM11105711783 [zlnx_009]
Logical device ID=711711615C54231128C4C83E26D3E111 [Lun 0611]
state=alive; policy=CLAROpt; priority=0; queued-IOs=0;
Owner: default=SP B, current=SP B       Array failover mode: 1
==============================================================================
--------------- Host ---------------   - Stor -   -- I/O Path --  -- Stats
---
###  HW Path               I/O Paths    Interf.   Mode    State   Q-IOs
Errors
==============================================================================
   5 lpfc                     sdb       SP B4     active  alive       0
 0
   5 lpfc                     sdc       SP A5     active  alive       0
 0
   7 lpfc                     sdd       SP A4     active  alive       0
 0
   7 lpfc                     sde       SP B5     active  alive       0
 0



# lspci | grep -i fibre
0a:00.0 Fibre Channel: Emulex Corporation Zephyr-X LightPulse Fibre Channel
Host Adapter (rev 02)
0a:00.1 Fibre Channel: Emulex Corporation Zephyr-X LightPulse Fibre Channel
Host Adapter (rev 02)
0c:00.0 Fibre Channel: Emulex Corporation Zephyr-X LightPulse Fibre Channel
Host Adapter (rev 02)
0c:00.1 Fibre Channel: Emulex Corporation Zephyr-X LightPulse Fibre Channel
Host Adapter (rev 02)

Thanks for all your suggestions.


On Wed, Aug 31, 2011 at 3:09 PM, Eugene Vilensky <evilensky@xxxxxxxxx>wrote:

> As suggested earlier, you need a new initrd which includes your san
> drivers.  Check your San documentation for anything including the "mkinitrd"
> command. You also likely missed important settings for path failure handling
> and retry policies, and driver settings for your hba.  Those settings are
> typically documented in close proximity to creating the new ramdisk.
> Sent via mobile.
>
> -----Original Message-----
> From: unix syzadmin <unixsyzadmin@xxxxxxxxx>
> Sender: redhat-list-bounces@xxxxxxxxxx
> Date: Wed, 31 Aug 2011 10:15:39
> To: General Red Hat Linux discussion list<redhat-list@xxxxxxxxxx>
> Reply-To: General Red Hat Linux discussion list <redhat-list@xxxxxxxxxx>
> Subject: Re: fsck.ext3: No such file or directory while trying to open
>         /dev/datavg/optOracle
>
> Hi,
>
> Thanks for the reply.
> My OS file-systems are created on sysvg volume group based on internal
> disk.
> I am creating  user file-systems on datavg based on EMC SAN disk.
>
> While in the maintenance shell I could not see any entries for datavg or
> its
> logical volumes in /dev.
>
> So I re-mounted the / file-system (mount -o remount,rw /); edited the
> /etc/fstab and commented out all the mounts for logical volumes on the
> datavg.
>
> After this the system booted fine.
>
> Strangely after the system booted; I see all the entries for datavg and its
> logical volumes in /dev.
> Also datavg is online and I can mount all file-systems  without any issues.
>
> The filter in lvm.conf is:
>
> # grep filter /etc/lvm/lvm.conf | grep -v '#'
>    filter = [ "a/sda[1-9]$/","a/emcpower.*/","r/.*/" ]
>
> I guess the system is having problem to recognize the powerpath disk
> "emcpowera" during boot.  That is why it is not able to recognize the
> datavg
> built on that EMC disk.  Consequently no entries found for datavg and its
> logical volumes in /dev.
>
> Since there are no entries in /dev for datavg and its logical volumes the
> entries in /etc/fstab to mount them at boot is failing.
>
> I guess I am missing some configuration step related to using EMC disk and
> having it recognized during boot for mounting file-systems.
>
> Please suggest,
>
> Thanks,
>
>
>
> On Wed, Aug 31, 2011 at 9:41 AM, grim76 <grim76@xxxxxxxxxx> wrote:
>
> > On 08/31/2011 06:01 AM, unix syzadmin wrote:
> > > Hi,
> > >
> > > We have a RHEL5.6 x86_64 server that throws the following error while
> > > booting:
> > >
> > > fsck.ext3: No such file or directory while trying to open
> > > /dev/datavg/optOracle
> > > /dev/datavg/optOracle:
> > > The superblock could not be read or does not describe a correct ext2
> > > filesystem.  If the device is valid and it really contains an ext2
> > > filesystem (and not swap or ufs or something else), then the superblock
> > is
> > > corrupt, and you might try running e2fsck with an alternate superblock:
> > > e2ffsck -b 8193 <device>
> > >
> > > Before restarting the server we got a LUN from EMC allocated to this
> > server.
> > > We use powerpath and used the "powermt config" to detect the LUN.
> > > We put the LUN to use through  regular lvm commands like pvcreate,
> > vgcreate,
> > > lvcreate, mkfs.ext3, mount etc.
> > >
> > > Please suggest / point me in the right direction.
> > >
> > > Thanks,
> >
> > You might want to look at lvm.conf.  Typically lvm looks at /dev/sda,
> > /dev/sdb and so on.  What you will likely want it to do is look at the
> > multipath device vs. the individual device.
> >
> > Just remember to test your changes prior to any reboot.  Otherwise your
> > change could knock off another lvm device on the system.
> >
> > --
> > redhat-list mailing list
> > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
> > https://www.redhat.com/mailman/listinfo/redhat-list
> >
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
>
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
>
-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list


[Index of Archives]     [CentOS]     [Kernel Development]     [PAM]     [Fedora Users]     [Red Hat Development]     [Big List of Linux Books]     [Linux Admin]     [Gimp]     [Asterisk PBX]     [Yosemite News]     [Red Hat Crash Utility]


  Powered by Linux