November 30, 201312 yr So, I got an email earlier from my Splunk server notifying me that I'm getting a ton of errors from my unRAID box. Well, I just popped in some new drives, as I've been in the process of getting it up and going for the past few weeks. Anyways, go and check Splunk to see whats in the logs, and holy crap, there's a TON of read errors. Nov 30 06:48:12 10.0.1.10 kernel: md: disk4 read error, sector=92608720 Nov 30 06:48:12 10.0.1.10 kernel: md: disk4 read error, sector=92608712 Nov 30 06:48:12 10.0.1.10 kernel: md: disk4 read error, sector=92608704 Nov 30 06:48:12 10.0.1.10 kernel: md: disk4 read error, sector=92608696 Nov 30 06:48:12 10.0.1.10 kernel: md: disk4 read error, sector=92608688 Nov 30 06:48:12 10.0.1.10 kernel: md: disk4 read error, sector=92608680 Nov 30 06:48:12 10.0.1.10 kernel: md: disk4 read error, sector=92608672 Nov 30 06:48:12 10.0.1.10 kernel: md: disk4 read error, sector=92608664 Nov 30 06:48:12 10.0.1.10 kernel: md: disk4 read error, sector=92608656 Nov 30 06:48:12 10.0.1.10 kernel: md: disk4 read error, sector=92608648 Okay? That disk was fine when it was in the Drobo... I precleared it and everything... Any ideas as to what's going on? I'll wait until the parity sync is done and then I'll run a couple of smart tests.
November 30, 201312 yr If you are getting read errors the parity will be invalid anyway so no point in letting it continue running. If you have just been moving the drives around then the most likely cause is a power or SATA connector not perfectly seated.
Archived
This topic is now archived and is closed to further replies.