HAMANY

Hi, I went through the same issue in this post (Disk rebuild lost data), and I did the same mistake. Yes, unfortunately, I formatted the drive when I got the format unsupported message. This is a brief of what happened: - Disk 1 got disabled while the array is running. - Restarted the server, didn't see any SMART errors, Disk 1 rebuild started. - After around 50%, Disk 1 got disabled again, and rebuilding stopped. - Checked the connections, restarted the server again, no SMART errors. - When I started the array, the rebuilding didn't start, but I got a message saying that Disk 1 format is not supported and I have to format it. - I did the format, thinking that the data still will be available through emulation. - I lost around 7TB of data, Disk 1 is showing 8TB free space Is there any chance for data recovery? I don't have a backup, the only way is to re-download all files again which will take months Please let me know if you require any further information. Your help means a lot to me. Much appreciated. Unraid Version: 6.7.2 CPU: AMD Ryzen 7 2700X Mobo: MSI X470 GAMING PLUS (MS-7B79) Memory: 16 GiB DDR4 tower-diagnostics-20190801-1744.zip tower-smart-20190801-2045.zip

After installing the cache drive, go to Shares and change the Use cache disk to Prefer to these shares: appdata, domains, system, and any other share you want. I think you have to run the Mover to take action.

Thank you. For reference, this has been resolved by adding the below line: store dos attributes = yes To: Settings -> SMB -> SMB Extras -> Samba extra configuration Keep it at the first line Then reboot unRaid or restart samba using the below commands: samba restart smbd restart

Thank you both. I think the problem is solved after disabling the c-states in bios. 2 days uptime for the first time.

Hi, Recently, I've upgraded my unRaid server from Intel i5 3570 to AMD Ryzen 7 2700x for more cores and HW pass-through. The old hardware was working just fine. At the beginning, the OS was crashing only after 30-45 minutes. I followed this video and added "rcu_nocbs=0-15" after "append" under (unRAID OS) and (unRAID OS GUI Mode). This made unRaid to remain a little bit longer, now it's crashing after 8-10 hours. I've attached the logs from Fix Common Problems (troubleshooting mode). Not sure if there is any other way to investigate further? Appreciate your help. New spec: CPU: AMD Ryzen 7 2700x Mobo: MSI Gaming Plus X470 (Latest Bios version) Memory: 16GB unRaid version: 6.6.7 logs.zip

Hi all, Recently, I moved from Windows 10 to unRAID for the storage server. I used to change the folder icons of my movies and TV shows with different colors to mark them as: Watched, To be watched next, not completed. After moving my data to unRAID, the icons didn't work as expected. I did a quick research and found that Linux doesn't treat the "Read Only" files same as Windows, so the "desktop.ini" and ".ico" files don't work. Is there any work around or a solution for this issue? any suggestions? Thank you

Yes, it happens to me also. The only workaround I found is to edit the configuration file (rtorrent.rc) located in (\\tower\appdata\rutorrent\rtorrent)

New unRaid user here, I've few questions and I hope to find some answers. Q1: Torrents downloaded by rTorrent creates folders/files with read permission only! Any idea how to fix it? The profileMask is already set to 0777 .. Running the "New Permissions" tool have fixed the files permission, but would like to know if there is a permanent solution. Q2: Anyway to stop ruTorrent from creating the completed/incoming/watched folders? I made the Host Path: /mnt/user/ so the docker has created new shares in my unRaid. Q3: Changes done in ruTorrent don't get saved. Every time I restart the docker I get the default settings. Any idea what's wrong? Q4: I've installed 2 different ruTorrent dockers which have created 2 folders in the appdata with the same name, but one of them with capital T (ruTorrent and rutorrent). I've removed the other docker but the appdata folder was not deleted. Since Windows treat both folders the same, how can delete the extra one? Thanks. Had the same issue, fixed it by 1) removing the ruTorrent docker, 2) reboot unRaid, 3) installed ruTorrent again.