Date: Mon, 23 Oct 2017 07:50:05 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 221075] regression: 11.1 is unable to mount ZFS / on boot Message-ID: <bug-221075-3630-qPmdtbGJdc@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-221075-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-221075-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=3D221075 Markus Wild <freebsd-bugs@virtualtec.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd-bugs@virtualtec.ch --- Comment #15 from Markus Wild <freebsd-bugs@virtualtec.ch> --- Just wanted to add a "me too" mention for this bug. Short summary: - Supermicro X10DRI-T motherboard, using UEFI boot, 128G RAM, 2 CPUs - 2 Intel DC P3700 NVME cards, to be used as mirrored zfs root and mirrored= log devices for a data pool - FreeBSD-11.1 release installs fine off memstick, and the built system boo= ts correctly, but this system uses the entire disks (so I need to shrink the system to make room for log partitions) - so I then rebooted into usb live system, and did a gpart backup of the nv= me drives (see later). zfs snapshot -r, zfs send -R > backup, gpart delete last index and recreate with shorter size = on both drives, recreate zroot pool with correct ashift, restore with zfs receive from backup, set bootfs, reboot - the rebooting system bootloader finds the zroot pool correctly, and proce= eds to load the kernel. However, when it's supposed to mount the root filesystem, I get: Trying to mount root from zfs:zroot/ROOT/default []... Mounting from zfs:zroot/ROOT/default failed with error 6. - when I list the available boot devices, all partitions of the nvme disks = are listed - I can import this pool without any issues with the usb live system, there= are no errors on import. - I then redid the whole exercise, but restored the previously backed up partition tables (full size zfs partition), did exactly the same steps as described above to restore the previous zfs filesystem, rebooted, and the system started up normally. I then tried to recreate the pool using nvd0p3/nvd1p3 instead of gpt-labels, but this didn't help. But, when I built a custom kernel as suggested here: include GENERIC ident CUSTOM nodevice mmc nodevice mmcsd nodevice sdhci this kernel booted fine! So, whatever went into the system for MMC support = is messing with correct mounting of zfs root pools... --=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-221075-3630-qPmdtbGJdc>