[Eisfair] Software-Raid-1 mit ext4

[Jürgen Witt]

Hallo Tom,

Am 06.07.2014 21:07, schrieb Thomas Bork:
> Am 06.07.2014 15:56, schrieb ich:
>
> Nach diesem Muster funktioniert das bei mir:
>
> sata # sgdisk -p /dev/sda
> Disk /dev/sda: 8388608 sectors, 4.0 GiB
> Logical sector size: 512 bytes
> Disk identifier (GUID): 225A5478-5E44-4F29-A07B-C5237D2C8D0A
> Partition table holds up to 128 entries
> First usable sector is 34, last usable sector is 8388574
> Partitions will be aligned on 2048-sector boundaries
> Total free space is 22494 sectors (11.0 MiB)
>
> Number  Start (sector)    End (sector)  Size       Code  Name
>     1            2048          100351   48.0 MiB    8300  boot
>     2          100352          362495   128.0 MiB   8200  swap
>     3          362496         2459647   1024.0 MiB  8300  root
>     4         2459648         8368094   2.8 GiB     8300  data
> sata # sgdisk -p /dev/sdb
> Creating new GPT entries.
> Disk /dev/sdb: 8388608 sectors, 4.0 GiB
> Logical sector size: 512 bytes
> Disk identifier (GUID): 64A8CE74-7CE2-400A-BCA3-09392C7C8114
> Partition table holds up to 128 entries
> First usable sector is 34, last usable sector is 8388574
> Partitions will be aligned on 2048-sector boundaries
> Total free space is 8388541 sectors (4.0 GiB)
>
> Number  Start (sector)    End (sector)  Size       Code  Name
>
> sata # for i in 1 2 3 4; do sgdisk -t ${i}:fd00 /dev/sda; done
> Warning: The kernel is still using the old partition table.
> The new table will be used at the next reboot.
> The operation has completed successfully.
> Warning: The kernel is still using the old partition table.
> The new table will be used at the next reboot.
> The operation has completed successfully.
> Warning: The kernel is still using the old partition table.
> The new table will be used at the next reboot.
> The operation has completed successfully.
> Warning: The kernel is still using the old partition table.
> The new table will be used at the next reboot.
> The operation has completed successfully.
>
> Reboot, da der Kernel die neue Tabelle erst nach einem Reboot nutzt.

Danke für das Ausprobieren. Es ist also der Reboot gleich am Anfang, der 
über den Erfolg der Aktion entscheidet. Ich probiere es gleich auch noch 
einmal und werde Dein erfolgreiches Ergebnis hoffentlich bestätigen.

Gruß
Jürgen