[Bug 209096] zfsroot bricked on 10.3-RELEASE
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Wed Apr 27 12:41:18 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209096
Bug ID: 209096
Summary: zfsroot bricked on 10.3-RELEASE
Product: Base System
Version: 10.3-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: misc
Assignee: freebsd-bugs at FreeBSD.org
Reporter: daniel at blodan.se
Hi,
I just tried going to 10.3-RELEASE from 10.2-RELEASE-p14
I'm running a zfsroot system in a single disk installed with default options
from the 10.2-RELEASE installer.
When i ran freebsd-update -r '10.3-RELEASE' and then rebooted once the kernel
stuff was installed I was displayed with this error:
ZFS: i/o error all block copies unavailable
I was then dropped to the boot loader
boot:
If entering ? there I could see the boot folder together with all the other
regular folders
Only way I was able to recover from this was booting with the 10.2-RELEASE
livecd and issuing the following;
zpool import -R /mnt -f zroot
mv /mnt/boot /mnt/boot.bricked
cp -Rp /boot /mnt/boot
cp /mnt/boot.bricked/loader.conf /mnt/boot/loader.conf
reboot
Trying the above commands with the 10.3-RELEASE livecd ended up with the same
result as with upgrading with freebsd (dropped to boot:)
My ZFS root looks like this:
===================================================================
[root at content-01-group-01-stockholm-se ~]# gpart show
=> 34 11710627773 mfid0 GPT (5.5T)
34 6 - free - (3.0K)
40 1024 1 freebsd-boot (512K)
1064 984 - free - (492K)
2048 8388608 2 freebsd-swap (4.0G)
8390656 11702235136 3 freebsd-zfs (5.4T)
11710625792 2015 - free - (1.0M)
===================================================================
[root at content-01-group-01-stockholm-se ~]# zpool status
pool: zroot
state: ONLINE
scan: scrub repaired 0 in 4h29m with 0 errors on Tue Apr 26 23:44:35 2016
config:
NAME STATE READ WRITE CKSUM
zroot ONLINE 0 0 0
mfid0p3 ONLINE 0 0 0
errors: No known data errors
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list