Error Reading Block Inode
Hello,This morning, when i powered on my machine, it failed to boot into archlinux.The windows partition still loaded properly.After concluding my morning business, I dug out my arch recovery CD and loaded into the live system. I was error reading block short read able to mount both my root and home partitions, i was able to establish
Error Reading Block Invalid Argument
a chroot environment (although, I hadn't upgraded any packages over the weekend so it just demonstrated that it worked).After some investigation, I error reading block force rewrite determined with fsck that my root partition has a filesystem error. My home partition came out clean.I'm not overly knowledgeable about the filesystem or fsck. I went through the interactive prompts, but selected the options that
Fsck Short Read Ignore Error
effectively changed nothing.I wrote down some of the (hopefully) relevant output:>> fsck /dev/sda4...[ 596.198487] Buffer I/O error on device sda4, logical block 8394655Error reading block 107933, (Attempt to read block from filesystem resulted in short read) while getting next inode from scan. Ignore error? yfore rewrite? nPass 2: checking directory structureEntry 'chcpu' in /sbin (262691) has deleted/unused node 272187. Clear? n...[ 1199.718449] Buffer I/O error on device sda4, logical bloc 8394655Error reading block e2fsck force rewrite 1049331, (Attempt to read block from filesystem resulted in short read) while getting next inode from scan. Ignore error? yforce rewrite? nEntry 'chcpu' in /sbin (262691) has an incorrect filetype (was 1, should be 0).fix? n...Entry 'poweroff' in /sbin (262691) has deleted/unused inode 272188 clear ? nEntry 'poweroff' in /sbin (262691) has incorrect filetype (was 1, should be 0).fix? nEntry 'reboot' in /sbin (262691) has deleted/unused inode 272188. clear ? nEntry 'reboot' in /sbin (262691) has incorrect filetype (was 1, should be 0).fix? nEntry 'eog.mo' in /usr/share/locale/sv/LC_MESSAGES (263153) has deleted/unused inode 272179. clear ? n...Error reading block 1049331, (Attempt to read block from filesystem resulted in short read) while getting next inode from scan. Ignore error? yforce rewrite? n...and it kept going on in this manner. Eventually I said "no" to one of the "Error reading block ..." options and aborted the remainder of the check.First after the "Error reading block ..." lines when it prompts "force rewrite" what is it rewriting? Is this to be embraced or feared?Second, on the deleted/unused inode prompts, What is it clearing (the inode itself, or the sign pointing to the inode)?On the entries about the incorrect filetype, I presume it's actually safe to just trust fsck on this one? Just double-checking so I don't put my system into a
Member Registered: 2009-04-05 Posts: 140 fsck: Force rewrite. What does it mean? Hey all,I'm running fsck on a drive, but I'm having trouble understanding (or finding documentation on) the messages fsck reports.Basically, running fsck -y /dev/sdc1
Fsck Attempt To Read Block From Filesystem Resulted In Short Read
produces messages like this...Error reading block 99456 (Attempt to read block from filesystem
Ubuntu Run Fsck On Reboot
resulted in short read) while getting next inode from scan. Ignore error? yes Force rewrite? yes Error reading block 99457 (Attempt fsck short read zero length partition to read block from filesystem resulted in short read) while getting next inode from scan. Ignore error? yes Force rewrite? yesWhat is a "short read"? What is "Force rewrite" all about? I've tried running https://www.redhat.com/archives/blinux-list/2012-September/msg00005.html fsck -cy, but that causes fsck to hang at 0.00% when scanning for bad blocks...Any insight, or even a link in the right direction, would be greatly appreciated. Thanks! Offline #2 2010-07-19 00:03:57 cybertorture Member Registered: 2010-05-05 Posts: 338 Re: fsck: Force rewrite. What does it mean? http://wiki.linuxquestions.org/wiki/Fsckthat is what i find, i don't realy understand that well but .... i did not like "hardware fail" part hope that https://bbs.archlinux.org/viewtopic.php?id=101281 ll give u a clueanyway good luck and best wishes to solve your problem O' rly ? Ya rly Oo Offline #3 2010-07-21 00:55:12 jalu Member Registered: 2009-04-05 Posts: 140 Re: fsck: Force rewrite. What does it mean? Thanks for the info, cybertorture. The article doesn't explain very much, it's a great start.As it happens, shortly after I wrote the original post my hard drive started clicking (I guess that's what the note abuot "hardware failure" was getting at). Thankfully, I didn't have any data on the drive when it crashed.If anyone has any more info about this, please feel free to post. I'm going to keep an eye on this thread for the future. Thanks! Offline Pages: 1 Index »Kernel & Hardware »fsck: Force rewrite. What does it mean? Board footer Jump to Newbie Corner Installation Kernel & Hardware Applications & Desktop Environments Laptop Issues Networking, Server, and Protection Multimedia and Games System Administration Other Architectures Announcements, Package & Security Advisories Arch Discussion Forum & Wiki discussion Pacman & Package Upgrade Issues [testing] Repo Forum Creating & Modifying Packages AUR Issues, Discussion & PKGBUILD Requests GNU/Linux Discussion Community Contributions Programming & Scripting Other Languages Artwork and Screenshots Atom topic feed Powered by FluxBB
Error reading block (Attempt to read block from filesystem resulted in short read) From: lee Date: Wed, 05 Sep 2012 21:11:11 +0200 Message-id: <[🔎]87d320s2sw.fsf@yun.yagibdah.de> Mail-followup-to: debian-user@lists.debian.org In-reply-to: <[🔎]k27gri$7jt$1@ger.gmane.org> (Kamaraju S. Kusumanchi's message of "Wed, 05 Sep 2012 08:31:23 -0400") References: https://lists.debian.org/debian-user/2012/09/msg00368.html <[🔎]87mx18320v.fsf@yun.yagibdah.de> <[🔎]k27gri$7jt$1@ger.gmane.org> Kamaraju S Kusumanchi writes: > lee wrote: > >> Kamaraju S Kusumanchi writes: >> >>> When I ran >>> >>> $sudo e2fsck -c -c -f -v /dev/sdb7 >>> >>> I am getting a lot of errors such as >>> >>> Error reading block 18022401 (Attempt to read block from filesystem >>> resulted >>> in short read) while reading inode and block bitmaps. Ignore error? >>> yes error reading Force rewrite? yes >>> 3) Is the drive going bad and need to be replaced? >> >> Corresponding entries in /var/log/syslog about the inability to read >> sectors from this device would indicate that there is a hardware >> problem. Provided that all connections and the power supply are ok, I >> would say the device is broken when there are such errors in syslog. >> >> In case there aren't errors error reading block in syslog, I would look somewhere else >> first. > > Yes, there are I/O errors in syslog such as > > Aug 30 08:27:20 kusumanchi kernel: [118453.218041] Buffer I/O error on > device sdb7, logical block 5384272 That seems to indicate that the disk is broken. At first I thought these messages look different from what I've seen, but googling shows quite some agreement that messages like this tell you that the disk is damaged. >> Are you really still using ext2fs? > > The partitions are ext3. Is there a better command to check ext3 partitions > other than ext2fs? See man fsck ... running "fsck -t ext2" probably ends up doing the same thing as calling the fs-type specific checking tool directly, though. -- Debian testing amd64 Reply to: debian-user@lists.debian.org lee (on-list) lee (off-list) References: Re: e2fsck errror: Error reading block (Attempt to read block from filesystem resulted in short read) From: lee Re: e2fsck errror: Error reading block (Attempt to read block from filesystem resulted in short read) From: Kamaraju S Kusumanchi Prev by Date: Concurso de Tiendas de Mascota RAZAS en las Mercedes Next by Date: Re: dev pts mystery [solved] Previous by thread: Re: e2fsck errror: Error reading block (Attempt to read block from filesyste