Linux - SoftwareThis 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.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
My Redhat box hangs on boot up after "SELinux: Disbled at runtime" ...
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.
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?
# 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:
# 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:
# 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.
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.