Bash /sbin/fdisk Input/output Error
Contents |
Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME Get UbuntuKylin Ubuntu Code of Conduct Ubuntu Wiki Community Wiki Other Support Launchpad Answers Ubuntu IRC Support AskUbuntu linux bash: input/output error Official Documentation User Documentation Social Media Facebook Twitter Useful Links Distrowatch Bugs: Ubuntu
Mkdir: Cannot Create Directory : Input/output Error
PPAs: Ubuntu Web Upd8: Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search Forum input/output error kali linux The Ubuntu Forum Community Ubuntu Official Flavours Support General Help Dell Ubuntu Support (CLOSED) [ubuntu] Bash: Input/Output Error on every command Hello Unregistered, Dell Support Forum has closed. Please take a moment to read reading directory input output error linux the details in the sticky, which you can find by clicking here Having an Issue With Posting ? Do you want to help us debug the posting issues ? < is the place to report it, thanks ! Results 1 to 6 of 6 Thread: Bash: Input/Output Error on every command Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to
Input/output Error Centos
Threaded Mode September 27th, 2008 #1 manish_jain View Profile View Forum Posts Private Message First Cup of Ubuntu Join Date Jul 2006 Beans 8 Bash: Input/Output Error on every command Hi I have a very old Dell Inspiron on which Ubuntu 7.04 is installed. The kernel version is 2.6.24-19-generic. Sometimes, suddenly something happens and then every command from bash gives the same error: ~$ autoconf -V -bash: /usr/bin/autoconf: Input/output error ~$ ad -bash: /usr/bin/python: Input/output error The file system becomes read-only and no files can even be 'touch'ed. However, uname -r (and possibly other commands) still keep working. If you press Tab-Tab at the terminal, it hangs and then there is no way other than hard-boot to get stuff to work again. Can anyone suggest something to repair this annoying recurrence. Last edited by manish_jain; September 27th, 2008 at 12:48 AM. Adv Reply September 27th, 2008 #2 MJN View Profile View Forum Posts Private Message Visit Homepage Ubuntu addict and loving it Join Date Jan 2006 Location United Kingdom Beans 2,787 DistroKubuntu 6.06 Dapper Re: Bash: Input/Output Error on every command If your file-system is becoming read-only then it is a likely sign you are having disk troubles. The read-only action is an
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of -bash: /root/.bash_profile: input/output error this site About Us Learn more about Stack Overflow the company Business Learn input/output error ubuntu more about hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _
.bashrc Input/output Error
Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question https://ubuntuforums.org/showthread.php?t=930991 Anybody can answer The best answers are voted up and rise to the top ubuntu input/output error up vote 5 down vote favorite 2 I'm having a problem with Ubuntu that I'm finding hard to troubleshoot for reasons that will become clear: reboot -bash: /sbin/reboot: Input/output error dmesg -bash: /bin/dmesg: Input/output error ps -e ps: error while loading shared libraries: /lib/libproc-3.2.8.so: cannot read file http://superuser.com/questions/225788/ubuntu-input-output-error data: Input/output error lsof -bash: /usr/bin/lsof: Input/output error fsck -bash: /sbin/fsck: Input/output error badblocks -bash: /sbin/badblocks: Input/output error So I can't see what is going on, and I can't remotely reboot. What can I do to get to the bottom of this? Interestingly: init 0 Segmentation fault I can cat /var/syslog but not /var/log/messages or several other important files. less and more don't work, neither do tail or head, etc. linux ubuntu share|improve this question edited Dec 26 '10 at 7:52 asked Dec 26 '10 at 7:23 rplevy 147116 1 Sounds pretty similar to what you get after running sudo rm -rf /. (I did it on purpose, just to see what actually happens.) –AJMansfield Sep 12 '13 at 19:27 add a comment| 1 Answer 1 active oldest votes up vote 6 down vote accepted The system is having severe trouble reading off of your hard disk. It's likely that the disk is dead (almost certain), but it could be something as simple as a loose/disconnected cable (don't count on it). There isn't anything you can do to troubleshoot it from here. Just power it off. Check for loose connection
# reboot bash: /sbin/reboot: Input/output error # shutdown -r now bash: /sbin/shutdown: Input/output error Obviously, there is a problem http://www.linuxjournal.com/content/rebooting-magic-way with your drive. These commands are failing because the kernel is unable to load the /sbin/reboot and /sbin/shutdown binaries from the disk so that it can execute them. A fsck on the next boot might be able to correct whatever is wrong with the disk, but first you need to get the system to reboot. If your machine is located at output error 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 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 : input/output error 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 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. __