Ext3-fs Dm-0 Error Unable To Read Superblock
Contents |
installed some updates to my 8.10 install. When it rebooted I got all sorts of disc errors; I booted with a live cd and after a bit of searching ran ext3 fs error journal has aborted fsck -yfv until it stopped reporting problems. I then re-booted and used the
Ext3-fs Error Unable To Read Inode Block
update manager to upgrade to 9.04. It reported that various things had failed and then rebooted to the same ext3-fs error (device sda6) in start_transaction journal has aborted sort of errors. I've booted from a live disc again and run fsck quite a lot of times (20 maybe, haven't been counting) and am still getting errors. I've just run fsck -p ext3-fs error (device dm-0) and got: ubuntu@ubuntu:~$ sudo fsck -p /dev/sda fsck 1.41.4 (27-Jan-2009) fsck.ext2: Bad magic number in super-block while trying to open /dev/sda /dev/sda: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try
Ext3-fs Error (device Dm-0) Ext3_journal_start_sb Detected Aborted Journal
running e2fsck with an alternate superblock: e2fsck -b 8193
HCL Search Reviews Search ISOs Go to Page... LinuxQuestions.org > Forums > Linux Forums > Linux - Server [SOLVED] Server booting issues(EXT3-fs: unable to read superblock 'etc') User Name Remember Me? Password Linux ext3 fs error ext3_journal_start_sb detected aborted journal - Server This forum is for the discussion of Linux Software used in a ext3-fs error fortigate server related context. Notices Welcome to LinuxQuestions.org, a friendly and active Linux Community. You are currently viewing LQ as a guest.
Detected Aborted Journal Ext4
By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. https://ubuntuforums.org/archive/index.php/t-1138451.html Join our community today! Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Are you new to LinuxQuestions.org? Visit the following links: Site Howto | Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here. Having a problem logging in? Please visit http://www.linuxquestions.org/questions/linux-server-73/server-booting-issues-ext3-fs-unable-to-read-superblock-'etc'-826691/ this page to clear all LQ-related cookies. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Click Here to receive this Complete Guide absolutely free. Search this Thread 08-17-2010, 01:52 AM #1 Goleteral LQ Newbie Registered: Aug 2010 Posts: 3 Rep: Server booting issues(EXT3-fs: unable to read superblock 'etc') Having some issues with a mail server running CentOS, don't really know what had been done do it so I'm a bit stumped, when booting the server I get the following error: Code: EXT3-fs: unable to read superblock mount: error mounting /dev/root on /sysroot as ext3: Invalid argument Setting up ot
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start 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 http://askubuntu.com/questions/379154/attempting-to-read-lvm-disk-in-ubuntu about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. 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 fs error Attempting to read LVM disk in ubuntu up vote 0 down vote favorite I pulled a disk formatted in LVM from a NAS after the device failed, and need to recover the data, but I can't seem to get it to mount. This is the closest I got: root@peter-desktop:/home/peter# pvscan PV /dev/sdd5 VG c lvm2 [1.82 TiB / 0 free] Total: 1 [1.82 TiB] / in use: 1 [1.82 TiB] / ext3-fs error (device in no VG: 0 [0 ] root@peter-desktop:/home/peter# vgscan Reading all physical volumes. This may take a while... Found volume group "c" using metadata type lvm2 root@peter-desktop:/home/peter# lvscan ACTIVE '/dev/c/c' [1.82 TiB] inherit root@peter-desktop:/home/peter# mount -t ext3 /dev/c/c /mnt/fcroot mount: wrong fs type, bad option, bad superblock on /dev/mapper/c-c, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so Does anybody know what is going wrong here? Is the drive corrupt? The filesystem type was confirmed to be ext3 using the file command root@peter-desktop:/home/peter# file -sL /dev/c/c /dev/c/c: Linux rev 1.0 ext3 filesystem data, UUID=3ecd91ba-161a-4d7f-bac7-a3b1a7095be4, volume name "c" (large files) and the last relevant errors in the dmesg log appear to be EXT3-fs (dm-3): error: bad blocksize 16384 I don't normally deal with command line mounting, but since the GUI couldn't mount the drive I didn't really have a choice, so please explain any code and I'll do my best to understand it. mount lvm ext3 share|improve this question edited Nov 19 '13 at 19:37 steeldriver 31.2k44474 asked Nov 19 '13 at 1:06 Pierowheelz 111 Looks like it's ext3 root@peter-desktop:/home/peter# file -sL /dev/c/c /dev/c/c: Linux rev 1.0 ext3 filesystem data, UUID=3ecd91ba-161a-4d7f-bac7-a3b1a7095be4, volume name "c" (large files) –Pierowhee