| 1 |
On Fri, 2012-01-06 at 02:42 +0100, Volker Armin Hemmann wrote: |
| 2 |
|
| 3 |
> in your case |
| 4 |
> |
| 5 |
> sfdisk -d /dev/sdb | sfdisk /dev/sdc |
| 6 |
> |
| 7 |
> of course ;) |
| 8 |
> |
| 9 |
One of the disks had a GPT partition table which I was eventually able |
| 10 |
to get rid of with gdisk (emerge -av gptfdisk). |
| 11 |
|
| 12 |
I'm close. I had a 2.7TiB RAID5 array using genkernal, comprising three |
| 13 |
1.5TB disks, using the commands |
| 14 |
mdadm --create /dev/md0 --level=5 |
| 15 |
--raid-devices=3 /dev/sdb1 /dev/sdc1 /dev/sdd1 |
| 16 |
|
| 17 |
mdadm --detail --scan >> /etc/mdadm.conf |
| 18 |
|
| 19 |
I formatted this array as an xfs filesystem. |
| 20 |
|
| 21 |
After reboot, however, /dev/md0 is still there, but I get a 'can't read |
| 22 |
superblock' error. |
| 23 |
|
| 24 |
What am I missing? |
Archives