Howe to recover the NAS if ADM 2.5.2.RCG2 upgrade failed

[Quote.L@AST]

Dear all,

According to the Technical notification in support center:
Technical notification for ADM 2.5.2 The Surveillance Center logging system may cause ADM 2.5.2 upgrades to fail.
If you have Surveillance Center already installed, please upgrade it to version 2.4.1.8805 first before upgrading your NAS to ADM 2.5.2.

If NAS can not boot after ADM 2.5.2.RCG2 upgrade, below is the procedure to recover the NAS :
(If you know what Linux commands such as ssh, ls , mdadm -A, you can follow below procedure to clean the tmp file of volume0.
If you are not familiar , please contact with support team in http://support.asustor.com. ASUSTOR support engineer will help you to
recover via the teamviewer or other remote access method.)

1. Power off the NAS, and remove all drives from NAS.

2. After NAS power on, use ASUSTOR Control Center to find the IP of NAS.

3. Use the putty.exe ( or ssh tool in Mac or Linux)

a) putty.exe in Windows:
input the IP of your NAS in putty.exe.
PS: putty.exe can be downloaded from
http://www.chiark.greenend.org.uk/~sgta ... nload.html

b) Example of Mac or Linux : Open a console , and input the ssh command
# ssh root@172.16.8.140

172.16.8.140 is the IP of your NAS.
When it ask for the password, input admin

4. After login into the NAS , please insert all of your drive back to the NAS.
Make sure the drives are poweron on after they are inserted.
Please use the following command to list all the disks.
#ls /dev/sd*

5. Use mdam to "assemble" volume0 by the following commands.
If you have disks /dev/sda, /dev/sdb , /dev/sdc, /dev/sdd, /dev/sde, /dev/sdg
You should use 2nd partition of disk.
Below is an example to assemble the md0 of AS606T ( it is 6 bays)
( #mdadm -A /dev/md0 /dev/sdxx /dev/sdxx..... )

Example
root@AS-606T-C491:~ # ls /dev/sd*
/dev/sda /dev/sdb4 /dev/sdc4 /dev/sdd4 /dev/sde4 /dev/sdf4 /dev/sdg4
/dev/sdb /dev/sdc /dev/sdd /dev/sde /dev/sdf /dev/sdg
/dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1 /dev/sdg1
/dev/sdb2 /dev/sdc2 /dev/sdd2 /dev/sde2 /dev/sdf2 /dev/sdg2
/dev/sdb3 /dev/sdc3 /dev/sdd3 /dev/sde3 /dev/sdf3 /dev/sdg3
root@AS-606T-C491:~ # mdadm -A /dev/md0 /dev/sdb2 /dev/sdc2 /dev/sdd2 /dev/sde2
/dev/sdf2 /dev/sdg2
mdadm: /dev/md0 has been started with 6 drives.

You can use "cat /proc/mdstat" to check if you had assemble the md0

# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md0 : active raid1 sde2[6] sdb2[5] sdf2[7] sdc2[8] sda2[9] sdd2[10]
2096064 blocks super 1.2 [6/6] [UUUUUU]


6. mount the /dev/md0 to /volume0, so you can clean the tmp files of volume0
root@AS-606T-C491# mount /dev/md0 /volume0

7. go to /volume0/usr/builtin/tmp, to clean the files/folders under this tmp directory.
Example:
root@AS-606T-C491:/volume0 # cd usr/builtin/tmp/
root@AS-606T-C491:/volume0/usr/builtin/tmp # ls
LrKQQn/ xcg9Bq/

=> you should fild some folders under /volume0/usr/builtin/tmp
root@AS-606T-C491:/volume0/usr/builtin/tmp#rm -r /volume0/usr/builtin/tmpLrKQQn/
root@AS-606T-C491:/volume0/usr/builtin/tmp#rm -r /volume0/usr/builtin/tmp/xcg9Bq/

8. Reboot the NAS, and it should boot up correctly.
root@AS-606T-C491:/volume0/usr/builtin/tmp#reboot

9. NAS shoud boot up

[Telek]

In my 602T all space on volume0 occupied Apache2 logs (1.7 Gb):
/volume0/usr/builtin/var/log/apache2

and the folder /volume0/usr/builtin/tmp was empty.

[Quote.L@AST]

Dear Telek,

According to your issue:
In my 602T all space on volume0 occupied Apache2 logs (1.7 Gb):
/volume0/usr/builtin/var/log/apache2

You can delete the apache2.log .
Basically the size of Apache server will be rounded , and limited in a smaller size.
You can delete them , and reboot the NAS.
When the Apache server starts , it will create the new log , or add the log into its current log file.
This will not be a problem.

Thanks,
Q