Missing files on CRIO (that where certainly deployed before)

[JeffreyH]

Hi,

Here's the case:

Last year around may we delivered a batch of devices based on CRIO 9075's to a customer. These all had the exact same image and the device's functionality were fully tested by us and tested again by the customer after reception. Now, a lot of these units stay on the shelf for a while before being deployed out in the field.

A couple of months ago I received back one unit which didn't boot the RT-application anymore. At that moment I didn't investigate, but simply applied the same image again that all units have and everything worked as it was supposed to again.

Now, I received another unit which seemed to have that same problem (RT application not starting up). Now, before applying the original image again to recover the unit, I've taken an image from the 'defective' unit and compared that with the original image.

The comparison results are surprising! Apart from the expected differences in the files systems (e.g. logs and config files and such) I see that the following files (that are present in the original image) are missing:

• ni-rt\system\webserver\modules\libsslModule.out
• ni-rt\system\www\Beyond,htm
• ni-rt\system\NiViSys.out
• registry.out

Furthermore, in the root of the filesystem there's a file with a whole lot of zero's in the name. It's a system exception log, but I can't make anything out of it.

Now, the last two missing file (.out files)  seem pretty important to me and probably the reason why the application won't startup anymore.

I was wondering if anyone ran into the same or a similar problem in the past or if it makes any sense to NI SE's on the forums here. Are there situations in which the filesystem of a crio can become corrupt in a similar way?

Any help or information on similar experiences are appreciated.

Thanks, Jeffrey.

[Hossein128]

Hello Jeffrey,

Thanks for your posting here but I think that the best way is to scalate it to our support in VS. Here we juct can test that issue and maybe conform that. Is that possible for you to contact them?

Hope to hear it from you and post the answer here too.

Best regards,

Hossien

[JeffreyH]

Hi Hossein,

Thanks for your reply.. I would, but I'm not sure who to turn to for this case. So I'll probably have to go through the regular channels I guess?

Best regards,

Jeffrey

[Hossein128]

Hi Jeffery,

Yes, If you contact person or go through the  regular channel, then they will handle that. Besides, you can talk with your manager and if that is an issue in every packet, then you can maybe start a CAR (Corrective Action Request) for that. 

Regards,

Hossein

[ThiCop]

Hello Jeffrey,

A colleague of mine asked me to take a look at the issue you're encountering.

Based on your description it does seem that at a certain point something got corrupted.

Can you give me some extra information about the following topics, so that I can make the search for the cause more specific?

- Do you have a MAX Report of such a system?

This will allow me to check if it might be some known/reported bug in a specific software version.

Also this way we can check if it would be possible to locally set up a system similar to yours.

- Which percentage of devices report this issue? Do the other working devices still function according to original design?

- Is it possible to share what was left on the system after the crash with us?
This will also allow us to browse through the system files and search for some useful information.
- Are there any special environmental circumstances that occured in the vicinity of the problematic cRIO's?
I'm thinking about things like power outages, etc.

On other targets I have before seen something like that happening, but in that case someone had tweaked/adjusted parts of the underlying OS (VXWorks).

[JeffreyH]

Hi Thierry,

Thanks.. I have the original image that we program the units with and the read image of the faulty unit. I can make them available to you. I'll PM you about it.

Best regards, Jeffrey

[ThiCop]

Ok thanks!

I personally don't have a 9075 at my side, but I think (must still verify this), that my neighbouring colleagues doe have one.

Do you have a MAX Report or the versioning of the NI software (eg. RIO version, LV version)?