AnyColourYouLike

Members
  • Posts

    31
  • Joined

  • Last visited

Everything posted by AnyColourYouLike

  1. Just got around to updating today and immedietely went looking for a solution. Notifications are completely out of site now and I really don't like it. I have temperature alerts set up that usually notify me when drives get too warm and now they sit docked in that little bell icon to be completely missed for hours. My solution is push notifications on my phone but I really miss that telltale red warning on my desktop to anticipate adjusting the A/C.
  2. This is my experience a year later. I set everything up with the API and Plex token but the scan results in this and that last line "Can't find ID to match..." over and over for the whole library.
  3. Latest update I can't get to webUI, similar errors as others above. 2019-12-23 17:31:39,382 DEBG 'watchdog-script' stderr output: terminate called after throwing an instance of 'std::bad_weak_ptr' what(): bad_weak_ptr 2019-12-23 17:31:39,709 DEBG 'watchdog-script' stderr output: Unable to initialize gettext/locale! 2019-12-23 17:31:39,709 DEBG 'watchdog-script' stderr output: 'ngettext' Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/deluge/i18n/util.py", line 118, in setup_translation builtins.__dict__['_n'] = builtins.__dict__['ngettext'] KeyError: 'ngettext'
  4. I did precisely this today, removed everything and air dusted it all out. Trying to preclear and rebuild again, i'll report back hopefully this week.
  5. This whole thing is a mess. I got one disk replaced, it rebuilt with only 390,116 errors 😫. I assume it was from what looks like (read?)errors attributed to disk 4, Which btw was a recently replaced fresh drive with currently only 2 months power on hours. The next replacement drive was supposed to be the drive above in my second post that originally got kicked out in my last thread 2 months ago, it passed extended SMART tests and never showed any reallocated sectors or notable issues, it is older though at 1yr power on hours. That drive did finally successfully clear so I began a rebuild process but that failed about 2 minutes in with errors similar to above, I/O and write errors. I really don't know what is happening, the disks all seem to be fine on their own, I can mount the 2 failed drives from my OP here and no errors are present. But my array is all sorts of messed up. I wondering what do do because it seems very fragile, I brace for every parity scan that it won't rack up a million errors or disable drives altogether. I can't afford all new hardware or I'd just build a new server that didn't have me questioning all the individual variables like my LSI card, 750w PSU, Kingwin KM-5000 adapters backplates and even RAM. tower-diagnostics-20191007-1506.zip
  6. One of my hopeful replacement drives is failing a post read after clearing. I have the feeling there may be something wrong with my HBA controller, a supposed genuine "LSI Logic SAS 9207-8i Storage Controller with SAS/SATA Cables H3-25412-00G" I picked up on Ebay this summer. I've attached the log from the preclear, the drive itself has passed an extended SMART test without error. I just get the feeling the i/o errors from my OP and this error now trying to preclear a replacement drive is all pointing to this HBA card. I'm at a loss. I re-seated and checked all cables, even replaced the mini-sas breakout cables with new ones to see if that was an issue. One of my OP drives is being rebuilt (crosses fingers) or i'd swap the disk from the errors below to a different bay to see if it's one affected part of my back-plane/case. tower-smart-20191003-1440.zip
  7. Hey guys, feels like I've been here a lot lately. I thought I got my array just about in working order. This error is a new one for me. My array was starting a scheduled parity scan at some point in the early AM, I woke up to find 2 newer drives have been disabled and show an alarming amount of writes. The parity scan canceled with 0 errors at only 5 minutes in. There doesn't appear to be any SMART errors on the affected drives but I'm afraid they will need to be rebuilt regardless. I really am not sure what happened or how to prevent this in the future. Hopefully someone wiser can shed some light on what happened? Was it a controller issue? Unraid 6.6.0 Dual Parity tower-diagnostics-20191001-1255-Anon.zip
  8. I went ahead and used one of my spares to do the rebuild of disk 4, that finished with 0 errors, though disk 10 did throw read errors so parity helped me through that one as well. I'm currently rebuilding disk 10 now so it's no longer a factor. The other disk with errors, disk 8 seems to be doing just fine but i'll be pulling it after this next rebuild. I'll be looking into the file integrity plug-in from here on out, this has been quite the ordeal. (just realized I already had it installed just never set it up) I really appreciate the help and guidance you have provided. I will go ahead and mark this post as solved. It's been a bumpy ride but I think I have survived with minimal damage, I guess I'll just have to take a closer look at the disk i rebuilt that had errors. Thankfully nothing I have is really critical data, I'm just a massive hoarder of archival media from my childhood, this might give me some excuse to actually watch and slow down the collecting Thanks guys.
  9. I guess i'm not sure how to know if it is 100% valid. Also I don't think the emulated disk would have been written to unless starting the array and promptly stopping docker would have resulted in incidental writes. When you say it could be re-enabled you are referring to a new config while trusting parity? I've had the array started and disks nearby have 5 writes showing since a reboot, could that have also happened to the emulated disk and would that be enough to not go the re-enable route? The diagnostics on my third post should be right after the disk7 was rebuilt "successfully" with 128 errors. As far as checksums go that is something I would have to have been prepared for correct? Is there a easy way to catalog files and their checksums for the future? I guess i'm not sure how one compares files once they have been replaced by possibly corrupt versions. Looking at my parity check history these aren't my first string of errors. I guess I always assumed these errors were being corrected and that was the point of doing parity checks regularly.
  10. I have two new 8TBs I plan to start preclearing overnight. The previous ditower-diagnostics-20190802-2352.zipsk4 is unassigned at the moment. I moved any critical data off of the disk8. I will be getting new SATA cables in the mail tomorrow and another 8TB will arrive Monday. I'd like to remove and send in the 4TB's with errors as they are under warranty until October.
  11. I don't make it a habit to ignore disk errors. As far as periodic health checks I haven't scheduled any extended SMART tests or anything out of the ordinary. These recent errors were made notice of by notifications on my main page, they have only been present in the past few days as I assess my options. Disk 8 passed an extended SMART test but the pending sector is what has me worried. I'm about to power things down and attempt to check all connections, I've done this recently though hence why I ordered all new SATA cables for all connections. Those will be here tomorrow. I just hope you are right about disk4 As for the disk8 and disk10 I just purchased replacements for them all and will be replacing them, I just don't know which to do first considering the likelihood of multiple failures during a rebuild. What happens if things go belly up during a rebuild? For what's it worth (not lost data obv) all my drives minus the oldest 3TB are all under warranty, i'd like to address all errors and RMA affected drives ASAP. What would be my best course of action going forward? The dual parity has gotten me thus far (thank jebus) but I'm still feeling like I'm flying too close to the sun here. Also what are the consequences of parity errors? is that a sign of corrupted files that I'll never really be sure about? Thank you all to have read my ramblings, I've used Unraid for years and obviously stumbled my way through it thus far. *EDIT* I moved disk4 to another bay and restarted the array, still shows as disconnected. No errors, nothing to explain that one. *Edit2* I screwed up and unassigned disk4 momentarily, now it detects it but won't start the array unless it rebuilds it. I am terrible at this. There doesn't seem to be anything wrong with the disk but I really don't want to put the array through the stress of rebuilding it when 8TB of data sits just fine on the disk as it is. WDC_WD40EFRX-68WT0N0_WD-WCC4E2CLT71C-20190802-1942.txt
  12. Hey I didn't want to make a new thread after having this one so recently. My array is in dire straits right now, I don't know what's happening. I was planning to remove and replace the drive I asked about in the OP, but then out of nowhere I had an older drive completely disconnect on me without warning (TOSHIBA_MD04ACA500_Y593KDFZFS9A). There really wasn't any warning with this disk except that its sister drive I bought at the same date recently failed as well so I didn't really question the validity of this failure and just immediately replaced it with a new 8TB I had precleared ready to go. Now this is where things get scary. While this drive was being rebuilt, and knowing the aforementioned drive referenced in OP was likely on its way out I watched biting my nails as it attempted to rebuild. About 60% in its rebuild a completely DIFFERENT drive, one of my newest ones completely disconnected without warning. So here I was deep into a 24hr rebuild and I just lost a drive, have another one that had read errors and reallocated sectors the day before (OP)... If that wasn't bad enough there is now ANOTHER drive that started throwing read errors and has a pending sector with multiple UDMA CRC errors where there were none before. I'm freaking out right now. This is a nightmare come true. Disk 4: New 8TB completely disconnects no warning Disk 7: A freshly rebuilt 8TB drive (it did finish) albeit with 128 errors (?) Disk 8: The disk that during the rebuild startower-diagnostics-20190801-1941.zipting throwing multiple errors including a pending sector Disk 10: The aforementioned disk in OP that I managed to empty but was reallocating sectors and read erroring the past day. Where do I go from here? I have the array stopped, I ordered another 8TB replacement drive as well as new mini-sas to Sata connectors for my 9207-8i and additional SATA cables for the 4 additional ports I use from my motherboard. Could this all be symptoms of faulty cables? Marvell controller on the motherboard, or the 9207-8i? I was really not prepared for this many things to snowball at once.
  13. I started moving some things off the problem drive onto another, fortunately this disk was just recently added to the array after being used in another build so it's not very full. Most directories aren't having any issue moving except the one that I was in the process of moving when I first discovered the issue. Though now it is showing reallocated sectors for the first time... This drive must be on its way out fast. I have a drive precleared and ready to rebuild, I just hope everything is good with my parity and there aren't further corruptions. (it's been about a month since a parity check)
  14. Hey guys I'm not so good at troubleshooting my drives. I was manually copying some files from /user to /user0 (might be a bad thing to do?) I was attempting to move things from a seeding folder (cache) to my array for storing/streaming. /user to /user then suddenly I started getting notifications on my dashboard for read errors... like hundreds, then thousands, It's sitting at 6000+ now. The copying I was doing didn't fail or show errors, I stopped it when I noticed but the read errors kept going. That's when I stopped the array and started again in maintenance mode, ran an extended Smart test and that's where I am. Any advice? The drive in question is #10.
  15. Ah so that's how you can add commands. I don't have a dedicated cache drive so yeah my appdata is on my main array. Unfortunately that didn't seem to change anything. I'll have to try some more tomorrow, it's getting late. Thanks for being online and so quick to respond. Edit* I think my issue is in particular to xfs, --storage-op size=X isn't a valid command. Hey now I have an excuse to finally buy a cache drive!
  16. I just kept it default /appdata. Same error trying Don't Starve. It seems like an existing issue with steamcmd incorrectly reading 0 bytes available space. I've found several others via google using steam on Linux. Something about a quota. I just found someone else using docker with the same issue albeit with ZFS (I have XFS) They added a command to docker run for a workaround. (I'm not even sure how to do that?)
  17. First time trying this, using 'the Forest' as my first attempt. I'm not sure if I'm doing something wrong here. First it says failed to determine free disk space but also says wine32 is missing. I have plenty of disk space available
  18. Did you also update unraid to 6.7.0? Your issue sounds like mine. It started working after rolling back to 6.6.x and restoring my Plex database from its own automated backup. (Plex Media Server > Plug-in Support > Databases ... the files such as 'com.plexapp.plugins.library.db-2019-X-X' to replace the current corrupted ones) *edit* More information relating to this occurrence is on the previous page (pg.27)
  19. Pretty sure I'm having the same problem as some are stating since updating to 6.7.0. I updated yesterday and things seemed fine, I added some TV shows and watched them successfully. Then suddenly now my libraries won't load and my log has a repeating error "...6 10000 /config/Library/Application Support 1000..." over and over. I'm really worried rolling back to 6.6.x won't fix things with the word 'corruption' being used. Will I really have to reinstall and rebuild my PLEX container? I don't have a recent backup of my appdata before this all happened. I'm not sure how you guys keep decent backups, with the size of my metadata and such (bajillions of files) it takes ages just to initialize a copy of my PLEX appdata. Is my current data really corrupted or can it be salvaged/copied to a new container? I have thousands of media files. their watched progress, custom covers and summary entries, renamed archived TV recordings ... I'd probably cry if it's all lost. As someone who is a set it and forget it noob, I really feel dumb for updating after all this time ignoring 6.7.0 only to be smacked in the face. This server's only purpose is PLEX.
  20. Edit the Docker. The debug flag is in there. There you can check the location of your config files as well.
  21. OK ill look in to it. As of right now I can only access it locally I believe. Thanks again!
  22. wow ok so it was the https that was the problem. I've never had to do that before... https://192.168.1.XXX:8112 got me to the webgui. Chrome did strike through https saying "not secure" but i was able to log in and can now disable certs. To the best of my knowledge i haven't tinkered with ssl in any cognizant way... Should I be using that? and if so why does chrome browser say it's "not secure"? Thank you so much btw, My queue is all sorts of messed up, my Deluge needs daily maintenance in a bad way lol Back in action!
  23. I believe it's "192.168.1.1" I've never seen it end in '.0' but yes it follows that format.
  24. Hmm.. Well I'm leaving to school here soon for the day so I'll try more later... but another browser and device was the same result.
  25. well I hope I masked what is necessary... I really appreciate you taking the time, as well as your rapid response thus far.