Jump to content

TODDLT

Members
  • Content Count

    713
  • Joined

  • Last visited

Community Reputation

0 Neutral

About TODDLT

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    Charleston, SC

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. TODDLT

    Case or cage Recommendation

    Still looking for any assistance on cages or other cases. Thanks again.
  2. TODDLT

    Case or cage Recommendation

    Looking for any thoughts on the cages, or of course any other case options. Thanks all.
  3. TODDLT

    Case or cage Recommendation

    .. and thanks for the thought. That case is definitely more compact that the 1200 and looks easier to get drives in and out. It probably is a bay or two short of giving me the hot swap capacity, but its definitely a great option. If i'd just buy one more 6 TB and consolidate a couple 3 TB's that would get my drive count down too. On the consideration board, so thanks for taking the time to put it out there.
  4. Thanks, After watching this for a few days it appears the exclusions have solved my issues too.
  5. I currently have 10 HDD's and 4 SSD's plus 2 - hot swap HDD's in my case. I use and Antec 1200 with a 4th factory cage installed. The SSD's are in racks that mount in expansion card slots. The case has been great, very well built, awesome at keeping everything cool during parity checks (except SSD's), but my only functional issue is it's a PITA to change out any drive. Opening the case is one thing, but you have to remove both side covers, completely unplug fans and 3 drives, then remove a cage to get one drive out. I'd like to try and find a solution that just makes this easier to deal with: Option 1 - use hot swap 3x4 or 3x5 cages. Does anyone have experience putting cages in an Antec 1200? What cages work or don't work and which ones are most effective at cooling during parity checks. From the photos a lot of the cages have circuit boards at the back of the cage and appear to greatly restrict airflow between the drive and the fan. I also hear some cages are too deep for some cases, though the 1200 is reasonably roomy. Also if 3x4's get me where I need to go should I bother with 3x5's? They appear as if they would make airflow for cooling a bigger challenge. My thought was to use 3 each 3 x 4's and a single 2 x 4. then use a 1x4 SSD cage at the top (12 5.25 slots total). That would give me 2 additional HDD bays even having two hot swaps. Below are some links to examples of cages I was looking at any any thoughts or suggestions for other products are appreciated. Does anyone know these will fit the 1200? The biggest issue here is the $350+ expense just on cages. https://www.newegg.com/Product/Product.aspx?Item=N82E16816215367&ignorebbr=1 https://www.newegg.com/Product/Product.aspx?Item=N82E16816215245&ignorebbr=1 https://www.newegg.com/Product/Product.aspx?Item=9SIA2W08HW8050&ignorebbr=1 Option 2 - with $350 in cages, is there a better case out there with drive access for similar money. They really dont need to be hot swaps, I just want to access without pulling everything apart. Removing one cover or door is fine. However, I've looked at other cases and can't find anything that gets to my current capacity and has a decent layout inside with HDD cooling in mind. Some take lots of drives with no direct airpath to a fan, which makes zero sense. There are cases with good access/cooling for a half dozen or so drives and then you jump to rack mounts for 20 or more drives and nothing I do justifies that expense. Thanks in advance!
  6. I used to use cache dirs long ago in unraid ver 5, and don't remember for certain when it dropped. I've been having some large hesitations in the navigation of my Plex directories and thought perhaps caching folders again may help. It seemed like certain functions were hesitating for drives to spin up. After turning cache dirs (folder caching), drives are spun up seemingly often even though changes aren't being made, and while CPU usage certainly isn't pegged it runs from 15-40% pretty consistently. I've just been using the default settings, is there some way to control this? I would rather it not scan unless it knows something has changed, or maybe once a day outside of known changes. ** note, while typing this I went and added "app data, dockers etc" to the exclusion list on the thought that perhaps Plex constantly doing it's thing may be triggering cache dirs to re-scan. I'll keep an eye on it to see if things change.
  7. TODDLT

    Sync Error Detected

    Installed, up and running and will start a parity check in about 30 mins when Plex DVR turns off for the night. 2 questions. 1. Should I expect to see 5 errors again? The box was restarted a couple times since the last parity check with the old card in it and that seems to have been the trigger from what I was seeing. 2. The LSI has it's own splash screen at startup, and you see the card ID itself, "spin up" and it shows connected drives. I used to see this happen once for the LSI and once for the Supermicro. Now I have 2 LSI cards installed. 4 drives on one, 8 on the other. I only see one LSI card splash screen with 4 drives showing (this is the old card). The new card has 8 drives connected and you never see it run the same startup. Is this a self test that is not occurring? Is there a setting in the card's BIOS I should change?
  8. TODDLT

    Sync Error Detected

    LSI card due Monday or Tuesday. I assume a correcting parity check should be done after install.
  9. TODDLT

    Sync Error Detected

    OK so this may not be going the way I want things to but here it is. Last night I moved drives off the Marvell controller as recommended and noted above. This morning there were 5 errors, presumably the same 5. This was a correcting check. Prior to my upgrade I had never seen the 5 errors occur. During my "upgrade" a few weeks ago, this was the process I followed:. 1. A single old 2 TB array drive was replaced with a new ST3000VN001. No Marvell controller changes made. 2. The two parity drives were replaced simultaneously as a single operation with the HGST 6 TB drives. No Marvell controller changes made. 3. I opened the case and reorganized drives. This is the first time any actual controller connections were changed, and the 2 - ST3000DM001's that were originally in the array would have been placed into new positions. As noted above only one of them is an ATA8-ACS drive. 4. 4 more drives were individually replaced and rebuilt from parity. I believe I recall this order correctly. - 1st The HGST 6 TB drive replaced a 3 TB drive. I am 98% sure the ATA8-ACS drive was not in the array at all at this time. - 2nd The non ATA8-ACS drive was used to replace an older 2 TB drives - 3rd The ATA8-ACS drive was used to replace an older 2 TB drive - 4th a 500 GB SSD was replaced. The first actual parity check was done 11/1 when this thread started and I saw the 5 errors. So my question is, would you think the 4 drives replaced AFTER step 3 above, probably/possibly now have 5 corrupt sectors? It seems the errors are occurring around the 1.8TB mark so the 500GB SSD should be safe. It also seems if I'm correct about the above order I am probably OK, but anything larger than 1.8TB replaced after the ATA8-ACS drive was put back into the array, is now suspect? Thoughts? OH, I DID order an LSI card last night too!!
  10. TODDLT

    Sync Error Detected

    Well one of the two remaining ST3000DM001's is an ATA8-ACS. All of the new drives were on the LSI Controller. The ST3000DM001 with the ATA-ACS was on the Marvell. AND... my 5 errors were at the exact same sector locations as your errors were in the thread above. So having said all that, about to start the parity check. It will probably run across that location in the middle of the night so I'll check in the morning.
  11. TODDLT

    Sync Error Detected

    Running my first test now, and also looking for another LSI controller.
  12. TODDLT

    Sync Error Detected

    Thanks for this. I see my original plea for help on the speed issue showed up in your thread and hopefully has been helpful to the community.... There were two drive types introduced in this last upgrade. Primarily 3 ea. HGST HDN726060ALE614 - 6 TB drives and 1 ea. 500 GB Samsung 860 EVO SSD. The SSD was a replacement at the last minute as I appeared to be one of the few with a failing SSD. Also of note, I do/did have several ST3000DM001 previously, but no idea which controller they were connected too then at the time and may never know. I doubt there has been any checking on that combination, but if you have any thoughts please do chime in. When I get home I will check which controller these drives are connected too. I THINK the SSD and two of the new HGST drives are on the MB, and one of the HGST's is on the Marvell. There may also be a warm spare HGST is on the Marvell as well but I'm assuming this is not playing in the issue. I'll also see where my ST3000DM001's are connected and see if I can figure what controller. I have not run a correcting parity sync yet (I think it defaults to a non-correcting parity check each month), so when I get home (later tonight) I'll make sure all the HGST's are moved to my LSI controller and re-run the parity check. Any thoughts please let me know and I'll check here before proceeding.
  13. TODDLT

    Sync Error Detected

    If this is a known issue, then are the errors in fact errors. IE should they be corrected? Is the SAS2LP causing an error in the parity or is it falsely reporting an error exists? There used to be an issue (previously fixed) with the SAS2LP causing a huge drag during parity checks. I think that was a driver issue. This is the first time I've had it cause parity check errors. Maybe I need to start looking for another LSI controller because I dont want to have this issue every month. It's not unusual to reboot at lest once during the month for some reason or another.
  14. TODDLT

    Sync Error Detected

    Last month I did a major upgrade involving both parities and the replacement or relocation of 4 out of 10 array drives. All of this happened without incident or error. This included going from 3 to 6 TB parity. Only one array drive is 6 TB. Today if the first parity check and it's now past the 3TB mark IE there is likely no new data in the mix. I am showing 5 detected errors and 3.5 hrs to go. I forgot to turn off Plex last night and as it turns out the DVR was running for 3-4 hours of the parity check time. In theory this shouldn't hurt it, but I have to wonder with errors and data being written at the same time over that duration. There is only the 2nd time in 5 or 6 years of unRaid I've had errors on a parity check. What is the next step in trouble shooting or would you just correct the errors and move on? My signature is up to date with configuration and drive types. Thanks for any help.
  15. I went ahead and replaced it. No explanation for it and for a drive to now consistently run at half speed just doesn't sit well. Speeds all back up to normal. during a parity check or re-build, it bounces up between 40 and 45. Where they are mounted in the case I can't really get a fan right on them but I think I can get one generally over the area they sit. That's next on the list. Thanks for the advice.