Re: broken raid level 5 array caused by user error

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Phil

Whoa!  Don't do that.  Upgrade to CentOS 7, or go back to the other
machine.  You didn't mention switching machines, btw.  That would
explain the different drive names vs. roles.  You need to document the
device names vs. drive serial numbers on the current setup before moving
or upgrading.  Then adjust the names worked out above based on the
serial numbers in the new environment.

oh I'm sorry, I should have make more clear, that I went back to the old system after the raid reshape failed. All outputs I posted were from the same (old one) machine.

Now I booted the latest centos 7 rescue, but fsck still tells the same:

/dev/md0 has unsupported feature(s): FEATURE_C16 FEATURE_C17 FEATURE_C18 FEATURE_C19 FEATURE_C21 FEATURE_C22 FEATURE_C23 FEATURE_C25 FEATURE_C27 FEATURE_C28 FEATURE_I29 FEATURE_R29
e2fsck: Get a newer version of e2fsck!

I created the array with this command:

mdadm --create --assume-clean -l5 -n4 --chunk 64 --data-offset 1024 --metadata 1.2 /dev/md0 ......

This both combinations

The devices names are now different, but I adjusted the names by serial numbers as you told.

Also mdadm --examine on on of the drives tells "Data offset: 2048 Sectors" when mdadm --create --data-offset 1024 is used. Is this normal? It's confusing me (using --data-offset 2048 on creation gives "Data offset: 2048 Sectors").

Thanks,

Mathias
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux