fatefree

Thank you very much for the explanation - its a bummer but at least I understand the reasons. In my scenario after parity rebuilt, the drive was identical to the previous and the repair had the same result. I'm currently going through the lost+founds - my biggest fear of course is that the files in here could be incomplete. I haven't seen any evidence of that (most of these files were movies or tv shows), and although individual files/seasons may be missing, anytime a file is there it appears to be complete. I am hoping that the repair tool would only put files here that were intact so I can trust them without having to watch them all haha. I am in the process of implementing better backups to prevent the sting of something like this in the future. I'm still not sure how this happened since there was no unclean shutdown and the drive was fairly new and precleared. It even seems like I can use the drive that failed again after another preclear - would that be a bad idea in your opinion? I attached my logs in case it helps anyone else. Thanks again for explaining everything to me. unraid-diagnostics-20220325-1501.zip check-2

Hello, I woke up this morning to a bunch of movies missing from my media library and I noticed one of my drives was unmountable. I attempted the repair steps and it sort of completed successfully, but the lost+found folder had tons and tons of files and some without any extentions, so I really didn't trust the drive contents anymore. I stopped the array unassigned the disk, swapped in a new drive, and parity is in the process of building. But even though its writing, it still says the new disk is unmountable. I was hoping that after parity that would be fixed but I'm growing less confident as I read about this. Is this a scenario where Parity won't be able to help? Would parity rebuild with the unmountable disk, effectively erasing the backup of the dead drive? Or would parity stay intact and allow me to replace the unmountable drive and save the contents? I'm very nervous about a scenario where a disk died and parity is no help, so I'd appreciate any info.

Hello, I've been running Unraid 6.8.2 with the latest version of the Plex docker app, and its been working fine for months until recently. I noticed the docker image was occasionally stopped, even though its set to auto start. In the docker logs I see this: Starting Plex Media Server. [services.d] done. Dolby, Dolby Digital, Dolby Digital Plus, Dolby TrueHD and the double D symbol are trademarks of Dolby Laboratories. double free or corruption (out) ****** PLEX MEDIA SCANNER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.19.3.2843-e3c1f7bcd/PLEX MEDIA SCANNER/216bde9b-aece-2cc2-45bca68f-1528bbf9.dmp [cont-finish.d] executing container finish scripts... Critical: libusb_init failed [cont-finish.d] done. [s6-finish] waiting for services. s6-svwait: fatal: timed out [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. Not sure what steps I should take to debug this? I have the dmp file but I dont really understand it. unraid-diagnostics-20200524-0855.zip 216bde9b-aece-2cc2-45bca68f-1528bbf9.dmp

Thanks Squid, I am supposed to have ECC ram, I have 4 sticks of this: NEMIX RAM 32GB Replacement for Samsung M391A4G43MB1-CTD DDR4-2666 ECC UDIMM 2Rx8 I will reboot and clear the error - thanks for your help!

Woe is me. Server's been running fine, its been up for like 73 days but I just saw this fix common mistakes message for the first time today. Anything to be concerned about? unraid-diagnostics-20200430-1712.zip