Will TOS 6 fix all the problems in TOS 5 or at least half of them.

[trasmussen]

Hi,

After reading for many many days i decided for the f4-423

Here are my conclusions so far and there are more i decided to put it in the closet for now its now reliable.
The heat problem is solved but software is horrible hope TOS 6 fixes some of that. And now for 3 days been doing this for now reason guess all data is gone now (see screenshot) https://ibb.co/YXqrccR

1. poor design overheats, have 2 nvme drives and they put them where there is basically no airflow and no room for heatsinks even i they are on their approved list.
2. Bougt the approved Seagate Ironwolf disks but you can have 4 slot 3 constantly overheats, i set the cooling to maximum but now its so noise its unbearable, i switched the cheap original fans and made a mod so it doesn't know, only the temperature. i run the fans on whats equivalent to silent/low on the original.
3. 5 times now i been locked out from gui "wrong username/password" fortunatly there is hdmi and usb so i can log in that way, now i have at least 5 different logins, investigating its a known "bug/feature" but wont disclose.
4. Half of the time after a reboot i can see the shares but not access, again bug in the system.
5. i Have to reinstall it 4 times now
6.5gb bond only supports one mode and is only faultolerance.
I can go on and on and on lesson learned pay the extra for quality have had my Synology's for 7 years running surveillence 24/7 never had a problem.
7. took a screenshot been doing this for days, and im no novice now my stuff
My recommendation build your own or buy a well know brand.

[TMpzhen]

Thank you for your feedback. TOS 6 will give you a different experience, please stay tuned.

[Gremlin]

Thank you for your feedback. TOS 6 will give you a different experience, please stay tuned.

Different is not necessarily better.

(7) The fallacy of non sequitur (“it does not follow”) occurs when there is not even a deceptively plausible appearance of valid reasoning, because there is an obvious lack of connection between the given premises and the conclusion drawn from them.

[TMroy]

We apologize for the poor user experience you have encountered. F4-423 and TOS 5.1 are the models and system versions that are currently being used by a large number of users. I'm curious that the issues you've reported haven't occurred frequently among other users, which means that some of the issues you've raised are not representative. Let's analyze the issues you've faced one by one.

1. Because of space limitation, the reserved space for F4-423 is not sufficient to prevent overheating of SSDs with higher heat sinks. right now you can only install 3mm height heat sinks.

2. Seagate Ironwolf and WD RED are two types of hard drives that we use extensively, but so far, we have not received any reports of overheating or alarms for these two types of hard drives. May I ask what temperature you refer to as overheating? And what was the fan speed at that time?

3. If you are sure that you have entered the correct username and password during login, but the system prompts "Username or password is incorrect!", it means that your system database is corrupted and the username cannot be found. This is an unusual error! If it happens frequently, you need to check if there is a fault with your hard drive.

4. It is because the database is damaged and the username cannot be found, so the system cannot verify your access, resulting in your access failure!

5. If this happens after reinstalling five times, please check the health status of your disk.

6. What do you mean by "5GB bond"? There are several types of bond modes, and your choice depends on what purpose you need to achieve.

I'm sorry, but the information you provided has not convinced me that these malfunction symptoms are related to a system bug. I hope you can try other methods based on my suggestions to solve the problem you encountered.

[curlsoybean]

We apologize for the poor user experience you have encountered. F4-423 and TOS 5.1 are the models and system versions that are currently being used by a large number of users. I'm curious that the issues you've reported haven't occurred frequently among other users, which means that some of the issues you've raised are not representative. Let's analyze the issues you've faced one by one.

1. Because of space limitation, the reserved space for F4-423 is not sufficient to prevent overheating of SSDs with higher heat sinks. right now you can only install 3mm height heat sinks.

2. Seagate Ironwolf and WD RED are two types of hard drives that we use extensively, but so far, we have not received any reports of overheating or alarms for these two types of hard drives. May I ask what temperature you refer to as overheating? And what was the fan speed at that time?

3. If you are sure that you have entered the correct username and password during login, but the system prompts "Username or password is incorrect!", it means that your system database is corrupted and the username cannot be found. This is an unusual error! If it happens frequently, you need to check if there is a fault with your hard drive.

4. It is because the database is damaged and the username cannot be found, so the system cannot verify your access, resulting in your access failure!

5. If this happens after reinstalling five times, please check the health status of your disk.

6. What do you mean by "5GB bond"? There are several types of bond modes, and your choice depends on what purpose you need to achieve.

I'm sorry, but the information you provided has not convinced me that these malfunction symptoms are related to a system bug. I hope you can try other methods based on my suggestions to solve the problem you encountered.

I've been using Seagate Ironwolf and WD RED for over a year now. I haven't had any problems with it at all. It seems that the reviews from the above article are not really objective

[trasmussen]

Hi,

1. Because of space limitation, the reserved space for F4-423 is not sufficient to prevent overheating of SSDs with higher heat sinks. right now you can only install 3mm height heat sinks.

Answer - My solution was installing heatsinks they dont overheat any more (the nvme drives that is). I know that limitation well with the heatsinks, the heat issue arises under heavier load, and due to lack of good ventilatiom, but funny enough the one nvm is generally 10C cooler always.
Fan speed is as full speed set manually as i got that advice. I even put a table ventilator to solve the constant overheating.

2. Seagate Ironwolf and WD RED are two types of hard drives that we use extensively, but so far, we have not received any reports of overheating or alarms for these two types of hard drives. May I ask what temperature you refer to as overheating? And what was the fan speed at that time?

Answer - I agree WD Red and Ironwolf drives are some of the most reliable and was bought according to yuor list of approved drives. i have used them in my NAS's and in my oldest since 2012 (swapped drives in one of them for bigger in 2018 as it been running surveillance recording 24/7 for all that time)i only have had a predictive failure once so swapped just to be safe. Same goes for my Seagates no errors.
Current temp in my old DS413 with WD drives all hold 25C WDC Red drives.
The drives and this is kind of funny bay 1,2,4 is the only ones overheating (60C) bay 3 is fine funny enough at max 40 C. Same raid workload and so on. I have screenshots and was sure i posted it here, problem is they are probably only on the tnas. Which is not working.
As for fanspeed i was recommended to manually set it to full speed which didnt do much other than create noise. So ended up putting a table fan blowing air 24/7 and that helped alot.

3. If you are sure that you have entered the correct username and password during login, but the system prompts "Username or password is incorrect!", it means that your system database is corrupted and the username cannot be found. This is an unusual error! If it happens frequently, you need to check if there is a fault with your hard drive.

Answer - was a bit scary fortunatly there is usb and hdmi on the back and a way in, funny thing it was only the master/root username that got affected i always have more than one admin account in case of emergency and it has never happened to the other admin accounts.
I log in with the secone account reset the password then i can log in again.

4. It is because the database is damaged and the username cannot be found, so the system cannot verify your access, resulting in your access failure!

Answer - a bit scary but there is a fix but dont think most users have the knowlegde.

5. If this happens after reinstalling five times, please check the health status of your disk.

Answer - i Did

6. What do you mean by "5GB bond"? There are several types of bond modes, and your choice depends on what purpose you need to achieve.

Answer 2.5GB x2 bond, LAG - but nm that

[TMroy]

Thank you for your feedback!
1. I am glad to know you have heatsinks installed.

2. when a drive overheat, the only possibility is that the drive is busy and fan does not work properly. But it seems that your situation is not like this, which is hard to understand. What type of array did you create? Is the overheating disk busy?

3. When the superuser lost its login next time, can we have a remote session to check out the issue?

4. I still don't quite understand why you only get one option when creating a bond.

[trasmussen]

Hi,

Update

1- i created a new usb boot stick and booted it in init mode.

2 - I ran the TNAS desktop app, found the nas, downloaded the common_bootloader_V5.1.48.img and installed that.
Then manually choose TOS_X642.0_5.1.131_00123_2404261051.ins to install and to a clean new HDD
It booted up fine and seemed all ok so i inserted the 3 normal HDD's (whích was in a traid config and is Seagate Ironwolf ST6000NT001 ) and after a while all the files and shares appeard and worked fine.
And all was accessible from my pc's and nas's too (after some minor config)

3 - I set up the bond this time i had 4 options to choose from so used Balance-alb as its called in TOS all worked great and with full speed too.

Great i thought happy after spending some hrs getting the usb setup correct.

4 - i inserted the 2 NVME drives (Samsung 970 EVO Pro 1TB) started the NAS again F4-423 tos version 5.1.131-00123.
Now problems.....

P1 - I could no longer see the folders from the traid any more in filemanager and all shared folders was gone, if i browse from the network they where
visible but not able to login to access them. All the shared folders on the nvme's was visible and working.

P2 - The bond stopped working as well easy fix though just unplug one cable and it was up again.

P3 - In the logfiles i now get this error but i can login to the webinterface and with ssh thank god
[2024/07/07 23:34:31.743765, 0] ../../source3/passdb/pdb_smbpasswd.c:1252(build_sam_account)
build_sam_account: smbpasswd database is corrupt! username admin with uid 0 is not in unix passwd database!
[2024/07/07 23:50:21.760195, 0] ../../source3/lib/sysquotas.c:566(sys_get_quota)
sys_path_to_bdev() failed for path [.]!

So the auth thing is re-occuring again i checked all disks and usb's for errors.

After some investigation i found out that it swapped Volume name from 1 to 3, i did try the guide here but looking in the mappings file it looked correct and i tried to create new shares users and no problems.

If i ssh to the nas i can see and access all volumes and files so hurried to backup it up to my other nas.
smb.conf is correct and also hold the new shares i created.

I'm getting a bit worried about stability now was planning to use it as primary nas for my files and then rsync to my other.
But now im starting to regret that choice.

Can we setup that remote session? Thanks.
My guess is that it has mixed in some of the old config as i understand if i didnt get it totally wrong is stored on the raided disks.
Im no linux guru but do know my way around and so far what i see is very weird in the logs and so on. And if i remove all drives except the one (new) i installed TOS on all seems normal again.

Thanks in advance.

Thank you for your feedback!
1. I am glad to know you have heatsinks installed.

2. when a drive overheat, the only possibility is that the drive is busy and fan does not work properly. But it seems that your situation is not like this, which is hard to understand. What type of array did you create? Is the overheating disk busy?

3. When the superuser lost its login next time, can we have a remote session to check out the issue?

4. I still don't quite understand why you only get one option when creating a bond.

[hzink]

Has this ever been addressed and/or fixed?

[TMbuddy]

Has this ever been addressed and/or fixed?

TOS 6 has resolved many issues present in TOS 5.
You did not specify which issue. May I ask which problem you are referring to and whether it has been fixed?