duggleb  Freshman Member

Thanks. It seems it was a Firmware problem. When I did a NAS "Check for Updates" was told that I was up tp date but this was untrue. Downloading the latest Firmware (V5.21(AAZF.14)) instead of the .90 I had , installed and the USB caddy is now accepted OK. It also seems to have solved a niggle that one of the USB drives…

Thanks but when I run ls /dev/sd? I get /dev/sda /dev/sdd /dev/sdi /dev/sdl /dev/sdo /dev/sdr /dev/sdu /dev/sdx /dev/sdb /dev/sdg /dev/sdj /dev/sdm /dev/sdp /dev/sds /dev/sdv /dev/sdy /dev/sdc /dev/sdh /dev/sdk /dev/sdn /dev/sdq /dev/sdt /dev/sdw /dev/sdz I have 2 internal disks, 2 USB connected disks so where do the other…

Followup HAve got the new drive to be recognised, but then later it has dropped out again. If I power off the drive, power it back on, then unplug and reconnect the USB the drive reappears for a while, but then drops out again

pity YOU don't seem able to CRACK the regular 100% CPU usage on the NAS326, the only fix being a Reboot (in 2023???)

Hi Ijnrsi Couldn't get WINscp to work. In the end I used cp to copy twonkyserver.ini to a shared folder I could access, edited it using a windows editor & then copied it back again. Restarted the NAS and at the moment the Twonky Media Service does work, and all my videos are visible under the TwonkServer icon in windows…

Thanks Ijnrsi Excuse the ignorance, but how do I export/import the INI file? Secondly, if I try your suggestion "/usr/local/btn/reset_and_reboot.sh", this will not affect any of the data on NAS, unlike when I did a system reset & lost all my data

I've had issues as well 1) the Twonky Media Server no longer works, It's there, allegedly on poor 9001, but you can't connect to it and looking at the TwonkyServer.INI file the HTTPPort=(nothing)..WOW 2) getting frequent 'stalling' when accessing for file copies or access. Using GUI control Panel the widget shows CPU=100%…

Using your Telnet advice Just looked at my twonkyserver.ini and see that httpport= (nothing) Allegedly the Media Server is enabled, 192.168.1.80:9001 (according to GUI) but when I change any Media Server | Share Publish I'm back to the dreaded "Unexpected Error"

IUsing your Telnet Trick I managed to find where the "disappeared" files were saved, and have moved them using the "File Manager | Drag | Move" option, but I need to perform teh Drag / Move twice for each folder. Is this by design or just a "Funny" on my NAS?

Just looked at my twonkyserver.ini and see that httpport= (nothing) Allegedly the Media Server is enabled, 192.168.1.80:9001 (according to GUI) but when I change any Media Server | Share Publish I'm back to the dreaded "Unexpected Error"

Thanks, the telnet does work, and I can see the files. However I can't do a block copy but have to move into each subfolder in turn & copy the files. It's a pain but I can at least get my files out.

Problem is the non-default folder doesn't even appear When I look at Storage Manager | Internal Storage | Volume | Volume on Disk Group 1 I see The Folder ("Data"), that it's ext4, and is 246GB (about right) but I just cant get that to appear as a folder in my File Manager, I can't see how to include a screen capture image…

until ~I find out if I can reconnect to my lost data I'm reluctant to do much with the NAS

No, the Twonky server link just gave a "Page not Found" In desperation I did a "factory reset" as it states in the manual the stored "Volume Data is not changed" but since then I now have a fully functioning Twonky Media Server, BUT, I can't see any of the data I'd put on the disks. I know it's there and the Storage…

I can't get into the TWONKY Management Page, all I have is Service | Media Server | Enable Twonky Media Server which is checked, but can't go any further, used to be able to! When I click I get redirected to "http://192.168.1.80:9001" but the page that comes up is "This site can’t be reached 192.168.1.80 refused to…