Latest Firmware Update (5.1.3.RI81)
Is anyone having issues since updating to this version?
Is anyone having issues since updating to this version?
So my mother dropped my Asustor AS5402T early in the afternoon, and told me when I’m back home at night. I saw a feint physical crack in the exterior, and the lights are still on, but I can’t connect it to my Macbook location as it usually does, nor can I access it in Ezconnect with lans as usual. I checked that it is ‘uninitialised’ now, and I tried pulling out the hard disks and back in but the status remains the same.
What should I do?
Ok home Asustor. I am looking for some input.
I have a reasonable home lab, but I am disappointed with my NAS. Its a Asustor Lockstar Gen2 6 6706t.. 6x14tb, 64Gb ram, a 4Tb SSD.. Nice.. Raid 5.
However when doing thumbnails it sucks, very laggy, and really seems to be hit hard with raid 5 thrashing.. My AI image server is pointing to this, so generating hundreds of large many Mb images, and then when trying to view all the mess its making the thrashing for thumbnails. It can take 20-30 seconds to get one thumbnail (but then lots come in pretty soon I assume its creating 10 thumb nails at the same time and not caching writes.).
I was looking at using 2 x 16Gb Optanes as cache (you need two under raid, although it will do Raid5 with 3 - but I want to keep my 4tb NVME as a workspace, and I have 10GbE AQ113 nvme to add 10GbE to it).
I thought the ram would solve my problem, but it doesn't seem to be caching writes, and it doesn't solve the raid 5 problems with small files. Seems great for reads.
Is 2 x 16Gb Optane enough, it would seem to be enough for small files ~30mb, low latency, high endurance. I have some 512Gb PCIE4 NVME I can use, but that seems like a waste for just cache, and honestly I worry about write cycles.. I have loads of ram for network buffering and read buffering, but the write stuff particularly with small files across a 6 drive raid 5 is painful. Sustain writes are fine..
These 16Gb Optane are cheap.. $10 USD delivered. Would this solve my problem and does anyone else use them? While 16Gb isn't that big, its still almost a minute of 2.5GbE bandwidth. So when writing lots of small files intermixed with reads, or thumbnailing etc it would seem to offer a big performance boost. It has lots of ram, the disks are fast, and I have 4tb nvme in there anyway.
Is anyone else using these?
Updated my AS3104T to firmware 4.3.3.RUN1, and it broke Iptables killing my Docker containers.
I've created a support ticket.
Please be advised if you are running Docker containers.
Edit: Solution ahead, beware with downgrading (I take no responsibility), but it worked great for me with no issues.
Download ADM Firmware 4.3.3.RTB1 from https://www.asustor.com/en/service/downloads_all_adm?product_id=59
Edit the following file in /etc/nas.conf
Change following values to the following:
version = "4.3.3.RSU1" Lastversion = "4.3.3.RSU1" Baseversion = "4.3.3.RSU1"
Do a manual update in Asustor ADM, and update with the firmware file you just downloaded.
Hi All,
As the title says it all, I have an ASUSTOR 1102TL. I installed NextCloud and was set up and worked. I was able to access the shared folder using the URL and uploaded files remotely without any issue.
All of a sudden, the NextCloud shared folder is inaccessible via URL. I see it installed through AppCentral, but cannot open.. I attempted to uninstall and reinstall and still cannot open.
Any ideas how to get NextCloud working again? ADM firmware is current. NextCloud version current.
Hi there, …an inexperienced NAS owner here. I desperately need some technical advice and a little bit of tolerance from you guys, mostly due to my silly questions...
I got a Lockerstor 4 AS6704T a few months ago and set it up with 4 x 6TB NAS HDDs. After tinkering with it a couple weeks, I just turned it off and put it away as I had to focus on my other projects, mainly local LLMs in a dedicated PC.
Yesterday I turned on my Asustor NAS again and wanted to access the NAS via its graphic user interface – the log in screen - with no success. ACC failed to find the NAS (as usual). When I checked the IP number on the screen of the NAS, I noticed the IP was not the same I used the last time. I tried the new local IP (192.168.0.30) but this time, instead of a graphic UI, I got this page (see the photos) with a message saying “Congratulations! You have successfully enabled the Web server on your Asustor NAS”. Now I have no idea when and why I did that, but even if I did it, I was still able to access the graphic UI before I turned off the NAS and put it away… I don’t know what has changed since then?
By the way, I am able to reach the NAS through windows explorer under the NETWORK so whatever I installed initially is still there, but I am a typical windows fan boy who needs the visual interface to function…☹ I have tried resetting the NAS through the pin hole at the back using a needle, but it just didn’t work, nothing changed. Other ways of resetting the device requires logging in the software, so I am literally out of options with my limited technical skills.
How can I disable this web server and access the Log in screen? Any help would be highly appreciated… thank you all in advance 😊
I've had an Asustor for about 5 years, for simple home / family use, happily doing its thing and backing up to a cloud service (BackBlaze) daily.
I noticed by chance last week that the backup jobs have been failing for about a month and although I have it set to email system alerts, this didn't apply to the Cloud Backup Centre app. Having a dig around it appears that the app places an entry to the System Log for job creation / job deletion, but not job started / completed / failed. The app does record these events but it seems to do it in another database, accessed from within the app.
My request is to have these log entries sent to me, but I can't figure out how (without going down the line of writing a cron job to read the app log and email me).
(The other side of the problem is there was an issue getting data to BackBlaze that they weren't helpful in resolving. I fixed that in the end by simply creating a new bucket (didn't change any other settings), which indicates the bucket on BackBlaze was not as it should be.)
EDITED : As it turns out the functionality isn't in the product, I created a script to read Cloud Backup Centre's log database, format each job (success or failure) into a readable line and runs every morning at 06:00 via cron, emailing results (remembering what has already been sent). Works a treat