| 1 |
On Fri, 2012-01-06 at 13:36 +0100, Volker Armin Hemmann wrote: |
| 2 |
> Am Donnerstag, 5. Januar 2012, 23:44:10 schrieb Jeff Cranmer: |
| 3 |
> > On Fri, 2012-01-06 at 02:42 +0100, Volker Armin Hemmann wrote: |
| 4 |
> > > in your case |
| 5 |
> > > |
| 6 |
> > > sfdisk -d /dev/sdb | sfdisk /dev/sdc |
| 7 |
> > > |
| 8 |
> > > of course ;) |
| 9 |
> > |
| 10 |
> > One of the disks had a GPT partition table which I was eventually able |
| 11 |
> > to get rid of with gdisk (emerge -av gptfdisk). |
| 12 |
> > |
| 13 |
> > I'm close. I had a 2.7TiB RAID5 array using genkernal, comprising three |
| 14 |
> > 1.5TB disks, using the commands |
| 15 |
> > mdadm --create /dev/md0 --level=5 |
| 16 |
> > --raid-devices=3 /dev/sdb1 /dev/sdc1 /dev/sdd1 |
| 17 |
> > |
| 18 |
> > mdadm --detail --scan >> /etc/mdadm.conf |
| 19 |
> > |
| 20 |
> > I formatted this array as an xfs filesystem. |
| 21 |
> > |
| 22 |
> > After reboot, however, /dev/md0 is still there, but I get a 'can't read |
| 23 |
> > superblock' error. |
| 24 |
> > |
| 25 |
> > What am I missing? |
| 26 |
> |
| 27 |
> have you set the type to linux raid autodetect? |
| 28 |
> |
| 29 |
> have you tried mdadm --assemble? |
| 30 |
> |
| 31 |
mdadm --assemble /dev/md0 didn't make any difference. |
| 32 |
Where do I set the type? |
| 33 |
|
| 34 |
Thanks |
| 35 |
|
| 36 |
Jeff |
Archives