ReadyNAS 314 shows status degraded

[twolcrazy]

I have a ReadyNAS which just notified me through email that its status changed from redundent to degraded.  There are four 2-3 TB drives in RAID 10.  None of the drives show any problems and are all green.  There are no apparent performance issues in the last several hours.  Would rebooting the NAS be the best thing to do?  I have two ReadyNAS that are timemachines for our Apple computers and one stores our business files.  I also have copies of all the files on another external drive.  Each the 314 runs backups of the company files to 424 after midnight. 

Thanks,

John (aka twolcrazy)  

[StephenB]

Maybe download the log zip file, and see if you can find what triggered the problem.

[twolcrazy]

The systemd-journal.log contains lots of these type of messages.  I am no expert reading the logs but this looks like a disk read error to me.  Is the drive with the error ata1.00.  I do have one spare drive and could swap it out.

Oct 05 17:48:32 nas-E5-61-42 kernel: ata1.00: status: { DRDY ERR }
Oct 05 17:48:32 nas-E5-61-42 kernel: ata1.00: error: { UNC }
Oct 05 17:48:32 nas-E5-61-42 kernel: ata1.00: configured for UDMA/133
Oct 05 17:48:32 nas-E5-61-42 kernel: sd 0:0:0:0: [sda] tag#4 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Oct 05 17:48:32 nas-E5-61-42 kernel: sd 0:0:0:0: [sda] tag#4 Sense Key : Medium Error [current] [descriptor]
Oct 05 17:48:32 nas-E5-61-42 kernel: sd 0:0:0:0: [sda] tag#4 Add. Sense: Unrecovered read error - auto reallocate failed
Oct 05 17:48:32 nas-E5-61-42 kernel: sd 0:0:0:0: [sda] tag#4 CDB: Read(16) 88 00 00 00 00 00 00 90 00 48 00 00 00 08 00 00
Oct 05 17:48:32 nas-E5-61-42 kernel: blk_update_request: I/O error, dev sda, sector 9437257
Oct 05 17:48:32 nas-E5-61-42 kernel: Buffer I/O error on dev sda3, logical block 1, async page read
Oct 05 17:48:32 nas-E5-61-42 kernel: ata1: EH complete
Oct 05 17:48:32 nas-E5-61-42 kernel: do_marvell_9170_recover: ignoring PCI device (8086:3a22) at PCI#0
Oct 05 17:48:32 nas-E5-61-42 kernel: ata1.00: exception Emask 0x0 SAct 0x200 SErr 0x0 action 0x0
Oct 05 17:48:32 nas-E5-61-42 kernel: ata1.00: irq_stat 0x40000008
Oct 05 17:48:32 nas-E5-61-42 kernel: ata1.00: failed command: READ FPDMA QUEUED
Oct 05 17:48:32 nas-E5-61-42 kernel: ata1.00: cmd 60/08:48:48:00:90/00:00:00:00:00/40 tag 9 ncq 4096 in
res 41/40:00:49:00:90/00:00:00:00:00/40 Emask 0x409 (media error) <F>

Thanks,

John (aka. twolcrazy)

[StephenB]

---

@twolcrazy wrote:

Oct 05 17:48:32 nas-E5-61-42 kernel: blk_update_request: I/O error, dev sda, sector 9437257

---

This is normally the first disk - you can confirm by looking in disk_info.log

If all these errors on on dev sda, then replacing that disk is the next step.

[twolcrazy]

Thanks for confirming what I suspected.

John (aka. twolcrazy)

[Sandshark]

The NAS probably did a re-sync on it's own once it again "saw" the bad drive, so it looked fine when you checked the GUI.  But that's not likely to last.

BTW, if your data is still available, a reset is the last thing you want to do.  Many users incorrectly think a reset is a panacea (too used to Windows, I guess) and go from a slightly degraded to a fully unavailable volume when they do so.  The first thing you do in those cases is make sure your backup is up to date.