1 |
On 01/-10/37 11:59, James wrote: |
2 |
> Background: |
3 |
> I worked on this last April can gave up on the (livedDVD) |
4 |
> install with too many other things to do, and pissed off at |
5 |
> a lack of usable (current) documentation. |
6 |
> |
7 |
> So, taking a fresh look at the BOTCHED system: |
8 |
> The 2 drives are identical 2TB: Seagate |
9 |
> drives: Model Number: ST32000542AS |
10 |
> |
11 |
> I read about the 4K block problem and could have |
12 |
> easily made a formating mistake....(?). |
13 |
> |
14 |
> fdisk /dev/sda (not the best tool to use... |
15 |
> |
16 |
|
17 |
fdisk does have a partition/drive limit of ~2.2TB, but this drive should |
18 |
still work with it. The only other option is GPT, but I don't think grub |
19 |
boots from that yet (unless you use grub2 with patches?) |
20 |
|
21 |
> |
22 |
> Disk /dev/sda: 2000.4 GB, 2000398934016 bytes |
23 |
> But in my attempt to install, I used this geometry: |
24 |
> fdisk -H 224 -S 56 /dev/sda |
25 |
|
26 |
That should align it to 4k blocks, I had to do the same on my SSD |
27 |
(224/56=4)... |
28 |
|
29 |
|
30 |
> using the livedDVD: |
31 |
> |
32 |
> cat /proc/mdstat |
33 |
> Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] |
34 |
> md125 : active raid1 md127p1[0] |
35 |
> 262080 blocks [2/1] [U_] |
36 |
> |
37 |
> md126 : active raid1 md127p2[0] |
38 |
> 5023680 blocks [2/1] [U_] |
39 |
> |
40 |
> md127 : active raid1 sdb[1] sda[0] |
41 |
> 1948227584 blocks [2/2] [UU] |
42 |
> |
43 |
> |
44 |
|
45 |
Are the partitions on each drive *exactly* the same? If the end cylinder |
46 |
and start cylinder for the other drive is off by one it will affect two |
47 |
partitions, leaving them in a dirty state and the third in a clean state. |
48 |
|
49 |
> |
50 |
> It has been suggested kernel >=2.6.37 will have (better?) |
51 |
> support for 4k sectors disks [1]. |
52 |
> |
53 |
|
54 |
I believe I have 2.6.37 on my htpc and it works fine with the 4k-aligned |
55 |
SSD. |
56 |
|
57 |
> Should I just start over? |
58 |
|
59 |
I would start over. |
60 |
|
61 |
Are you using BIOS-raid? (Such as Intel ICH*R?) I assume no, given the |
62 |
'fd' type partitions. If you are, you are using the wrong approach. It's |
63 |
already in a raid set and you need to create normal partitions on it, |
64 |
not type 'fd'. |
65 |
|
66 |
However, there's a lot of information on how to use mdraid and create |
67 |
native linux software raid partitions. |
68 |
|
69 |
If you are trying to use BIOS raid, it's a little different, and |
70 |
unneeded if you are not using Windows. The reason I mention this is that |
71 |
mdadm gave my BIOS fakeraid /dev/md126* partitions. When I created |
72 |
native linux raid partitions, they were /dev/md0, /dev/md1, etc. |
73 |
|
74 |
I can't really help more until I know exactly what you are trying to do. |
75 |
Right now (to me, anyway) it looks like you are mixing software raid and |
76 |
BIOS fakeraid, as with native mdadm you generally don't have partitions |
77 |
(/dev/md126p1, /dev/md126p2, etc) with native raid (which is /dev/md0, |
78 |
/dev/md1, etc) as I said above. |
79 |
|
80 |
If you are trying to use mdadm with a BIOS fakeraid, then you are |
81 |
correct in that there's no documentation. Just yesterday I finally got a |
82 |
working install after three weeks of messing around. |
83 |
|
84 |
What's the output of `mdadm --detail-platform`? |
85 |
|
86 |
Dan |