Restore Administrator Account Permissions for Black Synology

Restore Administrator Account Permissions for Black Synology
Character: 灰泽满Hazel -- Generated by Gemini

Background: One day, I logged into Synology and suddenly found that my account could not access the control panel and a series of other packages. It seemed that the admin privileges had disappeared. I suspected a hack, but it turned out to be a sudden error with the Synology system account permissions.

My black Synology NAS configuration is:
- Intel N100 machine
- RR boot disk tool (23.11.8)
- RR DSM model: SA6400
- DSM build: 7.2 (69057u4)


Solution method directly:
1. Boot up and select RR Loader Config, use another computer to access the displayed URL for settings
2. In Loader Config, find Advanced Settings, and look for Add Admin Account to create a new account
3. Select Boot Loader, the machine will reboot automatically
4. Log in with the newly created account, enter the Synology system
5. Access the control panel to reselect admin privileges for the account that lost them

The problem should be resolved.


I took many detours in the actual resolution process.


After discovering the problem, I decided to migrate the Synology system. In RR, use Force re-install DSM to rebuild a new version of DSM and migrate the old DSM onto it. RR automatically selected to build the latest 7.4 DSM version.

During the build, it prompted Error: Configuration for model SA6400 and product version 7.4 not found so I decided to upgrade to the latest RR version 26.9.0. Download img.zip from Github and use the Rufus tool to burn it onto the boot disk. Remember to save the user config file from the boot disk before burning, and put it back after burning.

In RR Loader Config, select version 7.4, then Build Loader. Boot Loader.

Enter the new Synology interface, choose to retain system settings for migration, the machine reboots automatically, but it couldn't enter the system. The router also didn't show the NAS device connection.

Suspecting that version 7.4 is not compatible with the machine, I opened the loader's advanced settings and ran a downgrade installation, downgrading version 7.4 back to version 7.2.

After resetting, it still couldn't enter the system, but the machine's hard drive was running normally.

Using the dbgutils plugin to capture logs didn't reveal any issues.

The facts combined at this point are: the machine kernel is alive (NumLock responds) + there is real disk I/O + no reboot + zero response from the network stack. It is very likely that the system is up but the network card is not driven/configured correctly.

So I changed the network cable to another port, the router showed the machine online, and I could successfully enter the system.

It turns out that on multi-port devices, the network configuration of the loader and DSM are two independent things. Linux's network configuration is saved "by interface," and the loader scans all ports.

After entering the system, I found that because of downgrading from 7.4 to 7.2, many packages showed as disabled and could not be repaired. After downgrading to 7.2, the system and package data configuration were still 7.4, causing incompatibility with 7.2.

So I decided to upgrade back to 7.4, which was successful. This proved that the combination of RR (26.9.0) + model: SA6400 + DSM7.4 is feasible.

Then, following the initial solution method, I successfully resolved the issue and upgraded the system in the process.


If any friends encounter similar issues, I hope this can help you.