[Help] F8 SSD

[shinegull]

It seems you have obtained and decided on a solution from the official website's Live Chat.

Unfortunately, not so lucky. still cant access

[shinegull]

Thanks your response.
Just out of curiosity - You found nas under TNAS-PC: What was the ip address shown and how did this compare to the old ip?

169.254.196.xxx is old
169.254.136.xxx is new

[TMnight]

According to your description, the NAS and the computer are currently connected directly, correct? Please try the following steps:

Open Control Panel > Network and Internet > Network and Sharing Center > Change adapter settings.

Locate the network port directly connected to the NAS, right-click it, and select Properties.

In Internet Protocol Version 4 (TCP/IPv4), manually set a fixed IP address, for example: 192.168.x.x.

After applying the settings, try searching for the NAS again using the TNAS PC tool.

If the NAS still cannot be found, please restart the NAS and try again.

[athurdent]

Thanks your response.
Just out of curiosity - You found nas under TNAS-PC: What was the ip address shown and how did this compare to the old ip?

169.254.196.xxx is old
169.254.136.xxx is new

Those are self-assigned IPs, is your DHCP server working?

A different approach to see what's going on is to simply connect a monitor and keyboard. You should be able to login and check / configure an IP using standard Linux ifconfig commands.

[Gremlin]

Those are self-assigned IPs, is your DHCP server working?

Agreed, but they are consistent with neither NAS or PC (ethernet) being connected to the router/dhcp server. Whichever way we may view the arrangement, it should allow both devices to communicate with each other provided they also auto-assign the same subnet mask of 255.255.0.0. I'm pretty sure Windows does that, but not so certain of TOS - (and I'm not going to test it right now with thunderstorms passing through and circuits tripping!!)

[athurdent]

Those are self-assigned IPs, is your DHCP server working?

Agreed, but they are consistent with neither NAS or PC (ethernet) being connected to the router/dhcp server. Whichever way we may view the arrangement, it should allow both devices to communicate with each other provided they also auto-assign the same subnet mask of 255.255.0.0. I'm pretty sure Windows does that, but not so certain of TOS - (and I'm not going to test it right now with thunderstorms passing through and circuits tripping!!)

I‘d focus my energy on getting the DHCP server running though, and additionally connect a monitor or KVM to see what is actually happening on the NAS. It’s not headless as my dumb QNAP was, so I loved to follow the install process with my KVM when I first got the F8 SSD.

[shinegull]

This may be a moot point now though...

I plugged in a couple drives while it was on. it restarted it self. and now im seeing 3 of the four drives i plugged in. I did the rest button on the back (took like a dozen+ tries) either way, its now at initiliation. Im a bit hesitant to go through it though, as it says to install on drive. will my data on the drive(s) be wiped?

[TMzethar]

If your SSDs has been used in another system or device, they will be formatted during TOS installation or when creating storage pools & volumes.
If the SSDs are already used for your F8 SSD system and storage, it will not be reformatted when you select them for TOS installation.
However, if you see a prompt to “Delete/Format,” this may indicate an unusual situation—do not proceed.

[shinegull]

ok now im really confused.

i tried selecting a disk. it says some sort of issue. and to power down and restart.
that got me a bit concerned

but then i started it up and its all working again????

I did notice that the terra-master certificate has expired warning has come up. what should i do with this?

next is, i kinda wanna make sure if i plug it in to a desktop or pc, it will be able to run. i mean its working now, but who know about next time? is there some kinda of test i can or should run right now?

[TMzethar]

It's great to hear that you have finally resumed usage. However, based on the available information, it is still difficult to accurately guess the reason.
Could it possibly be that the SSDs became loose due to accidental bumps during transportation? If you have the means, I recommend testing the SSDs.
You can collect a system report via TOS-Support-Report Issues and send it to the support email, perhaps we can identify something.
Regarding the expired certificate, you can go to TOS Control Panel-Security-Certificate, where you can update it.