Ext3-fs Error Device Sda3 Ext3_get_inode_loc
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 ext3-fs error fortigate Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu ext3-fs error unable to read inode block RTM Package (Find…) Project (Find…) Status Importance Invalid Undecided Assigned to Nobody Me Remote Watch None, the status of the
Ext3 Fs Error Journal Has Aborted
bug is updated manually. None, the status of the bug is updated manually. URL: The information about this bug in Launchpad is automatically pulled daily from the remote bug. Comment on this change (optional)
Ext3-fs Error (device Dm-0)
Email me about changes to this bug report linux (Ubuntu) Edit Invalid Undecided Unassigned Edit You need 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 ext3-fs error (device sda6) in start_transaction journal has aborted 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 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
error after running fsck Issues related to hardware problems Post Reply Print view Search Advanced search 10 posts • Page 1 of
Ext3-fs Error (device Dm-0) Ext3_journal_start_sb Detected Aborted Journal
1 maksaraswat Posts: 44 Joined: 2011/10/14 19:00:52 Location: New York Contact: linux ext3_get_inode_loc unable to read inode block Contact maksaraswat Website [SOLVED] EXT3-fs error after running fsck Quote Postby maksaraswat » 2012/01/31 20:43:31 Hi,For some ext3-fs error ext3_find_entry reading directory reason my RAID 6 mount was unmountable and I was getting the error message when I tried to mount it manually [root@server ~]# mount /dev/sdb1 /local1/mount: wrong fs https://bugs.launchpad.net/bugs/200747 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 code = 0x08000002sdb: Current: sense key: Hardware Error Add. http://www.centos.org/forums/viewtopic.php?t=24611 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: IO failureOne of the HDD looks bad and I am getting SMART messages which I will replace tomorrow. But
block Next message: PE2600 slow clock Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] On Mon, 8 Sep 2003 Zachary_Reneau at dell.com wrote: > Hope someone has seen this problem beside me and http://lists.us.dell.com/pipermail/linux-poweredge/2003-September/009879.html knows a fix: > > EXT3-fs error (device sd (8,2)): ext3_get_inode_Loc: unable to read inode https://www.redhat.com/archives/ext3-users/2009-March/msg00002.html > block Try shutting off write caching on the Perc3/Di. It may be the problem that has been effecting anything running the aacraid and doing heavier I/O. There is a transcript of a session I posted to the list within the past month or month and a half if you can find it. Regards James BOurne > > Error occurs fs error about every four days or so and the system must be rebooted. > Normal operation continues after reboot for a few more days. > > HDDs have been swapped out and OS reinstalled in some cases and the problem > continues. > > Four PE2650's with same symptoms. > Red Hat Enterprise Server 2.1 2.4.9-e.27smp bld 3170 > PERC3/Di FW 2.7-1 > > System partitions are laid out the same on each system. > > ext3-fs error (device # sfdisk -l #==== partition layout > > Disk /dev/sda: 4425 cylinders, 255 heads, 63 sectors/track > Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 > > Device Boot Start End #cyls #blocks Id System > /dev/sda1 * 0+ 12 13- 104391 83 Linux > /dev/sda2 13 4293 4281 34387132+ 83 Linux > /dev/sda3 4294 4424 131 1052257+ 82 Linux swap > /dev/sda4 0 - 0 0 0 Empty > > Disk /dev/sdb: 4425 cylinders, 255 heads, 63 sectors/track > Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 > > Device Boot Start End #cyls #blocks Id System > /dev/sdb1 * 0+ 12 13- 104391 83 Linux > /dev/sdb2 13 4293 4281 34387132+ 83 Linux > /dev/sdb3 4294 4424 131 1052257+ 82 Linux swap > /dev/sdb4 0 - 0 0 0 Empty > > > Thanks, > > Zachary Reneau, MCSE, CCA, A+, Linux+, DCEE|f > 1-800-624-9896 x46152 > Dell Enterprise Expert Center NOS Group > Normal Working Hours M-F 2p-11p CDT > Note: This email is not subject to a legally binding commitment > > -- James Bourne, Supervisor Data Centre Operations Mount Royal College, Calgary, AB, CA www.mtroyal.ca "There are only 10 types of people in this world: those who understand binary and those who don't." ***************************************************************************** This communication is intende
or hardware raid failure? Date: Wed, 4 Mar 2009 11:53:11 +0100 I had a busy mailserver fail on me the other day. Below is what was printed in dmesg. We first suspected a hardware failure (raid controller or something else), so we moved the drives to another (identical hardware) machine and ran fsck. Fsck complained ("short read while reading inode") and asked if I wanted to ignore and rewrite (which I did). After booting up again, the problem came back immediately and root was remounted read only. We moved the data from the read only drive to a new machine. While copying the data, we got this message from time to time (on various files): "EXT3-fs error (device dm-0): ext3_get_inode_loc: unable to read inode block - inode=22561891, block=90243144. I need to find the cause(s) of the problems. So far I have these questions/concerns: - Kernel bug? (This is Ubuntu 8.10 with 2.6.27-7-server) - Filesystem bug/failure? - Did the RAID controller fail to detect a failing drive? This is an Adaptec aoc-usas-s4ir running on a Supermicro motherboard. I suspect that one of the drives (RAID 6 btw) has failed, but I'm not sure what to do from here. Any ideas? Thanks in advance. dmesg: [ 38.907730] end_request: I/O error, dev sda, sector 284688831 [ 38.907802] EXT3-fs error (device dm-0): read_block_bitmap: Cannot = read block bitmap - block_group =3D 1086, block_bitmap =3D 35586048 [ 38.907956] Aborting journal on device dm-0. [ 38.919742] ext3_abort called. [ 38.919798] EXT3-fs error (device dm-0): ext3_journal_start_sb: = Detected aborted journal [ 38.919942] Remounting filesystem read-only [ 38.925855] __journal_remove_journal_head: freeing b_committed_data [ 38.925915] journal commit I/O error [ 38.925935] journal commit I/O error [ 38.925953] journal commit I/O error [ 38.943245] Remounting filesystem read-only [ 38.958907] EXT3-fs error (device dm-0) in ext3_reserve_inode_write: = Journal has aborted [ 38.958988] EXT3-fs error (device dm-0) in ext3_truncate: Journal has = aborted [ 38.959051] EXT3-fs error (device dm-0) in ext3_reserve_inode_write: = Journal has aborted [ 38.959137] EXT3-fs error (device dm-0) in ext3_orphan_del: Journal = has aborted [ 38.959222] EXT3-fs error (device dm-0) in ext3_reserve_inode_write