GDub25

Sorry, I was thinking the parity check might see the updated filesystem as an error and re-write the error thinking it was correcting a missing file or something. Everything seems to be working right now, fingers crossed it stays this way. Thank you guys very much for the help.

Ok, got the filesystem corrected with --rebuild-tree. Re-ran the check and it says no corruptions found. I am assuming I need to start a parity check now and NOT correct any errors found so that the parity is rebuilt without the corrupt file system?

In reading more about this I am confused where the problem actually is. I guess I don't understand what the filesystem is. The drive in question has been replaced. I guess that means the problem may have never been a bad drive in the first place but rather a filesystem problem which was copied over in the data rebuild to the new drive when I replaced the old one?

Here you go. And thank you for the help. Filesystem Check.txt

Here is the output of the filesystem check. Probably worth mentioning that disk1 is the disk that is brand new. I replaced it and used parity to rebuild the data about two weeks ago. I had replaced it due to some SMART reports warnings. The original disk that was showing the SMART report warnings was a relatively new disc as well. Filesystem Check.rtf

I've been running unraid for 8-9 years now, it's been fairly stable for me and I come here when I have the rare problem. I would say I'm still not that knowledgable about unraid, linux, or computers in general. I've had this persistent problem over the last few weeks where all my shares are getting converted into a read only permission state. I ran and re-ran the permission tool which did nothing initially. Then last week I replaced a couple of drives that looked to be having SMART report issues and that seemed to fix it until a couple of days ago. I ran the permissions tool and tried to move a file with no luck. I restarted the server and tried again and everything was working normally but only for a couple of days. Now I'm back to read only. It's across all shares as far as I can tell. This has me thinking about a bad wire or other hardware issue maybe? The server hardware is all relatively new. I built this one about a year ago with server grade parts however I did get the RAM, processors, and motherboard used from MET servers. tower-diagnostics-20200621-1748.zip

Got it recognized by plugging the drive directly into the SATA connector on the motherboard, it didn't like being plugged into the splitter from the motherboard.

I have a bad cache drive and want to replace it. I was using a 500g hard drive and bought a SanDisk Ultra 1tb 3D SSD to replace it with. I put the SSD in the hotswap cartridge and slid it into the server and the light comes on showing it's powered up but on the unraid GUI I can't select it as a drive. I searched and really can't find a good way to troubleshoot this, it seems everyone else just plugs their SSDs in and they work? I've rebooted the server, tried to make sure the drive is well seated, tried different slots, all no luck.

I thank you guys for the help. I've got some things I've got to do over the next couple hours but I'll work on this later this afternoon and see if I can get something figured out.

Paths are correct, double checked that already. itimpi, when you say mover, are you referring to unRaids mover or Couchpotato/Sickragemover? I don't use the unRaid mover, have always let Couchpotato and Sickragehandle it. Not sure if it makes a difference though. Also, I've gone through the logs of Couchpotato, Sickrage, and unRaid and I don't see anywhere that a new folder has been created on the cache drive. Attached is my unRaid log. A new TV Show folder has been created on the cache drive within the past hour but I don't see it in the logs. tower-syslog-20160327-1444.zip

I have always had it set to not use the cache drive. My server has been up and running for years now, first time I'm seeing this problem. I never noticed it until a few days ago. What made me realize it was SABnzbd quit downloading saying there wasn't enough free space and I had to start investigating what was taking up all the space. I had 40+ movies downloaded onto the cache drive and many TV episodes. It's hard for me to say when this all started since I didn't notice it right away. About two months ago I switched from unRaid 5 to v6 and started using Dockers so I suspect that's when this started. I'm using SABnzbd, Couchpotato, and Sickrage. My guess is that one of these (probably Couchpotato and Sickrage) are creating the shares on the cache drive.

I'm having the exact same problem. I replied to your other post as well. The user shares keep getting created on the cache drive somehow. I don't know the solution to this yet but hopefully someone here will be able to help us.

I'm having this exact same problem, and I mean EXACT! I have two user shares, Movies and TV Shows, and in both of those shares I have the option "Use cache disk = No". On my cache disk I have two folders, Apps and Completed Downloads. It has been this way for years now. I recently noticed my cache drive now has four folders, Apps, Completed Downloads, Movies and TV Shows. The Movies and TV Shows are newly created. In fact, when I first noticed them a couple of days ago I deleted them only to find they were recreated again as soon as a new movie download was completed.

I tried removing the failed drive from the server completely, as jonathanm suggested, but still no luck. The server still appears to boot normally, but web gui is not reachable, and when using "powerdown" command the machine hangs and never powers down. Attached is a syslog after a boot up and nothing else. What would be the best way for me to start fresh while maintaining the data I have on all of my presumed good drives? Can I just take my flash drive and upgrade to the 5.0 stable release and then rebuild parity? Seems like doing this would eliminate the software as a possibility of being the culprit. Then if I still have problems it would mean it's most likely hardware related, right? syslog-11-11-14.txt

Well, that was my next thinking. Remove the new drive and see if I can boot up. I don't know the first thing about syslog interpretation and was hoping someone here would look at it and say "ah-ha", there's your problem. Maybe not so simple to find the problem. The data on the failed drive I'm trying to rebuild is not that important to me. It's just some movies I had backed up. My main concern is to get the server back up and running and if that means losing the data on the failed disk so be it.