After connecting to the new network, why TNAS PC client failed to search my TNAS?

[vadersson]

OK, thanks for the advice, unfortunately, that did not work. I am not sure why the data was not restored to access.

The current situation. I have 2.16 TB out of the 10 TB TRAID showing as Volume 2. Volume 1 is the new NVMe drive I installed. File explorer will not show me the files on Volume 2. I was able to make a new folder on volume 2, but that is empty. The TNAS knows the drives are there, see the raid, but can't seem to access the data. I tried a few apps like Snapshot, but there is nothing to restore from. I need to find a way to access these drives. I did not see anything that seems to allow me to get into them. All the data was stored in the /public part of the old drives, and I see there is a new /Public from volume 1. Maybe there is some problem with them having the same name.

Sorry to need so much help. I guess maybe simple home users should not use NAS systems when they don't really understand them that well.

[CursaYang]

I'm very sorry for the trouble you've experienced.
Your idea is correct; having two directories with the same name can cause one of them to not display properly.
You can log into the terminal and rename one of the 'public' directories to another name.
If you're not familiar with Linux operations, you can visit the official website's live chat to schedule an engineer to assist you remotely.

[vadersson]

Ok, that helps. I think I can get it working now. Thanks for the assistance. I'll let you know how it goes.
Thanks,
Duncan'

[vadersson]

Hopefully my final check in (at least on this topic!) I want to thank everyone at TerraMaster that helped me solve this issue. I really messed up the set up of my TNAS and how I was using it. But after a session with some online support, we finally were able to get all my files accessible. Here is a quick summary of all the things that went wrong.

1. I set up my TNAS in Isolation mode and did not really know what that meant. Basically it made it so that when I switched by home network from one set of devices (google wifi) to another (eeros wifi) the addresses all changes and the TNAS would not let me hook up to it.
2. Since the original network was completely gone before I noticed or realized what happened, I could not fix it that way. I also could not remember the original network addresses.
3. My solution was to buy and install an NVMe drive on the both board and reinstall TOS on there. That would let me reconnect to the system. This actually worked fine for some of the old directories, but...
4. My second mistake was just using the /Public directory on the original TNAS drives as my main storage. When I added a new volume (the NVMe drive) and reinstalled TOS, it created a /Public directory.
5. Apparently you cant have two /Public folders on two different volumes, you can only access the /Public on the main volume 1, which in this case was the new NVMe and not the old hard drives.
6. The first solution was to rename /Public on volume 1, which then allowed /Public from volume 2 to be accessed.
7. But it turns out that when you reboot, the main volume with TOS on it creates a /Public again.
8. The final solution was to rename /Public on volume 1 to something else, then when the /Public on Volume 2 became accessible, we renamed it as well. Then when rebooted we have a new /Public on volume 1 and access to the renamed /Public_2 on volume 2.

And with that I found all my files. Now I just have to figure out how to set up my system better so we don't have these problems in the future.
(And find a new backup drive that won't fail on me!)

Thank you all again,
Duncan

[ARThornicroft]

I am having the same issue. After updating to the newest TOS 7 OS, both TNAS PC and the IP address will not load my TNAS. I cannot get into the drive, and I cannot access it.
This happens every single day when I log in to my drive int he morning. I restart my computer, I restart the NAS - nothing works!
I have changed the address to ensure it's secure, I have done everything. WHY CAN'T I ACCESS MY DRIVE?

On another note, please STOP changing the drive sleep time to a default of 10 minutes in the Power settings, as it will does not allow access to my drives after it goes to sleep. Why? They should wake up when I log back in, but they do not and I cannot access the drives.

[CursaYang]

I am having the same issue. After updating to the newest TOS 7 OS, both TNAS PC and the IP address will not load my TNAS. I cannot get into the drive, and I cannot access it.
This happens every single day when I log in to my drive int he morning. I restart my computer, I restart the NAS - nothing works!
I have changed the address to ensure it's secure, I have done everything. WHY CAN'T I ACCESS MY DRIVE?

On another note, please STOP changing the drive sleep time to a default of 10 minutes in the Power settings, as it will does not allow access to my drives after it goes to sleep. Why? They should wake up when I log back in, but they do not and I cannot access the drives.

Hello, what is your NAS model? Are you unable to find the NAS via TNAS PC? Please enter the BIOS when powering on to confirm that TOS is set as the first boot item.

[ARThornicroft]

My NAS is the F2-424. TNAS PC cannot find the NAS, even when I restart both the computer and the NAS. I am on MAC.

[TMzethar]

My NAS is the F2-424. TNAS PC cannot find the NAS, even when I restart both the computer and the NAS. I am on MAC.

If you can access the router management page, you can check if the NAS's IP is recognized and if you can successfully access the NAS using its IP. You can also try removing all HDDs and SSDs before starting the NAS to see if the TNAS PC Tool can detect it, which will help confirm whether the issue is caused by the system or the storage devices.

[TMroy]

Could you please confirm if your TNAS has completed the initialization and has ever functioned normally? Or is this a brand-new device that you are setting up for the first time?

[ARThornicroft]

I have it working now. It seems there was an updated version of the TNAS PC for Mac that's corrected the issue