Error No Journal Found. Mounting Ext3 Over Ext2
Contents |
Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME Get UbuntuKylin Ubuntu Code of Conduct Ubuntu Wiki Community Wiki Other Support Launchpad Answers Ubuntu IRC Support AskUbuntu Official Documentation User ext3 fs error loading journal Documentation Social Media Facebook Twitter Useful Links Distrowatch Bugs: Ubuntu PPAs: Ubuntu Web Upd8: jbd failed to read block at offset Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu
Ext3-fs Error Loading Journal Centos
Specialised Support Ubuntu Servers, Cloud and Juju Server Platforms [SOLVED] unable to mount new storage Having an Issue With Posting ? Do you want to help us debug the posting issues ? < is the
E2fsck Bad Magic Number In Superblock
place to report it, thanks ! Results 1 to 9 of 9 Thread: unable to mount new storage Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode August 24th, 2011 #1 yud_ View Profile View Forum Posts Private Message First Cup of Ubuntu Join Date Aug 2011 Location Sydney, Australia Beans 5 DistroUbuntu 11.04 Natty Narwhal unable to mount new storage attempt to read block from filesystem resulted in short read I'm a newby, please be gentle on me... my 11.04 installation is running beautifully in VM on ESXi. I'm trying to add storage so I added the disks, assigned them in vmware to the vm, then tried to mount them when I received the error: Code: mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so dmesg | tail gives: Code: EXT3-fs (sdb1): error: no journal found. mounting ext3 over ext2? I tried creating the new partition on the new disks in both webmin and CLI using fdisk but got exactly same errors above when trying to mount. The partition is formatted as ext3. my setup: HP Microserver, booting vmware from USB drive. Hardware RAID card (Adaptec RAID 2405), 2 x 250GB HDD in RAID1 (datastore1) with VM's, 2 x 2TB HDD in RAID1 (datastore2) - the storage I'm trying to add. A search of the above errors yielded many results, all of them were different scenarios to mine. Any help will be highly appreciated. Y. Last edited by yud_; August 24th, 2011 at 02:28 PM. Adv Reply August 24th, 2011 #2 Wayne_V View Profile View Forum Posts Pri
in Sign up Sign up Linode ForumLinode Community Forums FAQ Search Members Register Login [ Anonymous ] /home will not mount -
Couldn't Find Valid Filesystem Superblock
please help Post new topic Reply to topic Linode Forum » Linux Community tune2fs Forums » General Discussion Previous topic | Next topic Author Message mysoi Post subject: /home will not mke2fs mount - please helpPostPosted: Mon Dec 06, 2010 10:22 pm Offline Newbie Joined: Mon Dec 06, 2010 10:21 pm Posts: 2 Here is what I am getting in the console: mountall: https://ubuntuforums.org/showthread.php?t=1832087 mount /home [1872] terminated with status 32 mountall: Filesystem could not be mounted: /home EXT3-fs (xvdc): error: no journal found. mounting ext3 over ext2? mount: wrong fs type, bad option, bad superblock on /dev/xvdc, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so mountall: mount /home https://forum.linode.com/viewtopic.php?t=6362%3E [1877] terminated with status 32 mountall: Filesystem could not be mounted: /home EXT3-fs (xvdc): error: no journal found. mounting ext3 over ext2? mount: wrong fs type, bad option, bad superblock on /dev/xvdc, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so Please let me know if you can help or any additional information is needed. Top Profile Reply with quote tinono Post subject: PostPosted: Mon Dec 06, 2010 10:47 pm Offline Junior Member Joined: Sat Jul 11, 2009 7:19 am Posts: 30 Location: Martinique Go to your Linode dashboard. Is the disk image you attached as xvdc really an ext3 filesystem? Top Profile Reply with quote hoopycat Post subject: PostPosted: Mon Dec 06, 2010 11:34 pm Offline Senior Member Joined: Sat Aug 30, 2008 1:55 pm Posts: 1739 Location: Rochester, New York Try posting the result of these two commands: Code:cat /etc/fstabtune2fs -l /dev/xvdcThis will (hopefully) give you output something like this:Code:root@summerwheat:~# cat /etc/fstab# /etc/fstab: static file system information.##
Red Hat Certificate System Red Hat Satellite Subscription Asset Manager Red Hat Update Infrastructure Red Hat Insights Ansible Tower by Red Hat Cloud Computing Back Red Hat CloudForms Red Hat OpenStack https://access.redhat.com/solutions/161103 Platform Red Hat Cloud Infrastructure Red Hat Cloud Suite Red Hat OpenShift Container http://unix.stackexchange.com/questions/71758/ext3-root-filesystems-goes-read-only-with-aborted-journal-even-after-repairs Platform Red Hat OpenShift Online Red Hat OpenShift Dedicated Storage 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 Server Red Hat JBoss Portal Red Hat JBoss Operations Network Red Hat JBoss Developer fs error 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 Hat Enterprise Linux Developer Program Support Get Support Production Support Development Support Product Life Cycle & Update Policies Knowledge Search Documentation fs error loading 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 English español Deutsch italiano 한국어 français 日本語 português 中文 (中国) русский Customer Portal Search Products & Services Back View All Products Infrastructure and Management Back Red Hat Enterprise Linux Red Hat Virtualization Red Hat Identity Management Red Hat Directory Server Red Hat Certificat
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top ext3 root filesystems goes read-only with aborted journal even after repairs up vote 4 down vote favorite 1 Short version: ext3 root filesystem on rackspace (xen) VM detects aborted journal on boot and mounts read-only. I've attempted to repair this from a rescue environment with tune2fs and e2fsck as prescribed in many articles I read, but the error continues to happen. UPDATE: So based on this article I added "barrier=0" to the /etc/fstab entry for this filesystem and it mounted r/w fine at the next boot. I'm lead to believe this is a paravirtualization thing, but would love it if anyone fully understands what is going on here and can explain. Long version: Rackspace VM just upgraded from Ubuntu 11.10 to 12.04.2 dmesg output with the error: [ 14.701446] blkfront: barrier: empty write xvda op failed [ 14.701452] blkfront: xvda: barrier or flush: disabled [ 14.701460] end_request: I/O error, dev xvda, sector 28175816 [ 14.701473] end_request: I/O error, dev xvda, sector 28175816 [ 14.701487] Aborting journal on device xvda1. [ 14.704186] EXT3-fs (xvda1): error: ext3_journal_start_sb: Detected aborted journal [ 14.704199] EXT3-fs (xvda1): error: remounting filesystem read-only [ 14.940734] init: dmesg main process (763) terminated with status 7 [ 18.425994] init: mongodb main process (769) terminated with status 1 [ 21.940032] eth1: no IPv6 routers pre