Buffer I/o Error On Device Loop0
Contents |
to Milestone Wubi Edit Fix Released High Agostino Russo Edit 8.04 In Progress High Agostino Russo Edit linux buffer i/o error on device loop0 logical block (Ubuntu) Edit Invalid Undecided Unassigned Edit Hardy Invalid Undecided Unassigned Edit Intrepid clonezilla buffer i o error on device Invalid Undecided Unassigned Edit lupin (Ubuntu) Edit Fix Released Undecided Unassigned Edit Hardy Won't Fix Undecided Unassigned buffer i o error on device sr0 Edit Intrepid Fix Released Undecided Unassigned Edit ntfs-3g (Ubuntu) Edit Fix Released Undecided Unassigned Edit Hardy Fix Released Undecided Unassigned Edit Ubuntu ubuntu-8.04.2 Intrepid Fix Released Undecided Unassigned
Kernel Buffer I O Error On Device
Edit Also affects project (?) Also affects distribution/package Nominate for series Bug Description LATEST ISO TESTED: Ubuntu amd64 20080411 w/ wubi rev 482 ISO TESTED: Ubuntu amd64 20080319 After what seemed to be a successful install via wubi I am unable to login to the system. I booted into rescue mode and found in dmesg the linux buffer i o error on device following: Buffer I/O error on device loop0, logical block 872512 lost page write due to I/O error, on loop0 ... EXT3-fs error (device loop0): ext3_get_inode_loc: unable to read inode block - inode=114030, block=229669 Aborting journal on device loop0. __journal_remove_journal_head: freeing b_committed_data (repeat 6x) Remounting filesystem read-only See original description Tags: verification-done iso-testing Edit Tag help Related branches lp:ubuntu/karmic/lupin Evan (ev) wrote on 2008-03-20: #1 Brian, Were you by any chance using an amd64 image on VMWare? Brian Murray (brian-murray) wrote on 2008-03-20: #2 No, this was / is on real hardware. Brian Murray (brian-murray) wrote on 2008-03-20: #3 divide error and task_dirty_limit Edit (3.0 MiB, image/jpeg) This is from a crash when booting into single user mode. Brian Murray (brian-murray) wrote on 2008-03-20: #4 mark_buffer_dirty Edit (3.1 MiB, image/jpeg) 2nd call trace. Agostino Russo (ago) wrote on 2008-03-20: #5 Changed in wubi: assignee: nobody → ago importance: Undecided → Low status: New → Confirmed assignee: ago → nobody importance: Low → Undecided status: Confirmed → New David Bur
on device sr0 Issues related to hardware problems Post Reply Print view Search Advanced search 13 posts 1 2 buffer i o error on device sda Next BubikolRamios Posts: 67 Joined: 2009/10/04 09:14:05 buffer i/o error on
Buffer I O Error On Device Sdc
device sr0 Quote Postby BubikolRamios » 2011/10/15 23:19:03 Server ok like 2 years, now:memory for crash kernel
Buffer I O Error On Device Sdc1
(0x0 to 0x0 ) not within permiseable rangebuffer i/o error on device sr0, logical block 176935buffer i/o error on device sr0, logical block 176935buffer i/o error on https://bugs.launchpad.net/bugs/204133 device sr0, logical block 176935buffer i/o error on device sr0, logical block 176935buffer i/o error on device sr0, logical block 176935buffer i/o error on device sr0, logical block 176935buffer i/o error on device sr0, logical block 176935buffer i/o error on device sr0, logical block 176935if I put in live CD, it goes beyond that, othervise http://www.centos.org/forums/viewtopic.php?t=6970 not.Please suggest. I gues running fsck in rescue mode should do something to solve the thing ? Top TrevorH Forum Moderator Posts: 16715 Joined: 2009/09/24 10:40:56 Location: Brighton, UK Re: buffer i/o error on device sr0 Quote Postby TrevorH » 2011/10/16 00:22:05 /dev/sr0 is your CD/DVD drive. Top BubikolRamios Posts: 67 Joined: 2009/10/04 09:14:05 Re: buffer i/o error on device sr0 Quote Postby BubikolRamios » 2011/10/16 01:03:31 Thanks for replay.Yeah,right, was saving some data via live cd, obviously with some errors too.So, the real thing is:end request; i/o error, dev sdb sector 549222599end request; i/o error, dev sdb sector 549222599end request; i/o error, dev sdb sector 549222599....and then some errors, related to this, I think, on crontaband then:end request; i/o error, dev sdb sector "another sector"....The whole thing might not even come to that, it may stop at:.../dev/volgroup00/logvol00 clean ...boot: recovering journalboot:clean .../dev/volgroup01/logvol00 recovering journal/dev/volgroup01/logvol00 clean ......enabling /etc/fstab/ swaps FAILEDEDIT: that is the case now, on every reboot. Top TrevorH Forum Moderator Posts: 1
Member From: China Registered: 2012-07-08 Posts: 14 [Solved] Why is there a lot of I / O error? I am https://bbs.archlinux.org/viewtopic.php?id=144647 using Archlinux.I install it into a loop file is located in an NTFS.And modify the init script in initcpio can start.But the shutdown always a lot of I / O error.What is the reason?The loop file is jfs. root=/dev/sdb7 loop=/arch/arch.imgMy init script:#!/usr/bin/ash PATH=/usr/bin udevd_running=0 if [ -x /usr/bin/systemd-timestamp ]; then RD_TIMESTAMP=$(systemd-timestamp) fi . /init_functions mount -t proc proc error on /proc -o nosuid,noexec,nodev mount -t sysfs sys /sys -o nosuid,noexec,nodev mount -t devtmpfs dev /dev -o mode=0755,nosuid mount -t tmpfs run /run -o nosuid,nodev,mode=0755 mkdir -m755 /run/initramfs # parse the kernel command line parse_cmdline for d in ${disablehooks//,/ }; do [ -e "/hooks/$d" ] && chmod 644 "/hooks/$d" done . /config run_hookfunctions 'run_earlyhook' 'early hook' $EARLYHOOKS [ error on device -n "${earlymodules//[[:space:]]}" ] && modprobe -qab ${earlymodules//,/ } [ -n "${MODULES//[[:space:]]}" ] && modprobe -qab $MODULES # If rootdelay is empty or not a non-negative integer, set it to 10 if [ -z "${rootdelay}" ] || ! [ "${rootdelay}" -ge 0 ]; then rootdelay=10 fi run_hookfunctions 'run_hook' 'hook' $HOOKS # honor the old behavior of break=y as a synonym for break=premount if [ "${break}" = "y" ] || [ "${break}" = "premount" ]; then echo ":: Pre-mount break requested, type 'exit' to resume operation" launch_interactive_shell fi rootdev=$(resolve_device "$root") && root=$rootdev unset rootdev # Mount root at /new_root mkdir /hostmount.ntfs-3g ${root} /hostfsck.jfs /host${loop}mount -o loop=/dev/loop0 /host${loop} /new_rootmount -o bind /host /new_root/host run_hookfunctions 'run_latehook' 'late hook' $LATEHOOKS run_hookfunctions 'run_cleanuphook' 'cleanup hook' $CLEANUPHOOKS init=${init:-/sbin/init} if [ "${break}" = "postmount" ]; then echo ":: Post-mount break requested, type 'exit' to resume operation" launch_interactive_shell fi exec env -i \ "TERM=$TERM" \ "RD_TIMESTAMP=$RD_TIMESTAMP" \ /usr/bin/switch_root /new_root $init "$@" # vim: set ft=sh ts=4 sw=4 et:fstab:# # /etc/fstab: static file system information # #