v. 7.1.4syslogvader-diagnostics-20250914-1635.zip

Most recent syslog and diagnostics attached.

I have weekly backups of the flash and system.

Couldn't find a guide on restoring the USB or resetting beyond grabbing the two files (key and super.dat). Is it as simple as formatting it, loading the fresh system OS, then copying those files over?

I also have screenshots of my drive allocations on the MAIN page before I started the array in maintenance for the parity check. What else should I be looking at and considering?

If this is a hardware issue, where does one begin trying to figure that out?

If it works in safe mode, it suggests a plugin is the problem; remove the plugins and retest.

1 hour ago, JorgeB said:

If it works in safe mode, it suggests a plugin is the problem; remove the plugins and retest.

Booting from the USB and not choosing Safe Mode leads to a frozen UI... can't login, system frozen.

If I boot into Safe Mode, no array, no plugins installed. Are you suggesting booting into Safe Mode, then starting the Array without plugins? Or are you suggesting removing plugins somehow from the USB and booting straight up without Safe Mode?

36 minutes ago, danimal_0119 said:

If I boot into Safe Mode, no array

What do you mean, no array? If it works in safe mode, it suggests a plugin issue. You can remove them all, boot in normal mode, and if it still works, start reinstalling them one by one.

1 minute ago, JorgeB said:

What do you mean, no array? If it works in safe mode, it suggests a plugin issue. You can remove them all, boot in normal mode, and if it still works, start reinstalling them one by one.

Steps I took:

1. Booted to Safe Mode (no plugins).

2. GUI operational and functioning as I would expect.

3. Started the array.

4. Cancelled the parity check.

5. Array started.

6. GUI frozen and unresponsive.

Cannot access terminal or any other system resource.

I saw another comment you made to another user about renaming all the plug in files on the usb where you stated

"You can just rename all .plg files to for example .bak in /config/plugins, if still good you can start renaming one or a few at a time and rebooting to see if you find the culprit."

However, if the problem starts on array startup, what would the cause of that be? I can shut down the system and look at the logs. I set up the syslog to mirror to my flash. I just can't get to diagnostics since the system is unresponsive to generate another set.

If it crashes when you start the array, you can enable the syslog server and post that after it happens.

Additional Steps:

1. Renamed all .plg files on flash in plugins folder to .bak.

2. Ran a windows repair on the USB. Found problem, repaired it.

3. Booted to Normal GUI - not Safe Mode.

4. Array started.

5. Cancelled parity check.

6. Waited for Array to start and dockers to initialize.

7. GUI Froze

Appears to be 3 min after starting

Could it be docker related?

syslog attached.

The WebGUI had a system message in the bottom left that said "Transferring from localhost..."

syslog

Edited September 15, 2025Sep 15 by danimal_0119

Not seeing any issues with the array and pools, you can disable the Docker and VM services and retest.

1. Rebooted the system

2. Started in Normal with GUI

3. All plugins are disabled as well.

4. Started the Array

5. Stopped the parity check

6. Disabled docker and have no VMs.

System is stable.

What are next steps?

1. Start plugins one by one until something fails?

2. Is there a way to rebuild docker if that is the issue without trying to remember all the docker particulars and ports, etc? Or am I in for a slog to recreate all the containers?

New additional steps,

7. Re-enabled all plugins

8. Restarted the system

9. All plugins loaded properly.

10. Docker still disabled.

System is stable and accessible over WebGUI

So, it appears that the docker instance/img is corrupt. Is there a way to rebuild that? I have all container folders save for persistence, but want to blow away the whole thing and potentially recreate them from a template, one at a time. @JorgeB appreciate your help and input. This has been a learning experience for me.

Blew away the docker.img... System stable. New containers coming up slowly. Watching. Time will tell. Thanks so much @JorgeB . Appreciate the guidance.