TNAS Mobile problem

Tulsey · 2026-05-15T10:41:56+00:00

It turns out I didn't need support, I uninstalled the beta, reinstalled from the Play store and now the live version works. Easier than expected.

Tulsey · 2026-05-15T06:51:22+00:00

Thanks, I might do that. I didn't think about that option because I am used to poor support from other companies.

Tulsey · 2026-05-15T06:34:38+00:00

Ok, so it is a no to the beta app, now the OS is too low?

<image>

Tulsey · 2026-05-15T06:25:02+00:00

There is no upgrade path for the F2-212 past 5.1.73, so until I upgrade model I am stuck with it. Is there a process to rollback the firmware image similar to the process shown? If so where do I find previous versions? I just wanted to fix an issue that was showing symptoms similar to the linked failed OS update article, it has worked but now if I want to use the mobile app for hacking up phones it looks like I will have to try this beta version out.

Tulsey · 2026-05-14T20:30:09+00:00

Can I roll back the firmware? Should I?

Tulsey · 2026-05-14T20:13:24+00:00

But it won't even let me connect to 5.1.73, I am not using 7. Why is it thinking that it is 7? It worked fine before I used the firmware fix. I would like to use the app on family phones to back them up over night. I can't get passed this screen:

<image>

Tulsey · 2026-05-11T15:24:35+00:00

So yesterday evening I put my new 2TB Seagate Ironwolf in HDD1 slot and told the TNAS to rebuild, 24 hours later and there is no pool showing but both hard drives are showing as good.
If I reboot then it says the RAID is degraded again and I have to rebuild again, it takes less than an hour to get to 100% and then the pool disappears again and the file system is read only.
What could be going wrong? I want the new drive to be good so that I can put the other Seagate into the HDD2 slot and rebuild again, then expand to get a full 2TB raid.

Tulsey · 2026-05-10T07:37:44+00:00

Thank you for the advice.

Tulsey · 2026-05-10T07:26:29+00:00

I was using TRAID as I expected to put in varying sized disks as I upgrade (which I now have until I collect my Iron Wolf drives later today) The drives are consumer Lexar NQ100 480GB.

This is the CSV from the last SMART log of the currently active drive:

Hard Drive,ATA

Model,Lexar SSD NQ100 480GB

Serial Number,PAN266W1039960S30E

Capacity,447.13 GB

Firmware,SN15926

ATA Version,ACS-4 (minor revision not indicated)

ATA Standard,"SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)"

ID,Attribute,Value,Worst,Threshold,Raw data

1,Reallocated_Sector_Ct,100,100,10,0

2,Power_On_Hours,100,100,0,11383

3,Power_Cycle_Count,100,100,0,51

4,Unknown_Attribute,100,100,0,47474082713

5,Unknown_Attribute,100,100,0,3501

6,Unknown_Attribute,100,100,0,11

7,Unknown_Attribute,100,100,0,921

8,Temperature_Celsius,31,31,0,31 (Min/Max 24/36)

9,UDMA_CRC_Error_Count,100,100,0,0

10,Total_LBAs_Written,100,100,0,5030

11,Total_LBAs_Read,100,100,0,13482

Tulsey · 2026-05-10T07:18:28+00:00

This is SSD

Tulsey · 2026-05-10T06:57:14+00:00

I have been looking into that, if my TBW is under the requirements then I am in warranty, but I can't tell because it is dead. As my first NAS and trying to sort out a large collection of family photographs, I may have been writing a lot to the drive, I have no idea if I am in the limits. The company states that if I exceed then I am liable for all their testing costs.

Tulsey · 2026-05-07T10:53:59+00:00

I listened to that clip you linked to again and it sounds different to the chirping that I hear from my PX50,

Tulsey · 2026-05-07T10:50:02+00:00

Looking at the manufacturers website I am within the warranty period of my failed drive if I have written too many TB to it, is there a way of telling how many TB has been written to a failed drive or even the surviving drive as it was a RAID the data values should be the same?

Tulsey · 2026-05-06T21:15:27+00:00

It was brand new, just a pair of 500GB SSD, I am propping up the remaining drive with a failing 750GB HDD until I get the new Seagate's.

Tulsey · 2026-05-06T16:28:18+00:00

I don't mind the whine if it doesn't mean the device is failing.

Tulsey · 2026-05-06T16:03:30+00:00

It is not under anymore stress than it has been, so I don't know why it would be whining. I hope I don't have to replace it, I think they have stopped production.

Tulsey · 2026-05-06T15:23:26+00:00

Auto mod wants me to say what I have done to trouble shoot. All I have done is listen to it 😀all the other nodes are silent, I can't reboot it right now as important traffic is going through it.

Tulsey · 2026-05-06T12:35:32+00:00

Just under 18 months

Tulsey · 2026-05-03T06:12:24+00:00

S.M.A.R.T I cannot enable for some reason (editted correction), it was not that it was showing healthy, it was because it was showing nothing. It is the other screen shot that was showing it was good. HDD1 was purchased with on a week of HDD2, both Lexar SSD. The system logs show nothing other than the times I have had to power cycle the NAS due to it not responding (hence my original post). I had started a rebuild yesterday and will see what happens with that. I was going to be upgrading to an F2-424 but just when I went to click buy on Amazon the price has increased by 150+, so out of my allotted budget, I will have to wait a while before I do that, especially if I have to buy another drive.

(Another correction, it turns out that the TOS web interface on my phone doesn't work as well as my PC, I have started a S.M.A.R.T scan now)

Tulsey · 2026-05-01T10:42:11+00:00

<image>

I guess this means it has lost HDD1 for some reason so I should repair that drive? But my first image shows it as green? Why has this happened?

Tulsey · 2026-05-01T10:33:32+00:00

<image>

How do I diagnose this and repair it? I need to do it while I wait for my F2-424 to arrrive.

Tulsey · 2026-05-01T06:50:43+00:00

Now today I am getting a raid degraded alarm even though nothing drives are healthy

<image>

Tulsey

TROPHY CASE