I realise this is not an error but..

[coreplayer2]

I am constantly explaining to folks that this is not an error per se..  But the messages get a lot of attention which ultimately raises flags and doubt of stability in the whole operation.  So is there any way to hide the caching messages, it's not like we have any control over the issue, a USB thumb stick is what it is..

2x USB thumb drive's connected here

[tinypoodle]

Not clear what you refer to...

[gerald_clark]

Did you try the 'quiet' boot option?

[coreplayer2]

All my systems use the quiet boot code,
"quiet" boot code doesn't suppress the cache messages 

Messages occur if booting from a frugal install on a USB thumb drive, and
when booting to a freshly downloaded CorePlus ISO, 4 cache messages are displayed any time for each USB Thumb Drive attached to the system.

[tinypoodle]

Messages pertaining to attached storage media are generated by the kernel, not specific to core.
See boot parameters in kernel docs for advanced options of finetuning.

Linux defaults - not a bug.

[coreplayer2]

Thanks, like I said in the beginning I know it's not an error (bug) but am  looking for a way to suppress these messages which I haven't found yet..

[tinypoodle]

Main reason I pointed that out is that thread is posted under "TCB Bugs"

[coreplayer2]

Ah ha!  ok well I couldn't find a more appropriate place here sounds as good a place as any to me..

[curaga]

"quiet" sets the log level to 4. Replace with "loglevel=N" where N is the level you want, see kernel-parameters.txt.

[coreplayer2]

Thanks will investigate this option

[roberts]

Try replacing quiet with loglevel=3
It should suppress the spurious messages mentioned.

[coreplayer2]

Thanks roberts & curaga for the advise,  replacing quiet with loglevel=3 does in fact suppress the messages

Thank you

[lverns]

Awesome! I've got to try this solution. I've had to live with those messages for 8 months

[roberts]

Replacing quiet with loglevel=3 for 4.6 release.

[curaga]

Actually, instead of not showing errors (which the user may want to see), I'd prefer to change these two messages to warnings.

Just like in the squashfs code, we disagree with upstream that these messages qualify as errors. But since making this kernel change isn't urgent, let's lower the log level for now and in tc 5 do it the proper way, returning quiet.