Ext3-fs Error Device Sdb1 In Start_transaction Journal Has Aborted
Contents |
November 20, 2007 By Major Hayden 18 Comments If your system abruptly loses power, or if a RAID card is beginning to fail, you ext3-fs error in start_transaction journal has aborted might see an ominous message like this within your logs: XHTML
Ext3-fs Error Unable To Read Inode Block
EXT3-fs error (device hda3) in start_transaction: Journal has aborted 1 EXT3-fs error (device hda3) in start_transaction: Journal has ext3-fs error fortigate 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 ext3-fs error (device sda6) in start_transaction journal has aborted 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
Ext3-fs Error (device Dm-0)
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 tr
Us Facebook Twitter Google + LinkedIn Newsletter Instagram YouTube DirectoryNetwork InfrastructureWAN, Routing and Switching LAN, Switching and Routing ext3-fs error (device dm-0) ext3_journal_start_sb detected aborted journal Network Management Remote Access Optical Networking Getting Started with ext3 fs error device dm 0 in start_transaction journal has aborted LANs IPv6 Integration and Transition EEM Scripting Other Subjects SecurityVPN Security Management Firewalling
Ext3 Fs Error Ext3_journal_start_sb Detected Aborted Journal
Intrusion Prevention Systems/IDS AAA, Identity and NAC Physical Security MARS Email Security Web Security Other Subjects Service ProvidersMetro MPLS Voice Over IP https://major.io/2007/11/20/ext3-fs-error-device-hda3-in-start_transaction-journal-has-aborted/ XR OS and Platforms Video Other Subjects Collaboration, Voice and VideoIP Telephony Video Over IP Jabber Clients Unified Communications Applications TelePresence Digital Media System Contact Center Conferencing UC Migrations Other Subjects Wireless - MobilitySecurity and Network Management Wireless IP Voice and Video Getting Started https://supportforums.cisco.com/discussion/10940791/ext3-fs-error-device-sda6-error with Wireless WLCCA Other Subjects ServicesCisco ServiceGrid Connected Analytics Smart Call Home Smart Net Total Care Operations Exchange Mobile ApplicationsCisco Proximity Cisco Technical Support Online Tools and ResourcesCisco Bug Discussions Technical Documentation Ideas Cisco CLI Analyzer Support Community Help Data CenterApplication Centric Infrastructure Application Networking Intelligent Automation Server Networking Storage Networking Unified Computing Wide Area Application Services (WAAS) Other Subjects Small BusinessNetwork Storage Routers Security Surveillance Switches Voice and Conferencing Wireless Solutions and ArchitecturesBorderless Networks Collaboration Cisco User GroupsSeattle Cisco User Group (SEACUG) Silicon Valley Cisco User Group (SVCUG) Southern California Cisco User Group (SCCUG) Cisco Certifications Cisco.com Idea Center Cisco Cafe Expert CornerTop Contributors Leaderboards Cisco Live! Events Events Community CornerAwards & Recognition Behind the Scenes Feedback Forum Cisco Certifications Cisco Press Café Cisco On Demand Support & Downloads
and End-of-Life ProductsCisco 7800 Series Media Convergence ServersTroubleshoot and AlertsField Notices Field Notice: FN - http://www.cisco.com/c/en/us/support/docs/field-notices/632/fn63270.html 63270 - MCS-7835-I2, MCS-7845-I2, RAID Driver can cause Service Outage, SW upgrade required Print Available Languages Updated:Nov 04, 2009 Document ID:FN63270 Field Notice: FN - 63270 - MCS-7835-I2, MCS-7845-I2, RAID Driver can cause Service Outage, SW upgrade required November 4, 2009 NOTICE: THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS fs error AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME. Revision History Revision in start_transaction journal Date Comment 1.0 04-NOV-2009 Initial Public Release Products Affected Products Affected Comments MCS-7835-I2-xxx 7835-I2 Bare Metal, Appliance Servers, and IBM x3650 Customer-provided servers. MCS-7845-I2-xxx 7845-I2 Bare Metal, Appliance Servers, and IBM x3650 Customer-provided servers. Problem Description To be exposed to this issue, a server in the Products Affected section above must be running one of the affected application versions listed in the table found in the Workaround/Solution section. Certain IBM RAID driver versions can cause instability in the RAID environment and lead to hard drives being marked as Read-Only. The affected RAID drivers are contained in certain Application versions listed in the table in the Workaround/Solution section. Since Write access to the RAID array is required with Unified Communications Applications, this problem can prevent critical files from being written to the array and eventually can cause a service outage. For a list of affected and fixed Application versions, please see the table in the Workaround/So