configuring raid using gpt, large drives

2020-02-02 Thread MLH
I am still attempting to configure and use two 4T drives in a raid1 configuration and be able to boot from the raid partition. Not much progress and am hoping someone can determine what I am doing wrong. I especially want to thank Emmanuel Dreyfus for spending an inordinate amount of time trying to

Re: configuring raid using gpt, large drives

2020-02-02 Thread Piotr Meyer
On Sun, Feb 02, 2020 at 01:10:33PM -0500, MLH wrote: [...] > $ mount NAME=raid@ZFN15G3N /mnt > WARNING: autoselecting nfs based on : or @ in the device name is deprecated! > WARNING: This behaviour will be removed in a future release > mount_nfs: no : or @ spec > $ mount /dev/raid0a /mnt > mount_f

Re: configuring raid using gpt, large drives

2020-02-02 Thread MLH
Sorry, extreme frustration from working on this for far too long... The dmesg I copied after rebooting was the wrong one as that was after a reboot where NetBSD didn't recognise wd3 which is frustrating as often on reboot, NetBSD doesn't recognise wd3 and I have to reboot several times until it doe

Re: configuring raid using gpt, large drives

2020-02-02 Thread MLH
Piotr Meyer wrote: > On Sun, Feb 02, 2020 at 01:10:33PM -0500, MLH wrote: > [...] > > > $ mount NAME=raid@ZFN15G3N /mnt > > WARNING: autoselecting nfs based on : or @ in the device name is deprecated! > > WARNING: This behaviour will be removed in a future release > > mount_nfs: no : or @ spec > >

Re: configuring raid using gpt, large drives

2020-02-02 Thread MLH
Nathanial Sloss wrote: > Hi, > > gpt add -t raid -l raid@ZFN15G3N wd2 > > Results in: > > Feb 2 11:59:30 tiamat /netbsd: [ 41138.3587115] autoconfiguration error: > > wd2: error 22 > > adding entry 2 (9a30ad4e-8b61-492c-ab99-59eba0272f05), > > type 49f48daa-b10e-11dc-b99b-0019d1879648 > > > I

Re: configuring raid using gpt, large drives

2020-02-02 Thread Simon Burge
MLH wrote: > Thanks. The -s 5m is for the swap partition just in front of the > raid partition. [ ... ] Somewhat unrelated to your other issues, but why are you swapping direct to disk but using RAID for everything else? If you get disk error on one of your swap partitions that might lead to a

Re: configuring raid using gpt, large drives

2020-02-02 Thread Emmanuel Dreyfus
Piotr Meyer wrote: > It is rather long shoot and I'm not pretty sure about that, but at first > I suggest to remove '@' sign from GPT partition names and wedge names. > It leads to conflict with NFS scheme at least in mentioned case and I > affraid, that there are other places to fail. I use tha

Re: configuring raid using gpt, large drives

2020-02-02 Thread MLH
Simon Burge wrote: > MLH wrote: > > > Thanks. The -s 5m is for the swap partition just in front of the > > raid partition. [ ... ] > > Somewhat unrelated to your other issues, but why are you swapping direct > to disk but using RAID for everything else? If you get disk error on > one of your sw

Re: configuring raid using gpt, large drives

2020-02-14 Thread MLH
Continuation of a long story... Emmanuel has expended an immense amount of time trying to help me solve this problem. I finally have accepted that while my motherboard purports to support EFI booting of large drives, the bios doesn't appear to support it in any way we can determine. Nor does it

Re: configuring raid using gpt, large drives

2020-02-14 Thread Michael van Elst
m...@goathill.org (MLH) writes: >I had jsut (apparently) got that working, where the bootloader was >comoing up from either of my wd2 or wd3 boot wedges and askign for >the raid0 but then this happened, which is preventing the kernel >from seeing either wd2 or wd3: >[ 2.752630] autoconfigurat

Re: configuring raid using gpt, large drives

2020-02-14 Thread MLH
Michael van Elst wrote: > MLH wrote: > > I had jsut (apparently) got that working, where the bootloader was > > comoing up from either of my wd2 or wd3 boot wedges and askign for > > the raid0 but then this happened, which is preventing the kernel > > from seeing either wd2 or wd3: > > > > [ 2