Error Writing Block While Doing Inode Scan
here for a quick overview of the site Help Center Detailed answers to any questions you might e2fsck force rewrite have Meta Discuss the workings and policies of this site About either the superblock or the partition table is likely to be corrupt! Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges 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 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 After crash, e2fsck fails with weirdly high block numbers/sizes up vote 2 down vote favorite After a breaker trip a Raspberry Pi of mine started to halt boot with kernel panic (same message as here). This is a Raspberry Pi running Raspbian, so it runs from a SD card, from a main ext4 partition, which I've tried repairing on my PC with: sudo e2fsck -f -y -v /dev/sdx2 However, this eventually fails with some weird output: Error writing block 137439060017 (Invalid argument) while getting next inode from scan. Ignore error? yes Error reading block 183472412950529 (Invalid argument). Ignore error? yes Force rewrite? yes Error writing block 183472412950529 (Invalid argument) while getting next inode from scan. Ignore error? yes Inode 13329, i_size is 4096, should be 549755817984. Fix? yes Inode 13607, i_size is 69632, should be 137439023104. Fix? yes Error reading block 36983963385857 (Invalid argument). Ignore error? yes Force rewrite? yes Error writing block 36983963385857 (Invalid argument) while getting next inode from scan. Ignore error? yes Error reading block 179632729097217 (Invalid argument). Ignore error? yes Force rewrite? yes Error writing block 179632729097217 (Invalid argument) while getting next inode fro
Today's Posts Advanced Search Find the answer to your Linux question: Entire Site Articles Downloads Forums Linux Hosting Forum Your Distro Red Hat / Fedora Linux LVM Resize went wrong ! If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. ** If you are logged in, most ads will not be displayed. ** Linuxforums now supports the Tapatalk app for your mobile device. Results 1 to 2 http://unix.stackexchange.com/questions/100767/after-crash-e2fsck-fails-with-weirdly-high-block-numbers-sizes of 2 Thread: LVM Resize went wrong ! Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode Enjoy an ad free experience by logging in. Not a member yet? Register. 10-03-2011 #1 Saed View Profile View Forum Posts Private Message View Articles Just Joined! Join Date May 2011 Posts 13 LVM Resize went wrong ! Hello Friends , Sorry http://www.linuxforums.org/forum/red-hat-fedora-linux/183227-lvm-resize-went-wrong.html if this might sounds too old , but i `ve been looking round & round desperately trying to find a fix for the mess i`ve made and i got too confused ! Well let me cut it short :- i was trying to resize "reduce" my /backup lvm-partition on /dev/mapper/vol_raid-volbackup to freeup some space for /var on /dev/mapper/vol_raid-volvar but it all went wrong ! # although i`m aware of the procedure sequence :- 1- boot into single-user mode 2- umount /dev/mapper/vol_raid-volbackup 3- e2fsck -fc /dev/mapper/vol_raid-volbackup 4- resize2fs -f -p /dev/mapper/vol_raid-volbackup 1000G 5- lvresize -L 1T /dev/mapper/vol_raid-volbackup 6- e2fsck -fc /dev/mapper/vol_raid-volbackup i went for step 5 (lvresize) before step 4 (resize2fs) now this is what i get when i try any of the following :- Code: resize2fs -f -p /dev/mapper/vol_raid-volbackup 1000G resize2fs 1.39 (29-May-2006) Resizing the filesystem on /dev/mapper/vol_raid-volbackup to 262144000 (4k) blocks. resize2fs: Can't read an block bitmap while trying to resize /dev/mapper/vol_raid-volbackup Code: e2fsck -f -p /dev/mapper/vol_raid-volbackup /dev/mapper/vol_raid-volbackup: The filesystem size (according to the superblock) is 473956352 blocks The physical size of the device is 268435456 blocks Either the superblock or the partition table is likely to be corrupt! /dev/mapper/vol_raid-volbackup: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) Code: fsck /dev/mapper/vol_raid-volbackup fsck 1.39 (29-May-2006) e2fsck 1.39 (29-May-2006) The filesystem size (according to the sup
Common F23 Bugs Common F24 Bugs Communicate with Fedora The Documents Bug Reports Fedora Update System (Bodhi) Fedora Build System (Koji) Official Spins FedoraForum.org > Fedora 23/24 > Using Fedora (Invalid argument) while doing inode scan - error msg FedoraForum Search http://www.fedoraforum.org/forum/showthread.php?t=203394 User Name Remember Me? Password Forgot Password? Join Us! Register All Albums FAQ Today's Posts http://lists.uclibc.org/pipermail/uclibc/2003-March/026850.html Search Using Fedora General support for current versions. Ask questions about Fedora that do not belong in any other forum. Google™ Search FedoraForum Search Red Hat Bugzilla Search Search Forums Show Threads Show Posts Tag Search Advanced Search Go to Page... Thread Tools Search this Thread Display Modes #1 6th November 2008, 01:37 PM ub007 Offline Registered error writing User Join Date: Oct 2008 Posts: 67 (Invalid argument) while doing inode scan - error msg I'm running fedora 9 and added a hard drive.I've been playing around with this second disk -sdb,creating LVMs and may have ended up messing up the partition table.... When i rebooted ,i got the error msg : Quote: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY Quote: I tried #fsck /dev/sdb2 and get the following Either the superblock or the partition table is likely to error writing block be corrupt! Abort
scan Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] uclibc-0.9.19 e2fsprogs-1.32 linux-2.2.19 I have no problems running with e2fsck compiled against libc5; when trying uclibc I get e2fsck -fy /dev/hda3 (and hda4, it's ok on hda2) .. .. Error writing block 2097170 (Bad address) while doing inode scan. Ignore error