TOS 6.0.648 (X86) is Released for Update

[TheBacons]

Thank you Gremlin for checking the image file and your helpful suggestions.

I initially encountered validation errors when using BalenaEtcher on Windows, which led me to believe the image might be corrupted. However, I also tried an alternative approach by creating the bootable USB directly on the NAS using terminal commands:

```bash
# Installed pv (pipe viewer) on the NAS
apt install --no-install-recommends pv

# Wrote the image directly to USB
pv /Volume1/00_TNAS_ADMIN/USB_Initboot_UEFI-229.img > /dev/sdd

# Verified completion
sync
```

This method successfully created a bootable USB that functions correctly (I can boot from it and log in as root using root/admin). Unfortunately, it produced the same results as the original USB boot drive - showing the "No disk detected" message in the web interface without launching any reinstall scripts automatically.

Since I can access all system files via the terminal as root, it should be possible to install or repair them manually. Since 99% of the system is working correctly, I'd prefer a targeted solution to fix the main problem first:

1) Could anyone provide a list of specific files needed to rebuild just the main TOS web interface? (or share in the BBS)
OR
2) Provide the commands for the reinstallation scripts on the USB that I can run manually.
OR
3) I like your idea of using an installation (*.ins) package locally, although I'd then need to upgrade to 6.0 again, but that's not painful. Do you know how to launch that installation script from an SSH terminal?

Your suggestion about TNAS-PC for auto-installation is also interesting. I can't seem to login to the NAS from the PC atm (apart from SSH Terminal) - but I'll look into that as well if the more targeted approaches aren't viable.

Thank you for your continued support and ideas!

Best regards,
Colin

[Gremlin]

Use a TOS6 installation package if you have previously updated to TOS6. They are available under several model numbers (eg F6-424MAX) All the installation packages (at particular version levels) are the same across models (otherwise, TM would have to separately identify them, and they don't). Note that the next version .650 incorporates a kernel update as well but not seen any particular issues with that on the one device updated so far.

[FredMutter]

It has been verified that some devices may have permission issues that cause the shutdown plan to be invalid.
Please wait for the subsequent version to fix it.
Currently, you can try to execute the following command in the terminal to modify the file permissions to make the shutdown plan effective:

Code: Select all

chmod 644 /etc/crontab

chmod helped me ! Thanks!

[thierrys73]

Good morning
sometimes my remote access deactivates itself and is grayed out. I can no longer activate it.
I need to revalidate my IP settings to be able to reactivate my remote access.

t6-423

[TMnight]

You need to check if there is an issue with your network connection.You can verify whether the WAN connection is functioning properly in the "Dashboard".

[Gremlin]

You might also want to check that the device IP address in
Control Panel > Network > general
matches the expected IP address in
Control Panel > Network > general > interface

Sometimes, the system will appear to pick up a lan port "at random" as the gateway address.

[King7]

Installed on F4-424 Pro, works well currently.

[CathyW]

Installed on my F4-424 , run very good !

[King7]

When will the next version be released?

[crisisacting]

When will the next version be released?

A newer build, 6.0.650, was already released.