On 04.12.2014 02:06, Michael Schmiedgen wrote:> On 12/04/2014 01:47, Steven Hartland wrote: >> Unfortunately error 5 isn't very helpful as that's just EIO :( >> >> When booted from the old kernel try moving out the cache file e.g. >> mv /boot/zfs/zpool.cache /boot/zfs/zpool.cache.old >> >> If for some reason your cache file and your disks are out of sync that >> might help.I created a new cache file. It is slightly larger in size. But no luck either. I am running out of ideas. :( As I said I had a similar 'mount error 5' problem at home some weeks ago with CURRENT and custom kernel: https://lists.freebsd.org/pipermail/freebsd-current/2014-October/052900.html Solution was there to not remove the virtual machine stuff on bottom of the kernel config. Very strange. Also the commit r271963 (callout convert) that first triggered the problem seems to be unrelated. Strange. And some months ago I had a 'mount error 5' problem if loading nvidia driver in loader.conf, also on my desktop machine at home. I found similar 'error 5' problems on the mailing list, but no solution at all. One thing I can try is to 4K align the start of the boot partition, but at the moment this is a bit risky, I have no physical access to the machine. Please tell if I should provide some more information. Thanks, Michael
On 04/12/2014 11:26, Michael Schmiedgen wrote:> On 04.12.2014 02:06, Michael Schmiedgen wrote: >> On 12/04/2014 01:47, Steven Hartland wrote: >>> Unfortunately error 5 isn't very helpful as that's just EIO :( >>> >>> When booted from the old kernel try moving out the cache file e.g. >>> mv /boot/zfs/zpool.cache /boot/zfs/zpool.cache.old >>> >>> If for some reason your cache file and your disks are out of sync that >>> might help. > > I created a new cache file. It is slightly larger in size. But > no luck either. I am running out of ideas. :( > > As I said I had a similar 'mount error 5' problem at home some weeks > ago with CURRENT and custom kernel: > https://lists.freebsd.org/pipermail/freebsd-current/2014-October/052900.html > > > Solution was there to not remove the virtual machine stuff on > bottom of the kernel config. Very strange. Also the commit r271963 > (callout convert) that first triggered the problem seems to be > unrelated. Strange. > > And some months ago I had a 'mount error 5' problem if loading > nvidia driver in loader.conf, also on my desktop machine at home. > > I found similar 'error 5' problems on the mailing list, but no solution > at all. > > One thing I can try is to 4K align the start of the boot partition, but > at the moment this is a bit risky, I have no physical access to the > machine. > > Please tell if I should provide some more information.Did you try converting from tank from legacy to standard mount point?