Date: Wed, 03 Aug 2016 12:17:36 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 209096] zfsroot bricked on 10.3-RELEASE Message-ID: <bug-209096-3630-vMBB0dP765@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-209096-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-209096-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209096 --- Comment #27 from Andriy Gapon <avg@FreeBSD.org> --- (In reply to Daniel Ylitalo from comment #26) Based on the latest information that you have provided and the history of y= our problem I think that the problem is caused by the BIOS or other firmware components in your system. So, the next step would be to check if there are newer versions of BIOS and firmware for the disk controller and see if upgrading fixes the issue. If that does not help, or just as an alternative solution, you can break up your freebsd-zfs partition in two such that the first one does not cross 2 = TiB boundary (from the start of the disk). Then you can create a boot / root p= ool on top of that partition. You were prepared to go back to UFS, so this cou= ld allow you to keep using ZFS, but at the cost of moving data. BTW, if you go with this solution and you get a bootable system, then I sti= ll would like to see output of lsdev -v from the loader prompt (which you get = by selecting "escape to propmpt" option from the loader menu). --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-209096-3630-vMBB0dP765>