After a major firmware update many of our APs started to bootloop. Many of the have varying degrees of the same CRC error. I was able to force them to reset, reload firmware and config and the appear to be stable no, but should I be concerned?

[chris_tran]

After a major firmware update many of our APs started to bootloop. Many of the have varying degrees of the same CRC error. I was able to force them to reset, reload firmware and config and the appear to be stable no, but should I be concerned?

[samantha_lynn]

Thank you for that output, that is a standard startup message, which we would expect to see during a boot up process, sometimes multiple times. If you still have any APs that are bootlooping, I would recommend attempting the TFTP flash with one of our support technicians.

As for the CRC errors, CRC errors are usually related to environmental interference factors. These factors include mainly metal, glass, water, or large amounts of people. All of these factors tend to reflect, refract, or generally damage your signal, leading to more retries, which leads to slower WiFi speeds. To help with CRC errors we would like pictures of a few problem APs with as much of the environment showing around the AP as possible so we can help you rule out any environmental factors that could be damaging your wireless signal. 

[chris_tran]

Well, most have stopped bootlooping after the hard reset. I still see CDC errors during boot. "jffs2: notice: (55) check_node_data: wrong data CRC in data node at 0x0f2ab4d0: read 0x9ef1e32, calculated 0x42955a2d." One AP has two instances of this. Another has about a dozen.

[samantha_lynn]

We'll want to open a support case to see why this is happening. The data we're going to ask for in that case will be: tech data before the HiveOS update, tech data after updating (if possible, obviously if we're in a boot loop we won't be able to get tech data), and if we are seeing a boot loop we'll want to set up a support call with you so we can attempt to TFTP flash the device to get the boot loop to stop and see what the issue was.