I've noticed that if I use a persistent image file and for some reason it gets corrupted (powering off abnormally) that I'll get a bunch of filesystem errors in dmesg. I can fix it by booting with the "noimage" cheat code, like "knoppix64 2 noimage" and then run "fsck.ext2 /mnt-system/KNOPPIX/knoppix-data.img" and then "sudo reboot".
It'd be really nice if there were an automatic check of the ext2 image when knoppix boots. It would also let you know if errors have crept into your filesystem since knoppix still works but you see weird messages like "unable to write /etc/fstab".
1U Supermicro Server 10 Bay 2x Intel Xeon 3.3Ghz 8C 128GB RAM 480GB SSD 2x 10GBE
$273.00
HP ProLiant MicroServer Gen8 G8 G2020T 8GB RAM 4x 1TB HDD 4x 3.5" 712318-421
$269.99
1U BareMetal pfsense opnsense Router Firewall DNS Server 6x 10GB Ethernet Ports
$149.00
HP ProLiant MicroServer Gen8 Desktop Computer Intel Core i3-3240 8GB Ram
$224.99
Supermicro Server 505-2 Intel 2.4GHz 16GB SYS-5018A-FTN4 - pfSense Compatible
$220.48
DATTO-1000 Mini PC Micro Server 8GB RAM
$67.48
HPE ProLiant MicroServer Gen10 Plus v2 Ultra Micro Tower Server - 1 x Intel Xeon
$846.48
$100.00
$299.00
ReachEngine Supermicro 119-7 X9DRW-7/iTPF 2X E5-2660v2 132GB DDR3 NO HDD/OS #73
$136.00