I have same trouble too. My work around was working on other systemthat: cp /path/to/root/sbin/btrfsck /path/to/root/sbin/fsck.btrfs
But, it hasn't been a good hack. As you know, btrfsck's synopsis is very simple: btrfsck device But fsck.hoge did -a option. So, while boot, an error saying "-a device is not available" or so. And btrfsck does not do anything but just read. Judging from above, this way is possibly to be a good hack, ln -s /bin/true /sbin/btrfsck and/or Mail to root when a system dist-upgraded to recommend that: In fstab, the last column of / would be 0 Anyway, it is not friendly way when dist-upgrade, turned off, and reboot, then there is no rule to fsck.btrfs. Thanks.
