Re: RAID5 superblocks partly messed up after degradation

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

 



Neil Brown wrote:
I'll see what I can do :-)

The problem could be resolved by removing one of the two external SATA controllers (PCI card with ALI M5283) and using Kernel 2.6.20.6 Only removing the ALI PCI card brought the numbering scheme in line again so the old (degraded) array became accessible again. Even with no disks attached to it, the kernel did not get its disk naming in shape to assemble more than one ("sdd") of the four old devices although all 4 devices could be accessed with "mdadm --examine" or fdisk. Additionally, using 2.6.20.6 resolved the ghost device issue where one SATA drive appeared additionally as a PATA drive, too. Now I could create the new array and copy over all data from the degraded one. <wipes sweat>

Are there any kernel logs that this time which might make it clear
what is happening?
Not really, the logs contain quite a mess of trying different kernels and system configurations to get the data back
with the disc naming following the state of the moon.
I produced too much sweat to get the data back so I am reluctant to try anything now that it works until my backup
scheme is somewhat improved :)

Thank you for your help.

Frank

-
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