• Announcements

    • Polanskiman

      DSM 6.2-23739   05/23/2018

      This is a MAJOR update of DSM. DO NOT UPDATE TO DSM 6.2 with Jun's loader 1.02b or earlier. Your box will be bricked.  You have been warned.   https://www.synology.com/en-global/releaseNote/DS3615xs

bigsid

New Members
  • Content count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About bigsid

  • Rank
    Newbie
  1. Hi, I'm running DSM 5.0-4493 with Nanoboot and I'm trying to present iSCSI Block LUNs to an ESXi 5.5 server. The problem I have is that when I configure the Software iSCSI HBA on ESX and perform a rescan the ESXi server hangs for about 30 minutes before eventually displaying an error in the vSphere Client which looks like this... http://puu.sh/9F25w/b92e6bcd9c.png In the vmkwarning.log I see the following errors continuously between starting the rescan and the error occuring... 2014-06-22T13:16:22.589Z cpu1:32937)WARNING: ScsiPath: 6292: Set retry timeout for failed TaskMgmt abort for CmdSN 0x0, status Failure, path vmhba33:C0:T1:L0 2014-06-22T13:16:32.589Z cpu0:37422)WARNING: ScsiPath: 6292: Set retry timeout for failed TaskMgmt abort for CmdSN 0x0, status Failure, path vmhba33:C0:T1:L0 2014-06-22T13:16:32.589Z cpu1:35151)WARNING: iscsi_vmk: iscsivmk_TaskMgmtIssue: vmhba33:CH:0 T:1 L:0 : Task mgmt "Abort Task" with itt=0x7e (refITT=0x2e) timed out. 2014-06-22T13:16:42.592Z cpu1:35151)WARNING: iscsi_vmk: iscsivmk_TaskMgmtIssue: vmhba33:CH:0 T:1 L:0 : Task mgmt "Abort Task" with itt=0x80 (refITT=0x2d) timed out. 2014-06-22T13:16:52.592Z cpu0:35151)WARNING: iscsi_vmk: iscsivmk_TaskMgmtIssue: vmhba33:CH:0 T:1 L:0 : Task mgmt "Abort Task" with itt=0x81 (refITT=0x15) timed out. 2014-06-22T13:17:02.593Z cpu0:35151)WARNING: iscsi_vmk: iscsivmk_TaskMgmtIssue: vmhba33:CH:0 T:1 L:0 : Task mgmt "Abort Task" with itt=0x82 (refITT=0x22) timed out. It works fine with ISCSI File LUNs but when I try to configure iSCSI using a Block LUN this happens. Has anyone been able to get iSCSI Block working with ESXi 5.5 and DSM 5.0? Many Thanks
  2. Enabling SSD Cache Crashes System

    I've been playing around with this a lot today. I upgraded to from DSM 4.3 to DSM 5.0 with nanoboot to see if that made a difference. I was able to successfully configured SSD cache (DSM 5.0 also supports write caching it seems). Once thing I noticed however, that is common across both DSM 4.3 and 5.0. If you try to enable SSD Caching for a Volume it doesn't work. On 4.3 it crashes the system. On 5.0 it crashes the volume until you remove the SSD cache and then it goes back online with a status of normal. The only time I was able to successfully activate SSD cache was against an iSCSI LUN (Block NOT file). The only problem I have then, is that iSCSI Block LUNs don't seem to work with ESXi 5.5 U1. When I try to configure the iSCSI adapter and target on ESXi it hangs the ESXi system, and the vmkwarning.log is full of iSCSI "wait abort" and "timeout" errors.
  3. Hi, I'm new to XPEnology and recently purchased hardware to build my own NAS. Everything seems to be OK, except when I try to enable SSD Cache the system crashes. I bought 2 Plextor PX-0128M5S 128GB SSD as they showed as compatible for SSD cache on the Synology website see (http://puu.sh/9Bk6b/373666d309.png). The SSDs are reported as the same when I run syno_hdd_util --ssd_detect... DiskStation> syno_hdd_util --ssd_detect Model Firmware SN Dev is SSD? WD1002FAEX-00Y9A0 05.01D05 WD-WCAW30439621 /dev/sdg no ST3000DM001-1CH166 CC46 Z1F3JALX /dev/sdf no PX-128M5S 1.05 P02411111937 /dev/sde yes PX-128M5S 1.05 P02411111938 /dev/sdd yes WD30EFRX-68EUZN0 80.00A80 WD-WMC4N1680036 /dev/sdc no WD30EFRX-68EUZN0 80.00A80 WD-WMC4N2035566 /dev/sdb no WD30EFRX-68EUZN0 80.00A80 WD-WMC4N2034714 /dev/sda no If this is not right, please kindly report this to us When I try to create an SSD cache, it shows up the two disks but says they are not compatible: (http://puu.sh/9Bkf0/2b400d1da0.jpg). If I go ahead and try to create an SSD cache anyway, it comes up showing me the following screen: (http://puu.sh/9BksQ/6f89ea423b.png) then the system crashes. It stops responding, SSH sessions timeout, and on the console it comes up with a load of errors I don't understand, ending with [ end trace bff70cf8fdd00e94 ]. I can't scroll back up on the console to see anything more meaningful in the error. System Information is as follows: Model Name - DS3612xs CPU - 3.39GHz Cores - 1 Memory - 8192MB DSM Version - DSM 4.3-3810 Thanks