Knastrumpeten

Recently all my smart playlist have stopped showing up in the GUI. I have tried to delete the docker along with its appdata-folder and then reinstall the docker, but with no success. I can see in the log for daapd/OwnTone that there is a parsing error for every singel one of my playlist. I have consulted the manual (https://owntone.github.io/owntone-server/smart-playlists/) and stripped one playlist for every line except one just to understand what the problem might be. But still this entry shows up in the log: [2022-06-17 16:32:45] [ LOG] scan: Could not parse '"Ambient2" { media_kind is music }': syntax error, unexpected invalid token [2022-06-17 16:32:45] [ LOG] scan: Error parsing smart playlist '/music/Ambient2.smartpl' The playlist file looks like this: "Ambient2" { media_kind is music } As I said, I have not modified my smart playlist in a long time and they worked just fine a couple of weeks ago. I can't understand why daapd/OwnTone all of a sudden thinks this playlist contains an invalid token. I would really appreciate some help guys, thanks.

OMG Thank you sooo much!! I had the very same issue and your trick solved it!

Alright! Do you think they will include the RocketRaid drivers in the next stable release?

Hello! I'm new two Krusader (and unRAID) and this might be a stupid question. And it might not even be directly related to Krusader. However I have searched the internet to the best of my ability to find an answer with no luck. I also read the manual to Krusader with no luck. So I figured I would start here. I have a user share called "movies" with split level 2. This share currently spanns across two disks. When browsing through this share in Krusader as shown in the attached picture, all the individual movie folders on disk1 let me customize its permissions. But all the individual movie folders on disk3 has the permissions grayed out. Also in the Ownership box, there is a difference that individual movie folders on disk3 have user set to "???" while individual movie folders on disk1 has user set to "nobody", don't know if that is related. So my question is, why are these permissions grayed out on the individual movie folders on disk3 but no on disk1, and what does it mean? Is there some kind of inheritance going on? If so, how do I control this inheritance and why is it only that way on one of the disks? All the individual movie folders are transferred to the user share through SMB from a Windows machine. I'm running unRAID 6.3.5 and the latest Krusader docker. Thanks.

Thank you, that sounds very promising! Where did you found out this information? Can't find anything about it in the Prerelease Support.

Hello! I thought I should share my recent experiences with this controller in unRAID 6.3.5 and summarize to others who might thinking of using this controller with unRAID. And also to reach out for a final solution to the virtualization-problem. This is my hardware: Gigabyte GA-H270N-WIFI Intel Pentium G4600 3,6GHz Crucial Ballistix Sport LT White DDR4 PC19200/2400MHz CL16 2x8GB HighPoint RocketRAID 640 3 x WD Red WD40EFRX 64MB 4TB 3 x Samsung EcoGreen F4 HD204UI 32MB 2TB 2 x Seagate Momentus 7200.4 ST9250410AS 16MB 250GB This is the steps I had to take to make it work (kind of): 1) When I first plugged in this card in my unraid box, the thing wouldn't even boot any more. It freezed right after the the Highpoint RocketRAID BIOS screen. To get around this, I had to flash the controllers BIOS/Firmware to a version which disabled the raid features and simply transformed the controller to a plain sata-controller. This BIOS is refered to as "Non-RAID BIOS" or "Quick BIOS". I downloaded this BIOS from here: http://www.highpoint-tech.com/USA_new/rr600_download.htm 2) Then I hade to enable the controller using this custom script: 3) Then it turned out that this controller didn't work with VT-d enabled as described in this thread: And the provided fix with "iommu=pt" did not work for me. So I had to disable VT-d in my motherboard BIOS. So current status is that this controller "work", but with VT-d disabled in motherbord BIOS, which basicly means that unraid can not run any virtual machines.