- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: fsck.ext3: no such file or directory while try...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-17-2010 09:06 AM
тАО06-17-2010 09:06 AM
fsck.ext3: no such file or directory while trying to open /dev/mapper
First of all, I am remotely connected to this RedHatEnterprise Linux 5.0 server thru ILO2 connection in Europe. I'm in US.
when the server tries to reboot (I don't know how it went down), it comes with similar messages such as these:
fsck.ext3: no such file or directory while trying to open /dev/mapper/VolGroup15-Stageing
...........
it comes to "(Repair filesystem)" prompt.
So, I i
ls -l /dev/mapper does NOT show anything that has VolGroup15.
Could you please help!?
Thanks!
Ravi.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-17-2010 10:09 AM
тАО06-17-2010 10:09 AM
Re: fsck.ext3: no such file or directory while trying to open /dev/mapper
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-17-2010 12:12 PM
тАО06-17-2010 12:12 PM
Re: fsck.ext3: no such file or directory while trying to open /dev/mapper
/dev/dm-10 VolGroup15
/dev/dm-11 VolGroup10
/dev/dm-12 VolGroup11
/dev/dm-13 VolGroup12
/dev/dm-14 VolGroup13
/dev/dm-15 VolGroup14
it means /dev/dm-10 maps to VolGroup15, correct?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-17-2010 12:33 PM
тАО06-17-2010 12:33 PM
Re: fsck.ext3: no such file or directory while trying to open /dev/mapper
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-17-2010 12:36 PM
тАО06-17-2010 12:36 PM
Re: fsck.ext3: no such file or directory while trying to open /dev/mapper
but, could you also please let me know if when I do pvs in lvm, I get
/dev/dm-10 VolGroup15
/dev/dm-11 VolGroup10
/dev/dm-12 VolGroup11
/dev/dm-13 VolGroup12
/dev/dm-14 VolGroup13
/dev/dm-15 VolGroup14
does this mean /dev/... is the mapping to the /dev/mapper address?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-17-2010 01:16 PM
тАО06-17-2010 01:16 PM
Re: fsck.ext3: no such file or directory while trying to open /dev/mapper
pvs should list the physical volumes being used by LVM like this:
# pvs
PV VG Fmt Attr PSize PFree
/dev/cciss/c0d0p2 vg01 lvm2 a- 60.33G 30.33G
/dev/emcpowera1 vg00 lvm2 a- 33.71G 0
/dev/emcpowerb1 vg00 lvm2 a- 33.71G 7.43G
It will not show the logical device names, you can use the dmsetup program to verify the mappings..
PS: Don't forget to assign points if you found our answers useful
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-17-2010 01:51 PM
тАО06-17-2010 01:51 PM
Re: fsck.ext3: no such file or directory while trying to open /dev/mapper
Does vgdisplay VolGroup15 show anything?
or lvdisplay VolGroup15/Stageing?
Could it be a temp lv?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-17-2010 02:01 PM
тАО06-17-2010 02:01 PM
Re: fsck.ext3: no such file or directory while trying to open /dev/mapper
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-17-2010 02:52 PM
тАО06-17-2010 02:52 PM
Re: fsck.ext3: no such file or directory while trying to open /dev/mapper
There is a tweak that would make LVM use more informative device names: edit /etc/lvm/lvm.conf and find the "preferred_names" option. By default the list of preferred device names is empty, but there should be an example configuration line with a comment like "Try to avoid using undescriptive /dev/dm-N names". Comment out the empty default, and uncomment the example line. Then run "vgscan" to refresh the LVM metadata cache. Now run "pvs" again to hopefully get a more informative result.
Looks like the VolGroup15 is not active, yet the system is trying to run fsck on it.
Is this system part of a cluster?
The "_netdev" option tells the system "this filesystem requires network to be operational before it can be activated", which is important if VG activation depends on cluster-wide locks.
Normally the system tries to automatically activate all the VGs it sees, before starting to run file system checks. So something may have caused the activation of VolGroup15 to fail.
You might want to run "vgchange -a y VolGroup15". If the automatic activation failed, this will probably fail too, but it should display a helpful error message in that case. For example, this VG might contain more than one PV.
If the manual VG activation is successful, then I guess your system startup script might just have gone ahead faster than the SAN LUN discovery could complete. If that's the case, inserting a short delay to the FC driver loading procedure might help.
If your server really is RHEL 5.0 (i.e. no updates installed since RHEL 5 original release), then I'd strongly suggest upgrading to RHEL 5.4. There has been several kernel, LVM and dm-multipath updates to improve SAN functionality.
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-18-2010 06:20 AM
тАО06-18-2010 06:20 AM
Re: fsck.ext3: no such file or directory while trying to open /dev/mapper
No directory called VolGroup15 under /dev. There is /dev/VolGroup00, though.
Thanks!
Ravi.