Background:
I worked on this last April can gave up on the (livedDVD)
install with too many other things to do, and pissed off at
a lack of usable (current) documentation.
Currently:
Meds have kicked in ( peace and joy ) (yea right).
So, taking a fresh look at the BOTCHED system:
The 2 drives are identical 2TB: Seagate
drives: Model Number: ST32000542AS
I read about the 4K block problem and could have
easily made a formating mistake....(?).
fdisk /dev/sda (not the best tool to use...
Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xab83344a
Device Boot Start End Blocks Id System
/dev/sda1 * 1 33 262144 fd Linux raid autodetect
Partition 1 does not end on cylinder boundary.
/dev/sda2 33 659 5023744 fd Linux raid autodetect
Partition 2 does not end on cylinder boundary.
/dev/sda3 659 243202 1948227672 fd Linux raid autodetect
Partition 3 does not end on cylinder boundary.
But from what I read fdisk is not the best choice
for reading/formating 2T drives, so Here is what
sfdisk says:
Disk /dev/sda: 243201 cylinders, 255 heads, 63 sectors/track
Old situation:
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sda1 * 0+ 32- 33- 262144 fd Linux raid autodetect
start: (c,h,s) expected (0,32,33) found (0,36,33)
end: (c,h,s) expected (32,194,34) found (41,214,48)
/dev/sda2 32+ 658- 626- 5023744 fd Linux raid autodetect
start: (c,h,s) expected (32,194,35) found (41,214,49)
end: (c,h,s) expected (658,48,30) found (842,210,16)
/dev/sda3 658+ 243201- 242544- 1948227672 fd Linux raid autodetect
start: (c,h,s) expected (658,48,31) found (842,210,17)
end: (c,h,s) expected (1023,254,63) found (169,217,56)
But in my attempt to install, I used this geometry:
fdisk -H 224 -S 56 /dev/sda
Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
224 heads, 56 sectors/track, 311465 cylinders
Units = cylinders of 12544 * 512 = 6422528 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xab83344a
Device Boot Start End Blocks Id System
/dev/sda1 * 1 42 262144 fd Linux raid autodetect
Partition 1 does not end on cylinder boundary.
/dev/sda2 42 843 5023744 fd Linux raid autodetect
Partition 2 does not end on cylinder boundary.
/dev/sda3 843 311466 1948227672 fd Linux raid autodetect
Partition 3 does not end on cylinder boundary.
using the livedDVD:
cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md125 : active raid1 md127p1[0]
262080 blocks [2/1] [U_]
md126 : active raid1 md127p2[0]
5023680 blocks [2/1] [U_]
md127 : active raid1 sdb[1] sda[0]
1948227584 blocks [2/2] [UU]
mdadm -E /dev/sda1
/dev/sda1:
Magic : a92b4efc
Version : 0.90.00
UUID : 8939604f:676aa8df:cb201669:f728008a (local to host livecd)
Creation Time : Thu Apr 14 14:10:56 2011
Raid Level : raid1
Used Dev Size : 262080 (255.98 MiB 268.37 MB)
Array Size : 262080 (255.98 MiB 268.37 MB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 125
Update Time : Wed Jul 27 17:25:15 2011
State : clean
Active Devices : 1
Working Devices : 1
Failed Devices : 1
Spare Devices : 0
Checksum : f7f2bc6f - correct
Events : 20
Number Major Minor RaidDevice State
this 0 259 0 0 active sync /dev/md/125_0p1
0 0 259 0 0 active sync /dev/md/125_0p1
1 1 0 0 1 faulty removed
It has been suggested kernel >=2.6.37 will have (better?)
support for 4k sectors disks [1].
SOOOOOOOOOOOOOOO
Should I just start over?
(If so, what docs do I follow?)
Or should I first try to salvage the installation
from last april (chroot and install a newer kernel?
[1] http://forums.funtoo.org/viewtopic.php?pid=869
