Ext3-fs Sdb Error Unable To Read Superblock
Contents |
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 ext3 fs error journal has aborted this site About Us Learn more about Stack Overflow the company Business Learn ext3-fs error unable to read inode block more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ ext3-fs error (device sda6) in start_transaction journal has aborted Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody
Ext3-fs Error (device Dm-0)
can answer The best answers are voted up and rise to the top How to recover data from a corrupted ext3 partition? up vote 5 down vote favorite 1 A server of mine had a drive failure of some sort which caused the OS (CentOS 5) to crash and stop working (it refuses to boot). So we put another drive with a working OS ext3 fs error ext3_journal_start_sb detected aborted journal and from there we try to mount the partitions in the old drive. Most partitions mount fine except for one: the /var partition, where my MySQL tables reside. When I try to mount that one, I see these errors with dmesg: sd 0:0:1:0: Unhandled sense code sd 0:0:1:0: SCSI error: return code = 0x08100002 Result: hostbyte=invalid driverbyte=DRIVER_SENSE,SUGGEST_OK sdb: Current: sense key: Medium Error Add. Sense: Unrecovered read error Info fld=0x4a47e JBD: Failed to read block at offset 9863 JBD: recovery failed EXT3-fs: error loading journal. Is there a way I can recover the data in that partition? EDIT: As requested, the output of tune2fs -l /dev/sdb2 is: tune2fs 1.39 (29-May-2006) Filesystem volume name: /var1 Last mounted on:
in CentOS, Debian / Ubuntu, File system, Hardware, Linux, RedHat and Friends, Troubleshooting, Ubuntu LinuxQ. How can I Recover a bad superblock from a ext3-fs error fortigate corrupted ext3 partition to get back my data? I'm getting following
Ext3-fs Error (device Dm-0) Ext3_journal_start_sb Detected Aborted Journal
error:
/dev/sda2: Input/output error mount: /dev/sda2: can't read superblockHow do I fix this error? A. Linux ext2/3Ext3-fs Error Loading Journal
filesystem stores superblock at different backup location so it is possible to get back data from corrupted partition.WARNING! Make sure file system is UNMOUNTED.If your system will give http://serverfault.com/questions/493091/how-to-recover-data-from-a-corrupted-ext3-partition you a terminal type the following command, else boot Linux system from rescue disk (boot from 1st CD/DVD. At boot: prompt type command linux rescue).Mount partition using alternate superblockFind out superblock location for /dev/sda2: # dumpe2fs /dev/sda2 | grep superblock Sample output: Primary superblock at 0, Group descriptors at 1-6 Backup superblock at 32768, Group http://www.cyberciti.biz/faq/recover-bad-superblock-from-corrupted-partition/ descriptors at 32769-32774 Backup superblock at 98304, Group descriptors at 98305-98310 Backup superblock at 163840, Group descriptors at 163841-163846 Backup superblock at 229376, Group descriptors at 229377-229382 Backup superblock at 294912, Group descriptors at 294913-294918 Backup superblock at 819200, Group descriptors at 819201-819206 Backup superblock at 884736, Group descriptors at 884737-884742 Backup superblock at 1605632, Group descriptors at 1605633-1605638 Backup superblock at 2654208, Group descriptors at 2654209-2654214 Backup superblock at 4096000, Group descriptors at 4096001-4096006 Backup superblock at 7962624, Group descriptors at 7962625-7962630 Backup superblock at 11239424, Group descriptors at 11239425-11239430 Backup superblock at 20480000, Group descriptors at 20480001-20480006 Backup superblock at 23887872, Group descriptors at 23887873-23887878Now check and repair a Linux file system using alternate superblock # 32768: # fsck -b 32768 /dev/sda2 Sample output:fsck 1.40.2 (12-Jul-2007) e2fsck 1.40.2 (12-Jul-2007) /dev/sda2 was not cleanly unmounted, check forced. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summ
won't boot, all your filesystem checks tell you you've a bad superblock, but you cant seem to find how to fix it. Well, https://linuxexpresso.wordpress.com/2010/03/31/repair-a-broken-ext4-superblock-in-ubuntu/ here goes🙂 This guide is for ext4 , though I'll explain https://www.redhat.com/archives/redhat-list/2013-October/msg00047.html how other filesystems can be cured along the way. The easiest way to carry all this out, seeing as your computer probably won't boot at this stage, is to download and burn a copy of Parted Magic. Boot from that, and you'll access to a number of useful fs error tools. First, figure out what partition we're dealing with. sudo fdisk -l The above will list all the partitions on all the drives in your computer. To recover a lost partition, your going to need Testdisk. Testdisk is included in Parted Magic, and there's a great guide on their site. For this though, we just need the partition number, such ext3-fs error (device as /dev/sda3 or /dev/hdb1. Now, make sure your superblock is the problem, by starting a filesystem check, replacing xxx with your partition name. Here, you can change ext4 to ext3, or ext2 to suit the filesystem. sudo fsck.ext4 -v /dev/xxx If your superblock is corrupt, the output will look like this fsck /dev/sda5 fsck 1.41.4 (27-Jan-2009) e2fsck 1.41.4 (27-Jan-2009) fsck.ext4: Group descriptors look bad... trying backup blocks... fsck.ext4: Bad magic number in super-block while trying to open /dev/sda5 The superblock could not be read or does not describe a correct ext4 filesystem. If the device is valid and it really contains an ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193
Subject: Re: EXT3-fs: unable to read superblock Date: Thu, 24 Oct 2013 20:43:56 +0200 Hej List, Thank you for your Help! I was able to Restore form a Backup and mount the broken HDD to copy some SQL Databasedumbs. Cheers Seb On Monday, October 21, 2013 at 3:26 AM, Abhishek Tyagi wrote: > 1) dumpe2fs /dev/sda2 | grep superblock > > 2 ) fsck -b 32768 /dev/sda2 > > 3) mount sb=32768 /dev/sda2 /mnt > > 4 ) cd /mnt > > 5) mkdir test > > 6) cp file /mnt/test > > > > > > On Sun, Oct 20, 2013 at 7:11 PM, Daniel Tate