TOS 7.0.0375 Beta (X86) is Released for Update

[rfbjr]

The thing is I don't see it on my F4-425 Plus or the F4-223. Same Beta release. I thought I read somewhere that the location of the fan on the 424 doesn't blow the air towards the CPU as like on other models. So, cause and effect? Just my nickel, USA stopped making pennies.

[Gremlin]

Generally, the update process will clean up the .ins and .bz2 packages. Sometimes you might get lucky and find a snapshot has picked it up (but the odds are against it I think. I have started to make sure packages are downloaded to TNAS prior to update - avoiding the auto download/update function. Then I look for them and copy back to my main pc for posterity This works from Terminal:

Code: Select all

cd /
find -name TOS_X642.*

[rfbjr]

Generally, the update process will clean up the .ins and .bz2 packages. Sometimes you might get lucky and find a snapshot has picked it up (but the odds are against it I think. I have started to make sure packages are downloaded to TNAS prior to update - avoiding the auto download/update function. Then I look for them and copy back to my main pc for posterity This works from Terminal:

Code: Select all

cd /
find -name TOS_X642.*

[OttO1916]

After updating to 7.0.0375:
USBDisk/SingleDisk StorageManager/StoragePool: Raid(?!) Corrupted.
Mounting the StoragePool helped, Raid(?!) no longer corrupted, volume was OK, all data present.

(( When updating to 7.0.364, I had the same issue,
just mount didn't fix it, I had to rebuild StoragePool/Volume/Shares/Data.
In both cases I checked the disk, turned out fine - no bad blocks ))

[jdubya]

Just came here to say this is the first update that installed without error. Thank you.

[TMzethar]

After updating to 7.0.0375:
USBDisk/SingleDisk StorageManager/StoragePool: Raid(?!) Corrupted.
Mounting the StoragePool helped, Raid(?!) no longer corrupted, volume was OK, all data present.

(( When updating to 7.0.364, I had the same issue,
just mount didn't fix it, I had to rebuild StoragePool/Volume/Shares/Data.
In both cases I checked the disk, turned out fine - no bad blocks ))

This issue may not necessarily be related to updates. Have you been keeping the NAS running 24/7 for a long time? You could try simply restarting the NAS to see if a similar problem occurs. Additionally, what type of RAID do you have? Is it a RAID with a mix of HDDs and SSDs?
viewtopic.php?p=53487#p53487

[True1Santony]

I’m experiencing exactly the same issue. As soon as I try to connect remotely using the mobile app or the Windows app, the device becomes unresponsive. I also see multiple TOS spool/daemon processes appearing before it freezes.
In my case it’s even worse: when it happens, my router also becomes unusable — neither the NAS nor the router respond, and I’m forced to reboot both devices.
What should we do in the meantime? Should we just wait for a new update, or is there any workaround to avoid this?

[OttO1916]

Before each update I
- backup config
- restart NAS
- backup config
- update
Probably a bit overkill but it was necessary with previous - other brand - NASes

after the update the issue didn't re-occur after a reboot

About RAID: it was a single USB disk.. that's why the "?!" for the the message in storage pool that RAID was corrupted. A bit weird...

[OttO1916]

My F5-221 updated to TOS7.0.0375 without any issues.
Good job Terramaster !!

[TMzethar]

TOS 7 beta has released a new version. Regarding the problem you encountered, please try updating to the latest TOS 7 Beta and then test it again.
viewtopic.php?t=9655