ShortbreadUK

Hi @comet424 SpaceInvaderOne has answered this question in post number 2 of this thread. I have just done the whole video from scratch, encountered your error, then fixed it with this: On new installs it is now necessary to manually install the database files on first run. Going to http://xxx.xxx.xxx.xxx/8080/super and logging in you will see this Now goto the docker tab and select the shinobipro container and click console. This will open a terminal inside of the container. Now run these commands below: mysql source sql/framework.sql; source sql/user.sql; exit Now close terminal window and restart the container.

Just an update. The 'Wrong or no file system' issue came back every time I shut down my Win10 VM. Time for a cache reformat! I decided to Move everything off the cache using the Cache:Yes and initiate Mover to get it on to the array. Some stuff got a bit stuck but I used Dynamix File Manager to shift it across on to the array manually. I changed the file system to xfs on the cache drive, formatted it, then changed back to btrfs and reformatted. I set the Shares I had on the cache back to Prefer and moved everything back on to the cache. Whilst it seems like that should just work, I had all sorts of issues with my docker containers and VMs that didn't appear in the tabs as they couldn't read the appdata properly. I had to restore my original appdata from backup, then go in to Apps and Previous Apps to download my containers again from the saved templates and set to read from the restored appdata. Once I did that, the dockers came back with their previous settings. Also after that, the VMs appeared and were able to boot with no issues. Another issue that I had with the docker container was that the Plex database was corrupt. I tried SpaceInvaderOne's solution on his very helpful YouTube video, but that didn't work either. I did have 2 or 3 database backups in the same folder and replaced the database with the last backup. That's now working. A bit of a learning curve for me, but I hope that I have everything fixed now and a more stable cache drive!

Thanks for your assistance @JorgeB!

Ah! That's brought it back online for me, thank you so much! Do you think I should move everything (3 shares and VM) back on to my array, reformat my cache drive, then move them back on to the cache?

Hello everyone, I have one 2TB nvme drive that is running all my cache (appdata, domains and system) and also have my daily driver Win10 VM (with gfx passthrough) on that nvme. Just recently the VM went a bit haywire so I rebooted it. That didn't have any effect, so I rebooted the server. After that, the nvme drive on the Main screen is showing 'Unmountable - Wrong or no file system'. I have rebooted and tried reseating the drive, but no improvement. It gives me the option to Format the unmountable disks, but I don't want to go ahead with that until I have found out any possible issue (I do have backups of the three shares mentioned above and the VM). I did also stop the array, removing it as a cache drive and try mounting the drive as an unassigned device, but didn't like that either. Thanks in advance! shortraid-diagnostics-20230313-1456.zip

This fixed my issue too, thank you!

Hi UnRaiders, I'm getting to the end of my tether with stability of UnRAID, please help or I go back to Windows. I'm having a real issue with GPU passthrough to a Win10 VM. The IOMMU groups and split up quite nicely with my mobo, I dumped my own vbios and I'm referencing that in the VM settings. But when I start the VM up it doesn't show anything and I see a whole lot of this is the VM log: 2018-05-24T13:17:35.701483Z qemu-system-x86_64: vfio_region_write(0000:01:00.0:region0+0xf9788d8, 0x0,8) failed: Device or resource busy Seems like there is another driver in the host claiming resources or something, but can't manage to fix it. Someone please help? Thanks in advance serverbread-diagnostics-20180524-1424.zip

So how did you go about doing it?

I'm looking to get the Coffee lake working (i7-8700). Anyone managed it yet? Edit: @salora you have the same i7-8700? Please fill me in!