| 1 |
Daniel Frey <djqfrey <at> gmail.com> writes: |
| 2 |
|
| 3 |
|
| 4 |
> fdisk does have a partition/drive limit of ~2.2TB, but this drive should |
| 5 |
> still work with it. The only other option is GPT, but I don't think grub |
| 6 |
> boots from that yet (unless you use grub2 with patches?) |
| 7 |
|
| 8 |
|
| 9 |
The failed install used media from March, 2011. |
| 10 |
I'm going to use newer installation media: |
| 11 |
install-amd64-minimal-20110714.iso |
| 12 |
That should solve the gptpart and grub issues. |
| 13 |
|
| 14 |
|
| 15 |
|
| 16 |
> > fdisk -H 224 -S 56 /dev/sda |
| 17 |
> That should align it to 4k blocks, I had to do the same on my SSD |
| 18 |
> (224/56=4)... |
| 19 |
|
| 20 |
Nice to know. I'm new to linux software raid. I do run |
| 21 |
custom gentoo fire walls on 4 G Compact Flash; so I'll be |
| 22 |
seeking your advice, the next time I decide to build a |
| 23 |
new firewall, as it will use dual CF in a Raid 1 config... |
| 24 |
Once I gain some confidence in Raid1 for a workstation. |
| 25 |
|
| 26 |
|
| 27 |
> Are the partitions on each drive *exactly* the same? If the end cylinder |
| 28 |
> and start cylinder for the other drive is off by one it will affect two |
| 29 |
> partitions, leaving them in a dirty state and the third in a clean state. |
| 30 |
|
| 31 |
Identical drives, identical partitioning. A new RAID1 |
| 32 |
install to begin later on today. |
| 33 |
|
| 34 |
> |
| 35 |
> > |
| 36 |
> > It has been suggested kernel >=2.6.37 will have (better?) |
| 37 |
> > support for 4k sectors disks [1]. |
| 38 |
> > |
| 39 |
> |
| 40 |
> I believe I have 2.6.37 on my htpc and it works fine with the 4k-aligned |
| 41 |
> SSD. |
| 42 |
|
| 43 |
New install media should have the >= 2.6.37 kernel, solving |
| 44 |
this issue. |
| 45 |
|
| 46 |
|
| 47 |
> I would start over. |
| 48 |
YEP.... |
| 49 |
|
| 50 |
> |
| 51 |
> Are you using BIOS-raid? |
| 52 |
Nope. |
| 53 |
|
| 54 |
|
| 55 |
> not type 'fd'. |
| 56 |
|
| 57 |
I did use fd on the partition type. |
| 58 |
Originally, I use ext4 on the boot partition. |
| 59 |
Later I change it to ext2 but neither would work. |
| 60 |
I now assume the borked install was not due to using |
| 61 |
ext4 on boot partition, but grub-kernel-mdadm-diskformat issues |
| 62 |
from my research and the errors I saw..... |
| 63 |
|
| 64 |
|
| 65 |
> However, there's a lot of information on how to use mdraid and create |
| 66 |
> native linux software raid partitions. |
| 67 |
|
| 68 |
This is the best(most current)doc I have found. Let me know if |
| 69 |
a better doc to follow exists for gentoo Raid1 installation [1] |
| 70 |
|
| 71 |
|
| 72 |
> native linux raid partitions, they were /dev/md0, /dev/md1, etc. |
| 73 |
|
| 74 |
some of the errors I got were unique to that md125, md126, md127 |
| 75 |
type of errors. [1] talks about a work around for that. |
| 76 |
|
| 77 |
|
| 78 |
> |
| 79 |
> I can't really help more until I know exactly what you are trying to do. |
| 80 |
|
| 81 |
New install (new thread when trouble arises) |
| 82 |
|
| 83 |
Workstation (amd 64 dual 2t Seagate drives) all RAID1 for boot,/,swap. |
| 84 |
|
| 85 |
> Right now (to me, anyway) it looks like you are mixing software raid and |
| 86 |
> BIOS fakeraid, as with native mdadm you generally don't have partitions |
| 87 |
> (/dev/md126p1, /dev/md126p2, etc) with native raid (which is /dev/md0, |
| 88 |
> /dev/md1, etc) as I said above. |
| 89 |
|
| 90 |
I check the bios, no raid activated in Bios.... |
| 91 |
|
| 92 |
[1] http://en.gentoo-wiki.com/wiki/RAID/Software#Setup_RAID |
Archives