TerraMaster Forum

Anybody tried using with 3rd party rams?

Just tried on 5.1.33 with 16GB Crucial 3200 didn’t work.

Have half a mind to abandon TOS altogether.

lichkingxxl wrote: ↑10 May 2023, 02:38 Now, after reinstall 5.0.176 all my disks are in red led

Coming from 5.1.24 and I have the same issue. Both HDD lights are red

Finally got 5.1.34 installed. Not n00b friendly and remember kids, to clear browser cache and history (firefox) between each install after NAS reboots.

5.1.34 is nicer looking than 4.2 but 40% slower on same hardware and drives using rsync on GIG connection locally.

I was able to get the old partitions removed and install 5.1 with new partition sizes.

Had to flash the bzImage to new flash drive as the internal one became corrupted

Very cumbersome and with no clear guides for many of these "gotchas", but the forum did provide enough info to get everything back up and running.

Yesterday I tried to update my F2-221 from 5.1.33 to 5.1.34, and it became stuck on 'Loading..., please wait!' - I've left it for 24 hours and it's still stuck. Today I've restarted it and waited a few hours and it's still stuck. TNAS PC also doesn't recognise it.

I've also tried 'method 2' to reinitialise. (Turn off > Remove HDD > Wait >....) but it's still stuck on 'Loading..., please wait!'

Please can anyone help?

Updates to TNAS are SO unreliable and frustrating, is there any QA on these updates before they're released?!

Dave11 wrote: ↑09 May 2023, 22:34 Well I tried it but now after a period of time the NAS just stops responding, no HDD activity, no new messages from the console output via HDMI port.
Looks like I'll have to nuke it and start from scratch as it's no good just stalling.

F2-421

Well its finally back in action now, resolved the stalling/crashing issues by installing Open Media Vault, no issues with the device crashing now

Could this same problem also may be causing other more general issues?

My Plex said it was disabled the other day and would not start from within ToS. I used SSH for the first time and tried to start it from the command line and I got a lot of messages about the device being out of space which made no sense at the time when I had 300GB free on my data volume. More details here: viewtopic.php?f=51&t=4660&p=26946#p26946
Those disk space issues seem to make a lot more sense now in the context of this issue.

I am also having issues with setting permissions on folders which sit on "configuring" within ToS and never complete.
I uninstalled Plex to see if re-installing fixed it and now cannot re-install plex or any other software. Installations all fail.

Please can you provide guidance (preferably in a new post) as soon as possible for those of us who have already upgraded to ToS 5.1.x from a system setup that originally came from ToS 4 (or earlier).

We need clear guidance on what to do and what not to do at this point. My concern is that trying to regress to an earlier version is going to make things worse rather than better.

From the description of this issue it sounds like the solution that is required is for TerraMaster to provide something to increase the 2GB partition to 8GB so that it is in line with the size it would be for a clean 5.1.x install. Is this what you are working on or is this not feasible for some reason? If this is being worked on then it would be good to know roughly when can we expect this to be delivered?

I can see that the next issue might be where to find the extra 6GB to add to the partition as it has to come from somewhere.


As I see this, any solution that you put in place is also going to need to address your current recommended upgrade path from ToS 4 which as I understand it is:

ToS 4. Initialise. Install TOS 5.0.176. Upgrade to 5.1.24 and upgrade to 5.1.33

I assume that the two upgrades i've put in bold both can both cause partition size issues and are "unsafe" in terms of the above upgrade path and this issue. Either they will need to be replaced with new versions that include whatever the fix for this issue is or a fix will need to happen before these highlighted upgrades (assuming that these upgrades would not then regress that fix) . Alternately a new upgrade route from 5.0.176 is needed.

My F4-421 went to the white loading screen for hours. I tried removing the hard drives and booting but I get "booting form init system

error: invalid extent
failed to boot both default and fallback entries"

Can someone point me in a direction that would help?

StephenNaylor wrote: ↑13 May 2023, 05:52 Could this same problem also may be causing other more general issues?

Disk partition is not possible to be extended online without losing data. You need to follow our recommendation to back up your data and redo all the partitions.

csprog wrote: ↑13 May 2023, 10:04 My F4-421 went to the white loading screen for hours. I tried removing the hard drives and booting but I get "booting form init system

error: invalid extent
failed to boot both default and fallback entries"

Can someone point me in a direction that would help?

is this error shown on your web page? or somewhere else?
Never seen such an error before, would you share a screenshot?

"Disk partition is not possible to be extended online without losing data. You need to follow our recommendation to back up your data and redo all the partitions."

The implication here is TerraMaster have messed this up so badly that anyone with a system that was originally running on version 4 (or earlier) will either have to restart their systems from scratch or risk their system failing due to the partition running out of space down the line.

As I see it, "backup your data and redo all the partitions" is when I need to think very hard about whether I trust TerraMaster devices with my data going forwards.

TerraMaster need to come up with a better resolution to this issue and quickly.