First problem is that it WOULD NOT let me select SAMBA 4. At all. It ignored me. This kept Windows 10 from wanting to access shares. ACtivated CIFS1 in Windows.
Drive access is 50% the speed of what it was with Seagate firmware.
Attempted to use dd to see if it was disk access or SMB; version of included dd doesn't display speed.
Updated to 18-2.
Locked out of web console. It no longer accepts the set password or previous passwords. Can access via user; but that gets me nothing.
Update:
Wiped everything and started over from 18-1; upgraded to 18-2 without setting web interface password. This kept things working.
Still cannot get Samba 4 to actually work. Guess I will poke around a shell.
Update 2.0:
Lousy performance via SMB was due to the old SMB stuff I had to activate in order to make a SMB connection to this. Not an issue as I really didn't plan on using SMB directly from the device in the first place.
- Code: Select all
hdparm -Tt /dev/sda
/dev/sda:
Timing cached reads: 1090 MB in 2.00 seconds = 545.26 MB/sec
Timing buffered disk reads: 490 MB in 3.01 seconds = 162.94 MB/sec
Ok...so I can at least confirm data reads are what they should. dd doesn't display write speeds; no compilers to actually update coreutils.
sftp as normal yielded 3MB/s writes; likely something screwy with the configuration involving separate sftp option for port 8022. Ok.
Activated FTP. Can upload around 40MB/s and download around 60MB/s. I don't remember what write performance was with Seagate NASOS; but I do know 70 to 80MB/s over SMB was average on very large files.
I hadn't planned on using samba directly anyway and routing through a VM with a dedicated connection/network between PersonalCloud and virtualization machine. So I'll set up an nfs share; power the thing down, plug it in to the rack and see if at least my read speeds are acceptable.