Buffer I/o Error On Device Fd0 Logical Block 0 Ubuntu
Contents |
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour 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 buffer i o error on device sdb logical block 0 of this site About Us Learn more about Stack Overflow the company Business buffer i o error on device sdc logical block 0 Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ buffer i o error on device sr0 logical block 0 Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody buffer i o error on device sdc1 logical block can answer The best answers are voted up and rise to the top “Buffer I/O error on device fd0, logical block 0” error up vote 5 down vote favorite 2 I am using Ubuntu 12.10, today update notification popped up and I updated the system, then it asked for restart, I was doing some stuff so I restarted after ~30 minutes, after restart, Ubuntu
Buffer I O Error On Device Sda Logical Block
GUI was gone, there was no taskbar or unity, I fixed by entering this commands: sudo apt-get install linux-source sudo apt-get install linux-headers-generic sudo apt-get remove nvidia-current-updates sudo apt-get install nvidia-current-updates ... these commands fixed almost everything, unity is running, but there's problem when I go in terminal ctrl+alt+F1, before I write anything, many many messages appear, it says "Buffer I/O error on device fd0, logical block 0", what should I do? Here's image: http://i.imgur.com/JBD5x.jpg Another thing I noticed is that after few about an hour, messages disappear, this error keeps showing up for first hour roughly. gnome-terminal share|improve this question edited Nov 6 '12 at 11:09 asked Nov 6 '12 at 7:46 Paul Dirac 148116 add a comment| 3 Answers 3 active oldest votes up vote 11 down vote accepted This is indeed most likely an issue with Ubuntu thinking you have a floppy drive when you do not, and it thinks that because your BIOS is telling it to think that. My BIOS is an Award Software BIOS; I believe Phoenix is the same company. At boot of computer, press DEL to enter BIOS setup (this might be a diff
10, 2007 in CentOS, Hardware, Linux, RedHat and Friends, Suse, TroubleshootingQ. I’ve CentOS 5 server running on Dell hardware. I’m getting following error message in my /var/log/message file (some time
End_request I/o Error Dev Fd0 Sector 0 Vmware
message is also shown on console):
Jul 05 12:04:05 dell01 kernel: end_request: I/O ubuntu blk_update_request: i/o error, dev fd0, sector 0 error, dev fd0, sector 0 Jul 05 12:04:05 dell01 kernel: Buffer I/O error on device fd0, logical block 0 what is fd0 Jul 05 12:04:18 dell01 kernel: end_request: I/O error, dev fd0, sector 0 Jul 05 12:04:18 dell01 kernel: Buffer I/O error on device fd0, logical block 0 Jul 05 12:04:30 dell01 kernel: end_request: https://askubuntu.com/questions/213512/buffer-i-o-error-on-device-fd0-logical-block-0-error/233818 I/O error, dev fd0, sector 0 Jul 05 12:04:42 dell01 kernel: end_request: I/O error, dev fd0, sector 0What do they mean? How do I fix this problem?A. This message appears when you don’t have a floppy drive attached to Linux server. Solution is quite simple just disable driver for floppy and reboot the system. You can verify this with the following command (this solution http://www.cyberciti.biz/faq/linux-end_request-ioerror-dev-fd0-sector0/ works with RHEL, CentOS, Redhat, Ubuntu/Debian and other Linux distros) : # lsmod | grep -i floppy Output:floppy 95465 0Open file called /etc/modprobe.d/blacklist: # vi /etc/modprobe.d/blacklist Listing a module (driver name) in this file prevents the hotplug scripts from loading it. Usually that'd be so that some other driver will bind it instead, no matter which driver happens to get probed first. Sometimes user mode tools can also control driver binding. Append following line: blacklist floppy Save and close the file. Now reboot the Linux server: # reboot Share this tutorial on:TwitterFacebookGoogle+Download PDF version Found an error/typo on this page?About the author: Vivek Gite is a seasoned sysadmin and a trainer for the Linux/Unix & shell scripting. Follow him on Twitter. OR read more like this:Linux: Reset High Speed USB Device Using ehci_hcd Error and SolutionCentOS / Red Hat / Fedora Linux Turn off Beep / Bell Terminal SoundDebian Linux boot disk creationFATAL: Error inserting it87…You need to have the Linux kernel source installed for this driverLinux Disable Mounting of Uncommon FilesystemLinux Disable USB Devices (Disable loading of USB Storage Driver)Linux Broadcom Ethernet Card driver installationLinux Boot Disk under Rebug report is a duplicate of: Bug #820519: Live session boot time too hight (end_request: https://bugs.launchpad.net/bugs/932106 I/O error, dev fd0, sector 0). Edit Remove 6 This bug https://bugzilla.redhat.com/show_bug.cgi?id=565693 affects 1 person Affects Status Importance Assigned to Milestone linux (Ubuntu) Edit Confirmed Medium Unassigned Edit Also affects project (?) Also affects distribution/package Nominate for series Bug Description Hello Testing build 10.04.04 20120214.2 from usb key I can observe a very o error large boot time due to Buffer I/O error on device fd0, logical block 0 In a system without floppy and disable in the bios too. Thanks Fabio --to have this session working I have to substitute vesamenu.32 file// ProblemType: BugDistroRelease: Ubuntu 10.04 Package: casper 1.236.3 ProcVersionSignature: Ubuntu 2.6.32-38.83-generic 2.6.32.52+drm33.21 Uname: Linux 2.6.32-38-generic x86_64 error on device Architecture: amd64 Date: Tue Feb 14 15:09:47 2012LiveMediaBuild: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release amd64 (20120214.2) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: casper --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ubuntu 3878 F.... pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'ICH'/'Intel ICH with ALC850 at irq 23' Mixer name : 'Realtek ALC850 rev 0' Components : 'AC97a:414c4790' Controls : 42 Simple ctrls : 27 DistroRelease: Ubuntu 10.04 LiveMediaBuild: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release amd64 (20120214.2) Lsusb: Bus 002 Device 002: ID 046d:c050 Logitech, Inc. RX 250 Optical Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 003: ID 0718:0628 Imation Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) ProcCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- BOOT_IMAGE=/casper/vmlinuz ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-38.83-g
Format For Printing -XML -Clone This Bug -Last Comment First Last Prev Next This bug is not in your last search results. Bug565693 - Install boot hangs for a long time probing floppy drive Summary: Install boot hangs for a long time probing floppy drive Status: CLOSED WORKSFORME Aliases: None Product: Fedora Classification: Fedora Component: kernel (Show other bugs) Sub Component: --- Version: 13 Hardware: All Linux Priority low Severity medium TargetMilestone: --- TargetRelease: --- Assigned To: Kernel Maintainer List QA Contact: Fedora Extras Quality Assurance Docs Contact: URL: Whiteboard: Keywords: Duplicates: 574492 586037 (view as bug list) Depends On: Blocks: 494832 585927 Show dependency tree /graph Reported: 2010-02-15 18:09 EST by Orion Poplawski Modified: 2011-04-24 09:42 EDT (History) CC List: 21 users (show) anton bruno covex didierg-divers dougsland fcdanilo fedora gansalmon gilboad hdegoede itamar jan.mussche jonathan jon.dufresne kernel-maint megareg mike pcfe vanmeeuwen+fedora vedran wim.cos See Also: Fixed In Version: Doc Type: Bug Fix Doc Text: Story Points: --- Clone Of: Clones: 585927 (view as bug list) Environment: Last Closed: 2011-04-24 09:42:14 EDT Type: --- Regression: --- Mount Type: --- Documentation: --- CRM: Verified Versions: Category: --- oVirt Team: --- RHEL 7.3 requirements from Atomic Host: Cloudforms Team: --- Attachments (Terms of Use) Add an attachment (proposed patch, testcase, etc.) Groups: None (edit) Description Orion Poplawski 2010-02-15 18:09:58 EST Description of problem: PXE/ks install on old Dell laptop. Install hangs for quite a while probing for a non-existent floppy drive. Version-Release number of selected component (if applicable): 13.26 syslog contains messages like: 15:54:39,095 ERR kernel:end_request: I/O error, dev fd0, sector 0 15:55:17,226 ERR kernel:end_request: I/O error, dev fd0, sector 0 15:55:17,226 ERR kernel:Buffer I/O error on device fd0, logical block 0 15:55:55,361 ERR kernel:end_request: I/O error, dev fd0, sector 0 15:55:55,364 ERR kernel:Buffer I/O error on device fd0, logical block 0 15:56:33,492 ERR kernel:end_request: I/O error, dev fd0, sector 0 15:56:33,494 ERR kernel:Buffer I/O error on device fd0, logical block 0 15:56:59,697 ERR udevd: worker [374] unexpectedly returned with status 0x0100 15:56:59,700 ERR udevd: worker [374] failed while handling '/devices/platform/floppy.0/block/fd0' Comment 1 Hans de Goede 2010-02-16 03:10:40 EST The problem is the kernel thinks you have a floppy drive, while you don't. This is usually caused by the BIOS reporting a floppy d