Sounds to me like you either:
1) initialized md4 after there was already a
live file system on it, or
2) initialized md4, then used dd to copy a
file system onto it,
and you didn't take into account that the raid
superblock takes up the last bit of the partition
on which it's built, meaning that the md device
size is slightly smaller than the original partition
was. I would suggest backing up the data, re-running
mke2fs on md4 rather than on the underlying partition,
then restoring the data.
tw
On 04/12/2000 12:05 +0200, Patrick Peck wrote:
>> hello,
>>
>> i'm trying to get software-raid 1 started on my machine.
>>
>> kernel version 2.2.14 + ide patch + raid-0.90 patch
>>
>> so far, i've succeeded in setting up the array using mkraid.
>>
>> when booting the system, the raid partitions are auto-detected,
>> but mounting the filesystem fails with the following error:
>>
>> /dev/md4: The filesystem size (according to the superblock) is 2671444
>> blocks. The physical size of the device is 2671424 blocks. Either the
>> superblock or the partition table is likely to be corrupt.
>>
>> /dev/md4: UNEXPECTED INCONSISTENCY, RUN FSCK MANUALLY
>>
>>
>> i did 'fsck /dev/md4' but it did'nt help...
>>
>>
>> thanks in advance,
>> patrick
End of included message
--
+--------------------------+------------------------------+
| Tim Walberg | [EMAIL PROTECTED] |
| 828 Marshall Ct. | www.concentric.net/~twalberg |
| Palatine, IL 60074 | |
+--------------------------+------------------------------+
PGP signature
