AS-602T does not detect HDD

[Kerry]

I have a AS-602T as well. It failed recently with similar situation. Asustor support engineer told me it is related to the back plane board. Since AS-602T is already 5 years old with me and out of warranty, I purchased a new AS6102T and plugged in the same hard drives from AS-602T, then immediately everything is back. AS6102T is quite a bargain compared with AS-602T 5 years ago. Replacing with a new one should be less costly than asking for out of warranty repair which for sure will cost dearly. Personally I think 5 years is quite a long time for an electronic device turning on 24 hours, 365 days a year. My Asus laptops does not even last 2 years.

[triplee23]

#03 USB added this to the dmesg:

[ 390.692671] usb 9-2: new high-speed USB device number 2 using xhci_hcd
[ 390.712600] usb 9-2: New USB device found, idVendor=13fd, idProduct=1240
[ 390.719421] usb 9-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 390.726620] usb 9-2: Product: External
[ 390.731189] usb 9-2: Manufacturer: Generic
[ 390.735469] usb 9-2: SerialNumber: 57442D57584C373038303036
[ 390.744285] usb-storage 9-2:1.0: USB Mass Storage device detected
[ 390.750736] scsi7 : usb-storage 9-2:1.0
[ 391.764902] scsi 7:0:0:0: Direct-Access Generic External 2.08 PQ: 0 ANSI: 4
[ 391.780596] sd 7:0:0:0: [sdb] 293046768 512-byte logical blocks: (150 GB/139 GiB)
[ 391.792227] sd 7:0:0:0: [sdb] Write Protect is off
[ 391.797166] sd 7:0:0:0: [sdb] Mode Sense: 21 00 00 00
[ 391.797283] sd 7:0:0:0: Attached scsi generic sg1 type 0
[ 391.806884] sd 7:0:0:0: [sdb] No Caching mode page found
[ 391.812298] sd 7:0:0:0: [sdb] Assuming drive cache: write through
[ 391.828608] sd 7:0:0:0: [sdb] No Caching mode page found
[ 391.834047] sd 7:0:0:0: [sdb] Assuming drive cache: write through
[ 391.867527] sdb: sdb1 sdb2 sdb3
[ 392.191466] sd 7:0:0:0: [sdb] No Caching mode page found
[ 392.196909] sd 7:0:0:0: [sdb] Assuming drive cache: write through
[ 392.203103] sd 7:0:0:0: [sdb] Attached SCSI disk

#01 Hot-Swap

I hear the HDD spinning up but nothing happens in the dmesg.

#02 Move to ESATA

I don't have that possibility as I don't have that kind of equipment.

Can I somehow install the ADM on the USB drive that the system acknowledges? Then I can maybe reinstall the firmware?

Or can I reinstall the firmware using ssh and command line?

Or is the SATA controller dead?

Thanks for all the help so far.

Hey man. Marco from ASUSTOR here. I talked it over with my colleagues and found that it is likely the SATA backplane may be on its way out. You may send us the NAS for repair or I can try to talk with personnel to send you the part. The part is replaceable. If you do it, we cannot bear any responsibility.

Hi,

I think you are correct, the SATA backplane is bust. I can surely repair it myself. After more or less accepting that this is a not a SW issue, I have already opened it and dissembled and assembled it again. No worries. Are you saying that you are willing to support me with parts free of charge? If not, I think I just as well should buy a new one. I live in Europe btw.

[triplee23]

Recent update:

Asustor support sent me one last piece of hope that it could be a SW issue. They sent me a file to flash and reset the firmware through USB. I tried it but ended up with the same result.

The server starts and I am able to access the unit through SSH. The unit shows up in the Control Center but when trying to initialize, the web interface errors on the disk not being detected. The Control Center recognises the unit as AS0000T which is not correct and according to asustor support a sign that there is a HW failure somewhere. Unless I am able to get some parts (free or reasonable price) this unit is going to the junk yard as it is probably better to get a new one.

Thanks for all the help.

[Marco@ASUSTOR]

Hi,

I think you are correct, the SATA backplane is bust. I can surely repair it myself. After more or less accepting that this is a not a SW issue, I have already opened it and dissembled and assembled it again. No worries. Are you saying that you are willing to support me with parts free of charge? If not, I think I just as well should buy a new one. I live in Europe btw.

You and I both know that the NAS has a three year warranty which is already 50% more than our competitors. Normally we don't even sell the parts of the NAS. But I'm certainly willing to try to see if I can help you buy the part. The NAS is quite old already and I don't even know if we still have parts for that model. All I can say is I'm willing to try to do what I can for you.

[jozes01]

Hi,

I have the same issue on my AS602T.
It looks quite offen issue for AS602T model. Somebody in ASUSTOR did not test new firmware carefully.
I can not believe that firmware upgrade may damage SATA controller, however who knows, I do not know what type of controller is used there to study details.
Does anybody know?

I would like to try boot USB in the same way as SATA disk to be able pass initialization phase and to try load some older firmware which was working for sure.
Does anybody know at which mounting point is SATA disk mounted?

Other option I would like to test - to try boot other OS as described in this thread: viewtopic.php?f=29&t=9533

[ho66es]

this just happened to me on a 608t after rnn1 update

[jozes01]

today I have connected empty 160GB SATA disk via eSATA port back of the chassis.
After the boot, system see this disk, but the system still does not finish booting correctly - system LEB flashes and no long beep.
I think the issue is somewhere else, not in the SATA backplain.
I still can not initialize system and after the attempt to initialize it system say the same message I have had "Initialize your NAS
No disks detected. You must install at least one disk before you can continue."

On top of it I see there some issue on internal memory /dev/sdb1.
root@AS0000T-D585:~ # fdisk -l

Disk /dev/sda: 160.0 GB, 160000000000 bytes
255 heads, 63 sectors/track, 19452 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

Disk /dev/sdb: 1031 MB, 1031798784 bytes
238 heads, 49 sectors/track, 172 cylinders
Units = cylinders of 11662 * 512 = 5970944 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 1 173 1003519+ ee EFI GPT
Partition 1 has different physical/logical endings:
phys=(124, 237, 49) logical=(172, 23, 49)

I have no idea how to continue.
Does anybody have dmesg output from working system? or other useful info/tip how to detect the reason not to finish boot?

[orion]

root@AS0000T-D585:~ # fdisk -l

Disk /dev/sda: 160.0 GB, 160000000000 bytes
255 heads, 63 sectors/track, 19452 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

Disk /dev/sdb: 1031 MB, 1031798784 bytes
238 heads, 49 sectors/track, 172 cylinders
Units = cylinders of 11662 * 512 = 5970944 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 1 173 1003519+ ee EFI GPT
Partition 1 has different physical/logical endings:
phys=(124, 237, 49) logical=(172, 23, 49)

Your case should be different from OP. I "guess" system might not detect your drive during re-initialization. You can try:

• Remove all disks from NAS when NAS is off.
• Turn NAS on (this way should trigger another initialization process). Wait for ADM is ready.
• Insert 160GB drive into slot-1 (after NAS is ready).
• Check if ADM can initialize it.
• Check in ssh "fdisk -l" again.

[Marco@ASUSTOR]

Recent update:

Unless I am able to get some parts (free or reasonable price) this unit is going to the junk yard as it is probably better to get a new one.

Thanks for all the help.

Sir, It's not going to be free. I'm trying to help you, I'd appreciate not asking for things that can cost me my job.

[jozes01]

Your case should be different from OP. I "guess" system might not detect your drive during re-initialization. You can try:

• Remove all disks from NAS when NAS is off.
• Turn NAS on (this way should trigger another initialization process). Wait for ADM is ready.
• Insert 160GB drive into slot-1 (after NAS is ready).
• Check if ADM can initialize it.
• Check in ssh "fdisk -l" again.

Hi Orion,

NAS do not finish booting even without disks.
System LED is flashing, no beep end of boot.
I have inserted 160GB disk into slot 1 - cca. 2min after stating the boot process.
I see one green LED stable lighting on the disk chassis. Also I hear sound that system is trying to access the disk
In case I connect to NAS via ssh i see the disk is not mounted, only internal memory - I guess FLASH is visible - following output from fdisk:
root@AS0000T-D585:~ # fdisk -l

Disk /dev/sda: 1031 MB, 1031798784 bytes
238 heads, 49 sectors/track, 172 cylinders
Units = cylinders of 11662 * 512 = 5970944 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 173 1003519+ ee EFI GPT
Partition 1 has different physical/logical endings:
phys=(124, 237, 49) logical=(172, 23, 49)
root@AS0000T-D585:~ #