Kernel Ext3-fs Error Ext3_get_inode_loc Unable To Read Inode Block
Contents |
Edit You need to log in to change this bug's status. Affecting: Debian Filed here by: Jos van Hees When: 2008-03-11 Completed: 2008-10-11 Target Distribution Baltix BOSS Juju Charms Collection Debian Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu
Ext3-fs Error Unable To Read Inode Block
Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Invalid Undecided Assigned to linux ext3_get_inode_loc unable to read inode block Nobody Me Remote Watch None, the status of the bug is updated manually. None, the status of the bug is updated manually. URL: unable to read inode block ext4 The information about this bug in Launchpad is automatically pulled daily from the remote bug. Comment on this change (optional) Email me about changes to this bug report linux (Ubuntu) Edit Invalid Undecided Unassigned Edit You need
Unable To Read Inode Block Fortigate
to log in to change this bug's status. Affecting: linux (Ubuntu) Filed here by: Fred When: 2008-03-10 Completed: 2008-10-29 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Invalid Undecided Assigned to Nobody Me Comment on this change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for
Unable To Read Inode Block Linux
series Bug Description I am running Ubuntu 8.04 "Hardy Heron" (alpha). MSI P35 Neo Samsung SpinPoint T166 500 gb (7200 rpm, SATA-2, 16 mb cache) Samsung SpinPoint T166 250 gb (7200 rpm, SATA-2, 16 mb cache) sda1 = Windows XP sdb1 = Linux So I am listening to MP3 music in Rhythmbox 0.11.4, and surfing with Mozilla Firefox 3.0b3 and perhaps doing some other stuff, like maybe running apt-update && upgrade && clean && autoclean && autoremove or something in a Terminal or something. And then my computer becomes unresponsive. The HDD LED shine all the time on the computer case. Then I do Ctrl+Alt+F2 and try to login, and I type my username and press enter, and it waits there for a while, then it start spit some error messages, and wont let me in. Like: EXT3-fs error (device sdb1): ext3_get_inode_loc: unable to read node block - inode=1599522, block=3211298 And it can spam the console with that kind of stuff. Then I shut down the computer (by PSU switch), restart and it borked out again. Shut down computer by PSU switch again, and runned HUTIL v2.10 by Samsung, a disk diagnostic tool that checks SMART, does disk spin up, spin down, read surface scan, and couple other diagnostic stuff. It reported no errors, and said the disk were okay. Then I rebooted into my old Ubuntu 7.04 "Gutsy Gibbon
error after running fsck Issues related to hardware problems Post Reply Print view Search Advanced search 10 posts • ext3-fs error fortigate Page 1 of 1 maksaraswat Posts: 44 Joined: 2011/10/14 19:00:52
Ext3-fs Error Ext3_find_entry Reading Directory
Location: New York Contact: Contact maksaraswat Website [SOLVED] EXT3-fs error after running fsck Quote Postby maksaraswat unable to read inode block ext3 » 2012/01/31 20:43:31 Hi,For some reason my RAID 6 mount was unmountable and I was getting the error message when I tried to mount it manually [root@server https://bugs.launchpad.net/bugs/200747 ~]# mount /dev/sdb1 /local1/mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so [root@server ~]# dmesg | tail Add. Sense: Internal target failureend_request: I/O error, dev sdb, sector 806617154sd 1:0:0:0: SCSI error: return http://www.centos.org/forums/viewtopic.php?t=24611 code = 0x08000002sdb: Current: sense key: Hardware Error Add. Sense: Internal target failureend_request: I/O error, dev sdb, sector 3025928274JBD: recovery failedEXT3-fs: error loading journal.After analyzing the situation and some Googling I found out that I should do a file system check with fsck and that what I did nextroot@server ~]# fsck -f -y /dev/sdb1...after almost 5hrs it completed with following message: /dev/sdb1: ***** FILE SYSTEM WAS MODIFIED *****/dev/sdb1: 1064317/548929536 files (5.7% non-contiguous), 836681827/1097856503 blocksAfter this completion I was able to mount and I can see part (about 80-85%) of my data however the mount is READ-ONLY!!!! And I am getting following message [root@server ~]# dmesg | tailAdd. Sense: Internal target failureend_request: I/O error, dev sdb, sector 781189162EXT3-fs error (device sdb1): read_inode_bitmap: Cannot read inode bitmap - block_group = 2980, inode_bitmap = 97648641Aborting journal on device sdb1.ext3_abort called.EXT3-fs error (device sdb1): ext3_journal_start_sb: Detected aborted journalRemounting filesystem read-onlyEXT3-fs error (device sdb1) in ext3_new_inode: IO failureEXT3-fs error (device sdb1) in ext3_mkdir: