Fsck Bus Error Ubuntu
Contents |
Technology and Trends Enterprise Architecture and EAI ERP Hardware IT Management and Strategy Java Knowledge Management Linux
Bus Error Core Dumped Linux
Networking Oracle PeopleSoft Project and Portfolio Management SAP SCM Security Siebel linux bus error Storage UNIX Visual Basic Web Design and Development Windows < Back CHOOSE A DISCUSSION GROUP Research Directory TOPICS Database Hardware Networking SAP Security Web Design MEMBERS Paul_Pedant DACREE MarkDeVries MacProTX Inside-ERP VoIP_News Inside-CRM I_am_the_dragon maxwellarnold Michael Meyers-Jouan TerryCurran Chris_Day Andrew.S.Baker Ramnath.Awate JoeTorre Locutus Dennis Stevenson bracke Craig Borysowich DukeGanote Richard PCMag mircea_luca Nikki Klein iudithm AbhaiTripathi knowscognosdoi Clinton Jones Iqbalyk bluesguyAZ59 COMPANIES Service Max Fiberlink Communications Hewlett Packard Epicor Software ... View All Topics View All Members View All Companies Toolbox for IT Topics Linux Groups Ask a New Question Linux - General Discussions The Linux Administration group is for the discussion of technical issues technical issues that arise during the administration of Linux systems, including maintaining the operating system and supporting end-user applications. Home | Invite Peers | More Linux Groups Your account is ready. You're now being signed in. Solve problems - It's Free Create your account in seconds E-mail address is taken If this is your account,sign in here Email address Username Between 5 and 30 characters. No spaces please The Profile Name is already in use Password Notify me of new activity in this group: Real Time Daily Never Keep me informed of the latest: White Papers Newsletter Jobs By clicking "Join Now", you agree to Toolbox for Technology terms of use, and have read and understand our privacy policy. Unable to run some commands 'Bus error' sajesh pp asked Jul 19, 2010 | Replies (4) Hi, When i run the command ntsysv i am getting Bus error. I have c
List Slug Success Stories Slug-Related Articles Project Mailing Lists Project IRC Channels Donations and Sponsors NSLU2-Linux Photo Gallery OS/Firmware Projects NSLU2-Linux Development How Do I Get Involved? Unslung Firmware Debian Installation SlugOS Firmware OpenSlug Firmware SlugOS/LE Firmware OpenWrt Firmware Angstrom Firmware UcSlugC Firmware GentooSlug Firmware UpSlug Upload Tool Puppy Topfield Access Firmware Targets Linksys NSLU2 Iomega NAS 100d D-Link DSM-G600 Freecom FSG-3 Optware Optware Home Page Optware Packages Optware Targets Maxtor MSS II Qnap TurboStation Synology DS-101(g+) Linksys WRP400 Plug Computers Other Hardware Linksys NAS200 Iomega StorCenter Wiki Resources Wiki Documentation Wiki Sandbox Sponsored Links hosting by: edit · pmwiki.org view · edit · print · history FAQ » RepairingDiskErrors How to check your disk for errors http://linux.ittoolbox.com/groups/technical-functional/linuxadmin-l/unable-to-run-some-commands-bus-error-3641099 (and repair them) The scandisk function of the Linksys web interface will not work when the disk is unslung as it is then in use and cannot be unmounted. The following steps can be used instead. Boot the slug without disk. Enable telnet (http://IP-address-of-your-slug/Management/telnet.cgi user admin, password admin) Log in with telnet (user root, password uNSLUng as your own password resides only on the external disk. Connect the disk. After a short while the http://www.nslu2-linux.org/wiki/FAQ/RepairingDiskErrors partitions should be mounted automatically (note that mounting can take quite some time - perhaps 30 minutes - with disks that contain many files, due to the firmware 'quotacheck' function). Through telnet unmount all drives. umount /dev/sda1 umount /dev/sda2 (if you get an error that no device is mounted use "mount" to find out the name of the device; look for devices that are mounted as /share/hdd/data and /share/hdd/conf). The web interface may still not allow you to scan. The log may say: "Warning: Out of disk space, scandisk cannot proceed." Instead you can now, in the Telnet session, issue the commands /sbin/fsck.ext3 -f /dev/sda1 /sbin/fsck.ext3 -f /dev/sda2 This will check the disk for you, the -f flag forces a check even if the file system appears sane at first glance. If you want to you can add the -y flag to the command. This will answer all questions with yes automatically (which is generally the best choice anyway). WARNING: be sure to reboot your slug after doing this (to avoid that you accidentally fill up the flash filesystem) Alternative: you could also remove the USB hard drive / flash drive from the slug and connect it to a Linux box and run fsck from there as well. fsck and e2fsck is the same thing, so use either (one
Start 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 this site About Us Learn http://serverfault.com/questions/57920/bus-error-when-trying-to-reboot-linux more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and bus error rise to the top “bus error” when trying to reboot Linux up vote 5 down vote favorite 6 When trying to reboot a Linux server I got the typical 'System going down for reboot now', but the server has not rebooted. I have tried: reboot shutdown -r now The runlevel command returns 5. Any other options for getting this server to reboot? This is a remote machine, so I fsck bus error don't want to just shut it down if I can avoid that. I am trying to reboot because of a journal abort on /, so / is read-only. Most commands now return 'bus error' linux share|improve this question asked Aug 24 '09 at 13:06 Kyle Brandt♦ 57.6k41217385 A bus error is typically a result of a corrupted binary. One place I worked people would complain that the system was broken because their long running simulation would crash with a bus error whenever they compiled another simulation. "What did you call the simulation?" "huh" "okay -- what do you type to run the simulation?" "a.out" "okay, maybe you should rename your programs before you run them..." sigh. –chris Aug 24 '09 at 13:29 Oh -- except for netscape. For that, bus error was one of two common ways it exited. It was about 2/1 segfault vs bus error, but they changed it up to keep the internet fun... –chris Aug 24 '09 at 13:30 add a comment| 6 Answers 6 active oldest votes up vote 11 down vote accepted Kyle, I'm not quite sure if this is what you're looking for (since it's like pressing the reset button), but this has h