Real-Time Measurement and Control

cancel
Showing results for 
Search instead for 
Did you mean: 

cRIO goes to safe mode after modifying grubenv

Solved!
Go to solution

Hi all,

 

I modified /boot/grub/grubenv, changed hostname=xxx to FQDN (e.g. instead of crio1 to crio1.example.com). cRIO boots fine for the first reboot, but for the second briefly enters run mode, just to reboot and it starts in safe mode.

 

I see log files in safe mode in /mnt/userfs/var/log (/mnt/userfs seems to be mounted on the big runtime partition). I don't see a reason why cRIO started in safe mode. cRIO/LabView 18.5 if that matters.

 

How can I debug that? And how I can legally specify FQDN, so hostname will show it instead just local name?

 

Thanks

0 Kudos
Message 1 of 2
(166 Views)
Solution
Accepted by topic author lsstpkubanek

The problem was related to removal of SWS - see https://forums.ni.com/t5/NI-Linux-Real-Time-Discussions/System-Deployment-and-Image-Persistence/td-p.... [STARTUP] ValidateStartup=False in ni-rt.ini fixed the cRIOs.

0 Kudos
Message 2 of 2
(139 Views)