OneNAND: Always print error messages

[Adrian Hunter]

ext Kyungmin Park wrote:
> Yes, simple solution is separate read oob from normal and scanning.
> I think is is easy because we can use state variable, FL_SCANNING instead of FL_READING in bbt.

Also there are the issues of a load error or ECC error when scanning for bad blocks:

Is it possible to get an ECC error when scanning a bad block?

If a load error occurs when scanning a bad block, does that mean the dataRAM
has been updated or not?