Linux /sbin/shutdown Input/output Error
Contents |
# reboot bash: /sbin/reboot: Input/output error # shutdown -r now bash: /sbin/shutdown: Input/output error Obviously, there is a problem with your drive. These commands are failing because the kernel is unable to load the /sbin/reboot linux bash input/output error and /sbin/shutdown binaries from the disk so that it can execute them. A fsck on
Input/output Error Centos
the next boot might be able to correct whatever is wrong with the disk, but first you need to get the system to reboot. input/output error linux If your machine is located at a managed hosting provider then you could submit a reboot ticket, but you'll have to wait for someone to take responsibility. Wouldn't it be nice if there was a way to ask input/output error ubuntu the kernel to reboot without needing to access the failing drive? Well, there is a way, and it is remarkably simple. The "magic SysRq key" provides a way to send commands directly to the kernel through the /proc filesystem. It is enabled via a kernel compile time option, CONFIG_MAGIC_SYSRQ, which seems to be standard on most distributions. First you must activate the magic SysRq option: echo 1 > /proc/sys/kernel/sysrq When you are ready to reboot the machine simply
Input/output Error Kali Linux
run the following: echo b > /proc/sysrq-trigger This does not attempt to unmount or sync filesystems, so it should only be used when absolutely necessary, but if your drive is already failing then that may not be a concern. In addition to rebooting the system the sysrq trick can be used to dump memory information to the console, sync all filesystems, remount all filesystems in read-only mode, send SIGTERM or SIGKILL to all processes except init, or power off the machine entirely, among other things. Also, instead of echoing into /proc/sys/kernel/sysrq each time you can activate the magic SysRq key at system boot time using sysctl, where supported: echo "kernel.sysrq = 1" >> /etc/sysctl.conf If you would like to learn more about magic SysRq you can read the sysrq.txt file in the kernel documentation. ______________________ Cory Wright https://www.corywright.org/
Login to save this as favorite Comments Comment viewing options Flat list - collapsedFlat list - expandedThreaded list - collapsedThreaded list - expanded Date - newest firstDate - oldest first 10 comments per page30 comments per page50 comments per page70 comments per page90 comments per page150 comments per page200 comments per page250 comments per page300 comments per page Select your preferred way to display the comments and click "Save settings" to activate your changes. echo 1 > Submitted by asr (not verified) on Fri, 01/08/2010 - 07:18. echo 1 > /proc/sys/kernel/sysrq bash: /proc/sys/kernel/snot working (/sbin/reboot: Input/output error) - Reboot Linux in emergency using MagicSysRQ kernel sysctl variable I've been in a situation today, where reading directory input output error linux one Linux server's hard drive SCSI driver or the physical drive is cannot open directory . input/output error starting to break off where in dmesg kernel log, I can see a lot of errors like: [178071.998440] sd
Input/output Error Redhat
0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK [178071.998440] end_request: I/O error, dev sda, sector 89615868 I tried a number of things to remount the hdd which was throwing out errors in read only http://www.linuxjournal.com/content/rebooting-magic-way mode, but almost all commands I typed on the server were either shown as missng or returning an error: Input/output error Just ot give you an idea what I mean, here is a paste from the shell: linux-server:/# vim /etc/fstab
-bash: vim: command not found
linux-server:/# vi /etc/fstab
-bash: vi: command not found
linux-server:/# mcedit /etc/fstab
-bash: http://www.pc-freak.net/blog/how-to-reboot-remotely-linux-server-if-reboot-shutdown-and-init-commands-are-not-working-sbinreboot-inputoutput-error-reboot-linux-in-emergency-using-magicsysrq-kernel-sysctl-variable/ /usr/bin/mcedit: Input/output error
linux-server:/# fdisk -l
-bash: /sbin/fdisk: Input/output error After I've tried all kind of things to try to diagnose the server and all seemed failing, I thought next a reboot might help as on server boot the filesystems will get checked with fsck and fsck might be able to fix (at least temporary) the mess. I went on and tried to restart the system, and guess what? I got: /sbin/reboot init Input/output error I hoped that at least /sbin/shutdown or /sbin/init commands might work out and since I couldn't use the reboot command I tried this two as well just to get once again: linux-server:/# shutdown -r now
bash: /sbin/shutdown: Input/output error
linux-server:/# init 6
bash: /sbin/init: Input/output error You see now the situation was not pinky, it seemed there was no way to reboot the system … Moreover the server is located in remote Data Center and I the tech support there is conducting assigned task with the speed of a turtle. The server had no remote reboot, web front end or anything and thefore I n
reboot bash: /sbin/reboot: Input/output error $ shutdown -r now bash: /sbin/shutdown: Input/output error 记得之前在sina的时候测试机也出现过类似的问题,当时是直接给运维同事电话重启了。。。 If the above reboot commands http://iallex.com/inputoutput-error-bad-blocks-how-to-restart-linux/ doesnot work try either forced reboot or shutdown # Forced https://www.experts-exchange.com/questions/23032948/Input-output-error-cannot-issue-shutdown-command.html Reboot echo 1 > /proc/sys/kernel/sysrq echo b > /proc/sysrq-trigger # Forced Shutdown echo 1 > /proc/sys/kernel/sysrq echo o > /proc/sysrq-trigger see also for details Save To: Delicious Facebook Twitter Weibo WebIM QZone This entry was posted in linux and tagged centos on output error Aug 23rd, 2013 by Allex Wang. Post navigation ← osx (mac) 下面在 /home/新建目录或ln -sf 目录问题 libpcre.so.1: cannont open shared object file: No such file or directory. → Recent Posts Git Basics: branch cleanup Bash array tutorial Nodejs memory leak detector Add cron jobs to delete logs periodically Avoid Getting Redirected to Country-Specific Versions output error linux of Google VIM skills Git get back some commit from (no branch) Fix nginx ssi unsafe URI was detected error GitLab Installation on CentOS with nginx integration Running compass watch in the background Tagsandroid apache bash centos chrome compass cron DBA f2e git grub howto html5 issues javascript linux maven mobile mysql nginx nodejs offline optimization osx performance php project proxy readhat rpm sass server-security shell snippet ssh svn sysadmin tips tricks ubuntu vbox vim vps www yum Categories develop android java javascript mysql nodejs php web english howto linux osx programming server technical video vim virtualization Latest DeliciousData Loading, please wait... Hi, I'm Allex. since 2011, by Allex Wang Except where otherwise noted, content on this page is licensed under the Creative Commons Attribution 3.0 License, and code samples are licensed under the Apache 2.0 License. Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer’s view in any way.
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Input/output error - cannot issue shutdown command Want to Advertise Here? Solved Input/output error - cannot issue shutdown command Posted on 2007-12-19 Linux 2 Verified Solutions 9 Comments 2,094 Views Last Modified: 2012-08-13 One of our nameservers is not functioning propertly anymore (dns requests fail). I login to this server using SSH (putty). This works fine. A lot of command don't work anymore, all giving input-output errors. For example the shutdown command: ns2:~# shutdown -r now -bash: /sbin/shutdown: Input/output error Does anybody now what's wrong and how I can maybe restart the server in an alternative way? The server is not in the same location as me. 0 Question by:javelinict Facebook Twitter LinkedIn Google LVL 39 Active 2 days ago Best Solution byevilrix You'll need to check the error logs really. If could have been anything. Check /var/logs/* (usually 'messages'). Go to Solution 7 Comments LVL 39 Overall: Level 39 Linux 6 Message Active 2 days ago Expert Comment by:evilrix2007-12-19 Try sync init 0 0 Message Author Comment by:javelinict2007-12-19 Hi Evilrix, that doesn't work. No error but also no output, and no restart or shutdown. ns2:/usr/bin# ns2:/usr/bin# whois -bash: /usr/bin/whois: Input/output error ns2:/usr/bin# sync ns2:/usr/bin# init 0 ns2:/usr/bin# 0 LVL 39 Overall: Level 39 Linux 6 Message Active 2 days ago Expert Comment by:evilrix2007-12-19 What about telinit 0 ? Ultimately, if once you've run sync you could just power off the box. As long as you have ext3 journaling file system it's unlikely to cause any real problems. Even if you don't it'll almost certainly recover without any real issue. Sometimes, as a last resort, this is all you can do! 0 LVL 39 Overall: Level 39 Linux 6 Message Active 2 days ago Expert Comment by:evilrix2007-12-19 You c