SwimmingDiplodocus

after trying to reseat the cache drive nothing seemed to change (the cache drive was still not being detected). In order to see if the problem was the cache drive I bought a new SSD (WD 500GB M.2) and installed it. The drive is now recognized which makes me conclude the issue was the old drive. I haven't assigned and started my array yet. I've looked at the "replace a cache drive" instructions and there doesn't seem to be anything to do in preparation (all the recommended steps assume a functional cache drive) So my question to the community is - is there anything to do before assigning the cache and starting up the array? A secondary question is should I expect my old docker apps to still be available? I'm pretty sure they would have had the default setup as I don't recall customizing anything on that front.

I assume this means open the case, unseat the cache SSD, and reseat. Or are you referring to something else? Thank for the help!

Thanks ChatNoir, here are the diagnostics. The array was not on-line. padua-diagnostics-20201123-0931.zip

I think I had a cache failure and am unsure how to proceed. Brief description of my setup: - unraid 6.6.0 - 2x 3tb drives - 1x 3tb parity - ssd cache During a copy operation involving several GB my cache went up to 66C, the copy operation started hanging but eventually completed. Afterwards I could no longer start docker containers (e.g. plex). I rebooted and tried a complete power down (waiting several hours to make sure everything cooled). The cache drive no longer shows up and if I mount the array none of the docker containers appear. I just don't know what my next steps should be and if there is a way to recover my docker containers thanks for the help

It is a Bluray drive. I've only checked with CDs so I'm not sure about DVD or Bluray speeds. With a data CD inside the Ubuntu VM: pv whatever.tmp > ~/whatever.tmp 65.9MiB 0:00:12 [5.07MiB/s] [========================================================>] 100% and directly at the unraid terminal: pv whatever.tmp > /mnt/user/whatever.tmp 65.9MiB 0:00:13 [4.81MiB/s] [=====================================================================>] 100% These appear within error to me and as expected for a CD (>24x speed, so full speed spinning). So I do not see a slowdown for CDs

So after a variety of attempts from a number of forum posts, the following approach link1 link2 worked for me: >> lsscsi [2:0:0:0] cd/dvd HL-DT-ST BD-RE WH14NS40 1.03 /dev/sr0 And then hand modifying the ubuntu XML VM with <controller type='scsi' index='0' model='virtio-scsi'/> <hostdev mode='subsystem' type='scsi'> <source> <adapter name='scsi_host2'/> <address type='scsi' bus='0' target='0' unit='0'/> </source> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </hostdev> Other posts had suggested changing the controller value to "1" which did not work for me. I now have access to the Blu-ray drive from within the Ubuntu VM (it automatically detects a Audio disk insert and mounts it). I am now able to rip audio CDs which was my original objective.

Has the question of passing through a DVD (or Blu-ray) connected via SATA to the motherboard been resolved? I am looking to do audio CD ripping, disc backups, and movie rips. I am aware of the makemkv docker which works well but I have not found any docker solutions for CD audio ripping that work. To be clear, I have a 6.6.0 Unraid computer, I am running a Ubuntu VM, and am looking for a way to access the blu-ray drive from within the Ubuntu VM.