• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About shomrighausen

  • Rank
  1. I believe [0] = disabled. You can see the options for the syno_disk_ctl command by typing it without additional arguements. It should look something like this: Copyright (c) 2003-2014 Synology Inc. All rights reserved. Usage: synology disk control device: something like /dev/hda or /dev/sda options: ?: print this message --ncq-off: turn off ncq ex: syno_disk_ctl --ncq-off /dev/sda --wcache-off: turn off write cache and tell kernel don't allow open it anymore ex: syno_disk_ctl --wcache-off /dev/sda --wd-idle: Read, Set or disable the idle3 timer of Western Digital drives -d: disable wd idle3 timer ex: syno_disk_ctl --wd-idle -d /dev/sda -g: get wd disk idle3 timer ex: syno_disk_ctl --wd-idle -g /dev/sda -s: set wd disk idle3 timer ex: syno_disk_ctl --wd-idle -s80 /dev/sda fail iRet -1 If you notice the options for the --wd-idle arguement, you will find '-d' is an option - to disable the timer. After issuing the command 'syno_disk_ctl -d /dev/sd?' - where '?' is each WD drive in your system, it they should all be disabled. If it was already disabled, you should get a message like this: /dev/sdf already disable WD idle3 timer When you issue 'syno_disk_ctl -g /dev/sd?' - where '?' is each WD drive in your system, it should return output of: Get /dev/sdf WD idle3 timer [0] successfully
  2. If you have SSH enabled on your NAS, you can SSH into the server and issue the command 'cat proc/cpuinfo'. This will provide information about the processor identified by the underlying OS. It will give you information for each of the cores (or hyper-threaded cores) for your CPU. You should see 0 through 3 for the processor numbers if you have a quad core (or hyper-threaded dual core).
  3. I'm testing the speed of the disk locally on the NAS. You can SSH into the NAS and run this command to test the volume/device in question: 'hdparm -Tt /dev/md2' <---- generally volume1 within DSM Run it five separate times and manually average. It will output cached and buffered speeds in MB/s. This will help you find the volumes on your NAS: 'cat /proc/mdstat' <----- will provide a list of file systems. 'df' <----- will provide a list of disk usage information. This shows /dev/md0 as 2451064 1k blocks on each XPEnology system that I have. Additionally, you should be able to identify the device for the main volume via lvm - it may be something like /dev/vg1000/lv. You could run 'hdparm -Tt /dev/vg1000/lv' to get the speed of that volume. You will be bound by the network speed - if you have a 10GB network card in the NAS, you should be able to get greater than 1GB speeds, assuming that your client also has a 10GB card. If you only have 10GB on the NAS and 1GB on each client, you'll only get 1GB speed during the network-based tests. Additionally, there are some tweaks that you can make to the /etc/sysctl.conf to provide additional network throughput, based on the 1GB+ network configuration. In my environment, I have four 1GB NICs bound together on the NAS and have several clients with 2 x 1GB NICs. Additionally, I run VirtualBox with some VMs locally on the NAS. These benefit greatly from additional disk speed, as they are 'local' on the NAS. I can easily bury 2x1GB NIC bandwidth transferring large files. I suspect that I could do the same if I had additional NICs paired up on both the NAS and the clients. Ultimately, the network is the funnel that you're trying to fill.
  4. I setup my DS1512+ with 3x1TB and added a single drive as SSD cache. It created /dev/md3 for the SSD, I'm still digging to find out what else changes to try to figure out what the missing components are within XPEnology. I suspect that it is something simple. Creating the SSD cache was much faster than I thought, after watching the failed 'mounting' message within Storage Manager while trying to create the SSD cache in XPEnology. I understand that I could just create a separate volume with a pair of SSD drives. I'd like to see what type of increase/decrease in performance I would see in my environment - with the SSD cache on the single volume that I use. I expect that it would slow down the sequential data transfer, but there was an option to disable the cache for sequential data. Some interesting numbers doing 'hdparm -Tt /dev/md?' testing average of 5 runs: System cached (MB/s) buffered (MB/s) DS1512+ (3x1TB SHR) 908 187.5 DS1512+ (SSD-256GB R0) 941 249.8 DS214se (2x4TB R0) 373 139.8 XPEN x5460 (5x6TB SHR) 6667 424.3 XPEN 3800+ (5x4TB SHR) 830 249.8 If I understand correctly, the cached number tests the throughput of the system without the disk in the mix. The buffered number is essentially sequential read speed with no RAM caching by the system - this should represent sustained sequential read speed. It shows that the SSD cache performs at a higher level of sequential read than the 3x1TB array (both in the DS1512+). Given these results, my current SSD is limited by he hardware - it's a Samsung 830 and should perform at around 488 MB/s sequential ( ... _830_256GB). I believe the current 'flagship' SSD push the number to around 525MB/s ( ... _PRO_512GB). Given that the sequential speed of my x5460-based XPEnology system is already over 400MB/s, the SSD cache would provide little (if any) increase in performance for sequential data transfer. If we are talking about NON-sequential data, I hope that the performance of the SSD cache would hit stride and help with performance. I'm not sure if the SSD cache would help with enumeration of directories with a high file count, MariaDB, inbound writes of smaller files, etc. I'd like to find out.
  5. I'm trying to figure out why it doesn't work and possibly find a solution. It seems like it should be straightforward - it may be a matter of understanding what happens on Synology hardware/software. I'm trying to get more information that may help in that regard. I guess ultimately, it's not a showstopper that it's missing, but a 'nice to have' that I believe several folks want (not need). Since I have a few older SSD collecting dust, it's a good use of my time. Any input is welcome.
  6. I will also add... I've done a swap from old Athlon x2 3800+ to Intel Q8200 on nVidia chipset to E5800 on Intel chipset, back to the nVidia chipset with a x5460 Xeon processor... Pull the thumb drive, swap the hard drives to the new system (or swap the system board) - every time it has found the drives and looks like the same NAS. No data lost.
  7. I guess I'll ask another couple of questions... does anyone have SSD cache running on actual Synology hardware? I'm starting to wonder if there is a fundamental change when SSD cache is enabled - like a change to the /dev/md0/1/2/etc. or if there is an additional driver that is missing with XPEnology. I'm hoping to get some information before I take my DS1512+ offline and do some testing.
  8. I believe that I've read all of the threads regarding the non-functioning state of SSD cache. I also verified that I had issues (as described) when trying to create the cache - lock up the NAS/volume. Through further investigation, I read a thread regarding the modification of the /etc/support_ssd.db and /etc.defaults/support_ssd.db files. I've added the information for the SSD drives I had to test with, as follows: [sSD 830 Series] brand="Samsung" size="256GB" [sSD 830 Series] brand="Samsung" size="64GB" I recognize that these are older drives. I have a single 256GB and a pair of 64GB for testing. While I'm able to go through the process for creating the SSD cache (read cache with the single 256GB and read-write cache with the pair of 64GB), the cache creation goes through it's phases and then goes back to screen that lets me click the 'create' button again. The NAS doesn't lockup (which is progress?), but it doesn't successfully create the cache. Does anyone have drives that are on the compatibility list on Synology's site for the DS3615xs to test with? Alternately, has anyone successfully added an SSD cache to their XPEnology NAS? When I go through the process, it appears that it may be testing the SSD(s) for performance or compatibility during the process and they are failing (maybe not enough throughput?) Does anyone know where I can start looking through logs? I guess I'm bored for something to do and this seems like a nice feature that could improve performance... Any insight is appreciated. Thanks.
  9. I successfully installed the original .SPK file and manually updated the four files provided earlier (before the re-packaging). This is on 5.1-5022-update 2. I also tried the re-packaged .SPK file - on a DS1512+, VM running on an i7 and whitebox hardware. The new .SPK file will install successfully, but will never 'run'. I haven't had a chance to dig through the log files, but I suspect that there is an issue with the re-package. I tested on both 5.0-4482 and 5.1-5022-update 2.
  10. I can also confirm that it's working. Tested in generic hardware with an E5700 processor (VT-x enabled).
  11. Additionally, I've spun up a VM on my workstation, installed successfully and tried to reboot to install/upgrade mode and get the same results. The NAS is never showing up in 'upgrade' mode within Synology Assistant.
  12. When I double click the NAS within Synology Assistant, it takes me to the login web page for the NAS. I guess this is where I have the disconnect. If the 'install/upgrade' option on the bootloader menu is supposed to 'reset' the DSM back to an 'install' mode, it doesn't appear to be functioning. I've tried the OSX version of the Synology Assistant, the Windows version of the Synology Assistant and the URL in multiple browers on OSX and Windows... they're all consistent. I think the NAS itself isn't getting 'reset' to the point that it thinks it needs to be installed.
  13. Apologies for the questions, but I've searched the forum and haven't found a clear process to do a rollback or update of the DSM software. My setup is generic x86 hardware (test setup). Four SATA drives, booting off of a thumb drive. I installed 5.1 (the one with the time bomb issue)... a few days later, the time bomb went off. I tried to find the process to rollback/install the 5.0 version. When the new (fixed) version of 5.1 boot loader came online this morning, I eagerly created a replacement thumb drive and booted from it. I chose the installation/upgrade option. When I find the box via Synology Assistant, it eventually comes up with a 'ready' status, instead of allowing me to do an install of the .PAT file. When I try to do the upgrade via the Control Panel, it also fails. What steps am I missing to do an rollback or upgrade? It seems like I should have the option to re-install the DSM software at some point, while leaving my data intact. It's just a test environment, but I'd like to figure this out and make it part of my home lab. I also have two Synology NAS devices at home (DS1512+ and DS214se), so it's not critical, but I would like to understand the process for the 'DIY'-ology...