Hello, Here is an update. I could not make the OMV5 GUI network settings work, but I set up the IP and DNS manually and it worked!! Now everything is working! But the SMB still slower than the stock firmware. I am getting 60MB/s with OMV5, while the stock firmware transfer speed is about 105MB/s. I tried to use the stock SMB settings, it didn't make any effect. Iperf tests showsby nickba - Debian
Thanks for replying and for the suggestion. I will keep trying to find a way to make it work. This is the last piece of the puzzle to make OMV5 work...by nickba - Debian
Hi, I need some help here. I installed OMV, but after I edit any network setting in the web interface, if I reboot, I cannot access the NAS anymore. I connected it by the serial cable and I can see that it can't configure the network during the boot: Failed to start Wait for Network to be Configured. See 'systemctl status systemd-networkd-wait-online.service' for details.by nickba - Debian
Thanks for replying. Just tested it. It was already disabled. I enabled it just to test and it got slower. So I set it back to off. Any other suggestion?by nickba - Debian
Thanks for replying. How can I turn off network flow control in the NAS326?by nickba - Debian
Thanks for replying. Sorry for asking, but how can I run Debian with the stock kernel?by nickba - Debian
Thanks for replying. Everything I tried so far didn't change the transfer speed. Do you have any suggestion I could try?by nickba - Debian
Hi, I decided to create this thread to try to find the optimal Samba parameters to achieve maximum read/write speeds when using OMV installed on NAS326. With the stock firmware I was able to achieve about 105MB/s read/write speeds and with Debian and OMV 5 installed I get around 60MB/s read/write. Any suggestions?by nickba - Debian
Hi, Thanks for all the info. I hope the picture I sent in my last post could be useful. I tested the HDD boot a little bit more and seems it is not reliable. Sometimes it boots and sometimes it doesn't. Seems the problem is the quirk you already described. If I interrupt the serial console and run sata_init and wait for the HDD to be detected and issue a reset command, it works every time!!by nickba - Debian
Hello and thanks for replying again. I will try to find the FTDI RS232 TTL adapter I have to connect it to serial console. As I already formatted the HDD with the rootfs, could you tell if it should work with ext4 too? I am asking that because ext3 takes a long time to format. Update1: I uploaded a picture of the NAS326 board, as I saw you only have a picture of the NAS325. Update2: I haby nickba - Debian
Hi again, Tried to boot from HDD, but the NAS get stuck. If I remove the HDD, it falls back to stock firmware. I tried with only one HDD installed and with both. I checked the envs and tried a lot of times and always get the same result. Do you know if there is a partition size limit? It is a 8TB HDD. I tried with the HDD formatted as EXT3 and also tried it as EXT4. Should it work with EXT4 tby nickba - Debian
Bodhi, Thank you! I will try booting directly from HDD and use your suggested Samba config!!by nickba - Debian
Hello again, I decided to install Debian again and I installed Open Media Vault. I noticed the Samba transfer speed is about 40MB/s read and write and the stock firmware is about 100MB/s read and write. Is there a tweak that I can make to approach the stock speeds? Do you think it could be because I am booting from an USB Flash Drive?by nickba - Debian
Thanks again for replying! You were completely right!! After I went back to stock I was not logging as root!! Problem solved! Sorry for the trouble. Congratulations for your great tutorial, it works great! Thank you very much!by nickba - Debian
Thanks again for replying. I deleted the /var/lock/fw_printenv.lock, but after a reboot, it is there again! And the /etc/fw_env.config just have this: # Configuration file for fw_(printenv/saveenv) utility. # Up to two entries are valid, in this case the redundant # environment sector is assumed present. # Notice, that the "Number of sectors" is ignored on NOR and SPI-dataflasby nickba - Debian
Thanks for replying. Even with the error, the Nas326 is working with stock firmware now, but the fw_printenv only return this error. Do you know if the fw_setenv commands are stored in a file? Before installing Debian, I used the fw_printenv command and I saved all parameters in a file. Is there a way to restore it? Or it is not needed?by nickba - Debian
Hi, I have a Nas326 and I installed Debian using your tutorial. I decided to go back to stock firmware. After that I reset the NAS to factory defaults pressing the reset button(3 beeps). After that I noticed the firmware were a version earlier!! So I updated the firmware again. After that I SSH it to check the fw_printenv and I received the message: Error opening lock file /var/lock/fw_printeby nickba - Debian