Kacper

Hi guys, I have updated this plugin to work with unraid 7.2.4. I did it a bit lousy, by copying binaries from slackware, but it works. The INSTALL LINK IS: https://raw.githubusercontent.com/k4cus/unRAID/refs/heads/master/Plugins/ProFTPd.plg Update plugin message shouldn't be there, but I am too lazy to fix it. Debugging command is: ldd /usr/local/SlrG-Common/usr/local/sbin/proftpd - this will show You missing libraries if any (libsodium.so.26 is required and included in this package) sudo -u root /usr/local/SlrG-Common/usr/local/sbin/proftpd -c /etc/proftpd.conf - this will run daemon showing errors on screen

I have tried shinobi and it didnt work for me. I can recommend Frigate with Coral TPU for human detection. It is not perfect, but it is working well for me.

My script looks like that: #!/bin/bash container_name="frigate" if [ "$(docker inspect -f '{{.State.Running}}' "$container_name" 2>/dev/null)" = "true" ]; then printf -v date '%(%Y-%m-%d %H:%M:%S)T' -1 echo "Restarting $container_name at $date" docker restart "$container_name"; fi

Hi guys, I just want to share result of 3 day investigation. So I am running my Unraid on thinkpad W530 mounted on wall using 19 inch rack tray. However laptop is mounted vertically so I have elastic gum that i snap in to hold it by the wall. Recently I was having problem with express card usb not appearing, sometimes laptop didn't reboot but was stuck on lenovo logo screen. I had to open lid, kill it with power switch and boot again and so on. In dmesg I was seeing constantly ACPI BIOS Error... So what was the reason? In some unknown way when lid was closed and elastic gum was holding laptop against wall (not very strong, really light pressure) it was enough to press some buttons on touchpad or on the keyboard I suppose. This pressure was causing mysterious acpi error and was preventing from proper reboot and making express card usb 3.0 not visible. SOLUTION: I have glued two pieces of sponge on the top, where lid closes, so it is closed but not completely. Problem is gone completely!!! :D

Hi sorry for not responding. Yes my W530 works very well since 2020 i think. I had to move it outside rack box, because drives were overheating and failed twice. Now it is mounted to the wall, much cooler and is fine. I have attached TPU google Coral + Frigate as my home DVR with people detection. I am running many dockers and one virtual machine with mikrotik for dude monitoring. It is working quite well. I have 3 hdd drives installed as usb drives and 2+1 drives inside the pc. I would recommend ssd to put inside laptop, as hdd`s are getting quite hot. So basically my setup is: Array: 1 ssd 2.5 in primary drive bay - more often accessed data (owncloud) 1 hdd 2.5 in cdrom drive place - movies, installs, music, etc. 1 msata drive as cache drive for the array 2 hdds on usb - one drive to expand space of the array, and one drive is for parity. 1 spare drive attached by unassigned devices plugin for dvr recording. It is quite important to backup thumb drive with unraid install, as it tends to fail. I have tried many brands and had failure twice already. Good thing is that it was usually accessible when connected to another machine to copy files from it, however it was not booting. Even nvidia gpu is passed to frigate docker and is using it for video decoding from h264 streams, which reliefs cpu a lot.

You must download in Settings-> VMsettings virtio driver version virtio-win-0.1.215-2.iso Newer versions do like you described.

I am using lenovo w530 as unraid server for several years already. I have two internal data drives and parity + one data drive as external usb. Everything sits in my basement. Disks are attached to 19inch drawer with laptop and cooling fan. Performance isn't great, I have some issues but I am not convinced my problems come from usb connection. Basically avoid usb drives in array if you can - one uncertain point of failure less to worry about. However I have my Zoneminder DVR on unraid and this one is writing an usb drive, that is attached as separate drive (outside array) and this is very fine solution. In the worst case my Zoneminder will crash - not a big deal. So in last 5 years I didn't track any usb drives related problems. I had many software problems, I had internal drive failure due to overheating (external usb drives stay cooler). Once my w530 lenovo dies I will replace it with regular tower pc (3,5 HDDS are much cheaper and reliable than 2,5 inch!). Besides that I am planning to use flash storage for my owncloud (that is primary purpose of my unraid) and hdd for movies/music/backups/archives. If you are creating new server I would recommend full size pc. If you have any spare usb drive You want to use besides regular drives, go ahead, but avoid storing valuable data on it. Of course balance with your budget. I still keep my old setup, because I prefer to rent a sailboat that buy new file server for these money. That would be my recommendation.

Oh hi, ok, so to finish telling my story after Disk 1 was mounted properly and I could see my data I did following steps: 1. Installed nerd plugin to install screen 2. In root console I run screen -> mc (midnight commander) 3. I moved all data from /mnt/disk1 to /mnt/disk2 using mc F6 button. It took whole day long 4. Then I confirmed that Disk 1 does not contain any data. 5. I stopped the array. 6. I did a screenshoot of MAIN tab 7. I went to Tools-> New Config and created new empty config of an array, without coping any old configuration. Just completely new array. 8. Then I went to main tab and assigned hard drives to new array, paying supper careful attention that parity drive is the same drive as it was before and that cache drive is the same drive as it was before. I check disk IDs with the screenshoot (p.6) 10 times I added new drive (smaller) in slot where Disk 1 is, as a replacement of failed drive (original drive was 2TB). 9. Then I have stared the array. 10. Then I went to docker tab to stop all dockers as the will degrade array parity rebuild performance a lot! I also stopped all VMs. 11. After parity was rebuild and array was safe I moved some of the most important data from disk 2 to new disk 1. In my case this is appdata, because owncloud is the main reason I am using self hosted NAS and Unraid. All other dockers are my playground, but Owncloud I am using in my job to sync data between PCs, so it is feeding my family, it is priority no 1! Of course if I want to afford new 2TB hard drive to replace broken one (it must be equal size or bigger!), after fixing filesystem on drive 1 I could simply rebuild my array from parity. However I didn't want to do it simple way for those reasons: I didn't want to spend cash on 2TB 2,5 inch HD. My space usage was low enough that I didn't need that much space. I had server grade Intel ssd in my drawer, but it was 0,5 TB in size. It is sufficient to keep my owncloud data and even maybe whole appdata folder. Also my server is running quite hot as this is laptop in my garage, so I preferred to replace hdd with ssd as ssd is more resistant to temperature around 50-60 Celcius degree. Therefore I did procedure above to do it the way I wanted. The result I will show on screenshoot: So it is rebuilding parity now. Point 11 actually I am just about to do in 30 minutes after I am writing this post I hope that my summary will help any person that will get they array degradated. Remember, do not format, do not erase before You are 100% sure what it will do. Better wait and ask on forum, wait patiently for the answer, do not panic or rush thing as Your data might be still there! That was my case cheers! p.s. I didn't mention that I was not rebooting my server for two years almost, so when my disk 1 drive failed I rebooted and it booted correctly, but the second time I rebooted it didn't boot. It has appeared that at the same time my flash drive had fault usb connection, so it was disappearing and reappering. Obviously my flashdrive backup was one year old So I had to deal with two failures at the same time, but when it comes to flash drive just: Put old flash drive in any PC and copy whole content to another folder on your PC (if this does not work then You can only use backup if you have one or maybe you can recover configuration files partially, eg share configurations, etc.). I didn't have any up to date backup but luckily I was ably to copy all files from failing flashdrive! Then use unraid tool to format new flash drive -> do fresh install on new flashdrive. Then put new flashdrive into PC, delete all files from fat drive, and copy all files from folder where you have stored content of the old/failing flash drive. Safely remove flashdrive.

OK guys, huge thanks to "itimpi", you gave me a tip how to do this and I have figured it out !!! Your key answer was here: "Did you also do a repair (I.e. run without the -n option). This is required to actually fix the file system on the emulated drive." So my attempt to do check while array is started in normal mode did nothing. It just said 0 errors. To conclude, in situation when one drive fails, then it says "context emulated" disk is marked with red cross but actually content of the disk is not emulated (you cannot see browse button next to Disk 1 name - see my first post). In this case unraid says "unmountable: blabla". In my case filesystem was corrupted on Drive 1. So what You need to do is: 1. Stop array. 2. Star array in maintenance mode. 3. Click on removed or faulty disk and then run check for this one disk, however !!! MOST IMPORTANT !!! by default it adds -n option to check. It makes only do readonly check without fixing by default. Remove "-n" and click to check drive. 4. Stop array. 5. Start array in normal mode. Now you should be able to see emulated data from emulated drive. See the screen shoot of my array before and after check. Solution is so silly and it was impossible for me to figure it out from unraid docs. Doc are quite counterintuitive for me. Community is what makes this product really cool and my faith in unraid parity has been restored. Thanks again Mr "itimpi", I get You a beer if You come to my city Wrocław in Poland!

I clicked check in unraid GUI - do not know what command is run under this. How should I run this command? If disk is emulated what would be the device name and therefore the command ? I am not sure what is doing. On one hand I think it is running some kind of fs_check, but on the other hand in GUI it says: "Parity operation is running" so maybe it will calculate emulated drive out of parity ? That is the thing that unraid gui is not very intuitive and I am using it rarely so it is even more difficult to remember how to do things. I have found such an information in logs: [ 976.358462] XFS (md1p1): Mounting V5 Filesystem [ 977.592064] XFS (md1p1): Corruption warning: Metadata has LSN (179:604764) ahead of current LSN (179:604745). Please unmount and run xfs_repair (>= v4.3) to resolve. [ 977.592082] XFS (md1p1): log mount/recovery failed: error -22 [ 977.592264] XFS (md1p1): log mount failed I think this is the broken drive 1, which might be that I have to run xfs_repair /dev/md1p1 ?? I have no idea if this is correct thinking?

I did run check on disk 1 in maintenance mode, then I stopped array and started in normal mode, but disk 1 does not mount and I cannot see any data in shares that were on this drive. Now with array in normal mode I clicked "check" and it will do check for 5 hours now. So the timeline here is as follows: 1. I can remember that the first time I have logged in to unraid and saw Disk 1 as red cross it was emulating and I could see data. 2. Then I have rebooted my unraid server and disk 1 was still failed. 3. Then I had it shutdown and removed failed drive. 4. When I booted it there is no data from Disk 1. 5. Next I did check on Disk 1 in maintenance mode - still no data disk1 not mounted. 6. Now I am doing check of whole array in normal mode. What actually has happened? Did the parity messed up when I unplugged failed drive or what can this be?

So after doing disk check did your data reappeared in emulated drive or you had to recover from backup?

OK, I am reading it however it does not provide any new information on what is going on. My disk cannot be browsed as it claims to be emulated. I was even able to run check on Disk 1 when in maintenance mode, but data are still not accessible. I am wondering if I add 2TB drive will it rebuild and show all my data? The thing is I do not have spare drive and I do not want to spend money on it as I do not need such a capacity nas-diagnostics-20240720-1732.zip

Hi, I am terrified, because I have one failed drive. I have shutdown unraid and removed failed drive. Now I can star array, it says disk 1 is emulated, but there is no data available from this drive. Does it mean that my data is gone? That parity didn't protect my data? Or maybe I need to put back my failed drive into system again, which would be quite nonsense? I do not want to buy new drive and rebuild, because it is too expensive. I want to move my data to second drive, as I have plenty of space free and then recreate array. I have attached screenshot from my array. When it is started i do not see /mnt/disk1 as I should. Is there anything I can do or this unraid parity is complete garbage and I have lost my data? Help!

One more question, can You post Your: root@nas:/mnt/disk1/owncloud/config/www/owncloud# ls -l total 540 -rw-r--r-- 1 root users 8859 Jan 12 15:29 AUTHORS -rw-r--r-- 1 root users 411639 Jan 12 15:29 CHANGELOG.md -rw-r--r-- 1 root users 34520 Jan 12 15:29 COPYING -rw-r--r-- 1 root users 2425 Jan 12 15:29 README.md drwxrwxrwx 51 nobody users 4096 Mar 23 15:13 apps drwxr-xr-x 2 nobody users 6 Dec 10 2020 apps-external drwxrwxrwx 2 nobody users 79 Mar 23 15:10 config -rw-r--r-- 1 root users 4618 Jan 12 15:29 console.php drwxr-xr-x 16 root users 335 Jan 12 15:30 core -rw-r--r-- 1 root users 1717 Jan 12 15:29 cron.php -rw-r--r-- 1 root users 31204 Jan 12 15:29 db_structure.xml -rw-r--r-- 1 root users 179 Jan 12 15:29 index.html -rw-r--r-- 1 root users 3518 Jan 12 15:29 index.php drwxr-xr-x 6 root users 79 Jan 12 15:29 lib -rwxr-xr-x 1 root users 283 Jan 12 15:29 occ drwxr-xr-x 2 root users 23 Jan 12 15:29 ocm-provider drwxr-xr-x 2 root users 55 Jan 12 15:29 ocs drwxr-xr-x 2 root users 23 Jan 12 15:29 ocs-provider -rw-r--r-- 1 root users 3135 Jan 12 15:29 public.php -rw-r--r-- 1 root users 5618 Jan 12 15:29 remote.php drwxr-xr-x 4 root users 39 Jan 12 15:29 resources -rw-r--r-- 1 root users 26 Jan 12 15:29 robots.txt drwxr-xr-x 12 root users 209 Jan 12 15:29 settings -rw-r--r-- 1 root users 2231 Jan 12 15:29 status.php drwxr-xr-x 6 nobody users 150 Nov 14 2019 updater -rw-r--r-- 1 root users 280 Jan 12 15:29 version.php