[TRIM on new SSD receiving Input/output error (Solved)]

Thanks Johnnie. When I look at the logs, I see an additional error "print_req_error: critical target error, dev nvme0n1, sector 123..." which doesn't sound good for a brand new drive.

 

In the meantime, I'll order a different drive, and make sure appdata is being backed up nightly. I guess that's what I get for trying to save a few bucks. 

 

 

edit update 10/10/18: I grabbed a Samsung 970, and it's been working as expected the past 2 days. No errors during the TRIM operation.

[TRIM on new SSD receiving Input/output error (Solved)]

I installed a 512GB m.2 NVMe drive on a PCIe Lycom DT-120 adapter. After install, the SSD was immediately visible, and I replaced my old HDD cache drive with it without issue. However, I have been receiving an error when I attempt to run TRIM. Can someone take a look and help? Below is the error I receive via email, and attached is the diagnostics report

 

fstrim: /mnt/cache: FITRIM ioctl failed: Input/output error

or 

fstrim: /mnt/cache: FITRIM ioctl failed: Remote I/O error

 

 

 

[[Support] binhex - SABnzbdVPN]

Did you set up the /data (/mnt/user/Downloads) folder in Sonarr's Docker settings? Sonarr need to be able to access the folder Sab is the files.

[[Support] binhex - SABnzbdVPN]

In the image you provided, the completed download folder should be /data, not /mnt. If you click on the left arrow, you should go to the parent folder, and see the /data listed in there. Select /data, and you should be good to go.

[[Support] binhex - SABnzbdVPN]

Rikdegraaff, have you mapped the /mnt/disk7/UsenetDL folder in the SABnzbd docker?

 

 

In the example above, you would reference /data to get to the /mnt/user/Downloads folder. By mapping the folders, you don't reference the actual folder path. You can replace the Downloads folder with the path you listed (/mnt/disk7/UsenetDL)

[[Support] Linuxserver.io - SABnzbd]

I saw a similar error a couple weeks ago. My error was "/usr/bin/env: ‘python’: No such file or directory." The solution I found somewhere (either here in the unraid forums, or in the Sab forums) was to change the first line of the "sabToSickBeard.py" file

 

old:

#!/usr/bin/env python

 

new:

#!/usr/bin/env python2

 

Does your top line have an "\r" in it? If so, you may need to remove it.

[EncFs plugin for unRAID v5]

Where you ever able to get something working with v6?

 

With the ACD $5 sale recently, I'm looking for a way to encrypt my stuff before uploading to Amazon. When looking for different options, I stumbled across encfs, and then found your plugin when looking for an unraid variant. Thanks!

[Sickbeard + Sabnzbd not deleting folders....]

Have you reviewed the SB logs? I had this problem before due to SB not shutting down when it upgraded, which screwed something up.

 

To troubleshoot, can you perform a "manual post-processing" in SB, and see what errors you get? From what I remember, the error is near the end of the log file. If you search for the error, you'll likely find the answer in the SickBeard Forums.