08-15-2017 02:15 AM
HI,
We are facing intermittent issue with cRIO 9038 / cRIO 3039 that it fails to boot in NI Linux Real-Time OS.
We observe this behavior when there is loss of communication between chassis & host application or it was shutdown through power button or kept in power off state for 1-2 days. When we power up / power reset the chassis it reboots 5 times then it prompt to reboot & select proper boot device(check by connecting display). We can't access it from MAX. After which we keep power off for about 30-45 min & power up again then it boots in safe mode & it is accessible through MAX.
Does anyone have come across similar problem with cRIO 9038 / cRIO 9039 chassis & found a solution resolve this behavior.
08-15-2017 03:10 PM
Without more information, this sounds to me as if it's a hardware issue. Now, as for going about gathering that additional information, the best and easiest place to start is to enable the serial console and to connect to it from a second computer that is logging the console.
What you can check quickly would be the Error Logs from MAX. Start MAX, right-click on your controller, select "View Error Log", and see if any of the entries in the UI have kernel error logs associated with them.