December 2, 201015 yr Got a red dot on one of my drives while I was away on vacation. When I came back and copied the syslog, it looks like whatever caused the error didn't seem to be in there or it had been truncated off the syslog due to age. SO I restarted to generate a new syslog and hopefully during the restart the OS would identify the issue. I perused that log and there is nothing indicating what is wrong. The web GUI shows no errors anywhere; just the red dot. Unlike previous issues where it showed parity errors. What should my next step be? Attached is the syslog, FWIW... The machine is running 10+1 2TB -EARS drive (jumpered). OH, the drive in question is disk 3, pci-0000:00:1f.2-scsi-5:0:0:0 host7 (sdl) WDC_WD20EADS-00R6B0_WD-WCAVY0509974. syslog.txt
December 3, 201015 yr It is red because a write to it failed. As you said, it probably occurred in a syslog that was rotated out. (and gone now since you rebooted) You only have one choice if you think the drive is responding. Stop the array Un-assign the drive Start the array with it un-assigned. (This causes it to forget the serial number of the disk so it will accept it as its own replacement) Stop the array once more Re-assign the drive to it slot in the array on the "Devices" page. Start the array and it will re-construct the disk onto itself. If the drive is not writable, you'll learn of it again. Joe L.
December 3, 201015 yr Author Followed your advice and no errors after rebuilding the drive from parity!
Archived
This topic is now archived and is closed to further replies.