dialmformumbojumbo

Hi Djoss, restoring is now working just fine after the new update. Again, thanks a lot for the quick fix, all my files have been restored!

Right! I had found that restore button in the meantime. However, through the web, one can only restore up tot 250mb or something. What I was also able to do was install a Crashplan client on a different machine and restore from there. I'm going to upgrade my docker and give that another go. Again, thanks a lot for the quick fix!!

Awesome! Thanks Djoss! I tried going through the web portal but couldn't find any restore functionality. Must've overlooked it then. I'll have another look after work.

Hi everyone, I've lost a significant amount of files during the weekend and when I try to restore them now I can see a "Preparing files" message in the Crashplan GUI but nothing gets restored. I've tried setting the permissions on the /storage mount point to rw but the issue remains. This is what I can see in my logs: restore_files.log.0 shows me this: I 02/14/22 08:33AM 42 Restore from CrashPlan Central stopped: 0 files restored @ 0Mbps I 02/14/22 08:33AM 42 Restore from CrashPlan Central completed: 0 files restored @ 0Mbps W 02/14/22 08:33AM 42 1 file had a problem W 02/14/22 08:33AM 42 - Timed out waiting for restore tool to be started by UI for /data/documenten/Facturen/Proximus/2018/2018-12-09.pdf I've also tried restoring to other folders such as /data and a newly created /restore of which the permissions were set to rw but none of the settings seem to work. So, I think there could be a different issue. If anyone has any ideas I'd love to hear them because I really want these files back. Thank you.

I haven't had any issues anymore since I hooked up the disk outside of the Supermicro 1-in-3 unit so it seems there's something wrong there. A bad sata connector or something with the backplane. Anyway, the problem is resolved. Happy new year everyone!

OK, same thing happened again this past night. So, its' definitely not the disk (unless there's some incompatibility with this type as they're the same). I've now hooked up one of these disks to the same sata cable but outside the Supermicro 5-in-3 unit, trying to exclude possible problems one at a time. J.

Funny thing, this problem. Disk 9 got disabled again this past night. Wasn't just a one-off then. I'm now rebuilding onto a new disk, although the disk doesn't seem to be the problem judging from the SMART reports. Figured it can't hurt to try though. The only things that have changed on my system recently were the addition of disk 9 and an upgrade of Unraid from version 6.2.3 to version 6.2.4. I've attached the diagnostics again in case anyone feels like checking it. Let's see what happens with this new disk. tower-diagnostics-20161218-0730.zip

Hi tdallen, That was indeed the diagnostics from before the reboot. Here's one I generated just now. J. tower-diagnostics-20161216-1711.zip

Hi, I've attached the full diagnostics zip. After it had crashed I did disconnect all the sata cables from the Supermicro 5-in-3 enclosure and reconnected them. They're all locking sata cables though and they all seemed to still be connected properly. In the mean time the disk's been rebuilt successfully. J. tower-diagnostics-20161211-1233.zip

Hey everyone, Yesterday my Unraid had disabled a disk because of read/write errors, I guess. I wasn't able to perform a SMART self-test afterwards either until after a reboot. The SMART tests I performed on the disks turned out fine. I'm now rebuilding the disk onto itself. I think the disk is fine but I'm not sure what went wrong yesterday. I've attached the syslog from the 'event'. Perhaps someone here can shed some light on a possible cause. The system has been running stable since I built it in June. Thanks for looking. J. syslog.txt

Thanks johnnie.black, I'll request an RMA and see what happens.

disk attributes

array devices

Statistics from the dashboard

Thanks for you reply. I've just finished another SMART extended self-test > Completed without error I still have the reported uncorrectable value as a warning (value = 098, raw value = 2) And the unRaid status mails still say the array has failed (same message as in my earlier post) I'm just a bit afraid an RMA might not be accepted as SMART status is passed Is there anything I can try to get rid of the array fail? Or should I not bother any with any further troubleshooting and just ask for the RMA? I've attached the new SMART report. ST4000VN000-1H4168_Z304DKYE-20160612-2228.txt