shomrighausen

Members
  • Content Count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About shomrighausen

  • Rank
    Newbie
  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: dis
  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. Additionall
  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 i
  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
  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 find.synology.com 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