I/o Error Dev Fd0 Sector 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 ubuntu blk_update_request: i/o error, dev fd0, sector 0 Discuss the workings and policies of this site About Us Learn more end_request i/o error dev fd0 sector 0 vmware about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Ask Ubuntu
What Is Fd0
Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign
Blk_update_request Io Error
up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top blk_update_request: I/O error, dev fd0, sector 0 up vote 0 down vote favorite 1 This happened after a kernel update. Whenever I try to boot, my computer says "Error getting authority: Error initializing authority: Could not i o error dev fd0 sector 0 ubuntu connect: No such file or directory (g-io-error-quark, 1) Welcome to emergency mode!..." followed by abunch of things I can do. It spits the same error out if I ctrl-d to boot into default mode, and the fstab file matches the drive UUIDs perfectly. But I think I found the culprit. When I run blkid, it takes a while, and then spits out "blk_update_request: I/O error, dev fd0, sector 0" followed by the drives' data. What is happening, why, and how do I fix it? I tried the possible duplicate question, but it is a slightly different error and the solution doesn't work. filesystem share|improve this question edited Jan 9 at 15:31 asked Jan 9 at 14:17 Ben 62212 1 Possible duplicate of "Buffer I/O error on device fd0, logical block 0" error –Mark Kirby Jan 9 at 14:38 I figured out that I can get it to work if I boot into recoovery mode and then tell it to fix broken packages. It doesn't seem to matter if this was sucessful or not
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and
End_request I/o Error Dev Fd0 Sector 0 Redhat
policies of this site About Us Learn more about Stack Overflow the blk_update_request i/o error fd0 company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges kernel blk_update_request i o error dev fd0 sector 0 Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a http://askubuntu.com/questions/719058/blk-update-request-i-o-error-dev-fd0-sector-0 minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top blk_update_request: I/O error, dev fd0, sector 0 up vote 1 down vote favorite I recently started noticing some blk_update_request: I/O error, dev fd0, sector 0 errors on my second computer running Arch Linux that I use as http://unix.stackexchange.com/questions/282845/blk-update-request-i-o-error-dev-fd0-sector-0 a server. This began when I had to reboot the computer when I moved into a new apartment. I had the following /etc/fstab configuration: # # /etc/fstab: static file system information # #
based cloning solution on top of Ubuntu 9.04. Now, this is working with Linux kernels and all so I assume I can be helped here. Despite me getting these errors with 1 https://ubuntuforums.org/archive/index.php/t-1163250.html particular computer, the computer still images just fine. I'm just wondering what this particular error (seen in the subject) means, and how it works, etc. Can anybody offer any info in this department? RoastedMay 25th, 2009, 03:34 PMAny idea? I'm pretty sure this is a Linux thing since FOG is linux based, so I was just curious what the nature of that error was, because even when I get the error the imaging process still o error works fine. thedohmanMay 28th, 2009, 05:43 AMHi I have the same error. I get: [22.813835] end_request: I/O error, dev fd0, sector 0 [35.877830] end_request: I/O error, dev fd0, sector 0 [35.877869] Buffer I/O error on device fd0, logical block 0 the end_request line is every 13 seconds, and every other one is followed by the Buffer I/O line until the last one at 404.570280. the boot continues at 422 with "udev: starting version 141", and everything error dev fd0 seems to be fine after that 6-7 minute delay. Xubuntu 9.04, Live USB created with PORTABLELNX. I know it's trying to read the floppy drive, only it's a laptop and doesn't have a floppy drive. I found a reference to the same error on the redhat bugtracker (here: Bug ID 491230 (https://bugzilla.redhat.com/show_bug.cgi?id=491230)), but it turns out to be a kernal with compiled in floppy driver (not a module, as is norm), or could be caused by lvm or by specifying root (in the kernel cmdline, through grub.conf) as UUID= or LABEL=, lvm will scan all block devices (although it may skip floppies) for physical volumes and specifying root as UUID= / LABEL= will cause nash to scan all block devices to find the UUID / LABEL. You could try working around this by specifying your root= as /dev/.... in grub.conf My grub.conf uses (hd0,0) so that shouldn't be an issue. Since it's a live install, I can't use /dev/... anyway as it may show up different on other computers. (Someone correct me if I'm wrong! ;)) Live CD boots fine without the issue (but the CD drive has dust issues, so it really only boots half the time in this computer, hence the use of the USB drive.) I'll reboot now to see if there is an option in BIOS to disable the (nonexistant