elmuziko

Great idea. Consider it my next challenge!

Reserved for version 3.0.0

Good afternoon all. I've finally got round to updating both the website and PowerShell scripts. Both code improvements and new features. Website Update and Improvements. The website now hosts a 'SETTINGS' page, in which certain aspects can be controlled. Hard Drive order can now be set from small to large, large to small, Raw Device Mapping Naming convention, Controller Location, and Hard Drive Number. An option to hide Removed Drives (great for when you upgrade drives) Alter how many plot points there are on your temperature graph.

That was my understanding too. If fab198 has done it, maybe he could share with the community so we could build on it further

You have 6 on there? Amazing. I didn't think 6 was possible at all, thought we were stuck on 5.2. did you have to do anything special to get 6 on there?

Good afternoon all, and a happy new year to you all. So I use VMWare ESXi to host my Synology 6.2 - and though I know there's a plugin to retrieve SMART data, for me it doesn't work. Presumably because my server is a mish mash of random hardware; that or I'm too lazy to bugfix. Something I've wanted to do for as long as I can remember is to extract SMART data from ESXi and add to a database, then present it as a website that's super easy to read. What the site does Well, as you can see from the image below, I have ESXi SMART data presented in an easy to read f

@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!