The appliance's storage is being initialized. Please wait a few minutes, then try logging in again. - Connect IT Community

/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .super-nav { display: flex; justify-content: flex-end; align-items: center; margin: 0 auto; max-width: 1264px; padding-left: 40px; padding-right: 40px; height: 40px; text-align: right; } .super-nav a { color: #34427c; margin-right: 20px; padding: 10px; text-decoration: none; } .super-nav a:hover, .super-nav a:focus { background-color: #f7f9fa; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 0; } .footer-image { background-image: url("/themes/kaseya/assets/images/footerImage.png"); height: 500px; background-repeat: no-repeat; background-size: cover; margin-top: -100px; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer-main-content { background-color: #000; padding: 100px 0; } .footer .footer-col-title { color: #ffffff; font-weight: 700; font-size: 13px; padding-bottom: 10px; text-transform: uppercase; } .footer .footer-link { color: #9b9ca0; text-decoration: none; } .footer .footer-link:hover, .footer .footer-link:focus, .footer .footer-link:active { text-decoration: underline; } .footer-main-content .footer-link { padding-top: 10px; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-main-content-row { align-items: flex-start; } .footer-bottom-content { padding: 10px; align-items: center; } .footer-col { padding: 0 3px; display: flex; flex-direction: column; } .footer-col-copyRight { justify-content: flex-start; color: #9b9ca0; flex: 1; display: flex; } .footer-last-col { flex-direction: row; } .footer-last-col .footer-link { padding-right: 10px; text-transform: uppercase; } @media screen and (max-width: 768px) { .super-nav { padding-right: 0; } .footer-image { height: 250px; } .footer-main-content { padding: 40px 0; } .footer .footer-col-title { padding-top: 10px; } .footer-row:not(.footer-main-content-row) { display: block; } .footer-col:not(.footer-main-content-col) { width: 100%; text-align: center; padding: 10px 0; } .footer-main-content-col { width: 50%; } .footer-last-col { flex-direction: column; } .footer-last-col .footer-link { padding-bottom: 10px; } } /*# sourceMappingURL=styles.css.map */ Ask the Community Groups

The appliance's storage is being initialized. Please wait a few minutes, then try logging in again. - Connect IT Community | Kaseya

ISSUE

ISSUE: You have updated the Unitrends system or made modifications to the storage. You receive the following message when logging into the Web Administrative Interface.

The appliance's storage is being initialized. Please wait a few minutes, then try logging in again.

As presented in the HTML Web Administrative Interface:

RESOLUTION

Connect to the Unitrends system using an SSH capable client (e.g.: putty.exe) and authenticate as the user root.

Verify that the storage allocated (below in dark red) is what you expect by executing this command:

[root@UB1 ~]# df -hP
Filesystem                      Size  Used Avail Use% Mounted on
/dev/sda2                       976M  262M  664M  29% /
tmpfs                           7.8G     0  7.8G   0% /dev/shm
/dev/sda1                       239M   25M  201M  11% /boot
/dev/sda5                       5.8G  1.1G  4.5G  20% /usr
/dev/sda3                        50G  4.8G   42G  11% /usr/bp
/dev/sda6                       3.9G  211M  3.5G   6% /var
/dev/mapper/vg_state-lv_backup   12T  8.4T  3.7T  70% /_Stateless

If it looks normal, then it is possible a hidden stop file is to blame. Execute this command to see if it exists: ls -rlasth /usr/bp/lists.dir/.disable_rrc

[root@UB1 ~]# rm /usr/bp/lists.dir/.disable_rrc
4.0K -rw-r--r-- 1 root root 100 Apr 18 12:36 /usr/bp/lists.dir/.disable_rrc

If the results include details of the file, then it exists and must be removed. Execute this command to remove it: rm /usr/bp/lists.dir/.disable_rrc
Confirm that you want to file deleted by typing y and pressing the Enter key.

[root@UB1 ~]# rm /usr/bp/lists.dir/.disable_rrc
rm: remove regular file `/usr/bp/lists.dir/.disable_rrc'? y

Restart the Unitrends Database...
- Stop the database by executing this command: /etc/init.d/bp_rcscript stop
- ```
[root@UB1 ~]# /etc/init.d/bp_rcscript stop
Stopping Unitrends Agent...Success.
```
- Start the database by executing this command: /etc/init.d/bp_rcscript start
- ```
[root@UEBackup-01 ~]# /etc/init.d/bp_rcscript start
Starting Unitrends Agent...
Success.
```

You should be able to access the Web Administrative Interface now.

TASKS

CAUSE: The file is placed in order to ensure a that a consistent state is maintained on the system. In some cases, when a disconnect in communications occur (latency or network disruption for example), the call to remove the file is not received/processed and the file remains.

The file can be removed if you see that the system is functioning from the command line interface.