GDub25

Members
  • Posts

    87
  • Joined

  • Last visited

Everything posted by GDub25

  1. 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.
  2. 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?
  3. 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?
  4. Here you go. And thank you for the help. Filesystem Check.txt
  5. 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
  6. 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
  7. 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.
  8. 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.
  9. 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.
  10. 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
  11. 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.
  12. 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.
  13. 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.
  14. 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
  15. 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.
  16. No, I did not pre-clear the new drive. I have pre-cleared every time I've added a new disk...except this time. Yes, I double checked all cables. I am unable to get a smart report on the new drive. My server is acting up more and more. Most of the time it will not boot to completion, hangs in the middle, and when it does appear to boot it doesn't mount the new drive. Also, when it does boot "powerdown" and "reboot" commands don't work. Usually, when trying "powerdown" the console shows a message of ls: cannot access /dev/sd[a-z] Only way to turn off the server is to pull the plug. The web gui is no longer accessible at all, ever. Below is a syslog when the server boots but is unresponsive to any commands. syslog-11-8-2014.txt
  17. I am running 5.0-rc4 and have been for a year or more now with zero problems. However, I have just had disk 5 of my array become "red balled". I replaced it with a brand new drive and started a rebuild, however the rebuild causes the webpage to become unresponsive after some time and the rebuild will not complete. Initially the rebuild does start and has a speed of 50-60MB/s with estimated time to completion of ~800 minutes. Once the web GUI went down I went ahead and let the server run thinking it would go ahead and complete the rebuild. Two days later and everything is still unresponsive. The array appears to still be online because I'm able to telnet in, however I am not able to access any shares over the network and the server doesn't seem to function correctly to commands. For example, I'm not even able to force a shutdown using "powerdown". When typing this command I get no response. I have rebooted the system and attempted the rebuild 3 times now with the same outcome each time. Attached is a syslog after I rebooted the system, started a data rebuild and let it run for 24 hours. Motherboard is a Biostar A880G+ SATA Expansion Card is Supermicro AOC-SASLP-MV8 8-Port SAS/SATA Add-on Card syslog-11-6-2014.txt
  18. I have had a glimmer of hope. My server has been running for 13 days now with no red disks. What I've done different was to preclear a spare drive and then used it to replace the parity drive. Rebuilt parity and haven't had any problems. I won't call this problem solved just yet, but I am very happy to at least see some progress. Anyone have any idea why this seems to have helped...or why the parity drive could cause random disks to fail?
  19. Yes, as a matter of fact they are all seagate 3TB drives. What more can you tell me? Is there a solution to the problem? Anything I can check to see if I'm having the same problem you did? Got another red ball on disk2. Array wasn't even up 48 hours before it happened. On the console I am getting a message saying /dev/sda: No such file or directory /dev/sdd: No such file or directory /dev/sda: No such file or directory /dev/sdd: No such file or directory /dev/sda: No such file or directory /dev/sdd: No such file or directory /dev/sda: No such file or directory /dev/sdd: No such file or directory This refreshes every 10 seconds or so and continuously says the same thing over and over. Attached is a syslog. syslog-2012-06-23.txt.zip
  20. Once again, thank you. I rebuilt the drive and replaced all the wires, double checked all the connections. I'm really hoping this was just a coincidence and not a continuation of my problem. I post back with my results in a few days.
  21. I bought a new hard drive and replaced disk1 in my array in hopes that would fix the file-system problems and get my server running good again. It ran for 4 days and then I had another red balled drive. This time it's disk2. Attached is the syslog. I looked through it but don't know what I'm looking at or how to interpret it. Like before, I'd really appreciate some help. syslog-2012-06-19.txt.zip
  22. First, yes, I am running rc3. Yes, I did run it with the disk still red balled which I guess is disabled. Your explanation of the check being performed on the simulated drive makes sense. Attached is the syslog. As for smart reports, I ran the command... smartctl -a -d ata /dev/sda and the output is also attached. Thank you for the help so far. syslog.zip smart.txt
  23. I turned my server back on this morning and it started up with no problems, parity and disk2 were read as normal (thank goodness) and disk1 was red balled. I started the array and ran reiserfsck and the output was: No curruptions found There are on the filesystem: Leaves 716879 Internal nodes 4288 Directories 139 Other files 2318 Data block pointers 725213808 (0 of them are zero) Safe links 0 I was not given the option of fixing anything, I suppose because no corruptions were found. Should I do a data rebuild on disk1 and then run reiserfsck again? I'm confused why it didn't find any problems if the log file indicated there was one.
  24. Ok, I'll do that as soon as I get a chance to be home. That is assuming I turn my server back on and I am able to even start the array. If when I turn it on the parity drive, disk1 and disk2 are all still bad then I'll have another obstacle to overcome before I can try and fix the filesystem.
  25. I've been without access to any data on my array for about a week now hoping that I'd be able to get this thing figured out. Since I don't know enough about this stuff to try and figure it out on my own, instead of troubleshooting further I think what I may try is completely starting over. Starting over meaning buying a new flash drive and a couple new hard drives and throwing them in the box and setting up a new 3 drive server with nothing on it. Then add a few hundred gigs of data from one of my current disks and wait and see how it works for a few weeks. If it looks good then I'll start copying my drives containing data to the new disks and after each drive is copied I'll preclear it and add it to the array. If I still have problems then I'll assume it's hardware related and start replacing parts. Anyone care to weigh in with thoughts on this? I'm still open to other options, just don't want to wait around forever doing nothing if no one has any ideas on what's causing my problem.