Dear Suser's, I am faced with a rather weird problem. I have a raid personality running as /dev/md0. When issuing mdadm --detail /dev/md0 I get: /dev/md0: Version : 00.90.00 Creation Time : Sat Oct 11 08:19:27 2003 Raid Level : raid1 Array Size : 199125568 (189.90 GiB 203.95 GB) Device Size : 199125568 (189.90 GiB 203.95 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Sat Oct 9 04:12:14 2004 State : dirty, no-errors Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Number Major Minor RaidDevice State 0 3 65 0 active sync /dev/hdb1 1 22 1 1 active sync /dev/hdc1 UUID : 03f9846c:72f50436:af213782:c8e28b96 A person from the list mentioned that it would be a good idea to run fsck in order to correct the "dirty" mentioned in the state section of mdadm. So I did an fsck on /dev/md0 and I got the following report: server:/ # fsck /dev/md0 fsck 1.28 (31-Aug-2002) reiserfsck 3.6.2 (2002) Will read-only check consistency of the filesystem on /dev/md0 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes):Yes ########### reiserfsck --check started at Sat Oct 9 01:09:04 2004 ########### Replaying journal.. No transactions found Checking S+tree../ 1 (of 2)/ 3 (of 90)/ 31 (of 166)bad_stat_data: block 37758, [2 21119 0x0 SD (0)], SD has bad nlink number ok Comparing bitmaps..ok Checking Semantic tree... ok There were found 1 corruptions which can be fixed with --fix-fixable ########### reiserfsck finished at Sat Oct 9 01:09:38 2004 ########### fsck.reiserfs /dev/md0 failed (status 0x4). Run manually! Then I followed the reiserfsck --fix-fixable /dev/md0 and I got the following message which, by the way, does not mention anything about fixing the problem: server:/ # reiserfsck --fix-fixable /dev/md0 reiserfsck 3.6.2 (2002) Will check consistency of the filesystem on /dev/md0 Will fix what can be fixed w/o --rebuild-tree Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes):Yes ########### reiserfsck --fix-fixable started at Sat Oct 9 01:10:11 2004 ########### Replaying journal.. No transactions found Checking S+tree..ok Comparing bitmaps..ok Checking Semantic tree... ok No corruptions found There are on the filesystem: Leaves 31337 Internal nodes 220 Directories 70 Other files 22854 Data block pointers 30613642 (2217 of them are zero) Safe links 0 ########### reiserfsck finished at Sat Oct 9 01:11:08 2004 ########### When running again reiserfsck on /dev/md0 I get the above mentioned error again as if I never ran the --fix-fixable command. Can someone give me a good explanation or perhaps some advice on how to deal with this problem??? Thank you TonS!!! Chris