ADM 2.5.2.RCG2 killed my NAS

[rljones]

I have a AS3102T, likewise bricked by the 2.5.2 update.
I'm posting here because that specific forum has no talk of the issue, but it appears plenty of others do here, so please excuse my interjection.

I finally got my RMA'd unit today (bricked in late Oct).
Now it appears I'm facing the double whammy where the HDD is now coming up as uninitialized.

I don't know what the hardware differences are, but it is obvious they have let the work experience kiddies loose on this update.
My unit simply came to a screeching halt, no LEDs (other than LAN activity - MAC function I'd suspect), No fan, no beep, NO GO.

I only had the unit for a few days, and yep should have ignored the 2.5.2 update.
Really totally pissed off by the whole affair.

[orion]

I have a AS3102T, likewise bricked by the 2.5.2 _.
I'm posting here because that specific forum has no talk of the issue, but it appears plenty of others do here, so please excuse my interjection.

I finally got my RMA'd unit today (bricked in late Oct).
Now it appears I'm facing the double whammy where the HDD is now coming up as uninitialized.

I don't know what the hardware differences are, but it is obvious they have let the work experience kiddies loose on this _.
My unit simply came to a screeching halt, no LEDs (other than LAN activity - MAC function I'd suspect), No fan, no beep, NO GO.

I only had the unit for a few days, and yep should have ignored the 2.5.2 _.
Really totally pissed off by the whole affair.

Sounds a different problem from the original post. Do you mean that you got hardware problem and just got the returned RMA NAS back? The returned NAS looks like bad again (no LED, no FAN...)?! I think you'd better to send a support request to asustor again to check it.

[MikeG.6.5]

I have a AS3102T, likewise bricked by the 2.5.2 _.
I'm posting here because that specific forum has no talk of the issue, but it appears plenty of others do here, so please excuse my interjection.

I finally got my RMA'd unit today (bricked in late Oct).
Now it appears I'm facing the double whammy where the HDD is now coming up as uninitialized.

I don't know what the hardware differences are, but it is obvious they have let the work experience kiddies loose on this _.
My unit simply came to a screeching halt, no LEDs (other than LAN activity - MAC function I'd suspect), No fan, no beep, NO GO.

I only had the unit for a few days, and yep should have ignored the 2.5.2 _.
Really totally pissed off by the whole affair.

Sounds a different problem from the original post. Do you mean that you got hardware problem and just got the returned RMA NAS back? The returned NAS looks like bad again (no LED, no FAN...)?! I think you'd better to send a support request to asustor again to check it.

This is definitely a different problem than people are having with the ADM updates. Most everyone having issues with this update were running 60x models.

Your problem sounds like a power supply issue. The LEDs for the NIC are going to work even if the unit has no power plugged in, as it's powered from the Ethernet cable. Get in touch with Asustor's ticketing system and talk with them about it. Try to get them to send you a unit while you still have yours in hand, then swap it out. Then make sure they have someone that can log in via Teamviewer to make sure your data isn't gone.

Don't initialize that HDD your data is on!!! If you do that data is GONE!

If you have an older 250GB HDD or something to plug in, you can initialize with that to at least test the functionality of the unit when you get it. At least you can verify that the NAS works while you are waiting to get a TV session going. It just needs to be a SATA drive to work to test the NAS. Make sure it's not an old IDE drive!!!

[Quote.L@AST]

Dear all,

Below is the procedure to recover the NAS if NAS can not boot after ADM 2.5.2.RCG2 upgrade
(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 inser all of your drive into 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
*** If you are not able to mount /dev/md0 to /volume0, please don't use fsck to check file system .
Please contact with support team of ASUSTOR ***
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

[SteelZ691]

This is what the Asustor Tech did on my AS7008T as well and got it working.. Thanks Quote.L@AST

Dear all,

Below is the procedure to recover the NAS if NAS can not boot after ADM 2.5.2.RCG2 upgrade
(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 inser all of your drive into 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
*** If you are not able to mount /dev/md0 to /volume0, please don't use fsck to check file system .
Please contact with support team of ASUSTOR ***
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

[dexter]

Thanks for sharing.

Happy to not being upgraded by ASUStor.

[donniemcm]

Hi,

What would be the mdadm commands for below drives? I have 3 disks
/dev/sda /dev/sda3 /dev/sdb1 /dev/sdb4 /dev/sdc2
/dev/sda1 /dev/sda4 /dev/sdb2 /dev/sdc /dev/sdc3
/dev/sda2 /dev/sdb /dev/sdb3 /dev/sdc1 /dev/sdc4

[marka2k]

ktbken

Do you know how to clear the logs? I am having the same issue, I have not upgraded to 2.5.2.RCG2 but I run surveillance center.

Ok asustor tech support was able to fix the issue it seems to be caused by the surveillance centre logs getting to big and filling volume0
nas is back on line

[Din0]

Hello,

I updated yesterday my AS-602T to ADM 2.5.2.RDP1(from 2.5.10)After update and restart system does not run anymore.Control center will find NAS as uninitialized and marked as AS-000000. Through PUTTY i can see that system is running, but no units are connected.It is not possible to initialize system

[orion]

Hello,

I updated yesterday my AS-602T to ADM 2.5.2.RDP1(from 2.5.10)After update and restart system does not run anymore.Control center will find NAS as uninitialized and marked as AS-000000. Through PUTTY i can see that system is running, but no units are connected.It is not possible to initialize system

I think it's better to send a support request to asustor to check it. http://support.asustor.com/