Kevek79

There is one more solution that might save you some time. If you use a tool like MakeMKV you can extract the video and audio streams from a DVD or BD into a mkv container with little to no transcoding (Which of course is much faster than transcoding with handbreak). Those MKV files are perfectly readable by plex and should have the exact quality of the base material (MPEG for DVD / h.264 for BD). With those files in your library, plex server and client can handle the question of transcoding, if necessary for the player. And as there should be no quality loss in between ISO or the MKV created as described above you should not need your ISO files afterwards.

As far as I know, the short answer is - Yes. Anyone who has access to the share on the unraid box has access to all that is on this share. But from within nextcloud, users data should be seperated and their should be no access to another users files.

If someone has the same issue than me: After talking to the linuxserver.io team on their Discord, I used the tag 20.0.4-ls112 and my NC16 install is back up and running. I do not know if this is related as I did not use the Collabora integration, that I set up when installing NC for the first time, in a while, but my collabora container is not starting anymore. As their are some other things that I did not update in the past year or so and I do not need the office integration at the moment I will try to tackle that issue after getting my NC installation up to the current version. At least I can now enter my nextcloud again and start the update journey to the current release

Did some research today. Am I right that I need to go back to a container version based on alpine 3.12 as 3.13 Alpine would include a PHP 7.4 version ? Is 20.0.4-ls112 the last version based on Alpine 3.12 and if so, would that do the trick ?

Hi, I have not been updating my next cloud container in a while and I am pretty sure that I am still on nextcloud 16. I know I should have been updating in a while, but here we are. Now after updating the container today I was greeted by an Old friend. This version of Nextcloud is not compatible with > PHP 7.3. You are currently running 7.4.26. Can someone please tell me with which tag I have to reinstall the docker to get nextcloud 16 back up and running so I can start my update journey to the current release.

Please post the complete diagnostics file for the gurus to evaluate

I have a 40mm noctua fan mounted on the main heatsink of my lsi card. never had any issues with my card regardless of the season and it can get pretty hot in our appartement during the summer months.

Just because I am curious. Do you have active cooling on the lsi board. The chips on those can get very toasty when not cooled extensively,

I might not be of great help here but I will try to help you with what I would do in your situation First of all some questions: What Power Supply do you use in the system? Are you sure it works correctly and the power it delivers is sufficient? Is the RAM that you are using a set of 4 Sticks or did you have 2 Sticks from one Brand and added another pair form another Manufacturer? In your Log-Files I can see the Manufacturer of Channel B RAM but nothing for the Channel A RAM which made me curious. I am not a Guru in these matters but I would try a couple of things. 1. Remove any Overclocking if any is set in the BIOS incl. XMP Profiles for RAM - Test if the Error Persists 2. Run Memtest for at least 24h - Does it run through without errors? 3. Swap Power Supply with a replacement if availabel - Test if the Error Persists

After about 15h of rebuild the Server is back up and running as usual. Thanks for all the help. Thread Tagged Solved

Thanks to @trurl and @itimpi! Rebuild is now running. Will let you know how it goes.

Do I understand that correctly if I assume that stopping the array (not restarting the server) will also stop/cancel the read check that is paused now for whatever reason ? And the system will not resume this paused check after restarting the array but starting a rebuild of the disabled disk? Can I go forward with stopping the array and assign the hotspare to the slot of the disabled disk? Has anyone had the chance to look in my latest diagnostics so we can narrow down what happend? thanks for all your support Toby

Current diagnostics attached besides stopping all docker containers and stopping scheduler from running mover nothing has changed yet since pulling diagnostics this morning. Thanks for investigating @itimpi morpheus-diagnostics-20201115-2138.zip

So I am back in front of my server and there is one more question for the gurus in the forum before i atempt the rebuild of my disabled disk. As stated above the server was in the middle of a scheduled parity check when disk 3 got disabled this morning. When I look on my main page now under array operations it says "read check in progress" and it is indicating that the read check is paused. Is this expected behaviour? Do I need to stop the paused read-check first before I stop the array? Could the paused parity / read check somehow interfere with the rebuild i am trying to achive with the procedure above? I just want to make sure that I do not make my situation worse. Thank you all for your help.

Thanks @itimpi for confirming the procedure. I did see this portion of the syslog, and i do also think that the drive is just dying after its >60.000 h in operation (tough little spinner). I will start rebuilding on a new disk as soon as I am back home. In the meantime, lets see if anyone else has seen this error massages before and knows where it comes from.

Dear fellow UnRaiders, this morning during a nice breakfast with the family my server sent me a notification that one of my drives was disabled. As this is my first real "red X-Event" in my time using unraid I want to make sure to not make any mistakes. Regular monthly parity check was started tonight at 04:00 in the morning. Notification of disabled drive was received this morning at around 08:30. Data is emulated and i did a quick spot check on the network shares and data that resides on the emulated disk could be read. Array is still running, parity check was aborted by the server. The drive in question is one of my oldest and should have been replaced by now, but what should I say I have 2 precleared replacement drives (hot spares) available, so I should be in a good shape for replacing the disabled drive. Now I just want to make sure that I got the procedure for drive replacement correct and hope someone can look into my diagnostics to give me a hint what went wrong (besides using old drives ) and what would be the best way to go forward. Procedure to replace a data drive: 1. Stop Array 2. Unassign drive 3 (Do I need to start the array once with no drive assigned to the slot of disk 3 ?) 3. Assign one of the hot spares to disk 3 slot 4. Go to the Main -> Array Operation section 5. Put a check in the Yes, I'm sure checkbox (next to the information indicating the drive will be rebuilt) 6, Start the Array Is the procedure for disk replacement correct as described above ? Can someone help me in finding out what caused the disk to be disabled? Thanks in advance morpheus-diagnostics-20201115-0945.zip

Good to hear that your Server is back up and running. Please tag your Thread as (SOLVED) if you feel comfortable that the issue is solved. and BTW - Welcome to the Unraid Forum

Recovering from that state is out of my ballpark. @JorgeB Is there any chance for @steelrat to recover whatever was on the cache?

Adding the second drive in raid 1 would give protection and not more space, but if the 500 G drive was 90% full prior to adding the second drive it should not be overfilled just by adding the second drive. @steelrat Did you add any data to the cache after you added the second drive or did the docker and vm services go south directly after reboot.

I use PlexAmp while driving in the car via carplay. I nearly never use the tidal app itself. Management of Music from Tidal that I want to listen to, I do perform from the Plex Web App. Don't know about converting the Master quality to something else as I do not use a high quality HiFi system myself (I only have a standard Tidal subscription). My PlexAmp App is connected to my Plex server's music library which has Tidal content linked into it. I think my usecase might not be the same than yours

And as you have exchanged the failed drive, do not format or discard the old drive before your array is up and running again. Just in case anything goes south from here, you still have a copy of the data on that old disk! With a file system corruption of some kind, but still a viable source for data recovery just in case.

Yes this is possible, I moved in 2018 from a linux installation on an intel nuc to docker on unraid and did not loose anything from my meta data. @SpaceInvaderOne did a video about transferring Plex installations from one container to another (docker). Not completely your case but should help enough to get your head around. Plex2Plex by Spaceinvader One

As allready commented, you should never face your server to the internet. But most probably if the IP is always the one from your router, it might be as described above. Check if vulnarability scans are active on your router. Please attach your diagnostics file (Tools/Diagnostic) to your next post so someone can look into it.

The yellow triangles are shown because you have a single cache drive. The only way to get them green again is adding a second drive to a cache pool that is configured in RAID1 (redundancy) But in all cases you should have backups of the appdata and system folders in case anything goes south. Use CA Appdata Backup and restore from the community applications. For Q2 - @trurl allready requested your diagnostics file so some of the gurus can look into your reallocated sector issue.

did you have any Data on the 1TB drive that you are replacing ? Because from the dashboard picture you posted it looks like disk 2 and 3 are empty.