Jump to content

KR1SeS

Members
  • Posts

    47
  • Joined

  • Last visited

Posts posted by KR1SeS

  1. Hey all looking for some help please. I'm running V6.12.3.

     

    I have two cache pools:

    image.png.e8ef5f427c23452e57715ad8061633b3.png

     

    I have shares as follows:

    image.thumb.png.4fbeab344594481d52ca798ce0b78ccf.png

     

    What I want to happen is have all my downloads from NZBGet occur on the "cache_downloads" pool. Once everything is renamed I want to move it to my Media folder and live on the "cache" pool until the mover transfers it to the array on it's move schedule.

     

    NZBGet downloads are working proper and the files end up on "cache_downloads" pool. I manually move them using Midnight Commander (I navigate to user/downloads and move them to user/media). The problem is that it just created a "Media" folder on the "cache_downloads" pool instead of on the "cache" pool. Now when I invoke the mover there is nothing on "cache" to move to the array.

    I have a few questions at this moment:

    1. In Midnight Commander should I be moving direct from the "cache_downloads" download folder instead of user/downloads?
    2. What is the best way to get the files in the "Media" folder stuck on "cache_downloads" pool safely over to the array?
      • I'm thinking I change the Media share temporarily to be "cache_downloads" and invoke the mover and when finished put it back to "cache".
    3. Would the Dynamix File Manager work to transfer between pools or would it exhibit the same behavior as Midnight Commander?

     

    Maybe I'm not handling the smartest way, but my hopes were to have all the IO in downloading, repairing, extracting, renaming and so on happen on the unprotected cache pool then transfer it to the protected cache pool where I'll let it stay for quite some time before invoking the mover. Likely we will consume that media before it gets to the array and therefore spare some additional array wear and tear.

     

    Should I just run a single cache pool with all four drives in ZFS Raidz?

     

    TIA for any help or direction.

  2. Anyone one else having an issue loading files into the left window? I click and get the choice to Add Folder or Add Files, but when I make a selection nothing happens. I don't get the usual dialog box to navigate my directories anymore.

     

    I tried restarting the docker and refreshing the WebGUI but no luck. Docker is up to date.

  3. On 9/5/2019 at 7:49 AM, cliewmc said:

    Looks like I need to do the same, the SSD crc counts keep climbing, now 961. It may have crashed my system numerous times or killed my new 8TB hard drives. Generally making the unRAID very unstable. I’ll swap this on Saturday & see if it will work too.
     

    How'd it work out for you? I'm a couple months of uptime since the SSD change and no errors and all my UnRAID stability issues are gone.

    • Like 1
  4. I'm not technical enough in this area, but does this help us with Nvidia GPU transcoding in UnRAID:

    Quote

    Plex Media Server 1.17.0.1709 is available in the Beta update channel

    NEW:

    (Transcoder) Update to current upstream ffmpeg

    (Transcoder) Support for hardware transcoding on Linux with Intel 9th-gen processors

    (Transcoder) Support for VC-1 hardware decoding on supported platforms

    (Transcoder) Support for hardware decoding on Linux with Nvidia GPUs

    (Transcoder) Support for zero-copy hardware transcoding on Linux with Nvidia GPUs

    (Transcoder) Support for zero-copy hardware transcoding of interlaced media

     

    I'm running an older FX AMD processor and would love to just add a GPU to get more simultaneous transcoding streams without upgrading my CPU, MB and RAM.

  5. On 8/7/2019 at 5:41 PM, jonathanm said:

    How are you routing the cable? Make sure the ends are square against the drive and the port, and there is no tension in the cable. If you are fastening the cable somewhere along its length, don't. If there is tension pulling the connector out of alignment, it can cause issues.

    I tried all of those options and I even used a cable that was working for the same model SSD in my gaming rig, and in my UNRAID rig I get the errors. Finally replaced the cache drive Samsung SSD with a Western Digital and for 30 days so far I haven't had one error.

    • Like 1
  6. 10 minutes ago, nickro8303 said:

    You can try more sata cables but I can tell you you're wasting your time. I tried several brands and none of them stopped the errors. I replaced the Samsung SSD with WD and the errors stopped. So now I have a 1tb SSD I paid over $100 for working as coaster on my desk. I feel your pain.

    Which WD did you get? I'm considering the Western Digital Blue 2.5" 500GB or 1TB SSD.

  7. Just now, johnnie.black said:

    No, currently trim won't work with any LSI SAS2

    Well shoot. Thanks for letting me know and saving me some time! I'll try two more brands of SATA cables directly to my motherboard. If they don't work it looks like I have a 500GB Samsung 860 SSD as a coaster and have to purchase a different brand.

  8. 15 minutes ago, johnnie.black said:

    It might be worth a try, but note that trim will only work with SAS3 models like 9300-8i, etc.

    Excellent note. This is the only one I can get my hands on, can you tell me if trim will be supported?

    • LSI SAS2008-8I SATA 9211-8i 6Gbps 8 Ports HBA PCI-E RAID Controller Card

    If I can't use the trim plugin with my SSD on this controller than I won't even bother.

  9. On 6/6/2019 at 6:20 PM, nickro8303 said:

    Thanks for the help. I'm at my wit's end with these CRC errors. I've spent months trying to stop them. I'm ordering a WD SSD to see if that will resolve the issue.

     

    Sent from my SM-G950U using Tapatalk

     

     

     

     

    I'm in the same boat as you! Tried at least 4 different cables of 2 different brands in total. Tried all ports on my motherboard. I have an AMD setup with Samsung 860 SSD. RMA'd the drive and the new one has the CRC errors as well.

    On 6/10/2019 at 9:40 AM, nickro8303 said:

    Looks like Samsung brand SSD was the issue, replaced it with a WD SSD and I'm not getting any more CRC errors. Thanks for the help guys.

    I'd hate to have to change from the Samsung SSD but at this rate I might have to.

    On 6/11/2019 at 12:52 AM, johnnie.black said:

    Like mentioned the problem was likely not the SSD, but the cables you're using, since they are very picky with cable quality.

    I know you are experienced and very helpful, so thank you. I think I should try 2 more cable brands before giving up on this brand of SSD.

    Note: I've read a few posts about issues between Samsung SSDs and AMD board's SATA controller. I can likely acquire an LSI (or similar) PCIe 2-port SAS controller with the SAS-to-SATA breakout cables. Is it worth going through the effort of installing this in my build and trying the Samsung 860 SSD on that controller?

  10. On 5/9/2019 at 2:18 PM, Guest and_re said:

    I've had the same problem with the 860 EVO 250GB in my AMD system (AMD G785 mobo).
    The first symptom was that I couldn't get in the Win7 even though I cleanly reinstall the Windows and try again. When I fortunately succeed to enter, it got down soon working very unstably. The error was similar to the common SSD freezing but the mouse cursor can be moved being unclickable.
    I once solved it by exchanging "AMD AHCI Controller" into the Windows default driver "Standard AHCI 1.0 Serial ATA Controller". After the solution, it worked well only except CRC error count increasing. It always came with Event ID 11 atapi error (Windwos Event Log).

    Recently I got the solution from the site below. Now my SSD is working perfectly. The solution is to disable NCQ by creating a new registry value.
    https://superuser.com/questions/1294158/what-may-cause-very-high-crc-errors-on-ssd-apart-from-bad-sata-cables-if-any

     

    1) If you use the default storahci MS driver add to the registry [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\storahci\Parameters\Device] "NcqDisabled"=dword:00000001 or "SingleIO"=hex(7):2a,00,00,00,00,00

    2) If you use the AMD SATA driver add this instead: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\amd_sata\Parameters\Device] "AmdSataNCQDisabled"=dword:0000000F or "AmdSataQueueDepth"=dword:00000001

     

    I think this is caused by a kind of incompatibility or conflict between AMD SATA chips and Samsung 860 SSD as the latest Samsung Magician software even turns off RAPID mode automatically when a mobo has a AMD or ASMedia chipset.

    Dbdk1v9XcAAuKkC.jpg

    I'm using an AMD setup and i'm on my second Samsung 860 SSD. Changing cables, ports and drives have done nothing for the continuous CRC errors.

    Do you have any tips that are not Windows related, as I'm not using any VMs in my UnRAID setup.

  11. On 4/1/2019 at 9:25 AM, binhex said:

    ok cool, thanks for replying, i guess i will just need to buy from a decent manufacturer and hope for the best, i will try and remember to post back here if i do find a cable manufacturer that stops the CRC count incrementing.

     

    On 4/6/2019 at 5:29 PM, cliewmc said:

    I'd close this thread with grateful thanks. The SATA cables appear to be the culprit. My friend told me to flash the firmware for the Samsung SSD and the problem would go away. I might try that. 

    Did either of you guys find a SATA cable that works?

     

    I had a Samsung 860 Evo that had CRC error slowly increasing. Tried new cables and different ports to no avail. Finally decided to RMA the drive, put the new one in and after only 2 days I've already got 26 CRC errors again.

    Note that I also have an AMD setup.

  12. I'm still having issues. I've replaced the SSD with a mechanical drive and sent the SSD away for RMA.

     

    With the mechanical drive installed and formatted, I deleted the docker.img and recreated it. I still got the Docker Service Failed To Start error. I again used the method @Squid detailed in other posts, and edited the docker config to tell the service not to run. I restart the server, delete the docker.img and recreate and I was back in business after installing Previous Apps.

    Things worked well for a day or so, when I noticed Plex not responding. Went into the UI for UnRAID and on the docker tab I see I have the Docker Service Failed To Start again. I have no errors on my cache drive this time. I went through the steps again to recreate the docker image and sure enough it failed again within a few days. I attempted one last time last night to recreate it but this time it wouldn't even work using @Squid's steps.

    Please help me. My server is basically unusable without having NZBGet and Plex docker containers running.

     

    tower-diagnostics-20190516-0814.zip

  13. On 5/7/2019 at 3:06 PM, itimpi said:

    The syslog shows that you are having trouble communicating with the SSD.    This is probably why the system is not shutting down as it cannot successfully unmount the cache drive.    The error looks as if it is probably related to the SATA cabling for that drive.  The drive has a large number of CRC errors and that type of error is nearly always cable related.

    Thanks for the reply. I've tried changing the SATA cable twice now and I get the CRC errors still. I've also tried different SATA ports on the motherboard and still get the same errors. Is it possible the drive is bad?

     

    It's a Samsung SSD under a year old, do you think they'd honor warranty? I don't know how to prove to them it's bad though as it does run.

  14. Unraid 6.6.7

    This has happened twice in as many weeks now.

    • I update a docker application or update all and the update completes fine 
    • I only have two docker applications, NZBGet and Plex
    • After clicking Done in the completed update window I get the "Docker Service Failed to Start" error
    • Both my NZBGet and Plex are functioning still though
    • I try to stop the array to do a clean reboot, and I keep getting stuck at "Array Stopping - Retry unmounting disk share(s)..."

     

    First time this happened I performed a dirty shutdown and had to do a parity check, which ended up valid. I don't want to have to do a dirty shutdown again is my biggest issued here. Next is why the Docker service keeps failing to start. The last time I had to edit the config from "yes" to "no", reboot, delete docker image, recreate and reboot. I actually had to to this three times before I stopped getting the Docker service failed to start error.

     

    Please help, I ran a diagnostic, do I just upload the zip it created?

     

    Thanks in advance for anyone willing to help me.

     

    Edit: tower-diagnostics-20190507-0942.zip

  15. 6 hours ago, eschultz said:

    right now.

    Thanks for all your effort, it is much appreciated!

     

    It's not showing an update for me yet, but I'm sure it will come soon. Excited for the new subtitle feature in Plex.

     

    Edit: Never mind I thought I had already checked for docker updates but I hadn't. I got it.

     

    Edit 2: Well the "More" option for On-Demand Subtitles in Plex isn't showing for me. Not on the Android app or the Web App and both are up to date. Anyone else experiencing this issue?

  16. @Benson @Hoopster Sorry for the delay in following up. I appreciate the help and wanted to report back now that I have replaced my Marvell SATA controller with an LSI 9211-8i.

     

    None of the suggestions recommended allowed me to boot without a GPU like I used to be able to.

     

    I had been waiting for an LSI 9211-8i that I ordered from China and I just got it and installed it last night. I flashed the LSI controller to the latest firmware, as well as IT mode. I chose not to flash it with a BIOS. I can now successfully boot without my GPU inserted again! My previous issue must have been with the SATA controller I was using, but I still have no idea why I was able to boot without a GPU and using the Marvell for over a year. Oh well, I now have space for four extra SATA drives now thanks to the LSI.

  17. 28 minutes ago, johnnie.black said:

    No problem, you only need the bios if you want to boot from a device connected to the HBA, if not needed not having one just speeds up the booting process.

    Thanks for the help. I successfully flashed using the commands in my OP. Using '-listall' shows just like your reply, FW Ver: 20.00.07.00 and x86-BIOS: No Image.

     

    No I just need to wait to get home from work to test this beauty out! I'll be replacing a Marvel 4 port SATA controller that has been giving me issues.

×
×
  • Create New...