[HELP] Storage Manager - failed to retrieve data - after update [SOLVED]

[Nikdfish]

Storage manager was flagged that an update was available/needed. I clicked on the update button. Installation hung at 99%. After a reboot, storage manager shows as installed with version 1.0.053. When the open button is clicked I get the message "failed to retrieve data". There is no option available to uninstall or reinstall.

File manager now fails on open with the message "502 Bad Gateway nginx/1.18.0 (Ubuntu)"

File manager also shows the "Update" button, but any attempt to start the update gets the message
"Waiting ..."

Control panel device monitoring does not see any volumes or disks. The only thing shown is the space used by the system partition. Nothing is accessible.

Previously installed apps such as Jellyfin and Surveillance Manager now show as not installed. Vol2 is the designated app install location.


This is a F2-423 running TOS 7.0.777

[Bartman]

Mine is stuck at 99% updating F2-423 7.0.0777, not going to turn off now because of this report.

Any one from support?

[Grigorio]

exactly the same problem
А4-425+ TOS 7.0.780

[TMzethar]

We sincerely apologize for the inconvenience. Our team is currently developing a resolution, which will be made available upon confirmation of its validity. We kindly ask for your patience in the meantime.

[TMzethar]

To fix the Storage Management update that hangs at 99%, open a terminal and run these commands in order:

Code: Select all

systemctl stop StorageManager.service
dpkg --purge storagemanager
cd /
wget https://download2.terra-master.com/storagemanager_1.0.054_amd64.deb
dpkg -i storagemanager_1.0.054_amd64.deb
/etc/tos/scripts/mntdata

[Nikdfish]

To fix the Storage Management update that hangs at 99%, open a terminal and run these commands in order:

Code: Select all

systemctl stop StorageManager.service
dpkg --purge storagemanager
cd /
wget https://download2.terra-master.com/storagemanager_1.0.054_amd64.deb
dpkg -i storagemanager_1.0.054_amd64.deb
/etc/tos/scripts/mntdata

Would this fix still work if the NAS was rebooted following the stall at 99%?


Never mind, remote session applied the fix. All good now.