I got it working!!!
What Joel said was key. I had probably done it wrong the first time (didn't
use the b option in disklabel), and everytime I re-tried it after that, I
wasn't starting from scratch (zero'ing the two raid drives). So I booted
the SeaTools for DOS CD, and zero'ed the two 3TB drives
On Sun, Mar 03, 2013 at 07:54:07PM +0100, Robert wrote:
> On Sun, 3 Mar 2013 12:35:29 -0500
> Kenneth R Westerback wrote:
> > On Sun, Mar 03, 2013 at 11:15:54AM -0600, Brandon Tanner wrote:
> > > Joel,
> > >
> > > Would the fact that my two 3TB drives (ST3000DM001) use 4k sectors be the
> > > rea
On 03/03/13 20:17, Nick Holland wrote:
On 03/03/13 00:34, Joel Sing wrote:
On Sun, 3 Mar 2013, Brandon Tanner wrote:
...
OpenBSD area: 64-5860533168; size: 2.7T; free: 0.0T
#size offset fstype [fsize bsize cpg]
a: 2.7T 64RAID
c:
On 03/03/13 00:34, Joel Sing wrote:
> On Sun, 3 Mar 2013, Brandon Tanner wrote:
...
>> OpenBSD area: 64-5860533168; size: 2.7T; free: 0.0T
>> #size offset fstype [fsize bsize cpg]
>> a: 2.7T 64RAID
>> c: 2.7T0
On Sun, Mar 03, 2013 at 07:54:07PM +0100, Robert wrote:
> On Sun, 3 Mar 2013 12:35:29 -0500
> Kenneth R Westerback wrote:
> > On Sun, Mar 03, 2013 at 11:15:54AM -0600, Brandon Tanner wrote:
> > > Joel,
> > >
> > > Would the fact that my two 3TB drives (ST3000DM001) use 4k sectors be the
> > > re
On Sun, 3 Mar 2013 12:35:29 -0500
Kenneth R Westerback wrote:
> On Sun, Mar 03, 2013 at 11:15:54AM -0600, Brandon Tanner wrote:
> > Joel,
> >
> > Would the fact that my two 3TB drives (ST3000DM001) use 4k sectors be the
> > reason I wasn't getting it working then?
>
> Both of the drives in the d
On Sun, Mar 03, 2013 at 11:15:54AM -0600, Brandon Tanner wrote:
> Joel,
>
> Would the fact that my two 3TB drives (ST3000DM001) use 4k sectors be the
> reason I wasn't getting it working then?
Both of the drives in the dmesg you posted report 512-byte sectors.
Ken
>
> I will try to zero t
Joel,
Would the fact that my two 3TB drives (ST3000DM001) use 4k sectors be the
reason I wasn't getting it working then?
I will try to zero the drives and start from scratch again, and see if that
works too. I had a feeling that deleting the disklabels with 'z' option
wasn't actually getting thin
On Sun, 3 Mar 2013, Brandon Tanner wrote:
> By the way, does softraid on amd64 support 4096 bytes per sector?
No. There is a large amount of work required to fix this since everything in
softraid was originally designed around 512-byte blocks. It is somewhere on
my TODO list, however I do not cu
On Sun, 3 Mar 2013, Brandon Tanner wrote:
> Anyone else having trouble getting bioctl to see more than 2TB when
> creating softraid0?
>
> I've got 2 x 3TB drives, BIOS sees them fine.
>
> dmesg on bootup:
>
> sd1 at scsibus0 targ 3 lun 0: SCSI3 0/direct
> fixed naa.5000c5005e0bcda5
> sd1: 2861588M
On Sat, Mar 02, 2013 at 07:25:18PM -0600, Brandon Tanner wrote:
> By the way, does softraid on amd64 support 4096 bytes per sector?
I don't think so, but I haven't refreshed my memory of that recently.
Ken
>
>
> On Sat, Mar 2, 2013 at 5:05 PM, Kenneth R Westerback > wrote:
>
> > On Sat,
On Sat, Mar 02, 2013 at 07:25:18PM -0600, Brandon Tanner wrote:
> By the way, does softraid on amd64 support 4096 bytes per sector?
No matter what the architecture is softraid to date does not support
devices with anything other than 512 bytes/sector.
--
This message has been scanned for viruses
By the way, does softraid on amd64 support 4096 bytes per sector?
On Sat, Mar 2, 2013 at 5:05 PM, Kenneth R Westerback wrote:
> On Sat, Mar 02, 2013 at 01:18:09PM -0600, Brandon Tanner wrote:
> > Anyone else having trouble getting bioctl to see more than 2TB when
> > creating softraid0?
> >
> >
On Sat, Mar 02, 2013 at 01:18:09PM -0600, Brandon Tanner wrote:
> Anyone else having trouble getting bioctl to see more than 2TB when
> creating softraid0?
>
> I've got 2 x 3TB drives, BIOS sees them fine.
>
> dmesg on bootup:
>
> sd1 at scsibus0 targ 3 lun 0: SCSI3 0/direct
> fixed naa.5000c50
14 matches
Mail list logo
