mirror of
https://github.com/007revad/Synology_enable_Deduplication.git
synced 2026-04-25 12:46:03 +03:00
[GH-ISSUE #38] sbtd initialized in wrong place - breaks SAN manager #105
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_enable_Deduplication#105
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @darthstrydre on GitHub (Dec 29, 2023).
Original GitHub issue: https://github.com/007revad/Synology_enable_Deduplication/issues/38
In file syno_enable_dedupe.sh,
Line 882 “sbtd=support_tiny_btrfs_dedupe”
Should be moved up by line 859, since the variable sbtd is used on lines 872-876.
Without that, the synoinfo.conf gets messed up with an extra “= no” line near the end.
On my 1522+ this corruption somehow kills SAN manager, which in turn prevents Virtual Machine Manager from running.
@007revad commented on GitHub (Dec 29, 2023):
Thank you.
I've released a new version v1.2.15
I just tried synosetkeyvalue with an unset variable as the keyname and while it did return 1 as the exist code instead 0 it didn't create an
="no"line.@gallivanter commented on GitHub (Dec 29, 2023):
After applying v1.2.14 I also experiened this problem. I tried using the
--restorearg and rebooting but it didn't allow me to start or repair SAN Manager. I also tried applying v1.2.15 and rebooting but that also didn't help. There isn't a rogue= noline near the end of my synoinfo.conf.I don't use iSCSI so there are no targets or snapshots currently. If there's a quick way to clear the package config entirely so that I can get the package working I'd be open to that as a solution.
Attaching journalctl output when attempting to repair the SAN Manager and synoinfo.conf.
journalctl.log
synoinfo.conf.txt
@darthstrydre commented on GitHub (Dec 29, 2023):
The fix worked for me, thank you revad.
Gallivanter, I did have to reboot after manually restoring the synoinfo.conf.bak file once for SAN manager to be happy. Just using the —restore did not work because it left an unclean conf for me because of the extra “=no”. Give that a try.
I’m going to close, and though, because the initial issue is fixed.
@007revad commented on GitHub (Dec 29, 2023):
Download https://global.synologydownload.com/download/Package/spk/ScsiTarget/1.0.10-0314/ScsiTarget-x86_64-1.0.10-0314.spk
Then uninstall SAN Manager with the following command.
sudo synopkg uninstall ScsiTargetFinally in Package Center do a "Manual Install" of the ScsiTarget-x86_64-1.0.10-0314.spk you downloaded.
@gallivanter commented on GitHub (Dec 29, 2023):
Thanks for the suggestions @darthstrydre and @007revad .
I manually restored synoinfo.conf from synoinfo.conf.bak, rebooted and attempted to manually remove the ScsiTarget package and reinstall using the manual install method. Unfortunately SAN Manager still won't start. The relevant log lines appear to be:
/config exists but is empty.
@007revad commented on GitHub (Dec 29, 2023):
There is no /config folder on my DS1821+ with DSM 7.2.1. Where are seeing the config folder?
What DSM version are you using?
Another alternative is to reinstall the same DSM version: https://github.com/007revad/Synology_DSM_reinstall
@gallivanter commented on GitHub (Dec 29, 2023):
Interesting, you don't have a /config directory on your NAS? My DS1821+ has a /config dir:
I'm running DSM 7.2.1-69057 Update 3. If that /config path definitely shouldn't exist I'm tempted to remove it since it's empty, before trying anything more drastic like re-installing DSM.
@gallivanter commented on GitHub (Dec 29, 2023):
Checking if /config was referenced anywhere before removal, I found that it's actually mounted as configfs.
ETA: If I unmount and delete /config it's recreated and remounted in the same way after attempting to repair SAN Manager.
@007revad commented on GitHub (Dec 29, 2023):
Reinstalling the same DSM version is no different than upgrading DSM. All your files and settings etc are retained.
ScsiTarget-x86_64-1.0.10-0314 is the version included in DSM 7.2.1-69057 Update 3.
Oh, I do have /config
I was looking for a ScsiTarget config folder in
/var/packages/ScsiTarget/targetand/usr/local/packages/@appstore/ScsiTargetMy DS1812+'s /config folder contains a bunch folders and files:
@gallivanter commented on GitHub (Dec 29, 2023):
I bit the bullet and used Synology_DSM_reinstall to reinstall the current version of DSM. My /config path now looks like yours and SAN Manager is working as expected. Thanks for all the help!