Hard-locking the machine a minute after boot when /etc/fstab has certain valid but unusual things in it kind of sounds to me like a kernel bug between cgroups and clever VFS operations. I suppose the other possibility is that systemd segfaults, causing the kernel to panic (since it doesn't like killing init). But the most likely thing is probably that systemd set up the filesystem as you specified and used the features the kernel advertised (that nothing used before on your system), and the kernel broke.