sharrensen

Hi! Replacement key resent by support in notime, thank you very much!

Hey there, Needed to swap the USB because the old one went bad and requested a replacement key for the new USB earlier today, but unfortunately i still havent received any email reply (checked in JUNK as well) - it might be that i've requested the replacement be sent to my (ancient) hotmail address ? PS: Email sent to [email protected] just now. Thanks!

at first glance, that sounds perfect but given the difference in the output of the xfs-repair operations, isnt that indicative of something being "wrong" ? and if you know how to interpret that output i pasted above, does it say its "all okay" or does it say that something was "wrong" ?

Yes, i have also looked for the "lost+found" directory, both thru the UI aswell as thru krusader, just in case it wasnt showing up in the UI (for whatever reason) and i couldnt find such folder.

Yes, i removed the "-n" and added "-v" Also, is the output im getting indicative of something being "wrong", i assume ?

from the UI, is that problematic ?

Hi, Its been quite a while since i posted about this and trurl replied but due to various reasons, only now did i get around to tackling it - unfortunatelly, the story is a bit more complicated now... In the months that passed since i wrote about it, everything went well and i had no issues. However, a couple of days ago, i found that DISK1 was "UNMOUNTABLE: not mounted" and after trying to figure out what happend (with little success) i decided to just format the drive and be done with it. Also, previously i had all the WD drives connected to the LSI and the Toshiba drives to the SATA ports on the mobo and i decided to connect the Toshiba drives to the LSI aswell. Only after formating and everything did i find out that XFS corruptions can cause the "UNMOUNTABLE: not mounted" behaviour and how to run an xfs repair... So after DISK1 was formated and added to the array again as an empty drive, i thought of running the XFS-repair check just to see what comes up and this is the output: After that, i ran it on another one of my Toshiba drives, which i picked randomly as DISK3 and the same result came up and after researching a bit and cross-referecing with what other people had as output i concluded "it looks good" - please correct me if im wrong So i left my unraid alone and went about my business. The very next morning when i woke up however, i found that DISK2 had somehow been "disconnected", but then magically reconnected again, but of course it was showing in my Unassigned Devices now and the contets for DISK2 were being "emulated". I also found a notification that there was a power outage that mornining and the UPS (APC BR1200GI) had kicked in (the UPS is connected to my unraid and management is active): Im not sure if the power outage and flipping to the UPS had somehow caused this, but i really doubt it as i've had several power outages and there were no problems with the UPS kicking in. So i shut down my unraid, rechecked everything was plugged in correctly, i even decided to move DISK2 off of the LSI again and onto the SATA port on the mobo, connected thru a cable i had used in the past and was sure it worked fine (just in case the LSI SAS to SATA was "bad"). I then readded DISK2 to the array and the parity check started and also completed successfully running at expected speeds. After everything was "okay" again, i've installed and ran the DiskSpeed to see if this would indicate anything problematic with any of the DISKs and this was the output: If you ask me, it looks "good" and there doesnt seem to be an issue here. I've also ran controller benchmarks on both the LSI and the mobo integrated controller and the results were "good" aswell, as there were no differences in speeds shown between single disk and array operations, also the speeds were "as expected". I then decided to run an XFS-repair check and repair with verbose (-v) on DISK2 and this was the output: Given the results were different from what i had seen with DISK1 and DISK3 (which are also Toshiba drives), i figured there was "something" that was "repaired" so i ran the XFS-repair check verbose expecting the result to be as it was with DISK1 and DISK3 now but it was not and everytime i run the XFS-repair, the same output is given. So either the output is saying "everything okay" or there is a problem that its not getting fixed, but unfortunately i cant tell. If anyone can make heads or tails of my situation and is willing to take the time and explain it to me, i would REALLY appreciate it! PS: Again... sorry for the long post!

for people that need a little more help on how to do it exactly: 1. click on the deluge container and select EDIT 2. under Repository, modify it from the default linuxserver/deluge to linuxserver/deluge:amd64-2.0.3-2201906121747ubuntu18.04.1-ls127 and click APPLY

Thank your for the quick reply Trurl, i will go over the post you linked and see what comes out of it. Will come back with an update as soon as i have one.

Hi everyone, I'm gonna try to explain the situation the best i can, given im just a casual unRAID user, with no special setup, just using Plex, Piehole, Deluge, DuckDNS, OpenVPN (yes i know...) and a couple VMs. Any help or at least an explanation is very welcome! Firstly, my unraid setup: CPU - i7 8700k mobo - GIGABYTE Z390 M RAM - 32GB 3200mhz CL 16 Crucial Ballistix PSU - Corsair SF600 Gold HBA - LSI 9211 -8i IT mode, with 2x SAS to 4xSATA HDDs are as follows: PARITY disk - 1x Toshiba 16TB (MG08ACA16TE) DATA disk - 3x Seagate Exos x16 14TB DATA disk - 2x WD120EMAZ 12TB (WD Elements shucked drives) DATA disk - 1x WD80EDAZ 8TB (WD Elements shucked drive) DATA disk - 1x WD Pruple 12TB The "strange" behavior/problem: Initially i had 4x Seagate drives but decided to replace them with 4x Toshiba (MG08ACA16TE) drives. When i had first added my Seagate drives, every parity rebuild (each of the Seagates replaced old WD Reds) worked like a charm and started at a constant ~220MB and then slowley worked its way down as it reached the end of the platters, at around ~120MB or something like that. I then started replacing the Seagate drives with the first Toshiba, but got speeds, ranging from ~150MB to ~190MB. I decided to keep going and finished the rebuild. But when i got the second Toshiba drive in to replace the second Seagate, my parity rebuild speeds started swinging wildly between ~70MB and ~150MB, but never above ~150MB. Initially i thought the drive was "bad", so i stopped the rebuild 5min in and swapped this Toshiba drive with another Toshiba drive. But i was surprised to see that nothing changed and the rebuild was showing the same behavior with swinging speeds between ~70MB and ~150MB. I dare say, i cant be that unlucky and have two "bad" Tohsiba drives, with the exact same behavior. After looking around the unRAID forum for a while, i came across a post, someone was recommending to change the following disk settings if using "larger arrays" (not sure what constitutes a "large array", but i thought i might fit the bill): Tunable (md_num_stripes): 4096 Tunable (md_sync_window): 2048 Tunable (md_sync_thresh): 2000 When checking disk settings, i noticed i only have the first setting available to modify, so i did and changed it to 4096. After doing this, i started the parity rebuild process again and my speeds are still "swinging" but are now doing it between ~170MB and ~190MB. If anyone can explain all of this, please do, or give some additional info as to what is going on, that would be very much appreciated! More so, as i have no idea what any of those settings actully "do" and if using them/it creates any problems - sure im happy with the speed bump, but not at any cost. I've been struggeling with my unRAID ever since i decided to swap the 4TB WD Reds for the 14TB Seagates (a different story...) and now my pain appears to continue with the Toshiba drives and i've, more or less, reached the end of both my technical knowhow and patience and just want to have it stable and working again, with no new behaviours and "odd personality disorders" I swear, i've been an extremly happy user of unRAID for close to 2 years, until i decided to start "upgrading" Western Digital drives to anything else... im not sure if thats the issue or not but it sure looks like it. Sorry for the wall of text and as i've said before, any help/info is appreciated!