elmuziko

@blackburn Haven't tried the above, but nonetheless, thank you for picking this up after so long. Appreciate it

Hi IG-88, Thanks for the comment. It appears to be Docker making the racket. As soon as I disable it, things calm down immensely. That's the only software that's changed after the drive change. Shame that, liked the new way of running Sab, Sick and Couch!

HP N54L JunLoader DSM 6.1.7-15284 Update 3 3x Toshiba HDWG21E 14TB drives in RAID 5. Docker install for couchpotato, sabnzbd and sickchill Hard Drive's set to 15 minutes sleep with logs switched on. I recently moved from WD red drives. In the process upgraded to Update 3 from Update 2. The hard drives just aren't spinning down. Any ideas on what's going off? At times it sounds like there's thunderstorms going off. Any ideas where I can find out what's eating away at the drives?

Sorry if this is in the wrong area; Running Synology on ESXi 6.7. As we know this means not being able to access SMART data from Synology itself. I've got the SMART data out from bash, but what I'm curious to know is, is it possible to run a full SMART test at all? In Synology you can perform long tests, in Windows WDC has an app to perform a full scan, is there anything of this nature available to us for ESXi? And if so, does anyone know how to do it? Thanks

I'd still take a permanent fix to this any day of the week but getting around it for the time being using those steps albeit from the Synology site, to chmod wherever it is I'm going to, using winSCP as a standard user, then chmod back to what it was previously. It's not clean, nor is it straight forward, but it is a work around. Again, if someone has a more permanent fix I'd take it any day of the week. Thanks

Yo, has anyone got an idiots guide to enabling root on 6.2? I use winSCP to transfer files but can't do it any more since directories are locked down. i found a guide on YouTube however on my etc/ssh/sshd_config, PermitRootLogin is set to prohibit-password. Making the changes in the questions just makes the ssh service stop and won't come back up. Thanks

Ended up having to rebuild, a misplaced letter on a mdadm switch formatted the whole lot.

Morning all, DSM 5.2 user here - for the most part - works great, but when something happens to the Hyper-V host it often fails spectacularly. Today is one of those days. I'm not great at under the hood stuff but have Google'd around and come to the conclusion the whole thing is confused! I only have one RAID5 with 7 disks in total which seems to correspond to mdadm --detail /dev/md2. Can anyone give me any guidance on how to bring the volume back to life? SuperSyno> mdadm --detail /dev/md3 /dev/md3: Version : 1.2 Creation Time : Sun Apr 1 20:22:

Looks like it crashed. Turned it off and on again, it sat at BUSY Re-Scanning disks for twenty minutes, then moved on to starting services for an hour, then finally back in. Hooorah!

Hi everyone. So I've had a bit of a nightmare with my Xpenology and would welcome any advise to get things up and running again. About 2 weeks ago my DSM wanted to data scrub. I left it going over night and the next day found errors. It transpired the system did an update during the scrub and rebooted itself. Sigh. I repaired the RAID, only it transpired a disk had become unhappy, so I bought a replacement. Whilst trying to track down which one was dead I noticed the SATA card on my windows 10 machine (I run Hyper-V) was using basic drivers, so I updated that and the dr

Afternoon all, Anyone have any ideas on how to bring a volume back to life after a crash during drive expansion? I'm using 5.2 on Hyper-V. I was adding a new hard drive, it got to about 10% then I lost power to the Hyper-V host. When my machine came back up it said it'd crashed. I didn't panic so much, it started an integrity check that took just over 24 hours. Once it completed it didn't come back to life. I took the extra disk out, tried again, nothing. When I reboot, I get: "The system has detected one or more crashed storage spaces. Please check the following expa

By the looks of things it seems I'm one of the few (maybe the only one?) that hasn't found Salah troll like at all. Uncouth perhaps, and hasn't figured out how to use edit rather than reply, but not a troll. This post suggests a method around the QuickConnect kick yes? Surely that's helpful? I use VPN myself so don't know if such a thing has actually happened. And even if said person is a Synology employee, wouldn't we want that kind of inside information on the board? To give us a heads up on the direction they're taking?

If you have a few pennies available to you, get a new router, one that supports VPN. I uses an ASUS myself, most of the options in there are easy to understand so you can make your network fairly hardy. As for Syno security, have a look at: https://www.synology.com/en-uk/knowledg ... nology_NAS Even with all that in mind I still wouldn't set your Syno up to face the internet (as in open ports on your firewall and be able to log in from the outside world). A few years back there was a nasty program called SynoLocker that smashed through DSM ransomware style. ( https://forum.synology.co

No, not really. The best responses on StackOverFlow are the ones that come with an explanation into what each step does. Perhaps the manner in which the question was asked may have come across rude but remember we all have a common goal on here, to further progress Xpenology. The ones that deserve so little of the developers time are the selfish a******* that come on here as just an IP address, download what they need and contribute naff all, not even a thank you. Anyone signing up to the forum to comment (short of the spammers!) at the very least recognises the hard work Trantor and c

Wouldn't package updates or even DSM updates go via this?