Ext3-fs Error Device Sda2 Ext3_find_entry
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 Ext3_get_inode_loc Unable To Read Inode Block
Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu ext3 fs error ext3_find_entry reading directory offset 0 RTM Package (Find…) Project (Find…) Status Importance Invalid Undecided Assigned to Nobody Me Remote Watch None, the status of the linux ext3_get_inode_loc unable to read inode block 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) 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 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 again.
help? linuxpenguinOctober 23rd, 2008, 01:39 AMMy server has recently decided to start taking naps suddenly and unexpectedly. On the webpage side I see a nice ugly message about an incorrect key for a SQL table. Yesterday I checked all the tables and there were a few errors, but all got fixed. Then today this happened again. I was positive this whole time that the SQL was not the problem, because it's always working fine for quite a while once I reboot it. I was thinking that the thing was actually completely locking up until just now when it happened to lock up while I was connected https://bugs.launchpad.net/bugs/200747 through SSH to look at logs for any hints. I found NOTHING conclusive - but wouldn't you know, it locked up while I was looking. Rather than reboot I figured I'd see if it came back. After a couple minutes, my session came back responsive as ever. Then I tried to run apt-get update (as root) and got an I/O error. Fortunately though I am at least able to get the https://ubuntuforums.org/archive/index.php/t-956040.html output of dmesg, and here she be. I'm sorry for posting all of this here, but I'm at somewhat of a loss as to what I should do. [ 42.910404] ReiserFS: sdb1: checking transaction log (sdb1) [ 46.299828] ReiserFS: sdb1: replayed 418 transactions in 3 seconds [ 46.300166] ReiserFS: sdb1: Using r5 hash to sort names [ 46.876352] ip_tables: (C) 2000-2006 Netfilter Core Team [ 49.744080] No dock devices found. [ 51.729807] audit(1224713329.055:2): type=1502 operation="capable" name="sys_resource" pid=4757 profile="/usr/sbin/mysqld" namespace="default" [ 52.006241] eth0: no IPv6 routers present [ 7053.962378] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen [ 7053.962470] ata1.01: cmd ca/00:08:af:69:44/00:00:00:00:00/f0 tag 0 dma 4096 out [ 7053.962474] res 40/00:78:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) [ 7053.962531] ata1.01: status: { DRDY } [ 7058.987392] ata1: port is slow to respond, please be patient (Status 0xd0) [ 7063.952745] ata1: device not ready (errno=-16), forcing hardreset [ 7063.952766] ata1: soft resetting link [ 7069.137356] ata1: port is slow to respond, please be patient (Status 0x90) [ 7073.983773] ata1: SRST failed (errno=-16) [ 7073.983833] ata1: soft resetting link [ 7104.149643] ata1.01: qc timeout (cmd 0xec) [ 7104.149669] ata1.01: failed to IDENTIFY (I/O error, err_mask=0x4) [ 7104.149678] ata1.01: revalidation failed (errno=-5) [ 7104.149730] ata1: failed to recover some devices, retrying in 5 secs [ 7109.147
- GoAutoDial Change font size Print view FAQ Register Login EXT3-fs error (device sda2) General and Support topics relating to ViciDialNow and GoAutoDial ISO installers Moderators: enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, s0lid Post a reply 8 posts • Page 1 of 1 http://vicidial.org/VICIDIALforum/viewtopic.php?t=12869 Reply with quote EXT3-fs error (device sda2) by gmcust3 » Tue Aug 10, 2010 1:32 https://major.io/2007/11/20/ext3-fs-error-device-hda3-in-start_transaction-journal-has-aborted/ pm End_request: I/O error, dev sds, sector 420656157EXT3-fs error (device sda2) : ext3_find_entry : reading directory # 52527153 offset What is this Error ? GoAutoDial CEVERSION: 2.4-309aBUILD: 110430-1642 No other software installed on the box. I've read the manager manual. gmcust3 Posts: 1148Joined: Sat Oct 24, 2009 1:15 pm Top Reply with quote by williamconley » Tue Aug 10, 2010 4:06 pm fs error is your hard drive full? where are you seeing this error? did you google it? does this occur after your system comes back from "sleep" or "hibernate"? Vicidial Installation and Repair, plus Hosting and ColocationSugarCRM integration - Customization and Add-ons - We Bring It All Together.http://www.PoundTeam.com # 352-269-0000 # +44 (203) 769-2294 # +506 4001-8914 williamconley Posts: 16186Joined: Wed Oct 31, 2007 4:17 pmLocation: Davenport, FL (By Disney!) Website Top Reply with quote by gmcust3 » Tue ext3 fs error Aug 10, 2010 9:16 pm HDD is just 60% occupied. Server working perfectly but suddenly , Agent sees TIME SYNC ERROR and then Agent cannot open any PAGE. I see this Error on the SERVER when Agents cannot open any Page. After Reboot , it works perfectly for 1 hour or so but then it again gives the Error. Feedback from CentOS forum : https://www.centos.org/modules/newbb/vi ... 8&forum=39 GoAutoDial CEVERSION: 2.4-309aBUILD: 110430-1642 No other software installed on the box. I've read the manager manual. gmcust3 Posts: 1148Joined: Sat Oct 24, 2009 1:15 pm Top Reply with quote by williamconley » Tue Aug 10, 2010 9:42 pm my advice: g4l (ghost for linux) dupe the drive and put the image on another one OR use backup script to backup the system and get the data off the box, then do a full reinstall on another drive and do a restore OR spend a lot of time trying to figure out what the heck is causing this, and if it IS the hard drive ... go back to the two options above. Vicidial Installation and Repair, plus Hosting and ColocationSugarCRM integration - Customization and Add-ons - We Bring It All Together.http://www.PoundTeam.com # 352-269-0000 # +44 (203) 769-2294 # +506 4001-8914 williamconley Posts: 16186Joined: Wed Oct 31, 2007 4:17 pmLocation: Davenport, FL (By Disney!) Website Top Reply with quote by gmcust3 » Tue
November 20, 2007 By Major Hayden 18 Comments If your system abruptly loses power, or if a RAID card is beginning to fail, you might see an ominous message like this within your logs: XHTML EXT3-fs error (device hda3) in start_transaction: Journal has aborted 1 EXT3-fs error (device hda3) in start_transaction: Journal has aborted Basically, the system is telling you that it's detected a filesystem/journal mismatch, and it can't utilize the journal any longer. When this situation pops up, the filesystem gets mounted read-only almost immediately. To fix the situation, you can remount the partition as ext2 (if it isn't your active root partition), or you can commence the repair operations. If you're working with an active root partition, you will need to boot into some rescue media and perform these operations there. If this error occurs with an additional partition besides the root partition, simply unmount the broken filesystem and proceed with these operations. Remove the journal from the filesystem (effectively turning it into ext2): XHTML # tune2fs -O ^has_journal /dev/hda3 1 # tune2fs -O ^has_journal /dev/hda3 Now, you will need to fsck it to correct any possible problems (throw in a -y flag to say yes to all repairs, -C for a progress bar): XHTML # e2fsck /dev/hda3 1 # e2fsck /dev/hda3 Once that's finished, make a new journal which effectively makes the partition an ext3 filesystem again: XHTML # tune2fs -j /dev/hda3 1 # tune2fs -j /dev/hda3 You should be able to mount the partition as an ext3 partition at this time: XHTML # mount -t ext3 /dev/hda3 /mnt/fixed 1 # mount -t ext3 /dev/hda3 /mnt/fixed Be sure to check your dmesg output for any additional errors after you're finished! Share this post:TwitterGoogleLinkedInRedditEmailPrintTagged With: command line, emergency, filesystem Send to Email Address Your Name Your Email Address Cancel Post was not sent - check your email addresses! Email check failed, please try again Sorry, y