Author Topic: LS210 "disappears" from the network and becomes unresponsive after a few days  (Read 563 times)

aczlan

  • Calf
  • *
  • Posts: 4
I have a LS210D0401 that is the backup target for a folder on a TS5800D (the TS5800D backs up a folder to the LS210 every night).
That I am seeing is that the LS210 stops responding to the network after a few days (generally 4-6), it will then not power down when you flip the switch on the back and will not respond to pings or anything, but the power light is on steady. When this happens, it also stops sending the nightly status email.
If I pull power and let it sit off for a few minute before plugging it back in, it comes back and works fine.
Anyone run into this before?
I originally had it setup with sleep mode, but disabled that a while back.
It is running the 1.65-0.12 firmware, I have tried factory resetting it, but the same behavior occurs after it is set back up.

Thanks

Aaron Z
« Last Edit: May 03, 2017, 10:33:00 am by aczlan »

aczlan

  • Calf
  • *
  • Posts: 4
No ideas? How about it starting to show a "blink code" of 1 long and 2 short flashes with the red power LED (I moved it to my desk and it did that when I turned it on this morning after leaving it plugged in, but turned off for a day). That blink code should be "too hot" right? This is in a room where the thermostat says that it is 70F and the drive is not even warm to the touch.
Before it did that, it was sitting there with the drive seeking for a while (20 mins?)
I then powered it off, powered it back on and it seems to have booted normally now.

davo

  • Really Big Bull
  • VIP
  • *
  • Posts: 5681
Log onto the admin page, once done press CTRL+ALT_Shift+b, save the file when prompted and send it to me in a PM (upload it to dropbox/drive etc first), I'll have a look over it and see if there is anything unusual.
PM me for TFTP / Boot Images / LSRecovery.exe file.

aczlan

  • Calf
  • *
  • Posts: 4
There is a fair amount of info in there that I am not comfortable with sending out, which logs from that file do you need?

Aaron Z

Eastmarch

  • 1500 Lb Water Buffalo
  • Administrator
  • *****
  • Posts: 259
Since it backs up a TS, I'd contact support.

This can happen for a few reasons.

1. You have a bad drive. In the 'messages' log, you will have regular SMART reports. Look for re-allocated sectors, pending sectors, and offline uncorrectable sectors. Anything greater than 0 is a drive issue.
2. I have seen this when a unit isn't powerful enough for the task it is set to. If you are trying to backup hundreds of thousands of small files every night, this can happen.


You should also have the 5800 generate a backup log text file. It's an option under backup jobs. See if you can tell what file it hangs on.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 
**A single copy of data, even on a RAID array, is NOT a backup! Hard drive failure is not a question of IF, but WHEN! Don't take my word for it, take Google's!**

aczlan

  • Calf
  • *
  • Posts: 4
Currently, the 5800 just errors out and says
Quote
A backup error occurred.
Error Code: B101
[Backup Log]
array1/WindowsBackup/backuplog1_BackuptoQC_201705150045_01.txt
Looking in the log I see the following:
Quote
May  5 08:12:51 NAS usr.err krnl: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
May  5 08:12:51 NAS usr.err krnl: ata1.00: failed command: WRITE DMA EXT
May  5 08:12:51 NAS usr.err krnl: ata1.00: cmd 35/00:08:08:4b:cb/00:00:e8:00:00/e0 tag 0 dma 4096 out
May  5 08:12:51 NAS usr.err krnl:          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May  5 08:12:51 NAS usr.err krnl: ata1.00: status: { DRDY }
May  5 08:12:51 NAS usr.info krnl: ata1: hard resetting link
May  5 08:12:57 NAS usr.warn krnl: ata1: link is slow to respond, please be patient (ready=0)
May  5 08:13:01 NAS usr.err krnl: ata1: SRST failed (errno=-16)
May  5 08:13:01 NAS usr.info krnl: ata1: hard resetting link
May  5 08:13:07 NAS usr.warn krnl: ata1: link is slow to respond, please be patient (ready=0)
May  5 08:13:11 NAS usr.err krnl: ata1: SRST failed (errno=-16)
May  5 08:13:11 NAS usr.info krnl: ata1: hard resetting link
May  5 08:13:17 NAS usr.warn krnl: ata1: link is slow to respond, please be patient (ready=0)
May  5 08:13:42 NAS usr.info krnl: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
May  5 08:13:42 NAS usr.info krnl: ata1.00: configured for UDMA/133
May  5 08:13:42 NAS usr.warn krnl: ata1.00: device reported invalid CHS sector 0
May  5 08:13:42 NAS usr.info krnl: ata1: EH complete
The full log (minus the MAC and device name) is attached

Will support talk to me even though this is out of warranty? The 5800 is still in warranty, but this is not.

Here is the full (redacted) log on Pastebin: https://pastebin.com/98yxVrYM


Thanks

Aaron Z

Eastmarch

  • 1500 Lb Water Buffalo
  • Administrator
  • *****
  • Posts: 259
Just call in using the serial for the TS.

The log they'll want is the -backup- log. Not the system log. You create that as part of the backup job. The tarball doesn't have the same info.

Ben
**A single copy of data, even on a RAID array, is NOT a backup! Hard drive failure is not a question of IF, but WHEN! Don't take my word for it, take Google's!**