NAS Kapazitätserweiterung schlägt fehl

  • Ich hab ein älteres TS 439 (4 Bay) Modell und wollte die Kapazität mit größeren Platten erweitern. Soweit so gut . 1 TB Platten sollten gegen 4 mal 3 TB Platten (WD NAS RED) getauscht werden. Ich übernehme mal die Bezeichnungen der Slots (0,1,2,3)


    Platte in Slot 3 in degraded Mode. Platte raus, neue rein, resync startet -> alles OK
    Platte in Slot 2 in degraded Mode. Platte raus, neue rein, resync startet -> alles OK
    Platte in Slot 1 in degraded Mode. Platte raus, neue rein, resync startet -> alles OK
    Platte in Slot 0 in degraded Mode. Platte raus, neue rein, resync startet nicht . Ich höre sie laufen, nichts passiert ?


    Alte Platte rein - resync. OK. Dann tausche ich die neuen Platten in Slot 2. Kein Problem. Es liegt nicht an der Platte.


    OK. Probleme mit md4 swap. sdb2 fehlt. sdb2 liegt ja auf den der neuen Platte. Da scheint es einen Bug in der Firmware zu geben.


    Code
    [~] # cat /proc/mdstatpersonalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath]md0 : active raid5 sda3[3] sdb3[0] sdd3[2] sdc3[1]2925580800 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]?md4 : active raid1 sda2[0]530132 blocks super 1.0 [2/1] [U_]md13 : active raid1 sda4[0] sdb4[1] sdd4[3] sdc4[2]458880 blocks [4/4] [UUUU]bitmap: 0/57 pages [0KB], 4KB chunkmd9 : active raid1 sda1[0] sdb1[1] sdd1[3] sdc1[2]530048 blocks [4/4] [UUUU]bitmap: 0/65 pages [0KB], 4KB chunk[~] # mdadm --examine /dev/sda2dev/sda2:Magic : a92b4efcVersion : 1.0Feature Map : 0x0Array UUID : f850fb92:e7a0e567:860be8f5:51aeb2c2Name : 4Creation Time : Sun Jul 16 21:13:41 2017Raid Level : raid1Raid Devices : 2Used Dev Size : 1060264 (517.79 MiB 542.86 MB)Array Size : 1060264 (517.79 MiB 542.86 MB)Super Offset : 1060272 sectorsState : cleanDevice UUID : 13bc755e:484ee4b0:47d2343d:7a37293bUpdate Time : Mon Jul 17 03:01:08 2017Checksum : 96a6602d - correctEvents : 39Array Slot : 0 (0, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed , failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, faile d, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, fail ed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, fai led, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, fa iled, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, f ailed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed , failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, faile d, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, fail ed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, fai led, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, fa iled, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, f ailed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed,Array State : U_ 383 failed

    Man beachte die Superblock Versionsnummer 1.0 Die alte hat noch 0.9

    Code
    [~] # mdadm --examine /dev/sda1/dev/sda1:Magic : a92b4efcVersion : 00.90.00UUID : 4449873f:d1f539ae:cbab2c1c:b33450c9Creation Time : Wed Jun 17 18:17:38 2009Raid Level : raid1

    Jedenfalls bekomme ich mit

    Code
    [~] # swapoff /dev/md4[~] # mdadm -S /dev/md4[~] # mkswap /dev/sda2[~] # mkswap /dev/sdb2[~] # swapon /dev/sda2[~] # swapon /dev/sdb2

    das Problem nicht gelöst

    Code
    [~] # e2fsck -f -v -C 0 /dev/sda2e2fsck 1.41.4 (27-Jan-2009)e2fsck: Superblock invalid, trying backup blocks...e2fsck: Bad magic number in super-block while trying to open /dev/sda2The superblock could not be read or does not describe a correct ext2filesystem.If the device is valid and it really contains an ext2filesystem (and not swap or ufs or something else), then the superblockis corrupt, and you might try running e2fsck with an alternate superblock:e2fsck -b 8193 <device>

    Das Problem nicht gelöst. Und überhaupt: Warum hat die Platte in Slot 0 eine msdos Partion :?: während die anderen gpt haben?

    Fragen über Fragen. Wer kann helfen?