Re: Machine won't boot - softraid metadata version mismatch
Thank you so much Erling! With your help, I was able to comment out my existing volumes with the "ed" editor (thanks for showing me that, what a strange editor), and rescue everything with rsync from my OS drive (mostly /etc and /root), then do a fresh install of 6.3 (with my raid drives unplugged as Stuart Henderson suggested), and my softraid volumes are now back online. I opted to do the fresh install because I already know how to upgrade, and don't have the time for that process. My machine was a 5.0 originally, and I had upgraded it to 5.4 over the years, but when I got married, somehow I lost time for regular upgrades, and instead have only been doing the errata patches. I learned an important lesson when booting with a "Live USB" drive, I never would have thought it would touch my local system, but I guess when I think about it it makes sense. Now the only issue is that my Samba shares are not all working, it seems there is a big difference in Samba 4 from 3, regarding the use of guest accounts. I'll figure it out soon. I really appreciate all the replies though, I probably couldn't have restored my system without everyone's help! Thanks again. On Thu, May 3, 2018 at 12:09 PM, Erling Westenvik < erling.westen...@gmail.com> wrote: > On Thu, May 03, 2018 at 10:51:12AM -0500, Brandon Tanner wrote: > > I haven't posted here in years, and OpenBSD has been rock solid for a > home > > file server. However recently I somehow made the machine un-bootable and > > I'm kicking myself for it now. I've tried to google my heart out to fix > > this issue, but I doubt it is very common based on my searches. > > Don't panic. > > > My machine is OpenBSD 5.4, and has 2 x raid1 softraid with 4 disks, and a > > 5th disc for the OS only. > > > > So I was wanting to try out the latest kernel to see if sysctl hw.sensors > > would report my motherboard fan sensors since 5.4 does not, so I made a > > bootable USB live-stick using 6.3, based on this article ( > > http://astro-gr.org/openbsd-live-usb-stick/) which says to prepare the > > machine in QEMU and then dd it to a usb flash drive. I was able to boot > the > > USB stick fine, and run sysctl, and nope, my fan sensors are not there in > > 6.3 either. > > > > Now, when I removed the stick and booted the old system (5.4), it now > won't > > boot. The complaint is that my softraid volumes have a metadata version > > that is newer than it should be. I guess the live-USB stick actually > > upgraded them somehow. > > Quoting https://www.openbsd.org/faq/upgrade60.html: > > "softraid(4) metadata version changed. The current softraid metadata > version has been incremented as part of implementing support for sector > sizes other than 512 bytes. Since on-disk metadata is automatically > updated every time a softraid volume is mounted, once you mount a > softraid volume on a new kernel (including bsd.rd) that volume will no > longer be recognized by older kernels." > > As I see it, you have two options: > > 1. Upgrade your system to at least 6.0, carefully upgrading version by >version and following the steps for each upgrade guide: > > 5.4 -> 5.5 > 5.5 -> 5.6 > 5.6 -> 5.7 > 5.7 -> 5.8 > 5.8 -> 5.9 > 5.9 -> 6.0 > 6.0 -> 6.1 > 6.1 -> 6.2 > 6.2 -> 6.3 > > 2. Do a fresh install of 6.3. > > I would go for option 1. It takes time but you'll learn a lot during the > process, and in the end it may take you just as long to fine tune a > fresh install. > > > The error is basically: > > softraid0: cannot read metadata version 6 on sd1a, expected version 5 or > > earlier > > > > Full Pictures of it are here: > > https://imgur.com/a/jYhVwra > > Which tells us that your OS disk is probably just fine. If you comment > out the raid volumes from /etc/fstab, you won't get any complaints, > right? > > > It looks like this person has a similar experience: > > http://openbsd-archive.7691.n7.nabble.com/softraid-not- > bootable-in-5-4-after-visiting-5-5-td253121.html#a253330 > > > > At this point I'm not sure what to do, and I'm afraid to guess at options > > for fear of losing my data. My gut feeling is that I can probably fix > this > > or put a new O/S drive in and install 6.3 on it fresh, and somehow get my > > softraid volumes back up on it. But I wanted to run that theory by you > all > > first. > > > > Thanks, > > Brandon > > Good luck. > > Regards, > > Erling >
Machine won't boot - softraid metadata version mismatch
I haven't posted here in years, and OpenBSD has been rock solid for a home file server. However recently I somehow made the machine un-bootable and I'm kicking myself for it now. I've tried to google my heart out to fix this issue, but I doubt it is very common based on my searches. My machine is OpenBSD 5.4, and has 2 x raid1 softraid with 4 disks, and a 5th disc for the OS only. So I was wanting to try out the latest kernel to see if sysctl hw.sensors would report my motherboard fan sensors since 5.4 does not, so I made a bootable USB live-stick using 6.3, based on this article ( http://astro-gr.org/openbsd-live-usb-stick/) which says to prepare the machine in QEMU and then dd it to a usb flash drive. I was able to boot the USB stick fine, and run sysctl, and nope, my fan sensors are not there in 6.3 either. Now, when I removed the stick and booted the old system (5.4), it now won't boot. The complaint is that my softraid volumes have a metadata version that is newer than it should be. I guess the live-USB stick actually upgraded them somehow. The error is basically: softraid0: cannot read metadata version 6 on sd1a, expected version 5 or earlier Full Pictures of it are here: https://imgur.com/a/jYhVwra It looks like this person has a similar experience: http://openbsd-archive.7691.n7.nabble.com/softraid-not-bootable-in-5-4-after-visiting-5-5-td253121.html#a253330 At this point I'm not sure what to do, and I'm afraid to guess at options for fear of losing my data. My gut feeling is that I can probably fix this or put a new O/S drive in and install 6.3 on it fresh, and somehow get my softraid volumes back up on it. But I wanted to run that theory by you all first. Thanks, Brandon
Re: softeaid rebuild very slow
You can always do a super-rebuild. Simply, backup the contents of your drive to another computer or external drive. Then start from scratch with your softraid 1 array, which will just be re-created, and take < ~1 min. Then copy the data back. Given this kind of setup, you can probably be back up and running in a matter of hours rather than a matter of days. On Sun, Apr 13, 2014 at 7:32 AM, Joel Sing wrote: > On Sun, 13 Apr 2014, John Cox wrote: > > Hi > > > > I'm running OpenBSD 5.4 (dmesg below) with softraid in mirror mode. > > One of the drives failed so I replaced it - the first time that RAID > > has actually saved my data as opposed to simply making my life harder! > > Thank you softraid. > > > > They are 3T drives and it looks like the rebuild is going to take ~5 > > days to do. Is this expected? Is there any config parameter that I > > should have set up to improve performance? 5 days = ~7MBytes / sec > > and I know the drives can run a lot faster than that. > > The current code is designed to be robust rather than fast - it does a read > from one of the online chunks (in this case you presumably only have one of > those) and then does a write to all chunks (including both the online ones > and the rebuilding one). In order to speed things up you want to read from > one online chunk and only write to the chunk that needs rebuilding - the > problem with this is that you need to prevent changes to the blocks that > you > are rebuilding until that write completes. Unfortunately that means some > more > restructing and additional code, plus a whole bunch of testing... > > > Can I reboot the system during the rebuild or if I do will it start at > > the beginning again? I could try it but I'm now about 3 days in and > > don't wish to waste it. > > The rebuild progress is stored in the softraid metadata - if you reboot (or > even if the power goes out) it should pick up where it left off and > complete > the rebuild. > > > #dmesg > > OpenBSD 5.4 (GENERIC.MP) #41: Tue Jul 30 15:30:02 MDT 2013 > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > real mem = 16973672448 (16187MB) > > avail mem = 16514109440 (15749MB) > > mainbus0 at root > > bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xec420 (81 entries) > > bios0: vendor Intel Corp. version "MKQ7710H.86A.0065.2014.0318.1044" > > date 03/18/2014 > > bios0: Intel Corporation DQ77MK > > acpi0 at bios0: rev 2 > > acpi0: sleep states S0 S3 S4 S5 > > acpi0: tables DSDT FACP APIC FPDT TCPA MCFG HPET SSDT SSDT SSDT DMAR > > ASF! > > acpi0: wakeup devices PS2K(S3) PS2M(S3) UAR1(S3) P0P1(S4) USB1(S3) > > USB2(S3) USB3(S3) USB4(S3) USB5(S3) USB6(S3) USB7(S3) PXSX(S4) > > RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) [...] > > acpitimer0 at acpi0: 3579545 Hz, 24 bits > > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > > cpu0 at mainbus0: apid 0 (boot processor) > > cpu0: Intel(R) Core(TM) i5-3470T CPU @ 2.90GHz, 2893.85 MHz > > cpu0: > > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFL > > >USH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL, > > >VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLI > >NE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS > > cpu0: 256KB 64b/line 8-way L2 cache > > cpu0: smt 0, core 0, package 0 > > cpu0: apic clock running at 99MHz > > cpu1 at mainbus0: apid 2 (application processor) > > cpu1: Intel(R) Core(TM) i5-3470T CPU @ 2.90GHz, 2893.43 MHz > > cpu1: > > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFL > > >USH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL, > > >VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLI > >NE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS > > cpu1: 256KB 64b/line 8-way L2 cache > > cpu1: smt 0, core 1, package 0 > > cpu2 at mainbus0: apid 1 (application processor) > > cpu2: Intel(R) Core(TM) i5-3470T CPU @ 2.90GHz, 2893.43 MHz > > cpu2: > > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFL > > >USH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL, > > >VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLI > >NE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS > > cpu2: 256KB 64b/line 8-way L2 cache > > cpu2: smt 1, core 0, package 0 > > cpu3 at mainbus0: apid 3 (application processor) > > cpu3: Intel(R) Core(TM) i5-3470T CPU @ 2.90GHz, 2893.43 MHz > > cpu3: > > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFL > > >USH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL, > > >VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLI > >NE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS > > cpu3: 256KB 64b/line 8-way L2 cache > > cpu3: smt 1, core 1, package 0 > > ioapic0 at mainbus0: apid 2 pa 0xfec0, versi
Re: [OT] OpenBSD "Network Specialist" wanted in Kilgore, Texas
Ha, I work in Kilgore, small world. On Tue, Oct 1, 2013 at 12:55 PM, James Shupe wrote: > I know this is off topic, but I'm looking to help fill my old position > after moving away from East Texas. > > The company is located in Kilgore, Texas and runs a WAN based heavily on > OpenBSD (over a hundred OpenBSD boxes in router/firewall/VPN roles) and > Cisco/ Netgear Prosafe switches. They are looking for somebody who is > experienced with OpenBSD and capable of designing, implementing, and > maintaining OpenBSD infrastructure as well as supporting FreeBSD, Linux, > and Windows servers. The company is stable, has been around for several > decades, and has a few hundred full time employees. > > A few highlights of what you will need to know: > - i386/amd64 hardware (Alix, Soekris, Supermicro, HP, Dell) > - OpenBSD/ FreeBSD/ CentOS/ VMware ESXi > - BGP/ OSPF/ EIGRP > - LACP/ VLANs, subnetting, etc > - PF/ iptables/ Cisco ACLs > - IPv6 (the deployment is dual stack, so this is a huge plus) > - ZFS > - Perl > > There is an existing employee who is still there and has a good > understanding of the existing infrastructure, so you wouldn't be working > alone. Not everything is necessarily expected right away, but the ability > and willingness to learn is. > > Salary is DOE and ranges from 52-72K for this specific position, but any > applicants would unfortunately be expected to cover their own relocation > costs because of the way funding is distributed. This is an on site > position and telecommuting is off the table. Email me privately for more > information. > > -- > James Shupe, HermeTek > developer/ engineer > BSD/ Linux support & hosting > jsh...@hermetek.com | www.hermetek.com > Office 8662351288 | Mobile 9035223425
Re: ffs2
Sweet, didn't know about dumpfs, exactly what I was looking for. Thanks also, for the confirmation! On Sun, Mar 17, 2013 at 7:07 PM, Philip Guenther wrote: > On Sun, Mar 17, 2013 at 4:13 PM, Brandon Tanner > wrote: > > How do I know if I'm using ffs2 on a partition. > > sudo dumpfs /storage | head -1 > > > ... > > However, I think I read that > 2TB volumes automatically use FFS2 when > > using newfs, yet mount only shows ffs (is it transparent or something?). > > Yes, it's transparent: they're just different versions of the same > layout, so the same programs handle both. > > > Philip Guenther
ffs2
How do I know if I'm using ffs2 on a partition. My softraid 1 volume is 2.7TB, and mount shows it as: /dev/sd3a on /storage type ffs (local, nodev, nosuid, softdep) However, I think I read that > 2TB volumes automatically use FFS2 when using newfs, yet mount only shows ffs (is it transparent or something?). Thanks. Brandon
Re: Absolute OpenBSD 2nd Edition pre-orders are up.
I got mine ordered today, when do you think it will ship from NoStarch Press? On Sat, Mar 16, 2013 at 3:32 PM, Michael W. Lucas < mwlu...@blackhelicopters.org> wrote: > On Fri, Mar 15, 2013 at 11:59:28PM -0600, Austin Hook wrote: > > > > Pre-orders for the 2nd Edition of Michael Lucas' Absolute OpenBSD are now > > up on the main order website. Expected to arrive about the same time we > > start shipping pre-orders for OpenBSD 5.3. Pre-orders for the latter > will > > show up pretty soon as well. No special early discount, but the > > difference does go to support the project. Or, if you need to pinch > those > > pennies (before they are discontinued), take the early order path > > suggested by Michael's website, rather than through the big online > > monopoly. He gets a bit more that way. > > > > You thought you knew all there is to learn in an introductory book to > > OpenBSD? You might be surprised. A reference when you need it, and > worth > > a skim even just to see how OpenBSD has evolved over the last 10 years, > if > > you have the original volume. > > > > http://www.openbsd.org/books.html#B10 > > > > And follow the links. > > Excellent, Austin! Glad you got them. Linked from the book page. And > thanks for the plug. > > Before anyone asks: I don't really care where you buy it. > > ==ml > > -- > Michael W. Lucas - mwlu...@michaelwlucas.com, Twitter @mwlauthor > http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ > Latest book: Absolute OpenBSD 2/e - http://www.nostarch.com/openbsd2e > coupon code "ILUVMICHAEL" gets you 30% off & helps me.
Re: Absolute OpenBSD 2nd Edition pre-orders are up.
https://www.michaelwlucas.com/nonfiction/absolute-openbsd-2nd-edition On Sat, Mar 16, 2013 at 3:34 AM, James Griffin wrote: > [- Fri 15.Mar'13 at 23:59:28 -0600 Austin Hook :-] > > > Pre-orders for the 2nd Edition of Michael Lucas' Absolute OpenBSD are now > > up on the main order website. Expected to arrive about the same time we > > start shipping pre-orders for OpenBSD 5.3. Pre-orders for the latter > will > > show up pretty soon as well. No special early discount, but the > > difference does go to support the project. Or, if you need to pinch > those > > pennies (before they are discontinued), take the early order path > > suggested by Michael's website, rather than through the big online > > monopoly. He gets a bit more that way. > > > > You thought you knew all there is to learn in an introductory book to > > OpenBSD? You might be surprised. A reference when you need it, and > worth > > a skim even just to see how OpenBSD has evolved over the last 10 years, > if > > you have the original volume. > > > > http://www.openbsd.org/books.html#B10 > > > > And follow the links. > > That link did not work when I tried it just now. How much would this > book cost? Any chance of a student discount ;-) ? I like to buy a copy > but if it's going to be more 20 quid, I wouldn't be able to. > > -- > James Griffin: jmz at kontrol.kode5.net > jmzgriffin at gmail.com > > A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
Re: Softraid 3TB Problems
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 this time, and then re-installed with the March 1, 2013 snapshot of 5.3 (don't think this is what fixed it though), and did the same procedure in my first post, and now it works! When Joel said that, the light just went on in my head, cause I had been wondering how to reverse the procedure and start over, but had only been using the 'z' option in disklabel, and had only dd if=/dev/zero the resulting softraid volume, not the 2 real volumes each time I started over to try again. A warm Thanks to everyone for their input. Also, about the 4k sectors, I think Ken is right, I think Seagate's smartalign technology takes care of it all behind the scenes so to speak, and the OS still sees 512 byte sectors. Might be worth a mention in the FAQ or something that if you don't setup raid1 correctly the first time, to start over, you need to detach the raid using bioctl, clear the disklabels, zero the raid volumes, and reinit them in fdisk? On Sun, Mar 3, 2013 at 3:53 PM, Kenneth R Westerback wrote: > 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 > > > > reason I wasn't getting it working then? > > > > > > Both of the drives in the dmesg you posted report 512-byte sectors. > > > > > > Ken > > > > The Seagate datasheet [1] claims that this drive (ST3000DM001) uses 4k > sectors. > > > > Otherwise can I confirm that a Western Digital WD30EFRX 3TB drive with > 512b sectors works fine with crypto softraid. > > > > kind regards, > > Robert > > > > [1] > http://www.seagate.com/files/staticfiles/docs/pdf/datasheet/disc/barracuda-desktop-hdd-ds-1770-1-1212us.pdf > > > > Many drives use 4K internally but still report to the outside world that > they use 512 byte sectors. Handling the translation/packing/unpacking > themselves. OpenBSD just reports (and trusts) what the drive reports > in response to READ_CAPACITY/READ_CAPACITY_16. > > Ken
Re: Softraid 3TB Problems
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 things back to the way they were when I first started out. Thank you for your input! -Brandon On Sat, Mar 2, 2013 at 11:38 PM, Joel Sing wrote: > 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 currently even have the hardware for > development/testing. > -- > > "Reason is not automatic. Those who deny it cannot be conquered by it. > Do not count on them. Leave them alone." -- Ayn Rand
Re: Softraid 3TB Problems
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? > > > > 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: 2861588MB, 512 bytes/sector, 5860533168 sectors > > sd2 at scsibus0 targ 4 lun 0: SCSI3 > 0/direct > > fixed naa.5000c5005e15ec80 > > sd2: 2861588MB, 512 bytes/sector, 5860533168 sectors > > > > notice the correct # of sectors above. > > > > disklabel -E sd1 > > > > > p T > > OpenBSD area: 64-5860533168; size: 2.7T; free: 0.0T > > #size offset fstype [fsize bsize cpg] > > a: 2.7T 64RAID > > c: 2.7T0 unused > > > > disklabel -E sd2 > > > > > p T > > OpenBSD area: 64-5860533168; size: 2.7T; free: 0.0T > > #size offset fstype [fsize bsize cpg] > > a: 2.7T 64RAID > > c: 2.7T0 unused > > > > # bioctl -c 1 -l /dev/sd1a,/dev/sd2a softraid0 > > softraid0: SR RAID 1 volume attached as sd3 > > > > sd3 at scsibus2 targ 1 lun 0: SCSI2 0/direct > fixed > > sd3: 2097148MB, 512 bytes/sector, 4294961093 sectors > > > > Yet, bioctl only sees it for 4294961093 sectors :( > > Softraid apparently truncates at 32 bits somewhere along the line. > > You might try instrumenting places where ssd_size is set, and where > READ_CAPACITY/READ_CAPACITY_16 are processed. > > A quick scan did not cause a 32 bit truncation to leap out at me. > > Ken > > > > > # bioctl -h sd3 > > Volume Status Size Device > > softraid0 0 Online 2.0T sd3 RAID1 > > 0 Online 2.0T 0:0.0 noencl > > 1 Online 2.0T 0:1.0 noencl > > > > I have been troubleshooting this issue with the help of Scott McEachern > > extensively, and we are both stumped. He suggested I put this on misc to > > see if jsing might know anything. I have an Intel Desktop Motherboard > model > > DP43TF. I can newfs the drives individually and mount them as 2.7TB, it's > > only when trying to make a softraid volume that it doesn't see more than > > 2TB. > > > > I am using the Feb 21, 2013 snapshot of 5.3, and my dmesg is at: > > http://pastebin.com/jqnpSsnC > > > > Anyone else experiencing this? > > <http://search.gmane.org/?author=Scott+McEachern&sort=date>
Re: BSD-friedly companies producing embedded x86 computers
Congatec, although I don't know about BSD-friendly. They are at least, Linux friendly. Might look into it. On Mon, Feb 25, 2013 at 12:09 PM, Voland Levit wrote: > I know about Soekris and Alix. Please tell me if there is anyone else > worthy > of attention. > > Thanks!
Softraid 1 Help
Hello, This is my first time posting to this list. I am wanting to setup a softraid 1 array, with two 3TB drives. Every guide or howto I can find though is about installing onto such an array. My case however, the boot drive is on its own, a 250GB'er. I simply want to create the array with softraid, mount it at /storage, and use it. Does anyone know of any guides that cover this kind of scenario? I also have a few questions about what I read so far. 1. a few guides talk about using the MAKEDEV shell script. Do I still need to use that for my scenario? 2. Also, since my target array will not be a bootable array, do I still need to fdisk -yi the devices? I read in the FAQ that fdisk won't report the sizes correctly, but that I shouldn't worry though, since disklabel with the b option will cover it. 3. My two identical 3TB drives are sd1 and sd2, and bioctl reported that sd3 is created. I ran newfs -O 2 on it, and that seemed to work. I can't figure out how to mount it though. mount /dev/rsd3c /storage says something about block device required. That's about as far as I got. Thanks for any feedback. -Pyrite