Michael Niewöhner

I'm experiencing the same issues. These errors appeared out of nothing. I highly doubt that all 4 disks die at exact the same time. ~~~ [ 122.404043] ata6.00: exception Emask...

uhm. interesting. https://github.com/openzfs/zfs/issues/4873#issuecomment-269074579 seems to work for me, too. but WHY?!

Finally, this turned out to be a system firmware issue. See https://review.coreboot.org/c/coreboot/+/40877 You can try this: ~~~sh echo maximum_performance | sudo tee /sys/class/scsi_host/host*/link_power_management_policy ~~~ If that solves the problem, it's...

@BrainSlayer isn't that the same problem we had with #9034? o.O

> which again triggers the endless loop in memory allocation procedure i love so much which should be fixed by our patch; so maybe we even fix a very common,...

Awesome :-) I had a short look at the code secretsdump.py is using, it's pretty simple (just one additional flag to check IIRC)

doesn't seem to work unfortunately. the output stays the same, no history. at least I measured no slowdown at all with that massive ntds from #2

oh. my fault. guess I will never get used to go's strange behaviours... Tested with a ntds from Win 2016, which leads to "panic: Not yet implemented"

Two problems on the latest commit: - the decrypted hash is wrong - only the first history entry is getting printed

Looks better now but the history hashes are still wrong