bigrizz

I recently had one of my new drives go offline in my array. After checking, it reported file system corruption, so I started the array in maintenance mode and ran the fix, which seemed to have sorted it. A week or so later, I noticed my parity check was reporting a bunch of errors but the offending drive wasn't showing as offline, so I took the array down and once again started it in maintenance mode and ran a check. The drive yet again was coming up with file system corruption, so I ran the fix and it seemed to be ok. A week later, same thing again. I've just run the fix for the third time. I'm hoping someone can save me a whole lot of troubleshooting here. I'm wondering if the drive is faulty? No SMART errors are being reported even after running an extended check. The drive is a WD Red (WDC_WD40EFPX) and installed about 3 months ago. Coincidentally and for context, I also had just upgraded Unraid to the latest release candidate 7.2.0 rc1. I'm now on the official release 7.2.0. I'm not sure if it's correlation or causation. Could it be a dodgy connection to the drive? I'm not sure that would manifest this way. Anyone have similar experience? Any suggestions where I should start? I've probably blown away the logs now I've restarted the server. In hindsight, I should have saved logs to see if they revealed anything. Oops.

That's a good point. I'm yet to test that. I think the drives are still good. I'm just getting SMART errors based on old age. Experience tells me that it won't be long before they fail. I've just received my new drive in the post today, so that'll be a job for my weekend for sure.

I have two drives in my array starting to fail. One is 1.5TB and the other is 4TB. My plan is to remove both and replace them with a single 4TB drive. Effectively, I'm replacing the 4TB drive and removing the 1.5TB drive altogether. I found this guide that talks about replacing two smaller drives with one larger drive. I'm assuming it is equally valid in my scenario? The amount of data on my two failing drives is less than 4TB - less than 3TB, in fact. I think I'm safe but just thought I'd ask, just in case I'm missing something. Just want the simplest process to remove my two failing drives.

Hi @mjeshurun. Old post but wondering if you figured it out? I have the same situation with Adguard and no Wireguard support yet.

@abraunegg, I can confirm it was indeed the change in the config file location that was the problem as it now seems to be working properly after a resync. Thank you again for your response and your work on creating the integration. It is an indispensible part of how we access our files.

Thanks for your quick response. I've just gone in to check other files and they were fine. Just the files post re-installation. That prompted me to check if anything else changed and I think I found my problem. I think the config file location in the Docker configuration reverted to the wrong folder. I changed it which then once again triggered a --resync requirement. I've kicked off a resync and I'll test permissions again. I'll come back with an update once I've done the check.

I uninstalled and reinstalled the docker and that seems to have rectified the --resync requirement. My new problem is that I am unable to open files in my shares that have been synced from OneDrive to my NAS. I had this same issue with the previous version and uncommenting the lines sync_dir_permissions = "777" and sync_file_permissions = "777" in the config file solved the issue previously. I just checked my config file and those lines are uncommented but I still have the permission issue. @abraunegg, is there anything else in the new version that I might need to adjust or is there something else I can do to restore the sync permissions?

Has anyone else just updated this container and struggling to keep it running? I start the container and moments later, it stopped. Nothing in the logs seems to explain why. I get a message saying I require a --resync. I can't open the console from the container as it won't run. How do I run the --resync? I tried opening Unraid terminal and typing onedrive --resync but it tells me it's an unknown command.

It's only taken me some months to get around to trying your suggestion and I can confirm it works! Anyone that encounters permission issues needs to do this to ensure any documents and folders synced down from OneDrive have the right permissions. So to simplify it for all the other noobs (like me) out there just seeking to sort out permissions, here is what I did on my Windows machine. Go to https://raw.githubusercontent.com/abraunegg/onedrive/master/config and copy the content into Notepad. Remove the # to uncomment the following parameters and adjust the permissions to sync_dir_permissions = "777" and sync_file_permissions = "777". Save the file to the config folder you created in the OneDrive docker container and simply call is 'config'. Note, no extension. Restart the OneDrive docker container and do a test run by creating a folder in OneDrive, adding a file to it and wait for it to sync to your server. Test that you can open the folder and the file on your Unraid server. At this point, you should be all set! Thanks to @cholzer for pointing me in the right direction. This has been bugging me for a long time but I usually sync up from my Unraid server to OneDrive rather than the other way, so it didn't bug me enough to do anything about it until now.

Thank you so much for this! I've been waiting for an elegant solution to sync to OneDrive. Like @kri kri, I tried getting rclone to work and failed miserably. One issue I did encounter was that I didn't have permission to access any of the folders that were downloaded from OneDrive to my server from my Windows client machine. I ran the permission fix in settings and seems to have fixed the current ones. I'm hoping it's a permanent fix and that I don't have to fix the permissions every time a new folder is created on the server. Has anyone else encountered this issue?

@lotetreemedia just another vote of thanks for your guide. I wish all guides were this helpful. I quickly managed to get hw transcoding going on my new server after pulling my hair out following other information in my searches.

Hi everyone. I got an 'out of memory error' from fix common problems and it said I should upload my diagnostice here (see attached). Anyone able to offer any advice as to what's going on? Coincidentally, over the past week, I've been having issues with the Unraid GUI using Chrome on another desktop machine. The GUI would just lock up and the only way out was to close the tab and open a new tab. Not sure if it's related but thought I'd mention it anyway. The reason I'm not convinced it's related is that using MS Edge, running the GUI seems ok. So may well be a Chrome issue. Thanks in advance. ristic-server-diagnostics-20221112-1251.zip