Bug 204644 - lvm boot failure Volume group missing
lvm boot failure Volume group missing
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: lvm2 (Show other bugs)
5
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Alasdair Kergon
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-08-30 11:57 EDT by Frederic Hornain
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-08-30 12:16:50 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Frederic Hornain 2006-08-30 11:57:00 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)

Description of problem:
Hi,

Yesterday, I did a shutdown of my machine after to have played with security policies - mostly - firewall rules -. 
The shutdown seems to be succesfull however I am not so sure anymore now.
But at that time, I did not care.

Then I restarted my computer and during the boot process of my Fedora Core 5, I had aproximatly the following message after the filesystem check step.

>  Filesystem [ FAILED ]
>
>*** Warning -- SELINUX is active"
>*** Disabling security enforcement for system recovery"
>*** Run 'setenforce 1' to reenable.
>  Give root password for maintenance 
>  (or type Control-D to continue)

So I entered the root password and I did some fsck thinking one of my ext3 formatted logical volume were corrupted then I had something like this :

> fsck ?.?? - the question mark is there cause I did not remember the numbers -
> fsck.ext3: No such file or directory trying to open /dev/mapper/VolGroup01-LogVol00
>
> -Message that I did not remember- superblock not correct do an e2fsck -b 8128







Version-Release number of selected component (if applicable):
kernel-2.6.17-1.2174_FC5smp

How reproducible:
Always


Steps to Reproduce:
1. Install a Fresh Fedora Core 5 on a machine 
2. Enforce the SELINUX
3. Apply some update
4. Disable the SELINUX
5. Apply some update
6. Wait a long while.
7. Apply some update
8. Re Enforce the SELINUX.
9. Shutdown the machine.
10. Restart it and you probably should have this message.

Actual Results:
I was on something between the normal mode and the single mode.

So I was redirected on the command line :
> [ Filesystem rescue 1]

if I did an exit tha machine rebooted.


Expected Results:
The OS should have started correctly. As usual.

Additional info:
Comment 1 Frederic Hornain 2006-08-30 12:16:50 EDT
Hi again,

Well, before to go open this case I have already found the solution this 
afternoon.
The thing is that I did not found any information on Google or on Bugzilla 
related to this kind of problem. 
So I decided share it to the community.

Well,it was SELINUX and it was mentionned on the error message. Gosh !

>*** Warning -- SELINUX is active"
>*** Disabling security enforcement for system recovery"
>*** Run 'setenforce 1' to reenable.

So this what you have to do in order to fix this annoyance.

So reboot your machine and you should have this message again : 

 >  Filesystem [ FAILED ]
 >
 >*** Warning -- SELINUX is active"
 >*** Disabling security enforcement for system recovery"
 >*** Run 'setenforce 1' to reenable.
 >  Give root password for maintenance 
 >  (or type Control-D to continue)

Then you should be redirected to the prompt

 >[ Filesystem rescue 1]

Then tape the command

 >[ Filesystem rescue 1] mount -o remount,rw /
- In this case the /etc was attached to the logical patrition mounted on / -

Then go to /etc/sysconfig

Then edit with vi or emacs the selinux file named selinux
and remplace the variable SELINUX=enforcing by SELINUX=disabled
Save it and exit the shell.

The machine should reboot and the system should restart.

Hoping that I was clear in my explanations.
Anyway, feel free to contact me if you need more details.

Have a nice evening Alasdair and thanks for your help anyway. :)

Note You need to log in before you can comment on or make changes to this bug.