Hi! Michael Biebl <bi...@debian.org> writes: > Am 03.04.2015 um 23:00 schrieb Christoph Egger: >> Christoph Egger <christ...@christoph-egger.org> writes: >> >>> Michael Biebl <bi...@debian.org> writes: >>>> I assume the f2fs-tools package is installed? >>>> What output (and return code) do you get, if you run >>>> fsck.f2fs /dev/disk/by-uuid/691d5901-2f6b-4d33-abbb-131376511c53 >>>> from a rescue media? >>> >>> # fsck.f2fs /dev/disk/by-uuid/691d5901-2f6b-4d33-abbb-131376511c53 >>> Info: sector size = 512 >>> Info: total sectors = 62129119 (in 512bytes) >>> [ASSERT] (fsck_chk_dentry_blk: 623) >>> le32_to_cpu(de_blk->dentry[i].hash_code) == hash_code >>> # echo $? >>> 255 > > > Could you try replacing fsck.f2fs with a symlink to /bin/true? > > It's still unclear to me, if that is the reason for the reboot or some > other component (like a watchdog) triggers the reboot.
FWIW I've successfully booted with linux 4.0.0-1-amd64 without additional trouble. Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
