Fedora Linux Support Community & Resources Center
Old 1st January 2012, 05:28 PM
wajda Offline
Registered User
Join Date: Nov 2008
Location: Prague, CZ
Posts: 31
Exclamation Fedora 16 died! UNEXPECTED INCONSISTENCY. Duplicate or bad block in use!

Hi Guys,

New year 2012 for me began with crashing my Fedora 16. Can anybody please help me with the this?

I've been updating Fedora 16 (x86-64) on my Dell laptop using yum when the kernel suddenly crashed badly with the black screen similar to the blue one in windows. The system became totally unresponsive so I had to hard reboot it. But since then when it started booting it fails with the message: _Fedora-16-x86_6: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY (see the attached photo for entire message)

The issue I am facing is very similar to this one, but the fsck message is a bit different. In my case it says:
dracut Warning: _Fedora-16-x86_6: Duplicate or bad block in use!
dracut Warning: _Fedora-16-x86_6: Multiply-claimed block(s) in inode 1487: 1180126 1180127
dracut Warning: _Fedora-16-x86_6: Multiply-claimed block(s) in inode 3281: 1180126 1180127
dracut Warning: _Fedora-16-x86_6: (There are 2 inodes containing multiply-claimed blocks.)
dracut Warning: _Fedora-16-x86_6: File /var/log/gdm/:0-greeter.log (inode #1487, mod time Sun Jan 1 13:40:13 2012)
dracut Warning: has 2 multiply-claimed block(s), shared with 1 file(a):
dracut Warning: _Fedora-16-x86_6: /var/lib/rpm/__db.001 (inode #3281, mod time Sun Jan 1 13:52:55 2012)
I tried to fsck /dev/sda* with no result. Some partitions are Ok, the others are reported to be in use, so fsck cannot check them. I tried touch /forsefsck, but I get the same message and the shell screen when I reboot.

My questions:
1. How could that happen that ext4 being journaling filesystem became corrupted so easily because of a stupid kernel panic followed by hard reboot?
2. [SOLVED] How to cure this (if possible) completely without any undesired consequences?
3. If I happen to reinstall the OS, can I choose better filesystem, so that I never fall into such problem again? What about BTRFS or NILFS? I heard they support snapshots allowing easily recovering in cases like this, it that true?
Attached Thumbnails
Click image for larger version

Name:	IMG_6841.png
Views:	225
Size:	38.7 KB
ID:	22426  

Last edited by wajda; 1st January 2012 at 06:02 PM.
Reply With Quote
Old 1st January 2012, 05:53 PM
GallComp Offline
Nuke 'em Alfred! Administrator - Starring in Bill & Steve's Bogus Journey
Join Date: Mar 2004
Location: Fontana, CA
Age: 41
Posts: 2,462
Re: Fedora 16 died! UNEXPECTED INCONSISTENCY. Duplicate or bad block in use!

Read the forum rules, specially the cross-posting section:

Do Not Cross-Post (Double-Post)
Posting your thread in several parts of the forum is immature. Just because it's in more than one location doesn't mean that more people are going to answer it. In fact quite the opposite normally as experienced members have little time for this sort of behaviour, staff members will close all offending threads. Posts or threads advertising other posts are also seen as cross-posting.
Your post on that thread has been deleted.

"Since when has the world of computer software design been about what people want? This is a simple question of evolution. The day is quickly coming when every knee will bow down to a silicon fist, and you will all beg your binary gods for mercy. "

Reply With Quote
Old 1st January 2012, 06:01 PM
wajda Offline
Registered User
Join Date: Nov 2008
Location: Prague, CZ
Posts: 31
Re: Fedora 16 died! UNEXPECTED INCONSISTENCY. Duplicate or bad block in use!

Ok, I just managed ti fix the issue - I realized that I've been running fsck on wrong partitions. I'm using LVM, so running it on /dev/mapper/vg-something_lv-root/ helped. It found couple of dozens problems on my partition (ext4) showing me some totally meaningless numbers of nodes that need to be fixed asking me if I agree or not. Well, I doubt I could even have a choice in this case It does some magic and the system booted normally. Yum and rpm seem to be working fine, so I assume no data was left corrupted (hopefully).

So I'm closing the question #2, but leaving the other two questions opened - about how could such corruption happen on a journaling FS and which FS would have better resistance than ext4 to such problems?

Thank you!

---------- Post added at 06:01 PM ---------- Previous post was at 05:58 PM ----------

Originally Posted by GallComp View Post
Read the forum rules, specially the cross-posting section...
Ouch! No probs, sorry for that!
Reply With Quote

bad, block, duplicate, ext4, inconsistency, unexpected

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY...help EricSkoglund Using Fedora 17 3rd January 2012 07:30 AM
Unexpected inconsistency Scony Using Fedora 3 25th November 2011 05:37 PM
UNEXPECTED INCONSISTENCY problem balasubramanian Using Fedora 8 29th May 2009 03:42 PM
unexpected inconsistency problem!!! pitat450 Using Fedora 4 12th March 2006 04:45 AM
LogVol Unexpected Inconsistency ERROR Kommissar Using Fedora 11 2nd June 2005 09:57 PM

Current GMT-time: 20:44 (Tuesday, 19-09-2017)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat