Ext3-fs Dm-3 Error Unable To Read Superblock
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 ext3 fs error journal has aborted Location: New York Contact: Contact maksaraswat Website [SOLVED] EXT3-fs error after running fsck ext3-fs error unable to read inode block Quote Postby maksaraswat » 2012/01/31 20:43:31 Hi,For some reason my RAID 6 mount was unmountable and I was getting the ext3-fs error (device sda6) in start_transaction journal has aborted error message when I tried 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
Ext3-fs Error (device Dm-0)
info is found in syslog - try 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 ext3 fs error ext3_journal_start_sb detected aborted journal out that I should do a file system check with fsck 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 erro
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 ext3-fs error fortigate bit of searching ran fsck -yfv until it stopped reporting problems. I
Ext3-fs Error (device Dm-0) Ext3_journal_start_sb Detected Aborted Journal
then re-booted and used the update manager to upgrade to 9.04. It reported that various things had failed and
Detected Aborted Journal Ext4
then rebooted to the same 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 http://www.centos.org/forums/viewtopic.php?t=24611 still getting errors. I've just run fsck -p 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 https://ubuntuforums.org/archive/index.php/t-1138451.html or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193
Today's Posts Advanced Search Find the answer to your Linux question: Entire Site Articles Downloads Forums Linux Hosting Forum Your Distro Other Linux Distributions [SOLVED] EXT3-fs: unable to read superblock If this is your first visit, be sure to check out http://www.linuxforums.org/forum/other-linux-distributions/170086-solved-ext3-fs-unable-read-superblock.html the FAQ by clicking the link above. You may have to register before you can post: http://www.cyberciti.biz/faq/recover-bad-superblock-from-corrupted-partition/ click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. ** If you are logged in, most ads will not be displayed. ** Linuxforums now supports the Tapatalk app for your mobile device. Results 1 to 7 of 7 Thread: [SOLVED] EXT3-fs: unable to read superblock Thread Tools Show Printable Version fs error Email this Page… Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode Enjoy an ad free experience by logging in. Not a member yet? Register. 09-27-2010 #1 TiffDiff View Profile View Forum Posts Private Message View Articles Just Joined! Join Date Sep 2010 Posts 4 [SOLVED] EXT3-fs: unable to read superblock Hi, I am unable to boot my server and it is causing "Kernel panic - not syncing: Attempted to kill init!". Here ext3-fs error (device are my details: I have a brand new Dell PowerEdge T110 server with Quad-Core Xeon CPU and 2GB 1333MHz RAM. I have installed a hard disk (SATA, 7.2rpm) on this machine that I removed from another Dell PowerEdge T100 server with Dual-Core Xeon CPU that was running software RAID 1. Now when I boot the new T110 server, it displays the following error messages: Creating root device. Mounting root filesystem. EXT3-fs: unable to read superblock mount: error mounting /dev/root on /sysroot as ext3: Invalid argument Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init! I am running CentOs v5.5 x86-64. If I put the hard disk back into T100, it boots fine. I do not know why it is not working with T110 server. Please help!!! 09-28-2010 #2 ved View Profile View Forum Posts Private Message View Articles Linux User Join Date Jan 2008 Location New Delhi Posts 309 i am not sure about that but as i understand your new system is Quad-Core Xeon CPU and another system is Dual-Core Xe
in CentOS, Debian / Ubuntu, File system, Hardware, Linux, RedHat and Friends, Troubleshooting, Ubuntu LinuxQ. How can I Recover a bad superblock from a corrupted ext3 partition to get back my data? I'm getting following error:
/dev/sda2: Input/output error mount: /dev/sda2: can't read superblockHow do I fix this error? A. Linux ext2/3 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 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 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