Ext3 Error Messages
Contents |
error after running fsck Issues related to hardware problems Post Reply Print view Search Advanced search 10 posts • ext3 fs error journal has aborted Page 1 of 1 maksaraswat Posts: 44 Joined: 2011/10/14 19:00:52
Ext3-fs Error Unable To Read Inode Block
Location: New York Contact: Contact maksaraswat Website [SOLVED] EXT3-fs error after running fsck Quote Postby maksaraswat ext3-fs error fortigate » 2012/01/31 20:43:31 Hi,For some reason my RAID 6 mount was unmountable and I was getting the error message when I tried to mount it manually [root@server ext3-fs error (device sda6) in start_transaction journal has aborted ~]# mount /dev/sdb1 /local1/mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or other error In some cases useful 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
Ext3-fs Error (device Dm-0)
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 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:
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 ext3-fs error (device dm-0) ext3_journal_start_sb detected aborted journal Us Learn more about Stack Overflow the company Business Learn more about hiring developers ext3 fs error ext3_journal_start_sb detected aborted journal or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack
Detected Aborted Journal Ext4
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 http://www.centos.org/forums/viewtopic.php?t=24611 question Anybody can answer The best answers are voted up and rise to the top List of error messages available for a command in Unix up vote 7 down vote favorite Is it possible to find out what error messages a command includes? For example I want to see the list of error messages that mkfs.ext3 command will print in different error situations. Shall I look into the source http://unix.stackexchange.com/questions/105632/list-of-error-messages-available-for-a-command-in-unix code or are there other ways to achieve this? documentation return-status share|improve this question edited Apr 27 at 18:14 Anthon 47.5k1462125 asked Dec 17 '13 at 21:14 coffeMug 4,53262035 add a comment| 1 Answer 1 active oldest votes up vote 7 down vote accepted Source code is going to be your best bet. You can in a pinch use the command strings to get some basic ideas about a binary and text that it may contain. Example Here are the first 20 lines of the output. These are the lines that contain the string "error" in them. $ strings /usr/sbin/mkfs.ext3 | grep -i error | head -20 Syntax error in mke2fs config file (%s, line #%d) Couldn't init profile successfully (error: %ld). Error while enabling multiple mount protection feature. MMP error info: last update: %s node: %s device: %s Syntax error in profile section header Syntax error in profile relation [ERROR] %s:%d:%s:: Unable to allocate dquot [ERROR] %s:%d:%s:: Cannot initialize io on quotafile [ERROR] %s:%d:%s:: Cannot finish IO on new quotafile: %s [ERROR] %s:%d:%s:: Unable to allocate quota handle [ERROR] %s:%d:%s:: Failed to allocate quota context [ERROR] %s:%d:%s:: Failed to allocate dictionary [ERROR] %s:%d:%s:: while opening inode scan. ret=%ld [ERROR] %s:%d:%s:: while gettin
displayed on console during the boot.