mirror of
https://github.com/AlexFromChaos/synology_hibernation_fixer.git
synced 2026-04-26 03:06:02 +03:00
[GH-ISSUE #4] eSata volumes? #17
Labels
No labels
enhancement
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/synology_hibernation_fixer#17
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 @KirovAir on GitHub (Nov 21, 2023).
Original GitHub issue: https://github.com/AlexFromChaos/synology_hibernation_fixer/issues/4
Hi there!
First of all great job on the script and your DSM knowledge. It goes way beyond anything I could find online. :)
I am currently using a tiny external SSD connected using eSata on my Synology DS216+II. I've created a volume from it using a changes synoinfo.conf. I've described the process here:
https://gist.github.com/KirovAir/be5139181e272390a7300a1d5f26f811
It's simply another storage pool (volume2) now:
On this volume I have all my containers, and the docker installation running.
Will this fix also apply for my setup? Currently my drives on volume1 will not hibernate with docker running but I'm still trying to find out if this is due a Synology bug occuring or something else..
I am running on DSM 7.2.1-69057 Update 1.