Before I pull the trigger and start backing up, I wanted to double check. I use Synology SHR. So, when a drive goes bad, and I need to recover, I can't just restore the G: drive or whatever....since it's all combined into E: (which I like). That and because BackBlaze doesn't support NAS is why I...
Yes, exactly...8 bay external. I have it attached via eSATA. I have a very limited backup in the cloud, but it would be devastating if I were to lose this. It seems like I am just getting back in good shape from the last time I had trouble! :/
I'm thinking it's channel 1 since that's what has reported reading errors, but I am afraid to remove the drive and replace with a new one since it is degraded, and that's not the one reported as missing in the drives list:
Usage Capacity Model
Ch01 Raid Set # 00 3000.6GB Hitachi HDS723030ALA640...
I'm not even going to say what was wrong :), but I was able to get in. Here's the events log:
2015-10-01 13:02:43 192.168.001.241 HTTP Log In
2015-10-01 12:57:41 H/W Monitor Raid Powered On
2015-10-01 12:56:45 Raid Set # 00 Rebuild RaidSet
2015-10-01 12:56:45 ARC-5040-VOL#00 Failed...
After I reboot it, it will work and the files are accessible, but whenever I try to start copying files from it again to finish the transfer I mentioned for a family member, it will fail again.
What's even more ironic is that is the very thing I was doing when it went south - writing from the RAID to that drive (after having just copied it over there from the failing drive, which took forever).
Thanks for the reply. I installed the app you mentioned, but not right away aware of proper usage. I had a partial backup until yesterday, ironically. I had to repurpose the drive I was using for that because of disk problems on a family member's drive. I do not have any media large enough...
I was copying files and watching a movie from my RAID last night. The movie kept buffering, which I don't recall happening, even when copying files usually. However, at the time, I attributed it to the lengthy list of files being copied. That is, until the system started beeping and said...