Tesla3327

That did fix the issue at least. Hopefully it was just a fluke... Thanks!

I am having the same issue of being unable to load any disc. Oddly enough I didn't have any problem until December. I successfully ripped some blu-rays last on 2022.10.13. On 2022.12.07 I attempted to rip a disc, and while it loaded I was unable to encrypt. It was a pretty new release so I figured I'd wait a week or so. On the 14th I attempted a different disc and started to get the issue of no disc loading. I tried a number of different discs but none of them will load in the container. I also confirmed these discs were working on another computer running the windows version (makemkv v1.17.2) so it seems to be a container issue. I was running the latest image up until today when I tried to run it on 1.22.1 & 1.22.0. Neither of those fixed the problem. MakeMKV_log.txt

Your friendly reminder to check price histories for these. The 'discount' can often be misleading to what the 'normal' price is My real suggestion is to not shop with Amazon (especially on prime day), but if you do, looking at the price history can stomp the impulsiveness of seeing a good deal.

Update: I received my new SATA cables and tried them out. Unbeknownst to me I swapped the power cables that went to the ADATA system drives, and the power cables that were going to the Samsung drives. When booting on the computer I heard a pop and smelled ozone. Both ADATA drives are now dead. So it seems like there WAS an issue with the power cable heading towards the Samsung drives. I can't say if that was for sure what was causing the drives from disappearing but it's the best theory so far. That doesn't explain to me why the NVME drive disappeared in the first place (or why nomadgeek was having a similar problem), but I had to move that drive back into my system now that the ADATA drives are dead, so I'll be able to see if the problem comes back. Thanks again to JorgeB and trurl for shooting ideas at me while I tried to troubleshoot.

Thank you for the suggestion, I had not considered that before. I just checked, and unfortunately both of my drives were already up to date with firmware. 😕

For the motherboard? I did upgrade to the latest BIOS version sometime before I initially posted.

Interesting. Glad I'm not alone at least. For me though simply trying to copy a 32GB folder onto the cache drive is enough to do it. Would you mind posting your build's specs if you have the time? I am considering a new MB at this point.

For the record, I just tried everything in Safe Mode and still had the same problem

Thanks for helping out too! Not on these drives. The only splits that happens is the SAS -> SATA breakout cables on the HBA cards. For all the cache drives they are plugged directly into the MB and the power cables are run directly from the PSU. The two ADATA Systemdrives are on a separate power cable than the Samsung Cache Drives too.

Just tried different power cables too. No dice

That's what I was using actually. Just tried a different set of cables (I used to use these on my my Array drives before getting the HBA card), and the drive still goes missing under load... I think I'll just order some brand new ones to try just in case, but until they arrive do you have any other suggestions?

Thank you for the suggestion. The Cache drives sat idle overnight without any issues, so before trying your suggestion I copied some files to and from those drives to see if that triggered the disks going missing. Sure enough that did it. So it seems to happen only when the drives experience load. So I swapped the ports used for the Systemdrives for the ones used for cache drives as you suggested and tried to reproduce. Interestingly enough while I was copying files (From the array to the Systemdrives) one of the Cache drives (which were sitting idle) went missing. So it seems like it's only when the chipset is under load? Do you think it could be the SATA cables? My gut says no since the NVME Drive also went missing at some point. Please let me know if you have any other suggestions, and thanks again for taking the time to read it the first time. tomservo-diagnostics-20220609-0853.zip

Hello, I posted this on the ASRock forum too because I believe the problem is hardware based, but would appreciate any additional insight from people if possible. I use an ASRock Z690M Phantom Gaming 4 as the MB in my unRAID system. Full specs at the end. TL;DR is that drives plugged into SATA3_0, SATA3_1. & M.2_2 have started to spontaneously disappear and are not recognized by the MB again until the system is completely shut down and powered back up. Important to note that I have a cache pool consisting of two SSDs in RAID1. 4 days ago I received a notification that one of the drives in my cache pool has gone missing. It was a Western Digital PCIE gen 3 nvme drive installed in the 2nd m.2 slot of my MB. I did not have anything installed on the SATA port that is shared with m.2 slot (SATA3_0). I assumed that the drive had just failed and pulled it from the system and went to order a replacement. I ended up deciding to replace both cache drives with two Samsung 870 EVO SATA SSDs. I installed these drives into SATA3_0 & SATA3_1 slots. I still did not have anything in the second M.2 slot. The next day I get another notification that the drive has gone missing. Through some troubleshooting I have determined that the drives will disappear, and will not re-appear until the system is shut down. Rebooting the system via the unRAID web interface does not cause the drives to re-appear. To reiterate that last part. If a drive has disappeared, and I hit "Reboot" the drives do not re-appear; however, if I shutdown the system completely, and then walk over and turn it back on, the drives re-appear (for a little while) Also important to note: I have two other SSDs plugged into SATA3_2 & SATA3_3 that have not disappeared at all. After the brand new drives disappeared I did try upgrading unRAID from 6.10.0 > 6.10.2. No help. Also my MB was running BIOS V3.01, but I did upgrade it to V7.02 during troubleshooting and it made no difference. I have a feeling there may be an issue with the MB chipset, but I'm not sure why it would effect M.2_2, SATA3_0, & SATA3_1 only. System Specs: CPU: Intel Core i7-12700K 3.6 GHz 12-Core Processor Motherboard: ASRock Z690M Phantom Gaming 4 Micro ATX LGA1700 Motherboard Memory: Corsair Vengeance LPX 64GB (4 x 16 GB) DDR4-3600 CL18 Memory x2 ADATA SU630 480 GB 2.5" SSD in RAID1 used for docker containers and VM Drives - plugged into SATA3_2 & SATA3_3 x1 WD Black SN750 1 TB NVME SSD - 1 of the NVMEs used in the original Cache Pool - Installed in M.2_1 x1 WD Green 960 GB NVME SSD - The other NVME that was the first drive to go missing - Previously installed in M.2_2, now uninstalled x2 Samsung 870 EVO 1 TB 2.5" SSD - in RAID1 as the new cache pool. Plugged into SATA3_0 & SATA3_1 x8 Various 3.5" HDDs for the array - No issues with any of these drives - Installed via LSI Card flashed into IT mode tomservo-diagnostics-20220608-1410.zip

Ha! Never noticed that feature before. Thanks!

Yes lol. Thanks for this, and your original post!

Sorry, new to the forum here so may have double posted. I noticed on the official "doc" guide that step three states "Click on Shares and set all shares present on your Cache disk to Use cache disk: No." which obviously gave me some issues until I found this thread. Do you know where I can direct this to be corrected? Thanks.