Hello all,

 

My first question is would a failed drive cause my server to beep?  Secondly, Why did unraid not notify me via email that this error happened?  All the tests I ran indicate email should work.

 

The drive in question is pretty new.  So im surprised by this.

 

 

Mar 23 04:40:01 Unraid syslogd 1.4.1: restart.

Mar 23 04:40:03 Unraid emhttp: mdcmd: write: Input/output error

Mar 23 04:40:03 Unraid kernel: mdcmd (20712): spindown 1

Mar 23 04:40:03 Unraid kernel: md: disk1: ATA_OP_STANDBYNOW1 ioctl error: -5

Mar 23 04:40:13 Unraid emhttp: mdcmd: write: Input/output error

Mar 23 04:40:13 Unraid kernel: mdcmd (20713): spindown 1

Mar 23 04:40:13 Unraid kernel: md: disk1: ATA_OP_STANDBYNOW1 ioctl error: -5

Mar 23 04:40:23 Unraid emhttp: mdcmd: write: Input/output error

Mar 23 04:40:23 Unraid kernel: mdcmd (20714): spindown 1

Mar 23 04:40:23 Unraid kernel: md: disk1: ATA_OP_STANDBYNOW1 ioctl error: -5

Mar 23 04:40:33 Unraid emhttp: mdcmd: write: Input/output error

Mar 23 04:40:33 Unraid kernel: mdcmd (20715): spindown 1

Mar 23 04:40:33 Unraid kernel: md: disk1: ATA_OP_STANDBYNOW1 ioctl error: -5

Mar 23 04:40:43 Unraid emhttp: mdcmd: write: Input/output error

Mar 23 04:40:43 Unraid kernel: mdcmd (20716): spindown 1

Mar 23 04:40:43 Unraid kernel: md: disk1: ATA_OP_STANDBYNOW1 ioctl error: -5

Mar 23 04:40:53 Unraid emhttp: mdcmd: write: Input/output error

Mar 23 04:40:53 Unraid kernel: mdcmd (20717): spindown 1

Mar 23 04:40:53 Unraid kernel: md: disk1: ATA_OP_STANDBYNOW1 ioctl error: -5

Mar 23 04:41:03 Unraid emhttp: mdcmd: write: Input/output error

Mar 23 04:41:03 Unraid kernel: mdcmd (20718): spindown 1

Mar 23 04:41:03 Unraid kernel: md: disk1: ATA_OP_STANDBYNOW1 ioctl error: -5

Mar 23 04:41:13 Unraid emhttp: mdcmd: write: Input/output error

Mar 23 04:41:13 Unraid kernel: mdcmd (20719): spindown 1

Mar 23 04:41:13 Unraid kernel: md: disk1: ATA_OP_STANDBYNOW1 ioctl error: -5

Mar 23 04:41:23 Unraid emhttp: mdcmd: write: Input/output error

Mar 23 04:41:23 Unraid kernel: mdcmd (20720): spindown 1

Mar 23 04:41:23 Unraid kernel: md: disk1: ATA_OP_STANDBYNOW1 ioctl error: -5

Mar 23 04:41:33 Unraid emhttp: mdcmd: write: Input/output error

Mar 23 04:41:33 Unraid kernel: mdcmd (20721): spindown 1

Mar 23 04:41:33 Unraid kernel: md: disk1: ATA_OP_STANDBYNOW1 ioctl error: -5

Mar 23 04:41:43 Unraid emhttp: mdcmd: write: Input/output error

Mar 23 04:41:43 Unraid kernel: mdcmd (20722): spindown 1

Mar 23 04:41:43 Unraid kernel: md: disk1: ATA_OP_STANDBYNOW1 ioctl error: -5

Mar 23 04:41:53 Unraid emhttp: mdcmd: write: Input/output error

Mar 23 04:41:53 Unraid kernel: mdcmd (20723): spindown 1

Mar 23 04:41:53 Unraid kernel: md: disk1: ATA_OP_STANDBYNOW1 ioctl error: -5

I tried a reboot and now the drive is reporting as a 2,147,483,616 size drive, when it should only be 1.5TB

 

So now im getting an error that my parity drive is not the biggest.

I replaced the drive with a 2TB drive that I have.  It would not let me preclear as it said its part of the array.  I went ahead and started the array.  Its rebuilding now.  I am assuming it will preclear on its own?

 

As a side note, after removing what I assume is a faulty drive, the beeping has stopped

Preclear is only necessary when adding a drive to a new previously unused slot and you want to avoid unraid downtime while it clears the disk. it's advantageous to use Joe's preclear script on a drive before trusting it to hold any data, but never necessary. When rebuilding a failed drive, unraid doesn't need to know that the whole drive is zeros, because it's going to write the entire content of the failed drive to the new drive anyway.

 

As far as the beeping, I've heard failing drives make beeping noises.