I did a scrub, it finished within 30 seconds. But the error was that it could not find the boot device it was looking for. I’ve seen this before: If you create a boot device in slot 0 (gets named da0) then move that drive to a different slot, FreeBSD will fail in the same manner. Joe McGuckin ViaNet Communications joe_at_via.net 650-207-0372 cell 650-213-1302 office 650-969-2124 fax > On Feb 1, 2021, at 4:34 PM, Tim Rice <tim_at_xinuos.com> wrote: > > > > On 2/1/21 3:56 PM, joe mcguckin wrote: >> I tried this but it’s not quite working. >> >> LSI controller flashed with IT firmware. >> >> 2) 1T SSD drives >> >> During the install process, I select to create a mirrored ZFS root. It appears to be created >> and there is a zroot dataset. zpool status shows everythings ok. >> >> Now it gets interesting: >> >> I pull one drive after poweron but before FreeBSD starts - everything boots ok, zpool status reports one drive missing and suggests that I replace the missing drive and do a “zpool online” >> I do so and zpool reports everything’s ok. >> >> Now lets reboot and just after Bios power on, pull drive 2. FreeBSD boots until it wants to mount the root partition, can’t find it, dumps me into a menual drive selection prompt. >> >> Hmm, I thought the point of a mirror was that *either* drive could fail. >> >> What am I doing wrong? > You did wait for the resilver to complete after bringing the 1st drive > back online > before the 2nd test, right? > >> >> Thanks, >> >> Joe >> >> >> Joe McGuckin >> ViaNet Communications >> >> joe_at_via.net >> 650-207-0372 cell >> 650-213-1302 office >> 650-969-2124 fax >> > -- > > Tim Rice > tim.rice_at_xinuos.com > > > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"Received on Mon Feb 01 2021 - 23:50:05 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:27 UTC