TerraMaster Forum

Hello,
Today, as I started my NAS (F2-220) after a few days off, and I am not able to connect to it anymore.

- It is starting, LAN and disks leds are green, and startup bip has been executed, tho I can't connect to it in any way. The disks leds blink a lot at the beginning, then calm down a bit.
- I tried various devices (PC, phone, console) and protocols (HTTP, SMB, SSH) to remotely connect to it, none succeed
- The NAS shows up in the list of connected devices on my router
- TNAS PC is able to find the device, but web page is infinitely loading without showing anything
- I tried this method: viewtopic.php?f=76&t=423, but I can't get past Method B step 6, since the web page is infinitely loading (so, even without disk, the NAS does not respond to tell me to insert the disks)
- It still turns on and off normally using the power button

Does anyone already had this issue?
I'm starting to be afraid that it could be more of an hardware issue than just a simple OS or file system corruption...

Thanks a lot in advance for the help

If the total storage pool is large, the system will take some time to load, please just wait for a moment patiently.
When there are errors found on the file system, the system will try to correct it, which may take several hours or even days.
You mentioned that the light stop blinking, so it's likely that there are too many errors to fix, or not enough RAM to support a fix. You could try plugging the disk into a Linux computer or a virtual machine with more RAM to repair the file system. (You need to install the mdadm tool and LVM tool first.)
This is a reference for repairing filesystems, and should also apply to other Linux environments.
viewtopic.php?t=2575

Disks are looking to run properly. All lights are on and green.
And even with no disk inserted, the web page is inaccessible (the one that should ask me to insert disks), where it should if it was a disk issue.
I'm going to let the NAS running for the night to see if some disk repair was needed.
If it is not accessible yet, I'll try to connect the disk to my Linux computer to analyze them.

Could it be related to the initboot in some kind of way ?

The simple Linux environment of initboot gives you the opportunity to debug, but may still be limited. Also, do you remember if your volume filesystem is EXT4 or BTRFS?

So, after connecting the drives to my computer with linux, the disk appeared healthy.

This is where I feel kind of dumb...:
I tried to connect the NAS directly to my router, instead of going through my network switch, and... it worked, I am able to connect to the NAS normally.
So this is my network switch which is dead (which is awesome news compared to a dead NAS or worse, dead drives).

Thanks a lot for the help, I learned in the process about mdadm and lvm, and sorry for the trouble with the false alarm issue.

It can happen to anyone. Bit surprised for a switch to die like that. Did you check for miss-directed VLANs? Cables (router to switch for example)?

Yes, cables and everything else is fine. The switch was a cheap one, I guess it didn't like the couple of times it fells from the desk lately...

I am having the same issue. but my NAS is already connected to my router. furthermore, when I restart my NAS i AM able to connect to it and see it in TNAS PC for a couple minutes. but then it vanishes again

GoldenSpider wrote: ↑22 Aug 2024, 23:58

Your equipment model and system are different from the topic starter's, and if you observe the phenomenon and conversation, you can also find that there are some differences．