Re: Problems after reshaping of Raid5 array

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

 



On 29/11/10 21:04, Michele Bonera wrote:
The problem is that I added a device partition (sdc1) but after the
crash the array has sdc (the device) as one of his components. The
partition table on the disk was wiped-out.

The result is that the filesystem on it (dev/md6) is unreadable and
fsck.ext3 can't fix it.

Right. This is consistent with what I've seen as well.

I can't help you repair this filesystem, but when you do my suggestion remains to change the partition types of the RAID members. This is because I've noticed that the in-kernel RAID detection and assembly code sometimes gets it wrong (leading to the kinds of symptoms you've reported), whereas mdadm run from the initrd does not.
--
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