NAS Posted December 23, 2014 Share Posted December 23, 2014 Perhaps its my wording but the addon I upgraded was unRAID itself as per the OP? Does this change your thoughts? Quote Link to comment
heffe2001 Posted December 23, 2014 Share Posted December 23, 2014 Had a hard crash today, not sure what caused it, server was completely unresponsive. Took a hard reset to get it back up and going again. I'll keep a closer eye on it to see if I can figure out what caused it. Only thing that I can think of that's different on the system than prior to the crash is that I did have 2 dockers running that I normally don't cAdvisor and MediaBrowser. cAdvisor has been running for about 3 days, where MediaBrowser was started about 1am last night. Had this again over the weekend (noticed it Sunday morning). Got a picture of the monitor screen (if it'd be any help). The system had been up since the 15th without any issues at all. I did start (then stop) cAdvisor on Saturday, so at this point I'm guessing the problem has something to do with that (last time I had this crash, it was the following morning after installing cAdvisor, and I've not used it since that day until Saturday afternoon). Quote Link to comment
Nokoff Posted December 25, 2014 Share Posted December 25, 2014 I'm having a problem where docker containers can't be started or stopped via the docker page. I can start them manually from SSH, but the buttons just seemingly have no impact in the web interface. Any ideas? PS: I'm missing a drive at the moment and my log consists basically of this: Dec 25 02:51:07 Tower kernel: parent transid verify failed on 775929856 wanted 241434 found 239369 Dec 25 02:51:07 Tower kernel: parent transid verify failed on 775929856 wanted 241434 found 239369 Dec 25 02:51:07 Tower kernel: parent transid verify failed on 775929856 wanted 241434 found 239369 Dec 25 02:51:07 Tower kernel: parent transid verify failed on 775929856 wanted 241434 found 239369 Dec 25 02:51:07 Tower kernel: parent transid verify failed on 775929856 wanted 241434 found 239369 Dec 25 02:51:07 Tower kernel: parent transid verify failed on 775929856 wanted 241434 found 239369 Dec 25 02:51:07 Tower kernel: parent transid verify failed on 775929856 wanted 241434 found 239369 Dec 25 02:51:07 Tower kernel: parent transid verify failed on 775929856 wanted 241434 found 239369 Dec 25 02:51:07 Tower kernel: parent transid verify failed on 775929856 wanted 241434 found 239369 Dec 25 02:51:12 Tower kernel: verify_parent_transid: 60 callbacks suppressed Dec 25 02:51:12 Tower kernel: parent transid verify failed on 775929856 wanted 241434 found 239369 Dec 25 02:51:12 Tower kernel: parent transid verify failed on 775929856 wanted 241434 found 239369 Dec 25 02:51:12 Tower kernel: parent transid verify failed on 775929856 wanted 241434 found 239369 Dec 25 02:51:12 Tower kernel: parent transid verify failed on 775929856 wanted 241434 found 239369 Dec 25 02:51:12 Tower kernel: parent transid verify failed on 775929856 wanted 241434 found 239369 Dec 25 02:51:12 Tower kernel: parent transid verify failed on 775929856 wanted 241434 found 239369 Dec 25 02:51:12 Tower kernel: parent transid verify failed on 775929856 wanted 241434 found 239369 Dec 25 02:51:12 Tower kernel: parent transid verify failed on 775929856 wanted 241434 found 239369 Dec 25 02:51:12 Tower kernel: parent transid verify failed on 775929856 wanted 241434 found 239369 Dec 25 02:51:12 Tower kernel: parent transid verify failed on 775929856 wanted 241434 found 239369 Dec 25 02:51:18 Tower kernel: verify_parent_transid: 60 callbacks suppressed And there is no log event when I press the start button on the docker page. Quote Link to comment
JarDo Posted December 25, 2014 Share Posted December 25, 2014 Just decided to look at the syslog and noticed the following happen every half hour. Dec 12 00:38:26 UNRAID kernel: ata6.00: exception Emask 0x52 SAct 0x0 SErr 0x1280d00 action 0x6 frozen Dec 12 00:38:26 UNRAID kernel: ata6.00: irq_stat 0x09000000, interface fatal error Dec 12 00:38:26 UNRAID kernel: ata6: SError: { UnrecovData Proto HostInt 10B8B BadCRC TrStaTrns } Dec 12 00:38:26 UNRAID kernel: ata6.00: failed command: IDENTIFY DEVICE Dec 12 00:38:26 UNRAID kernel: ata6.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 8 pio 512 in Dec 12 00:38:26 UNRAID kernel: res 50/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x52 (ATA bus error) Dec 12 00:38:26 UNRAID kernel: ata6.00: status: { DRDY } Dec 12 00:38:26 UNRAID kernel: ata6: hard resetting link Dec 12 00:38:26 UNRAID kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Dec 12 00:38:26 UNRAID kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140724/psargs-359) Dec 12 00:38:26 UNRAID kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff880217073eb0), AE_NOT_FOUND (20140724/psparse-536) Dec 12 00:38:26 UNRAID kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140724/psargs-359) Dec 12 00:38:26 UNRAID kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff880217073eb0), AE_NOT_FOUND (20140724/psparse-536) Dec 12 00:38:26 UNRAID kernel: ata6.00: configured for UDMA/133 Dec 12 00:38:26 UNRAID kernel: ata6: EH complete Otherwise, everything appears normal. Does anyone recognize what this might mean? Quote Link to comment
WeeboTech Posted December 25, 2014 Share Posted December 25, 2014 I've forked off the doublewhatever's issue as this seems to be the 4th time for a similar issue. Kernel crashes w potential reiserfs corruption: 6.0-beta12-x86_64 http://lime-technology.com/forum/index.php?topic=37316.msg344859#msg344859 Quote Link to comment
RobJ Posted December 25, 2014 Share Posted December 25, 2014 Just decided to look at the syslog and noticed the following happen every half hour. Dec 12 00:38:26 UNRAID kernel: ata6.00: exception Emask 0x52 SAct 0x0 SErr 0x1280d00 action 0x6 frozen Dec 12 00:38:26 UNRAID kernel: ata6.00: irq_stat 0x09000000, interface fatal error Dec 12 00:38:26 UNRAID kernel: ata6: SError: { UnrecovData Proto HostInt 10B8B BadCRC TrStaTrns } Dec 12 00:38:26 UNRAID kernel: ata6.00: failed command: IDENTIFY DEVICE Dec 12 00:38:26 UNRAID kernel: ata6.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 8 pio 512 in Dec 12 00:38:26 UNRAID kernel: res 50/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x52 (ATA bus error) Dec 12 00:38:26 UNRAID kernel: ata6.00: status: { DRDY } Dec 12 00:38:26 UNRAID kernel: ata6: hard resetting link Dec 12 00:38:26 UNRAID kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Dec 12 00:38:26 UNRAID kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140724/psargs-359) Dec 12 00:38:26 UNRAID kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff880217073eb0), AE_NOT_FOUND (20140724/psparse-536) Dec 12 00:38:26 UNRAID kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140724/psargs-359) Dec 12 00:38:26 UNRAID kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff880217073eb0), AE_NOT_FOUND (20140724/psparse-536) Dec 12 00:38:26 UNRAID kernel: ata6.00: configured for UDMA/133 Dec 12 00:38:26 UNRAID kernel: ata6: EH complete Otherwise, everything appears normal. Does anyone recognize what this might mean? It's essentially a moment of communications corruption. When you say 'every half hour', is that exact? Normally I would point out the BadCRC flag and tell you to replace the SATA cable with a better one, as BadCRC means a packet was corrupted and didn't transmit across the cable correctly. But you have so many other indicators of momentary corrupted communications, plus an indication of repeatably timed occurrences, that I would look for a power glitch source, perhaps something that occurs every half hour that puts an abnormal demand on the circuit, or something that goes off that could be a source of interference or noise on the line. The ACPI errors do not normally ever repeat. Are you saying that they too occur every half hour? They typically occur as part of the initial setup, and are quite normal and generally harmless. Most setups have one or more issues like that, but they shouldn't repeat. A BIOS update *may* eliminate them. Quote Link to comment
BRiT Posted December 25, 2014 Share Posted December 25, 2014 Just decided to look at the syslog and noticed the following happen every half hour. Dec 12 00:38:26 UNRAID kernel: ata6.00: exception Emask 0x52 SAct 0x0 SErr 0x1280d00 action 0x6 frozen Dec 12 00:38:26 UNRAID kernel: ata6.00: irq_stat 0x09000000, interface fatal error Dec 12 00:38:26 UNRAID kernel: ata6: SError: { UnrecovData Proto HostInt 10B8B BadCRC TrStaTrns } Dec 12 00:38:26 UNRAID kernel: ata6.00: failed command: IDENTIFY DEVICE Dec 12 00:38:26 UNRAID kernel: ata6.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 8 pio 512 in Dec 12 00:38:26 UNRAID kernel: res 50/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x52 (ATA bus error) Dec 12 00:38:26 UNRAID kernel: ata6.00: status: { DRDY } Dec 12 00:38:26 UNRAID kernel: ata6: hard resetting link Dec 12 00:38:26 UNRAID kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Dec 12 00:38:26 UNRAID kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140724/psargs-359) Dec 12 00:38:26 UNRAID kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff880217073eb0), AE_NOT_FOUND (20140724/psparse-536) Dec 12 00:38:26 UNRAID kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140724/psargs-359) Dec 12 00:38:26 UNRAID kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff880217073eb0), AE_NOT_FOUND (20140724/psparse-536) Dec 12 00:38:26 UNRAID kernel: ata6.00: configured for UDMA/133 Dec 12 00:38:26 UNRAID kernel: ata6: EH complete Otherwise, everything appears normal. Does anyone recognize what this might mean? It's essentially a moment of communications corruption. When you say 'every half hour', is that exact? Normally I would point out the BadCRC flag and tell you to replace the SATA cable with a better one, as BadCRC means a packet was corrupted and didn't transmit across the cable correctly. But you have so many other indicators of momentary corrupted communications, plus an indication of repeatably timed occurrences, that I would look for a power glitch source, perhaps something that occurs every half hour that puts an abnormal demand on the circuit, or something that goes off that could be a source of interference or noise on the line. The ACPI errors do not normally ever repeat. Are you saying that they too occur every half hour? They typically occur as part of the initial setup, and are quite normal and generally harmless. Most setups have one or more issues like that, but they shouldn't repeat. A BIOS update *may* eliminate them. What is your spin down timer set to? Is it 30 minutes? Do you have a media scanner running every 30 minutes, like is the drive trying to spin up every 30 minutes if it's spindown is set to 15? Quote Link to comment
JarDo Posted December 25, 2014 Share Posted December 25, 2014 Just decided to look at the syslog and noticed the following happen every half hour. Dec 12 00:38:26 UNRAID kernel: ata6.00: exception Emask 0x52 SAct 0x0 SErr 0x1280d00 action 0x6 frozen Dec 12 00:38:26 UNRAID kernel: ata6.00: irq_stat 0x09000000, interface fatal error Dec 12 00:38:26 UNRAID kernel: ata6: SError: { UnrecovData Proto HostInt 10B8B BadCRC TrStaTrns } Dec 12 00:38:26 UNRAID kernel: ata6.00: failed command: IDENTIFY DEVICE Dec 12 00:38:26 UNRAID kernel: ata6.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 8 pio 512 in Dec 12 00:38:26 UNRAID kernel: res 50/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x52 (ATA bus error) Dec 12 00:38:26 UNRAID kernel: ata6.00: status: { DRDY } Dec 12 00:38:26 UNRAID kernel: ata6: hard resetting link Dec 12 00:38:26 UNRAID kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Dec 12 00:38:26 UNRAID kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140724/psargs-359) Dec 12 00:38:26 UNRAID kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff880217073eb0), AE_NOT_FOUND (20140724/psparse-536) Dec 12 00:38:26 UNRAID kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140724/psargs-359) Dec 12 00:38:26 UNRAID kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff880217073eb0), AE_NOT_FOUND (20140724/psparse-536) Dec 12 00:38:26 UNRAID kernel: ata6.00: configured for UDMA/133 Dec 12 00:38:26 UNRAID kernel: ata6: EH complete Otherwise, everything appears normal. Does anyone recognize what this might mean? It's essentially a moment of communications corruption. When you say 'every half hour', is that exact? Normally I would point out the BadCRC flag and tell you to replace the SATA cable with a better one, as BadCRC means a packet was corrupted and didn't transmit across the cable correctly. But you have so many other indicators of momentary corrupted communications, plus an indication of repeatably timed occurrences, that I would look for a power glitch source, perhaps something that occurs every half hour that puts an abnormal demand on the circuit, or something that goes off that could be a source of interference or noise on the line. The ACPI errors do not normally ever repeat. Are you saying that they too occur every half hour? They typically occur as part of the initial setup, and are quite normal and generally harmless. Most setups have one or more issues like that, but they shouldn't repeat. A BIOS update *may* eliminate them. What is your spin down timer set to? Is it 30 minutes? Do you have a media scanner running every 30 minutes, like is the drive trying to spin up every 30 minutes if it's spindown is set to 15? Thank you all for the feedback. Yes, even the ACPI errors were happening every half hour. My spin down timer is set for 3 hours on all drives. I rebooted and the pattern of errors every half-hour has stopped for now. I will keep watch. Quote Link to comment
shire Posted December 28, 2014 Share Posted December 28, 2014 Hi, is that problem known? I get this message every time; even when there is nothing to move: Dec 28 02:42:09 Tower kernel: mdcmd (164): spindown 1 Dec 28 03:02:54 Tower kernel: mdcmd (165): spindown 2 Dec 28 03:10:44 Tower kernel: mdcmd (166): spindown 14 Dec 28 03:40:01 Tower logger: mover started Dec 28 03:40:01 Tower logger: skipping Download/ Dec 28 03:40:01 Tower logger: mover finished Dec 28 04:40:01 Tower logrotate: ALERT - exited abnormally. Bye. Quote Link to comment
Frank1940 Posted December 28, 2014 Share Posted December 28, 2014 Hi, is that problem known? I get this message every time; even when there is nothing to move: Dec 28 02:42:09 Tower kernel: mdcmd (164): spindown 1 Dec 28 03:02:54 Tower kernel: mdcmd (165): spindown 2 Dec 28 03:10:44 Tower kernel: mdcmd (166): spindown 14 Dec 28 03:40:01 Tower logger: mover started Dec 28 03:40:01 Tower logger: skipping Download/ Dec 28 03:40:01 Tower logger: mover finished Dec 28 04:40:01 Tower logrotate: ALERT - exited abnormally. Bye. You need to post the ENTIRE syslog for those folks who are more knowledgeable than me to review. You should also check to see if your flash drive has been changed to a read-only state. Quote Link to comment
dlandon Posted December 28, 2014 Share Posted December 28, 2014 The logrotate error is a known issue and it will be fixed. It has something to do with permissions. It has nothing to do with the mover. Quote Link to comment
dougnliz Posted December 28, 2014 Share Posted December 28, 2014 I just upgraded from Beta6 to Beta12 and that went fine. I'm having issues with Docker though. How do I get it start? The webGUI doesn't seem to do anything. I did remove the old docker plugin before upgrading per the instructions. Thanks, Doug Quote Link to comment
trurl Posted December 29, 2014 Share Posted December 29, 2014 I just upgraded from Beta6 to Beta12 and that went fine. I'm having issues with Docker though. How do I get it start? The webGUI doesn't seem to do anything. I did remove the old docker plugin before upgrading per the instructions. Thanks, Doug Maybe a screenshot? Quote Link to comment
dougnliz Posted December 29, 2014 Share Posted December 29, 2014 Okay I got it to work. I had to use this path for the docker image: /mnt/cache/docker/docker.img If I left it at the default or tried /mnt/cache/docker.img like I was doing the page would just reset and nothing happened. In the syslog I was getting: Dec 28 19:22:54 TowerB php: Not starting Docker: no image file defined Once I tried putting the docker folder in the path and clicked Start it came right up. Thanks, Doug Quote Link to comment
shire Posted December 29, 2014 Share Posted December 29, 2014 The logrotate error is a known issue and it will be fixed. It has something to do with permissions. It has nothing to do with the mover. Thanks.;-) Quote Link to comment
assur191 Posted December 29, 2014 Share Posted December 29, 2014 Hello All, I just upgraded from unRAID version 5 to 6beta12. I set up docker and was able to run sonarr and sabnzbd, but I tried running too many dockers at once, and I think I screwed up my cache drive on which all dockers are installed. When I try to start docker, I get the following error in the log file: Dec 29 22:20:37 Tower php: /etc/rc.d/rc.docker start Dec 29 22:20:37 Tower kernel: BTRFS info (device loop8): disk space caching is enabled Dec 29 22:20:37 Tower kernel: parent transid verify failed on 873005056 wanted 3294 found 3290 Dec 29 22:20:37 Tower kernel: parent transid verify failed on 873005056 wanted 3294 found 3290 Dec 29 22:20:37 Tower kernel: BTRFS: failed to read tree root on loop8 Dec 29 22:20:37 Tower php: Not starting Docker: mount error Dec 29 22:20:37 Tower php: Dec 29 22:20:37 Tower kernel: BTRFS: open_ctree failed I've restarted the server a few times, and ran scrub on the cache drive, but that didn't resolve it. I've search on here for a solution and found similar issues, but not this one exactly. Any help would be greatly appreciated. Thanks. Quote Link to comment
jonp Posted December 29, 2014 Share Posted December 29, 2014 Hello All, I just upgraded from unRAID version 5 to 6beta12. I set up docker and was able to run sonarr and sabnzbd, but I tried running too many dockers at once, and I think I screwed up my cache drive on which all dockers are installed. When I try to start docker, I get the following error in the log file: Dec 29 22:20:37 Tower php: /etc/rc.d/rc.docker start Dec 29 22:20:37 Tower kernel: BTRFS info (device loop8): disk space caching is enabled Dec 29 22:20:37 Tower kernel: parent transid verify failed on 873005056 wanted 3294 found 3290 Dec 29 22:20:37 Tower kernel: parent transid verify failed on 873005056 wanted 3294 found 3290 Dec 29 22:20:37 Tower kernel: BTRFS: failed to read tree root on loop8 Dec 29 22:20:37 Tower php: Not starting Docker: mount error Dec 29 22:20:37 Tower php: Dec 29 22:20:37 Tower kernel: BTRFS: open_ctree failed I've restarted the server a few times, and ran scrub on the cache drive, but that didn't resolve it. I've search on here for a solution and found similar issues, but not this one exactly. Any help would be greatly appreciated. Thanks. Step 1 (optional): Remove your docker image file and recreate it. You can remove the image using Windows Explorer and browsing to your server's cache folder, then deleting the docker.img file located there (or on whichever disk device you specified the docker image to live on). Step 2: Navigate on the unRAID webGui to the "Docker" page and restart docker (it will automatically recreate the image file then). If you didn't perform step 1, you will need to rename the file in the "Docker image" field to something like Docker1.img (make sure it's not the same name as the previous). Step 3: Click "add container" and then notice your templates appear at the top of the dropdown list (e.g. PlexMediaServer will say My-PlexMediaServer). Simply select your templates (one at a time) to have all your container settings from your initial setup applied automatically. This will trigger the necessary files to redownload for each dockerized application but apply the same ports/volume mappings that you had in your old docker image. Step 4: Relax and enjoy! If you don't perform step 1, the space consumed by the original docker image will remain. Quote Link to comment
assur191 Posted December 29, 2014 Share Posted December 29, 2014 Step 1 (optional): Remove your docker image file and recreate it. You can remove the image using Windows Explorer and browsing to your server's cache folder, then deleting the docker.img file located there (or on whichever disk device you specified the docker image to live on). Step 2: Navigate on the unRAID webGui to the "Docker" page and restart docker (it will automatically recreate the image file then). If you didn't perform step 1, you will need to rename the file in the "Docker image" field to something like Docker1.img (make sure it's not the same name as the previous). Step 3: Click "add container" and then notice your templates appear at the top of the dropdown list (e.g. PlexMediaServer will say My-PlexMediaServer). Simply select your templates (one at a time) to have all your container settings from your initial setup applied automatically. This will trigger the necessary files to redownload for each dockerized application but apply the same ports/volume mappings that you had in your old docker image. Step 4: Relax and enjoy! If you don't perform step 1, the space consumed by the original docker image will remain. Thank you. I'll do this, but I was hoping there was some way to restore my current dockerfile, as I've put in a bunch of work on setting up sonarr and sabnzbd. What steps should I take to prevent this from occurring again the future? Thanks again. Quote Link to comment
trurl Posted December 29, 2014 Share Posted December 29, 2014 Thank you. I'll do this, but I was hoping there was some way to restore my current dockerfile, as I've put in a bunch of work on setting up sonarr and sabnzbd. What steps should I take to prevent this from occurring again the future? Thanks again. I don't use those specific dockers, but typically a docker's "working storage" is not in the docker img file. That is what the /mnt/cache/appdata (or whatever) folder is all about. Quote Link to comment
jonp Posted December 30, 2014 Share Posted December 30, 2014 Thank you. I'll do this, but I was hoping there was some way to restore my current dockerfile, as I've put in a bunch of work on setting up sonarr and sabnzbd. What steps should I take to prevent this from occurring again the future? Thanks again. I don't use those specific dockers, but typically a docker's "working storage" is not in the docker img file. That is what the /mnt/cache/appdata (or whatever) folder is all about. This is correct. Quote Link to comment
Kryspy Posted December 30, 2014 Share Posted December 30, 2014 If one is to keep their appdata folder backed up you should never need to reconfigure your containers. You just re-pull and point to that directory and all is good. Hope I am not stating the obvious here. Kryspy Quote Link to comment
mostlydave Posted December 30, 2014 Share Posted December 30, 2014 it would be great if limetech could give us a way to backup our cache based appdata folder to the array automatically! Quote Link to comment
dalben Posted December 30, 2014 Share Posted December 30, 2014 They did. Cron and rsync Quote Link to comment
assur191 Posted December 30, 2014 Share Posted December 30, 2014 I don't use those specific dockers, but typically a docker's "working storage" is not in the docker img file. That is what the /mnt/cache/appdata (or whatever) folder is all about. Thank you. I didn't even think about that, but it worked as you said. Quote Link to comment
mostlydave Posted December 30, 2014 Share Posted December 30, 2014 They did. Cron and rsync Yeah I meant maybe a gui based system that doesn't require someone to be a linux ninja, or maybe doesn't take longer to setup than the docker data it is backing up. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.