Journal Has Aborted Ext3-fs Error
Contents |
error after running fsck Issues related to hardware problems Post Reply Print view Search Advanced search 10 posts • Page 1 of 1 maksaraswat Posts: 44 Joined: 2011/10/14 19:00:52 Location: New York Contact:
Ext3-fs Error Unable To Read Inode Block
Contact maksaraswat Website [SOLVED] EXT3-fs error after running fsck Quote Postby maksaraswat » ext3-fs error fortigate 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 ext3-fs error (device sda6) in start_transaction journal has aborted to mount it manually [root@server ~]# 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
Ext3-fs Error (device Dm-0)
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. 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
Ext3-fs Error (device Dm-0) Ext3_journal_start_sb Detected Aborted Journal
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 is it possible to make the mount READ-WRITE? It keeps some of our automated backups and I don't want backups to miss anymore.Please help!Thanks in advance!Mayank Top pschaff Retired Moderator Posts: 18276 Joined: 2006/12/13 20:15:34 Location: Tidewater, Virginia, North America Contact: Contact pschaff Website [SOLVED] EXT3-fs error after running fsck Quote Postby pschaff » 2012/01/31 21:13:43 You need to get the hardware problems fixed before attempting to
Red Hat Certificate System Red Hat Satellite Subscription Asset Manager Red Hat Update Infrastructure Red Hat Insights Ansible Tower by Red Hat Cloud Computing ext3-fs error in ext3_reserve_inode_write journal has aborted Back Red Hat CloudForms Red Hat OpenStack Platform Red Hat Cloud Infrastructure
Ext3 Fs Error Ext3_journal_start_sb Detected Aborted Journal
Red Hat Cloud Suite Red Hat OpenShift Container Platform Red Hat OpenShift Online Red Hat OpenShift Dedicated Storage detected aborted journal ext4 Back Red Hat Gluster Storage Red Hat Ceph Storage JBoss Development and Management Back Red Hat JBoss Enterprise Application Platform Red Hat JBoss Data Grid Red Hat JBoss Web http://www.centos.org/forums/viewtopic.php?t=24611 Server Red Hat JBoss Portal Red Hat JBoss Operations Network Red Hat JBoss Developer Studio JBoss Integration and Automation Back Red Hat JBoss Data Virtualization Red Hat JBoss Fuse Red Hat JBoss A-MQ Red Hat JBoss BPM Suite Red Hat JBoss BRMS Mobile Back Red Hat Mobile Application Platform Services Back Consulting Technical Account Management Training & Certifications Red https://access.redhat.com/solutions/24301 Hat Enterprise Linux Developer Program Support Get Support Production Support Development Support Product Life Cycle & Update Policies Knowledge Search Documentation Knowledgebase Videos Discussions Ecosystem Browse Certified Solutions Overview Partner Resources Tools Back Red Hat Insights Learn More Red Hat Access Labs Explore Labs Configuration Deployment Troubleshooting Security Additional Tools Red Hat Access plug-ins Red Hat Satellite Certificate Tool Security Back Product Security Center Security Updates Security Advisories Red Hat CVE Database Security Labs Resources Overview Security Blog Security Measurement Severity Ratings Backporting Policies Product Signing (GPG) Keys Community Back Discussions Red Hat Enterprise Linux Red Hat Virtualization Red Hat Satellite Customer Portal Private Groups All Discussions Start a Discussion Blogs Customer Portal Red Hat Product Security Red Hat Access Labs Red Hat Insights All Blogs Events Customer Events Red Hat Summit Stories Red Hat Subscription Benefits You Asked. We Acted. Open Source Communities Subscriptions Downloads Support Cases Account Back Log In Register Red Hat Account Number: Account Details Newsletter and Contact Preferences User Management Account Maintenance My Profile Notifications Help Log Out Language Back
Assigned to Milestone kernel-package (Ubuntu) Edit Invalid Medium Ben Collins Edit You need to log in to change this bug's status. https://bugs.launchpad.net/bugs/27056 Affecting: kernel-package (Ubuntu) Filed here by: Paul McGarry When: 2005-12-14 Assigned: 2006-01-13 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD http://linux.empulsegroup.com/removing%20and%20re-enabling%20journal%20for%20ext3.html Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Invalid Medium Assigned to Me Ben Collins (ben-collins) Comment on this fs error change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description I have a development server running Ubuntu 5.04 HWDB ID: f7759e4f272e325092d2736243ee163c uname -a: Linux dev 2.6.10-5-686-smp #1 SMP Mon Oct 10 11:40:56 UTC 2005 i686 GNU/Linux Overnight there appears to have been journal has aborted a filesystem problem of some sort and the console was spewing: EXT3-fs error (device sda1) in start_transaction: Journal has aborted If I hit ctrl-alt-del then it also says: scsi0 (0:0): rejecting I/O to offline device * cannot execute /sbin/shutdown scsi0 (0:0): rejecting I/O to offline device scsi0 (0:0): rejecting I/O to offline device so a hard reboot was necessary. If there is any more info I can provide, or something I should do to obtain more info if it happens again, please let me know. I don't think there's anything logged about the occurance because with the disk gone there was nowhere to log it.... Add tags Tag help Ben Collins (ben-collins) wrote on 2005-12-14: #1 This is a hardware issue in either the scsi host controller or the driver itself. Check the cables, reseat the host controller in the PCI slot, etc. The ext3 error you were seeing is a consequence of the scsi controller making the drive off-l
you have to remove and then re-enable a corrupt or aborted ext3 filesystem. Try this for single user, read-only mode. 1. tune2fs -O ^has_journal /dev/*** <------ strips the journal 2. fsck the partition 3. tune2fs -j /dev/*** <----- adds back the journal Once this is done, remount the filesystem as read-write (mount -o remount,rw /) and create a test file (touch test.txt) to see if the filesystem is indeed writeable. If this doesn't work then a trickier option is also available to you. 1. debugfs -w -R "feature ^has_journal, ^needs_recovery" /dev/*** 2. fsck the partition e2fsck -y /dev/*** 3. tune2fs -j /dev/*** If that doesn't work the drive is probably hosed. -------- tune2fs: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda5 Can't find valid filesystem superblock. hardware error! -------- Indications e100: eth1: e100_watchdog: link up, 100Mbps, full-duplex journal_bmap_R3246d747: journal block not found at offset 1036 on ide0(3,2) Aborting journal on device ide0(3,2). ext3_abort called. EXT3-fs abort (device ide0(3,2)): ext3_journal_start: Detected aborted journal Remounting filesystem read-only Error (-5) on journal on device 03:02 journal commit I/O error EXT3-fs error (device ide0(3,2)) in start_transaction: Journal has aborted EXT3-fs error (device ide0(3,2)) in start_transaction: Journal has aborted EXT3-fs error (device ide0(3,2)) in start_transaction: Journal has aborted EXT3-fs error (device ide0(3,2)) in ext3_delete_inode: Journal has aborted EXT3-fs error (device ide0(3,2)) in start_transaction: Journal has aborted EXT3-fs error (device ide0(3,2)) in start_transaction: Journal has aborted EXT3-fs error (device ide0(3,2)) in start_transaction: Journal has aborted ip_tables: (C) 2000-2002 Netfilter core team EXT3-fs error (device ide0(3,2)) in st