Date: Wed, 22 Feb 2017 12:30:35 -0800 From: Eric Altman <eric@lumaforge.com> Cc: freebsd-fs@freebsd.org Subject: Re: 10.2 zfs-on-root will not boot after an unclean reboot Message-ID: <CAMOrpB0RYM2PScDjro1Z6gUwOb4odL8sC0OFj0Y_iNJKyUANfg@mail.gmail.com> In-Reply-To: <B13D37D1-6C91-4CB3-AC4D-49DFC70E1E60@gmail.com> References: <B13D37D1-6C91-4CB3-AC4D-49DFC70E1E60@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Generally when I see those kinds of boot errors, I check hardware first. Especially after hard shutdowns. Check that BIOS settings (particularly on your HBA) were not affected. Make sure all the drives are showing up. Might need to boot from a Live USB and check the pool's status and/or repair the ZFS cache. Run a scrub if you can import but not boot from it. On Feb 22, 2017 10:53 AM, "Ricky Huang" <rhuang.work@gmail.com> wrote: > Hello all, > > Server got power-cycled by the datacenter (accident) and now it won't > boot. Previous =E2=80=9Cclear" reboots have always been fine. > > It's a ZFS-on-root setup installed via FreeBSD installer and it's now > displaying: > > > FreeBSD/x86 boot > > ZFS: I/O error - blocks larger than 128K are not supported > > ZFS: can't find dataset u > > > > Any suggestions on where I can begin to diagnose this issue? > > Note: I have infrequent access to the server, so please "batch" the > suggestions so I can try them when I make my way into the d.c. > > > Thanks in advance! > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMOrpB0RYM2PScDjro1Z6gUwOb4odL8sC0OFj0Y_iNJKyUANfg>