[Internal Network file transfers extremely slow (5mbps)]

I didn't know what the problem was, but I reinstalled DSM ages ago and I no longer have the issue now.

[DSM 6.1.6-15266 Update 1]

- Outcome of the update: SUCCESSFUL

- DSM version prior update: DSM 6.1.6-15266

- Loader version and model: JUN'S LOADER v1.02b - DS3617xs

-  Using custom extra.lzma: NO

- Installation type: BAREMETAL - Custom (AMD)

- Additional comments: NO REBOOT REQUIRED

[Greetings. VMM not working.]

Very similar to Centeredki69's post. I don't need VM, just would have been nice. The apps I needed the VM for run just fine in Docker.

 

[Internal Network file transfers extremely slow (5mbps)]

Greetings again. I have another issue. It seems my internal network is really slow. I'm trying to figure out how to fix it.

When I transfer files, upload to the server is extremely slow. It tends to maintain around 5 mbps though it has a range of 1 to 8 mbps. I'm gonna assume that internet transfers will also see the same rate, but I can't properly test as I only have a single 30/5 downstream/upstream connection. Downloads from the server is only slightly better. Haven't thoroughly tested, but estimated at 11 mbps. Tested clients include Alienware 17 R4 running Windows 10 Fall Creators Update and Samsung Galaxy Note 5 running Android 6.0.1 using SMB, Browser, Drive Client, and DS Files for Android.

 

Spoiler

CPU: AMD Phenom II X4 965

MoBo: Biostar TA970 Version 5.3

LAN: Realtek RTL8111F - 10/100/1000 Controller

Ram: 24 GB

BootLoader: Jun Loader 1.02b

DSM Version: 6.1.4-15217 Update 3

 

Spoiler

Disk 1 and 3 is configured as Raid 0 and set up as the main storage. Disk 2 and 4 are Raid 1 RW SSD Cache.

 

This is the Resource Monitor log during the Bandwidth test. 1.05 GBPS write is pretty impressive imho. Too bad I can't make full use of it. Please note that due to my RAID configuration that I wasn't able to test for write speeds using the Bandwidth tester.

  

Spoiler

1+0 records in
1+0 records out
1073741824 bytes (1.1 GB) copied, 13.8489 s, 77.5 MB/s

 

Spoiler

Disk /dev/sda: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 3F771EAF-D55F-11E7-86FE-B8975AD1CE17

Device       Start        End    Sectors  Size Type
/dev/sda1     2048    4982527    4980480  2.4G Linux RAID
/dev/sda2  4982528    9176831    4194304    2G Linux RAID
/dev/sda3  9437184 7813832351 7804395168  3.6T Linux RAID

Disk /dev/sdb: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x46d52e00

Device     Boot Start       End   Sectors   Size Id Type
/dev/sdb1        2048 488392064 488390017 232.9G fd Linux raid autodetect

Disk /dev/sdc: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x3f4578a5

Device     Boot   Start       End   Sectors   Size Id Type
/dev/sdc1          2048   4982527   4980480   2.4G fd Linux raid autodetect
/dev/sdc2       4982528   9176831   4194304     2G fd Linux raid autodetect
/dev/sdc3       9437184 976568351 967131168 461.2G fd Linux raid autodetect

Disk /dev/sdd: 58.7 GiB, 63023063040 bytes, 123091920 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x634360f1

Device     Boot Start       End   Sectors  Size Id Type
/dev/sdd1        2048 123090029 123087982 58.7G fd Linux raid autodetect

Disk /dev/md0: 2.4 GiB, 2549940224 bytes, 4980352 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/md1: 2 GiB, 2147418112 bytes, 4194176 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/zram0: 3.5 GiB, 3791650816 bytes, 925696 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/zram1: 3.5 GiB, 3791650816 bytes, 925696 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/zram2: 3.5 GiB, 3791650816 bytes, 925696 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/zram3: 3.5 GiB, 3791650816 bytes, 925696 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/md2: 4.1 TiB, 4491019354112 bytes, 8771522176 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 65536 bytes / 131072 bytes

Disk /dev/md3: 58.7 GiB, 63019941888 bytes, 123085824 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mapper/cachedev_0: 4.1 TiB, 4491019354112 bytes, 8771522176 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

 

Spoiler

Modem/Router Combo: Arris TG1672G (provided by Time Warner Cable)

Server is connected via a 50 ft CAT 7 Ethernet directly to the above modem via the Ethernet port on the MoBo.

All clients are connected wirelessly via the 5 GHz band on 802.11n.

Configured to use 1000 Full Duplex on server, modem, and all connected wireless devices.

[Greetings. VMM not working.]

Greeting. I am having trouble getting VMM (Virtual Machine Manager) to work. If it matters, I'm using an AMD Phenom II 965 on a Biostar TA970 mobo with 24 GB of RAM.

 

Using Jun Loader 1.02b and DSM 6.1.4-15217 Update 3. Jun Loader is unmodified, except the Grub.cfg, where "disable_mtrr_trim" was added to make full use of available memory. I tried replacing zimage with the file found at *below* for better AMD support, but it wouldn't connect to the internet. find.synology.com couldn't find it either and my router wasn't leasing an ip to it.

 

 

Error  

Failed to power on the virtual machine Windows 10 due to insufficient memory on the host. 

Possible solutions: 
1. Choose another host. 
2. Decrease the memory size on the virtual machine. 
3. Decrease the number of running virtual machines on the host. 
 

Hide  

 

Memory - Resource Monitor  

Hide  

[Greetings. Reserved Ram is absurdly high. (over 20gb)]

Issue resolved. I have other issues, but I will open a new thread for them.

[Greetings. Reserved Ram is absurdly high. (over 20gb)]

Sorry, forgot the most important bit. Using Jun Loader 1.02b and DSM 6.1.4-15217 Update 3

[Greetings. Reserved Ram is absurdly high. (over 20gb)]

Greetings. First, I wanted to pay my respects to the team who make Xpenology possible. Thank you.

 

Now, as you can see from the screenshot below, my system has 24 GB of ram, but 20.8 GB of it is reserved and seeming unusable. How does one fix this?

 

Screenshot:  

Hide  

 

I'm still new to Linux and BSD operating systems, but I do know some ssh commands. I know how to use Putty and WinSCP as well as editting files in nano and basic file/directory management commands, such as rm, rmdir, mkdir, chmod, chown.