docfallingapart

Any idea why I get "OCI runtime exec failed: exec failed: container_linux.go:367: starting container process caused: exec: "bash": executable file not found in $PATH: unknown" when I try the Console? I mean it looks like the container path, but I don't know why that would be not already working, and I have no idea how to change it. I can send docker commands. Tried installing 'bash' that way, and the install worked fine, but bash actually missing doesn't appear to be the issue. Thanks for all your work on this! It's the only good solution for my setup and I'd be SOL without it.

It appears that last Friday night Unraid decided to deleted all the files that were at the root of all of my shares. In two cases were the share had no subfolders, the entire share was deleted with the files. Any file that was in a subfolder of any share was not deleted. As my Unraid server is primally used as a Plex server, the lost was ~10TB of movie files, as these were at the root of the share. Unfortunately, before I released the extent of the issue I had, I rebooted the server and lost the log. So I'm actually guessing the files were "deleted". The files are gone, however it was done. I didn't think about how rebooting an OS that runs completely in ram would be an issue for things like log retention. Probably should have thought that thought a bit more, but I'm new to the ways of Unraid. The server had been running for at least three weeks without issue before this happened. My drives are all BTRFS formatted with two parity and two cache drives. I could not find any scheduled jobs for Friday that might have kicked this off. I can't find a system setting that explains what happened. I'm at a complete lost as to what could have caused this, so I really hope someone here can help me as to the cause of this. As for recovering my files I assume I'm going to have to use a file recovery utility like 'btrfs restore'. So, I'm mostly looking for root cause here unless there is an "easy" way to recover that I don't know about. I just want to make sure this doesn't happen again. Here is my log with my array online. For what it's worth. unraidserver-syslog-20211019-0657.zip

None what so ever. As I said it's just my opinion. Also, I'm using BTRFS on my array. It's not worth doing it over as like you said BTRFS is fine and will work. However, if I could go back in time three weeks, I would have gone with XFS as I don't see any plus of using BTRFS on Unraid. Most of the cool features that make BTRFS great on a desktop, just don't apply on Unraid. As least as far as I've figured out in the limited time I've been doing this. I am an Unraid noob for sure so I"m hardly authoritative on the matter. If you see some benefit to using BTRFS on Unraid, please share it with the group, for the next guy that is just getting started.

Turns out I'm and idiot. I finally found Spaceinvaders excellent video explaining how Unraid parity works. https://youtu.be/HybwCOVDg9k From what I now know after doing my homework, in regards to my original question about using BTRFS on the array drives, I see no good reason to do it. BTRFS will not hurt anything but XFS would be a simpler, faster, and better choice. IMO BTRFS should only be used on the cache pool in Unraid. Hopefully this will help someone that had the same question about using BTRFS that I had. On an unrelated note BTRFS is great for your Linux laptop or workstation which is why I thought of using it on Unraid. So, use it there but not on Unraid array drives.

I updated to the new version (2021.09.26) . Unfortunately, I'm getting a different but similar error. Looks the same expect the last line number has changed. Everything does seem to be working fine. If you need anything from me, please let me know. Warning: syntax error, unexpected '!' in Unknown on line 41 in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1816

Sounds great. If not I'll let you know. Thanks.

Here you go. Thanks! unassigned.devices.ini.txt

I'm getting the following syntax error. Warning: syntax error, unexpected '!' in Unknown on line 41 in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1834 This is a new Unraid server and I've temporarily connected a USB3 Probox drive encloser with 4 sata drives until I can complete coping the data of it. I also have two sata drives connected to sata ports on the Intel Z170 motherboard. The Unraid array itself is using a LSI HBA. As far as I have found the syntax error has not impeded the functionality of the UD plugin. unraidserver-diagnostics-20210926-0245.zip

From what little I could find I thought that was the case. Thanks for the conformation. I do think it's too bad the Unraid devs don't have a high level architectural document somewhere so that it wasn't such a black box. At least for people like me that worry about things like that.

First, I know that I should and must use btrfs on my cache pool. However, I also used it on my array or host drives. I should have done more homework on this. I looked a bit at ZFS, but I do like GUI's and I hate Oracle with a passion so said, "Ok I'll go btrfs". I should have looked a xfs more and found out why it was the default during setup, but I didn't. Now a week later and I read an Ars Technica article about btrfs and how it does raid and it scared the crap out of me. Not sure about linking on the forum so if you want to read the article you can look it up on their site. In short, the article gives some very good examples of why btrfs is a pain at least, and catastrophic at worst when you have raid issues. So, I decided I needed a better understanding of how Unraid NAS features work under the hood as I think Unraid isn't using btrfs raid for redundancy in the array. If that's the case then btrfs should be fine to use "I think!". However, the only thing I can find about Unraid under the hood it that "It's like a MAID (Massive Array of Individual Disks), but that's it. I can find anything else. So, I'm writing this (sorry for the length) post, and I hope someone can give a brief explanation on how the NAS features of Unraid work. Why btrfs is or isn't an issue? Why is xfs recommended over btrfs assuming it still is? Thanks.