- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- LVM File System failing the booting of a RHEL5 ser...
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
тАО01-12-2010 05:08 AM
тАО01-12-2010 05:08 AM
A file system (/dev/vgdb/lvdb /oradb) is preventing a RHEL5 from booting. At a certain stage of the startup, it says that mkfs.ext3 cannot recognize or find or FSCK /dev/vgdb/lvdb, and gives me access to a shell command prompt.
In the shell command prompt, whenever I decide to comment or remove the(/dev/vgdb/lvdb /oradb) line in the /etc/fstab with vi command, it says that FSTAB is open in read-only and therefore cannot be amended.
Please Advice
Regards,
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2010 05:35 AM
тАО01-12-2010 05:35 AM
Solutionmount -o rw,remount /
That will enable your root file system in read write mode to modify the file and boot or troubleshoot your missing device.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2010 09:16 AM
тАО01-12-2010 09:16 AM
Re: LVM File System failing the booting of a RHEL5 server
You might want to boot your system into rescue mode in order to make repairs to the system.
fsck.ext3 might need to be run manually.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-13-2010 02:44 AM
тАО01-13-2010 02:44 AM
Re: LVM File System failing the booting of a RHEL5 server
Maybe you are using raw devices?
Do you get reasonable output when issuing
# dumpe2fs -h /dev/vgdb/lvdb
or
# tune2fs -l /dev/vgdb/lvdb
Also, maybe you inadvertently entered a wrong fstype or mount options for the lvdb entry in fstab?
Check
# grep /lvdb /etc/fstab
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-13-2010 03:16 AM
тАО01-13-2010 03:16 AM
Re: LVM File System failing the booting of a RHEL5 server
Though in most initrds you will find a "vgchange -ay" in its init, it might be that your vgdb for some strange reason hasn't been activated.
At the recovery root shell maybe try
# lvm vgscan
# lvm vgchange -a y vgdb
This should usually have open the LV lvdb as well.
You can check the LV attributes. The 5th position should read an "a" like so:
# lvm lvs -o lv_name,lv_attr vgdb
LV Attr
lvdb -wi-a-
You could still try to activate that LV explicitly by
# lvm lvchange -a y /dev/vgdb/lvddb
Remember, when issuing at a normal run level you may omit the leading word "lvm".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-13-2010 03:24 AM
тАО01-13-2010 03:24 AM
Re: LVM File System failing the booting of a RHEL5 server
I was able to remove the problematique file system and my RHEL5 system can boot successfully.
One thing I would like to do is to make the file system mounting persistent after each reboot.
What is the best way to do that ?
Is it just only by putting the related filesystem in fstab?
Note: I am using DM Multipath
Here is my DF:
/dev/mapper/VolGroup01-LogVol00
130805104 3063008 120990252 3% /
/dev/cciss/c0d0p1 101086 13830 82037 15% /boot
tmpfs 16777216 0 16777216 0% /dev/shm
none 16777216 104 16777112 1% /var/lib/xenstored
/dev/mapper/vg01-lvol0
100791728 192272 95479456 1% /oradevap
/dev/mapper/vg02-lvol0
100791728 192272 95479456 1% /oratstap
/dev/mapper/vg03-lvol0
100791728 192272 95479456 1% /oratrnap
[root@localhost ~]#
Please Advice,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-13-2010 03:55 AM
тАО01-13-2010 03:55 AM
Re: LVM File System failing the booting of a RHEL5 server
Yes.
Example:
/dev/vg01/lvol0 /oradevap ext3 defaults 0 0
/dev/vg02/lvol0 /oratstap ext3 defaults 0 0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-13-2010 08:25 AM
тАО01-13-2010 08:25 AM
Re: LVM File System failing the booting of a RHEL5 server
I definitely think there is leftover entries in /etc/fstab
Make sure everything in there is valid.
mount -a
See what the errors are.
Clean em up.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-13-2010 10:28 AM
тАО01-13-2010 10:28 AM
Re: LVM File System failing the booting of a RHEL5 server
[root@rcbdev ~]#
[root@rcbdev ~]# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/VolGroup01-LogVol00
130805104 3500936 120552324 3% /
/dev/cciss/c0d0p1 101086 13830 82037 15% /boot
tmpfs 16777216 0 16777216 0% /dev/shm
none 16777216 104 16777112 1% /var/lib/xenstored
[root@rcbdev ~]#
[root@rcbdev ~]# mount -a
mount: special device /dev/vg01/lvol0 does not exist
mount: special device /dev/vg02/lvol0 does not exist
mount: special device /dev/vg03/lvol0 does not exist
[root@rcbdev ~]#
[root@rcbdev ~]# vgchange -a y vg01
1 logical volume(s) in volume group "vg01" now active
[root@rcbdev ~]# vgchange -ay vg02
1 logical volume(s) in volume group "vg02" now active
[root@rcbdev ~]# vgchange -a y vg03
1 logical volume(s) in volume group "vg03" now active
[root@rcbdev ~]#
[root@rcbdev ~]# mount -a
[root@rcbdev ~]#
[root@rcbdev ~]# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/VolGroup01-LogVol00
130805104 3500944 120552316 3% /
/dev/cciss/c0d0p1 101086 13830 82037 15% /boot
tmpfs 16777216 0 16777216 0% /dev/shm
none 16777216 104 16777112 1% /var/lib/xenstored
/dev/mapper/vg01-lvol0
100791728 2262044 93409684 3% /t24devap
/dev/mapper/vg02-lvol0
100791728 2262024 93409704 3% /t24tstap
/dev/mapper/vg03-lvol0
100791728 2262048 93409680 3% /t24trnap
[root@rcbdev ~]#
There is an improvement now, but look:
Why should I vgchange -a y the VGs anytime I reboot, before they can be mounted ?
Please Advice,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-13-2010 10:35 AM
тАО01-13-2010 10:35 AM
Re: LVM File System failing the booting of a RHEL5 server
Why should I vgchange -a y the VGs anytime I reboot, before they can be mounted ?
No, the system is supposed to do this for you as part of the boot process.
Make sure you log in as root.
root can write to /etc/fstab under most circumstances.
see the command chattr
chattr -i /etc/fstab
Then try again.
Use chattr to display other annoying attributes that might interfere with your changes.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com