[Help] F4-424 not possible to connect anymore

[TMzethar]

System configuration generally includes almost all settings except for users/user groups/shared folders on the control panel.

[HeliaWu]

Resetting the system configuration from the control panel, it mentions obviously it will erase all system configurations. My question what a good list of screens that I should capture so I can restore the values I need. Yes I know, backup data.......

And does it matter if I'm running TOS 7 version 375?

Resetting the system configuration will clear all your personalized settings but does not affect any data on the disks. It is recommended that you back up your current configuration before reinstalling the system. After the installation is complete, you can restore the backup. If you are concerned that some settings may not be restored properly, you can also take screenshots for reference.

[rfbjr]

That's my point, take screen shots of what? My wallpaper and font size? Big deal.
Sounds like since no one is giving specifics I will just take screen shots of everything.
NIC, Power schedule, UPS settings, scheduled jobs, etc.
Good to have anyway

[rfbjr]

Even better last night I did a graceful shutdown of my F4-424 Pro. Left it off until early this morning, figure off for about 7hrs ish.
When I powered it back on and watching the console I saw just a few correctable errors. Point is the system came up and the journald process was taking less than 1%. Last few days the journald was 95% and the CPU temp was 70C. Reason is the syslog was constantly logging correctable PCIE errors. Sometimes I could logon other times it would fail.

[TMzethar]

Is the issue you mentioned here related to this update? (Did it appear after the update?)
viewtopic.php?t=9626

[rfbjr]

I believe I noticed it with the last release, forget the number. I only noticed it because I happen to display the processes by CPU %. I think just a few days before 375 was released. This unit of mine I have it shutdown at 11pm daily and power it back up at 5am daily. So for all I know that was masking the issue?

[TMjack]

Hello! Please go to the TOS control panel and navigate to "General Settings" > "System" > "Configuration". Back up the system configuration and save the exported file to your NAS or computer. Afterwards, you can proceed to the "Access Rights" module, export the user configuration, and save it to your NAS or computer as well. There is no need to take screenshots of each configuration for saving.

[TMjack]

Journald is a service process responsible for log collection and management. You can try leaving the NAS running without shutting it down for an extended period, and then observe whether this process continues to occupy CPU resources.

[rfbjr]

Hello! Please go to the TOS control panel and navigate to "General Settings" > "System" > "Configuration". Back up the system configuration and save the exported file to your NAS or computer. Afterwards, you can proceed to the "Access Rights" module, export the user configuration, and save it to your NAS or computer as well. There is no need to take screenshots of each configuration for saving.

Thank you for this.

[rfbjr]

Journald is a service process responsible for log collection and management. You can try leaving the NAS running without shutting it down for an extended period, and then observe whether this process continues to occupy CPU resources.

I will and provide the feedback/results.