General :: Kill XServer (Init 3 / 5 Does Not Work)
Feb 23, 2011
I'm running Linux Mint 10, although I've had this same issue with other variants of Linux. I've been told/found while researching that if the X server hangs or otherwise errors, one can drop to a root prompt, usually at another tty, and execute init 3 (to drop to single user mode) and then init 5 to return to the default, graphical session. Needless to say, I've tried this before in multiple configurations on multiple machines to no avail.
The only feedback I receive form executing those two commands is a listing of VMWare services (from a kernel module) that are stopped and then restarted. If I run startx (either before or after init 3), then I am told that the xserver is still running and that I should remove /tmp/.X0-lock. Having tried that, it removes that error message, but claims that the xserver cannot be attached as another instance is running. How do I kill the xserver completely? Can I killall some process name?
For a special purpose I needed a initramfs - that didn't work. So I reduced the initramfs setup to the simplest.
Mount the root and switch_root into it. But that didn't work either.
If I go with the init-script for the initramfs I posted below the system prints out the switch_root usage-text from busybox. But the syntax is right, ain't it?
When I use chroot instead of switch_root then it prints the usage-text of init before the kernel panic.
If I try with "/sbin/init 5" then, after a while the system reports "init: timeout opening/writing control channel /dev/initctl".
In the other cases I get the following error messages before the system hangs: "Kernel Panic", "Attempted to kill init", "init not tainted"
(With the init script below there is a error saying:"sh: can't access tty; job control turned off". I know why it's there - but don't know if it is connected to this problem.)
This information may be important: - The machine boots from a usb-harddisk - /sbin/init on the new root is available - the system on newroot is sane and runs perfect standalone (without initramfs) - the system on newroot uses baselayout-2 with openrc - busybox is built as static binary - busybox version is v1.15.3
I used ubuntu in my ARM board. but now i rebooted it says that "kernel panic - not syncing: Attempted to kill init!" i have to reinstall my OS or any other way to get retify?
Our email server and fax server configured in a Linux server.2day mornin onwards i am getting the error.kernal panic -not syncing : attempted to kill init.
Bootin "powerserver"(Centos-4 i386)-up( 2.6.9-11 EL) root (hd0,0) Filesystem type is ext2fs,partition type 0*fd
How to resolve "kernel panic not syncing attempted to kill init" problem in Linux?? And why this error occurs? In my case, this error occurs when i boot my computer and after this error my computer goes on rebooting..
I was unable to access the server and had to reboot it. When the server was booting after the Grub, it errored out withKernal Panic -not syncing Attempted to Kill init!!exec of init (/sbin/init/) failed No such directoryI reboot into the recuse mode from the CD and when looking for the installed OS.I got an error like thisFound OS but with errors.Mounting part or all of your system at /mnt/sysimage.. something of the sort. I've run fsk -y on the /boot and root drives and rebooted but still the same issues.Here is my grub.conf:
# grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file
I recently installed new hard drive and cloned old hard drive software onto it. The bootloader installs either linux or other operating system. Ever since the cloning, boot hangs. Words in the thread title are the last to appear before everything grinds to a halt. Just before the kernal panic message appears, "Initrd finished" is last line. Will have to try booting again to find more info before this.
I'm running the latest Xubuntu and can't seem to kill the xserver to install the nvidia dev drivers. where I could find the program to kill the server? I tried Top and it kept coming back!
I Downloaded the 6 CD's of CentOS installation , and I start install them on my machine : Processor : Intel Pentium 4 -2.08 Ghz Ram: 256 MB cash :512kb HDD: 80GB (it is for home server purposes)
After the fourth disc the system ask to reboot the system ; so I restart it ok? What I get ? No OS. Just a long text : I think the bootup run ok, then this line came out I think it reveal some thing that Pros will know it: nash received SIGSEGV Backtrace : [0x804fb35] [0x488420] [0x......... [0x........ [0x......] then Kernel panic - not syncing: Attempted to kill init!
am trying to interface ade7758(adc) to at91sam9261...i have written a sample code which registers an spi driver and sends an address to ade7758 and receives a data...every thing is fine.My device is registered but kernel is giving a crash message....below is the message....
exec of init (/sbin/init) failed!!! : 2 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill init! My server is at remote end which I access through Public IP.
I just imaged my RHEL 4 system that was running on a Dell Poweredge 2950 server using Acronis software and I restored the image to a VmWare virtual machine.
Dell Poweredge 2950 - RAID 5 VmWare - using ESX 4.0 OS - Red Hat Enterprise Linux 4 ES Update 5 x64 kernel - 2.6.9-55.0.9.ELsmp
I'm getting the following when I try to boot on the new virtual machine. I'm thinking it has to do with the fact that it's new hardware and it's having trouble either finding the right drivers or pointing to the correct place.
"No Volume Groups found Volume Group "Volgroup00" not found ERROR: /bin/lvm exited abnormally! (pid505) mount: error 6 mounting ext3 mount: error 2 mounting none switchroot: mount failed: 22 umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!" I was able to boot into Linux rescue mode using the boot CD. Then I typed: #chroot /mnt/sysimage
Here's all the info from the commands I typed: #ldd /bin/bash libtermcap.so.2 => /lib64/libtermcap.so.2 libdl.so.2 => /lib64/libdl.so.2 libc.so.6 => /lib64/tls/libc.so.6 /lib64/ld-linux-x86-64.so.2 #uname -a Linux localhost.localdomain 2.6.9-89.EL x86_64 #df -h ....
I've tried the following: 1. mkinitrd -v -f /boot/initrd-2.6.9-55.0.9.EL.img 2.6.9-55.0.9.EL 2. modified the device.map to point to /dev/sda3 3. changed the SCSI controller in Vmware to use BusLogic instead of LSI Logic. (didn't work because I'm running 64 bit.. gave me an error message) 4. grub-install --recheck /dev/sda 5. tried booting to differerent OS versions (i.e. 2.6.9-55.0.6, etc.). I tried all of the versions listed in the boot menu. None of these worked.
I got the following error after compiling kernel version 2.6.38.2 from sources with this Howto:[URL].. Creating root device.
Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults
Today I was upgrading my netbook with Ubuntu 10.10 on it to 11.04 via the Update Manager. I got a few errors and the Update Manager seemed like it wasn't continuing, so decided to exit it. It didn't respond so after a while I decided to restart the netbook. However the on/off/standby/restart, etc. button in the top right wasn't responding either, so I decided to force a shutdown with the power button on my netbook. Now Ubuntu doesn't start up, and gives me an error along the lines of:
Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not tainted 2.6.35-28-generic #50-Ubuntu Now could I in some way repair my Ubuntu installation while still keeping the files I already have on my computer? Maybe via booting from a flash drive or something...?
When loading puppy linux on my computer from a CD I get an error message on the third step which is (loading the lup525.sfs mainfile)to ram. kernel panic not synching attempt to kill init. The CD works on other computers with no problems. My computer is a dual boot XP and Win7 machine.
I have CentoS 5.3 and switching init levels does not work.when I login console mode,doesnot work ctrl+F7 key...and on the contrary.when Im in graphical mode, does not work ctrl+F1...ctrl+F6 keys.
I boot from CD (Tried both debian-506-i386 and the Netinstall) I also tried the flags acpi=off noapic nolapic And when it starts booting the install, it appears: "Kernel panic- not syncing: attempted to kill init"
I'm running XBMC media center which is built on Ubuntu and I'm trying to mount a network share, but I can't seem to automate it. If I manually run:
Code:
mount -t cifs -o file_mode=0777,dir_mode=0777 //192.168.1.20/disk7/xbmc_thumbs/Thumbnails /home/kevin/.xbmc/userdata/Thumbnails
The mount is created and everything works fine. But obviously the mount eill be lost on the next boot. A few months back, when I was running a previous version of XBMC and first instructed on how to do this, I was told to put that command in /etc/init.d/rc.local so the mount would automatically be created at boot. I did and it worked. The other day I upgraded to a new XBMC build (which is built on the newer Lucid Ubuntu) and while the same command creates the mount, putting it in /etc/init.d/rc.local does not create it on boot. Someone suggested the fstab was the better place to create the mount. So I inserted the following in /etc/fstab:
I'm trying to write a init.d script to daemonise a sagemath notebook server. Here's what I've done so far, I've copied /etc/init.d/single for the structure, and tried to use dtach to provide a handle to access the process. However, my main problem is issuing the signals to kill the process (Ctrl-C) from a bash script and exit dtach (Ctrl-`)
Now I tried installing the KDE destop enviremont, the install went just fine but when I try to log into KDE I see the startup screen for a second then everything goes dark.It stays that way in the background i think the desktop is there because the mouse cursor is there, I can move it around but that's all.Does KDE work differently and so can the different xserver be the cause of KDE not working?
It does this all the time whenever I reboot and I hadn't rebooted my PC in months simply because it's a GOD DAMN pain to figure this crap out. I need a REAL fix.
My computer turns off and boots, it goes directly into Recovery Menu. It refuses to boot normally. I load low graphics mode, it doesn't even let me make changes to the configuration file, OR let me have ONE session in low graphics mode. I've tried reconfiguring xserver, re-installing nvidia drivers, STILL the same effing garbage. It's starting to **** me off. I'm mostly a Linux noob, and I hate trying all these "tips" that don't work to make my stupid display work. I use gnome. Any advice, tips whatever to make this work? If you need something, I'll try my best to get it but I'm on my other computer right now so displaying my configuration files will be a pain. :/ Before I installed vesa, low graphics mode wouldn't work because it said the vesa module didn't exist and it also said no screens.
I just installed my machine with ubuntu 9.04. When I run "init 3" or "telinit 3", nothing happens. I need to exit the X server to install a video driver.
This is my first init script, so far, it atleast starts the daemon but it fails at creating a pid, so later on I can use to, to either stop it or reload it. Here's the current code: Further more, the script returns ok that it started the pid, when in fact, the pid fails in the background, this script needs MUCH improvement, some help would be nice to fix this script. :/
Today I run OpenOffice.org extensions update and it freezed fter showing me that everything was successful.When i xkilled it it refused tolaunch without any problem indication.killall soffice.bin didn't report "No process found" after 1,2,3...20 times.So I tried killall soffice.bin -i
the process is mcelog. When I do as root kill -9 2323 which is pid of mcelog the process is not killed. I tried doing the same from top, press K and enter pid of mcelog. doing ps auwx | grep mcelog I see there are several results. I tried killing all of them like kill -9 2355 2341 3425 2345. But re-running the above commands still shows them as running. How else would I troubleshoot this to avoid restarting of the box.
What a nuisance after upgrading from Fedora 12 to Fedora 13 the terminal initialisation and the running of agetty agetty doesn't work any more. Same for printer configurations. Apparently this should now be done in /etc/sysconfig/init but where is the documentation? how to use the new /etc/sysconfig/init to do what the event.d scripts used to do.
