1 |
Am Samstag, 7. Januar 2012, 13:27:04 schrieb Jeff Cranmer: |
2 |
> > > I tried changing the type of each array element in fdisk to fd (linux |
3 |
> > > raid autodetect. |
4 |
> > > |
5 |
> > > The array is still not being recognised at boot, with the same 'cannot |
6 |
> > > read superblock' error. |
7 |
> > > |
8 |
> > > I also tried re-running mdadm --create /dev/md0 --level=5 |
9 |
> > > --raid-devices=3 /dev/sdb1 /dev/sdc1 /dev/sdd1 |
10 |
> > > I get the error |
11 |
> > > mdadm: device /dev/sdb1 not suitable for any style of array. |
12 |
> > > |
13 |
> > > What is going on here? |
14 |
> > |
15 |
> > I am thinking ;) |
16 |
> |
17 |
> LOL! |
18 |
> |
19 |
> Me too. |
20 |
> |
21 |
> mdadm --detail /dev/md0 thinks that /dev/sdc1 is faulty. |
22 |
> I'm not sure whether it's really faulty, or just that my setup for RAID |
23 |
> is screwed up. |
24 |
> |
25 |
> How do I get rid of an existing /dev/md0? |
26 |
|
27 |
you stop it. Override the superblock with dd.. and lose all data on the disks. |
28 |
|
29 |
|
30 |
> |
31 |
> I'm thinking that I can try creating a RAID1 array using the two |
32 |
> allegedly good disks and see if I can make that work. |
33 |
|
34 |
yeah |
35 |
|
36 |
> |
37 |
> If that works, I'll get rid of it and try recreating the RAID1 with one |
38 |
> good disk and the one that mdadm thinks is faulty. |
39 |
> |
40 |
|
41 |
you don't have to. You can migrate a 2 disk raid1 to a 3 disk raid5. Howtos |
42 |
are availble via google. |
43 |
|
44 |
|
45 |
just saying - box in suspend to ram. I change the cable (and connector on |
46 |
mobo) on a disk with two raid 1 partitions on it. |
47 |
|
48 |
One came back after starting the box. |
49 |
|
50 |
The other? Nothing I tried worked. At the end I dd'ed the partition.. and did |
51 |
a complete 'faulty disk/replacement' resync.... |
52 |
|
53 |
argl. |
54 |
|
55 |
|
56 |
-- |
57 |
#163933 |