LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices

Reply
 
Search this Thread
Old 03-08-2010, 05:36 PM   #1
DaveJL
LQ Newbie
 
Registered: Mar 2010
Posts: 7

Rep: Reputation: 0
Boot hangs after SELinux: Disabled at runtime


Hello,

My Redhat box hangs on boot up after "SELinux: Disbled at runtime" ...

Code:
raid1: raid set md0 active with 2 out of 2 mirrors
md: ... autorun DONE.
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
SELinux:  Disabled at runtime.
type=1404 audit(1268063367.600:2): selinux=0 auid=4294967295 ses=4294967295
This boot hanging problem started after I ran /etc/rc.d/rc.sysinit to reset the hostname, but the power went out before the script completed.

I'm suspecting that the hard kill messed up some boot files, and I'm hoping a kind & wise soul can help guide me on how to restore them properly.

Thanks very much.
Dave
 
Old 03-08-2010, 06:16 PM   #2
John VV
Guru
 
Registered: Aug 2005
Posts: 12,698

Rep: Reputation: 1687Reputation: 1687Reputation: 1687Reputation: 1687Reputation: 1687Reputation: 1687Reputation: 1687Reputation: 1687Reputation: 1687Reputation: 1687Reputation: 1687
off hand i would guess that the hang is the file system rewriting the se context to the WHOLE drive
this can take anywhere from 5 min to 2+hours depending on the size of the drive/s

to temporally turn off SE use the command " setenforce 0 "
 
1 members found this post helpful.
Old 03-08-2010, 06:32 PM   #3
DaveJL
LQ Newbie
 
Registered: Mar 2010
Posts: 7

Original Poster
Rep: Reputation: 0
Thanks for the ray of hope, John.

Yeah, just now (after 2 hours), the boot output pushed an inch forward to include "RAID1 conf printout":

Code:
SELinux:  Disabled at runtime.
type=1404 audit(1268063367.600:2): selinux=0 auid=4294967295 ses=4294967295
RAID1 conf printout:
 --- wd:2 rd:2
 disk 0, wo:0, o:1, dev:sda3
 disk 1, wo:0, o:1, dev:sdb3
But, like before, it's hanging here again.

So, does the boot process appear to be progressing properly, such that it's just a matter of time before the boot completes properly? (The HD size is 500 GB.)

Thanks again,
Dave
 
Old 03-08-2010, 06:48 PM   #4
John VV
Guru
 
Registered: Aug 2005
Posts: 12,698

Rep: Reputation: 1687Reputation: 1687Reputation: 1687Reputation: 1687Reputation: 1687Reputation: 1687Reputation: 1687Reputation: 1687Reputation: 1687Reputation: 1687Reputation: 1687
that is what happens every time you turn SE no and off
the driver need to be updated

that is why " setenforce 0" is preferd for temporally turning it no and off.
 
Old 03-08-2010, 07:21 PM   #5
DaveJL
LQ Newbie
 
Registered: Mar 2010
Posts: 7

Original Poster
Rep: Reputation: 0
Ok, thanks.

Just for the record, I did not purposely change the SE setting.
After the hard-kill during /etc/rc.d/rc.sysinit , the boot-up started to hang like this. I didn't even know what SE was before this problem.

Should I just let it continue to hang and hope it eventually finishes whatever it is doing?

Thanks again,
Dave

Last edited by DaveJL; 03-08-2010 at 07:22 PM.
 
Old 03-08-2010, 10:44 PM   #6
DaveJL
LQ Newbie
 
Registered: Mar 2010
Posts: 7

Original Poster
Rep: Reputation: 0
I'm now in Recovery Mode.

My /etc/fstab :

Code:
/dev/md1                /                       ext3    defaults,usrquota        1 1
/dev/md0                /boot                   ext3    defaults        1 2
tmpfs                   /dev/shm                tmpfs   defaults        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0
LABEL=SWAP-sdb2         swap                    swap    defaults        0 0
LABEL=SWAP-sda2         swap                    swap    defaults        0 0
fdisk -l yields:

Code:
# fdisk -l

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0001c6cf

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          13      104391   fd  Linux raid autodetect
/dev/sda2              14         655     5156865   82  Linux swap / Solaris
/dev/sda3             656       60801   483122745   fd  Linux raid autodetect

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0002ec98

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1          13      104391   fd  Linux raid autodetect
/dev/sdb2              14         655     5156865   82  Linux swap / Solaris
/dev/sdb3             656       60801   483122745   fd  Linux raid autodetect

Disk /dev/md1: 494.7 GB, 494717566976 bytes
2 heads, 4 sectors/track, 120780656 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000

Disk /dev/md1 doesn't contain a valid partition table
mdadm -E -s shows:

Code:
# mdadm -E -s
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=629bfb37:53a8883f:537f768e:e9290991
ARRAY /dev/md1 level=raid1 num-devices=2 UUID=adc78fa5:fac6da39:5ea2599b:29ca6912
When I try to mount /dev/md0, I get the error:

Code:
# mount -t ext3 /dev/md0 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/md0,
       missing codepage or helper program, or other error
       (could this be the IDE device where you in fact use
       ide-scsi so that sr0 or sda or so is needed?)
       In some cases useful info is found in syslog - try
       dmesg | tail  or so
dmesg | tail shows:

Code:
# dmesg | tail
[ 1349.012161] unionfs: new lower inode mtime (bindex=0, name=mdadm)
[ 1356.803854] md: md1 still in use.
[ 1356.870311] md: bind<sdb3>
[ 1356.906846] raid1: raid set md1 active with 1 out of 2 mirrors
[ 1356.906867] md1: detected capacity change from 0 to 494717566976
[ 1356.906978]  md1: unknown partition table
[ 1389.504015] EXT4-fs (md0): unable to read superblock
[ 1398.655582] EXT3-fs: unable to read superblock
[ 1808.394513] EXT2-fs: unable to read superblock
[ 1836.473091] EXT3-fs: unable to read superblock
When I try to fsck /dev/md0, I get:

Code:
# fsck /dev/md0
fsck 1.40.8 (13-Mar-2008)
e2fsck 1.40.8 (13-Mar-2008)
fsck.ext2: Invalid argument while trying to open /dev/md0

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:
    e2fsck -b 8193 <device>
I'm not sure how to proceed ... any guidance would be much appreciated.

Thanks,
Dave

Last edited by DaveJL; 03-08-2010 at 11:52 PM.
 
Old 06-23-2014, 06:56 AM   #7
arun5002
Member
 
Registered: Aug 2011
Location: Chennai,India
Distribution: Redhat,Centos,Ubuntu,Dedian
Posts: 549
Blog Entries: 5

Rep: Reputation: Disabled
Pressed e on the GRUB screen to edit the selected boot option. Scroll down to the kernel line and press e again to edit. Remove any instances of a serial console such as console=ttyS0 or console=ttyS1,115200. Press Enter to temporarily save changes and return to the previous screen, press b to boot the edited option.

Fixed the issue
 
  


Reply

Tags
boot, hangs, raid1, selinux, time


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
How can I disabled SELinux? abefroman Linux - Kernel 3 09-17-2006 10:22 AM
getsebool: SELinux is disabled ?? dansawyer Linux - Security 4 09-14-2006 03:31 PM
Mandriva 2006, Averatec notebook, ACPI causes IRQ 11 disabled, network hangs a2brute Linux - Laptop and Netbook 5 02-24-2006 07:31 PM
Sound disabled at boot DonMiner Fedora 1 07-12-2004 04:12 AM
DMA intermittently disabled, spontaneous reboots and hangs ... Tinkster Linux - Hardware 3 04-01-2004 01:54 PM


All times are GMT -5. The time now is 01:18 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration