On Monday, October 27, 2014 6:46:17 pm Michael Schmiedgen wrote: > On 10/27/2014 22:29, Ryan Stone wrote: > > On Mon, Oct 27, 2014 at 4:21 PM, Michael Schmiedgen <schmied...@gmx.net> wrote: > >> Hi List, > >> > >> my ZFS does not mount. I bifurcated to r271963 that > >> does not work anymore. The commit seems not directly > >> related to ZFS, but is rather a conversion from timeout(9) > >> to callout(9). > >> > >> After booting the kernel it drops to the mount prompt, > >> stating that ZFS cannot be mounted because of 'error 5'. > >> > >> Any hints? Can I provide some more information? > >> > >> Thanks, > >> Michael > > > > The changes to the 3 files there look to be independent, so can you > > narrow this down further by applying the patch to only a single file? > > Of those three only ACPI looks like it could affect ZFS or disks, so > > this will be the patch to try first: > > > > https://svnweb.freebsd.org/base/head/sys/dev/acpica/acpi.c?view=patch&r1=271889&r2=271963&pathrev=271963 > > > > If you can get a verbose boot log from the machine that would be > > helpful, but you'd need a serial console to capture that. > > > > I applied first acpi.c, then atkbd.c and at last kern_cons.c that > triggered the error. > > https://svnweb.freebsd.org/base/head/sys/kern/kern_cons.c?r1=271963&r2=271962&pathrev=271963 > > In previous months I had already the same problem with ZFS if > nvidia driver was loaded via /boot/loader.conf. It triggered > the same error. So I loaded the driver on demand with kldload > after login and everything (X + stuff) worked fine. > > Very strange... > > Does anyone have a clue what is going on here?
So not loading the nvidia driver during boot fixed it? That seems odd indeed. Did you recompile the driver after updating? -- John Baldwin _______________________________________________ firstname.lastname@example.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"