*New 12.1 series Release:
2019-11-08: XigmaNAS 12.1.0.4.7091 - released!

*New 11.3 series Release:
2019-10-19: XigmaNAS 11.3.0.4.7014 - released


We really need "Your" help on XigmaNAS https://translations.launchpad.net/xigmanas translations. Please help today!

Producing and hosting XigmaNAS costs money. Please consider donating for our project so that we can continue to offer you the best.
We need your support! eg: PAYPAL

Fixing Raid 5 with fsck fails

Software RAID information and help
Forum rules
Set-Up GuideFAQsForum Rules
Post Reply
tulamidan
NewUser
NewUser
Posts: 4
Joined: 12 Aug 2019 21:11
Status: Offline

Fixing Raid 5 with fsck fails

#1

Post by tulamidan » 16 Aug 2019 08:16

Hello
After successfully syncing my RAID5 (all ok, no errors) I decided to do a fsck to verfiy file system integrity. And it is like I expected: the FS is in serious mess. Fsck is apparently not able to fix it.
The interwebs have very limited information on my particular problem so I decided to give it a shot here.

First my raid configuration:

Code: Select all

Software RAID Information und Status
Geom name: raid
State: COMPLETE CALM
Status: Total=3, Online=3
Type: AUTOMATIC
Pending: (wqp 0 // 0)
Stripesize: 131072
MemUse: 0 (msl 0)
Newest: -1
ID: 2065418888
Providers:
1. Name: raid5/raid
   Mediasize: 2000409591808 (1.8T)
   Sectorsize: 512
   Mode: r1w1e2
Consumers:
1. Name: ad14
   Mediasize: 1000204886016 (932G)
   Sectorsize: 512
   Mode: r2w2e3
   DiskNo: 1
   Error: No
2. Name: ad12
   Mediasize: 1000204886016 (932G)
   Sectorsize: 512
   Mode: r2w2e3
   DiskNo: 0
   Error: No
3. Name: ad4
   Mediasize: 1000204886016 (932G)
   Sectorsize: 512
   Mode: r2w2e3
   DiskNo: 2
   Error: No
A fsck show this (cropped)

Code: Select all

fsck_ufs -yf /dev/raid5/raidp1
** /dev/raid5/raidp1 (NO WRITE)
** Last Mounted on /mnt/raid
** Phase 1 - Check Blocks and Sizes
PARTIALLY ALLOCATED INODE I=471040
UNEXPECTED SOFT UPDATE INCONSISTENCY

CLEAR? no

UNKNOWN FILE TYPE I=471041
UNEXPECTED SOFT UPDATE INCONSISTENCY

CLEAR? no

PARTIALLY ALLOCATED INODE I=471042
UNEXPECTED SOFT UPDATE INCONSISTENCY
...
a lot of similar messages
...
fsck_ufs: bad inode number 494592 to nextinode
The last line is where it breaks. (This output is from a mounted fs, but it does not matter for showing the error)
I have tried various options (unmountend, fsck_ffs ..., but I can't seem to get the bad inode fixed. This is where fsck always breaks and can't get past stage 1

This is a serious error and I did not find any post about it getting fixed successfully.
The result is that a lot of files are not accessible and when I try to, the process (ls or whatever) breaks and becomes unkillable.


Here my Freenas infos again:

Code: Select all

0.7.1 Shere (revision 5024)
FreeBSD 7.2-RELEASE-p6 (revision 199506)
i386-embedded auf Intel(R) Atom(TM) CPU 330 @ 1.60GHz

Post Reply

Return to “Software RAID”