Post by tjmotter on Jan 22, 2021 21:58:19 GMT -5
My current theory is that the decision by TI/Onkyo to use a NAND flash as a hard drive is the cause of these types of issues. NAND flash is nice in that it supports large sizes but it sucks in that blocks do wear out. Uboot is supposed to fix this but like any desktop computer, these types of solutions struggle when faced with multiple block failures at the same time. This is why "Server" computers add multiple points of redundancy to protect against multi-bit errors. Since the NAND is acting like a hard drive, it will be writing to the NAND pretty regularly during normal operation. The only solutions I can think of are to either replace the NAND with one that has no bad blocks (it can be challenging to find one) and then copy a working version and load it onto the NAND. The second option is to do what Geduxaz did which is to reinitialize Uboot and let it re-identify all the bad blocks and then manually reload the linux environment.
