This has happened twice now in the last month.  Not sure if it's just a bad sata cable or what.  The first time it happened, I opened the box and one of the cables did seem like it might have been loose, so I secured it and booted back up, and after a parity check everything was fine (other than the fact that I mistakenly did a restore, but that's on me).

 

Now I've got the red ball again on the same disk, and before I do anything just wanted to post my syslog here since I don't know what these errors mean.  My disk status page shows 2 errors on the disk.  It's one of the dreaded WD EARS disks (2TB).  I'm running a 3 disk array + cache + parity drive.  unRAID v4.5.

 

On an unrelated note, what's up with all the FTP pings?  Is there a way to combat that, or do I just leave it be since they can't get in without a password.  There were actually a TON more of those that I pulled out of the log.  The errors shown below were also repeated many times and I truncated it down to keep under the character limit of a post.

 

Sep 26 04:40:01 fileserver syslogd 1.4.1: restart.
Sep 26 07:40:27 fileserver kernel: mdcmd (28181): spindown 0
Sep 26 07:40:28 fileserver kernel: mdcmd (28182): spindown 1
Sep 26 07:40:29 fileserver kernel: mdcmd (28183): spindown 2
Sep 26 07:40:29 fileserver kernel: mdcmd (28184): spindown 3
Sep 26 07:40:30 fileserver emhttp: shcmd (40): /usr/sbin/hdparm -y /dev/sda >/dev/null
Sep 26 19:28:53 fileserver emhttp: shcmd (41): /usr/sbin/hdparm -y /dev/sda >/dev/null
Sep 26 22:42:12 fileserver kernel: ata3: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen
Sep 26 22:42:12 fileserver kernel: ata3: edma_err_cause=00000020 pp_flags=00000000, SError=00180000
Sep 26 22:42:12 fileserver kernel: ata3: SError: { 10B8B Dispar }
Sep 26 22:42:12 fileserver kernel: ata3: hard resetting link
Sep 26 22:42:17 fileserver kernel: ata3: link is slow to respond, please be patient (ready=0)
Sep 26 22:42:20 fileserver kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 26 22:42:20 fileserver kernel: ata3.00: configured for UDMA/133
Sep 26 22:42:20 fileserver kernel: ata3: EH complete
Sep 26 23:21:55 fileserver kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Sep 26 23:21:55 fileserver kernel: ata3.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0
Sep 26 23:21:55 fileserver kernel:          res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Sep 26 23:21:55 fileserver kernel: ata3.00: status: { DRDY }
Sep 26 23:21:55 fileserver kernel: ata3: hard resetting link
Sep 26 23:22:00 fileserver kernel: ata3: link is slow to respond, please be patient (ready=0)
Sep 26 23:22:05 fileserver kernel: ata3: SRST failed (errno=-16)
Sep 26 23:22:05 fileserver kernel: ata3: hard resetting link
Sep 26 23:22:10 fileserver kernel: ata3: link is slow to respond, please be patient (ready=0)
Sep 26 23:22:15 fileserver kernel: ata3: SRST failed (errno=-16)
Sep 26 23:22:15 fileserver kernel: ata3: hard resetting link
Sep 26 23:22:20 fileserver kernel: ata3: link is slow to respond, please be patient (ready=0)
Sep 26 23:22:50 fileserver kernel: ata3: SRST failed (errno=-16)
Sep 26 23:22:50 fileserver kernel: ata3: limiting SATA link speed to 1.5 Gbps
Sep 26 23:22:50 fileserver kernel: ata3: hard resetting link
Sep 26 23:22:55 fileserver kernel: ata3: SRST failed (errno=-16)
Sep 26 23:22:55 fileserver kernel: ata3: reset failed, giving up
Sep 26 23:22:55 fileserver kernel: ata3.00: disabled
Sep 26 23:22:55 fileserver kernel: ata3: EH complete
Sep 27 01:35:48 fileserver kernel: mdcmd (34617): spindown 2
Sep 27 01:35:49 fileserver kernel: mdcmd (34618): spindown 3
Sep 27 01:35:49 fileserver kernel: md: disk3: ATA_OP_STANDBYNOW1 ioctl error: -5
Sep 27 01:35:59 fileserver kernel: mdcmd (34620): spindown 3
Sep 27 01:35:59 fileserver kernel: md: disk3: ATA_OP_STANDBYNOW1 ioctl error: -5
Sep 27 09:30:19 fileserver kernel: md: disk3: ATA_OP_STANDBYNOW1 ioctl error: -5
Sep 27 09:44:22 fileserver kernel: md: disk3: ATA_OP_SETIDLE1 ioctl error: -5
Sep 27 13:14:54 fileserver vsftpd[14790]: connect from 221.148.81.46 (221.148.81.46)
Sep 27 13:14:54 fileserver vsftpd: Mon Sep 27 13:14:54 2010 [pid 14791] CONNECT: Client "221.148.81.46"
Sep 27 13:14:54 fileserver vsftpd: Mon Sep 27 13:14:54 2010 [pid 14790] [www] FAIL LOGIN: Client "221.148.81.46"
Sep 27 13:14:56 fileserver vsftpd: Mon Sep 27 13:14:56 2010 [pid 14790] [www] FAIL LOGIN: Client "221.148.81.46"
Sep 27 13:14:57 fileserver vsftpd: Mon Sep 27 13:14:57 2010 [pid 14790] [www] FAIL LOGIN: Client "221.148.81.46"
Sep 27 13:14:58 fileserver vsftpd[14792]: connect from 221.148.81.46 (221.148.81.46)
Sep 27 13:14:58 fileserver vsftpd: Mon Sep 27 13:14:59 2010 [pid 14793] CONNECT: Client "221.148.81.46"
Sep 27 13:14:59 fileserver vsftpd: Mon Sep 27 13:14:59 2010 [pid 14792] [mail] OK LOGIN: Client "221.148.81.46"
Sep 27 13:14:59 fileserver vsftpd: Mon Sep 27 13:14:59 2010 [pid 14794] [mail] FAIL RMDIR: Client "221.148.81.46", "/sarcaxxo"
Sep 27 16:10:12 fileserver kernel: mdcmd (41264): spindown 0
Sep 27 16:10:13 fileserver kernel: mdcmd (41265): spindown 1
Sep 27 16:10:14 fileserver kernel: mdcmd (41266): spindown 2
Sep 27 16:10:14 fileserver kernel: mdcmd (41267): spindown 3
Sep 27 16:10:14 fileserver kernel: md: disk3: ATA_OP_STANDBYNOW1 ioctl error: -5
Sep 27 16:10:24 fileserver kernel: mdcmd (41269): spindown 3
Sep 27 16:10:24 fileserver kernel: md: disk3: ATA_OP_STANDBYNOW1 ioctl error: -5
Sep 27 16:51:28 fileserver kernel: mdcmd (41761): spindown 3
Sep 27 16:51:28 fileserver kernel: md: disk3: ATA_OP_STANDBYNOW1 ioctl error: -5
Sep 27 16:51:29 fileserver kernel: md: disk3: ATA_OP_SETIDLE1 ioctl error: -5

Basically, communications to the disk is timing out.  (could easily be the cable)

 

as far as FTP, you run the risks of opening up any port on the unRAID server to the outside world.  There is ONLY one way to make it secure and EVERY other method is insecure.    (and the more somebody knows about networking and security, the more likely they'll NOT be able to secure your machine)

 

I hope you used a GOOD password.  Numbers/letters and special characters Upper and Lower case.  Otherwise the hackers will use a dictionary attack and get in soon enough.

as far as FTP, you run the risks of opening up any port on the unRAID server to the outside world.  There is ONLY one way to make it secure and EVERY other method is insecure.    (and the more somebody knows about networking and security, the more likely they'll NOT be able to secure your machine)

 

I hope you used a GOOD password.  Numbers/letters and special characters Upper and Lower case.  Otherwise the hackers will use a dictionary attack and get in soon enough.

 

What is the ONLY secure way?

Do you consider Hamachi secure enough?

 

as far as FTP, you run the risks of opening up any port on the unRAID server to the outside world.  There is ONLY one way to make it secure and EVERY other method is insecure.    (and the more somebody knows about networking and security, the more likely they'll be certain they will NOT be able to secure your machine)

 

I hope you used a GOOD password.  Numbers/letters and special characters Upper and Lower case.  Otherwise the hackers will use a dictionary attack and get in soon enough.

 

What is the ONLY secure way?

Allow no network connection.  Put in a shielded, guarded room, limit physical access.

Do you consider Hamachi secure enough?

No, because your flash drive is still writable to anybody who has physical access, or anybody who can take control of any PC on your LAN and incrementally gain privileges.   You might be locking the front door and leaving all the "Windows" open.

 

Joe L.

Joe,

 

It seems like you're saying the only way to be 100% secure is to have a local box that's not even connected to your LAN.  Isn't that a little extreme?

 

I only access my server internally, but I realize now the reason I was getting those FTP pings is because I had port 21 open from a past FTP server I used to have.

 

That said, it would be nice if there was an easy and at least pretty secure way to access my unRAID box externally.

externally from your local LAN or outside your network?

 

externally from your local LAN or outside your network?

From outside my network.