Support Forum

is there a better place that I should be posting this?
i moved everything over to C:\ and manually move the files over. same thing.

SABcomplete /incomplete are on C:\ now as you asked.
it is unpacking in d:\tv because it is in the tv category , ahich sab tries to unpack in d:\tv hence the error.

I did exactly as you asked to troubleshoot and moved complete /incomplete where you asked me to move it to

sander wrote:

905jay wrote:sure i can try that, but any idea why this fails suddenly?

No. Therefore this test.

Hi Sander it failed again with unpack error on d:\_UNPACK.......
i checked and i can write /move files freely without issue to and from that path

i added the log and new screenshots for you in the google drive

sander wrote:

905jay wrote:sure i can try that, but any idea why this fails suddenly?

No. Therefore this test.

ok done. took a screencap. i will document everything in that google drive share from page1 of this post
I will monitor tonight and will let you know

sure i can try that, but any idea why this fails suddenly?
this setup has been going for 2 years now without issue

In the JPG, I only see "ERROR: write error". Correct? On your Windows, open a CMD (DOS) box, and type wmic logicaldisk get name,filesystem and post the output here. Example output: wmic logicaldisk get name,filesystem FileSystem Name NTFS C: D: FAT E: NTFS G: NTFS H: NTFS M: NTFS Q: NTFS ...

Just copy-paste the 30 lines from sabnzbd.log around your error message. No need for a big log file. FWIW: You have not given public access to the google drive file: You need permission Want in? Ask for access, or switch to an account with permission. My apologies, It should be available now for yo...

On phone now so can't read the log, but the whole restart thing sounds very clearly to me like you're sabnzbd is being started with extra command line parameters. This is maybe done by a script provided by unraid? You can see it in the first page of the Config which command line parameters were use...

ive got the log, sorry for the delay. i will pop it on my google drive https://drive.google.com/open?id=0B1rYNZ28amgucjg0V3R0MGhNdXM another odd behaviour i have noticed is that every time sab restarts, weather by restarting the application or rebooting the system the host ip in sab (general tab) ch...

yes i apologize, i believe it is "unpacking failed, write error disk full" I am waiting for shows to be added via sonarr and downloaded via Sabnzb so I can post the debug log output. This afternoon I will manually add some to reproduce the error so I can show you the logs. Thanks for your ...

I have confirmed this by writing to the disk manually every time I see the error As soon as I see all the red in Sabnzbd gui, i try (again) to write a file, read a file, delete a file, move a file. It always works. he disk is fully writable, and my Intel RAID config shows all good -- no concerns. Th...

OS in Windows10x64 on Samsung 850 Pro SSD Downloads go to RAID 1 disk pair, FS is NTFS Downloads range from 800mb - 3gb depending on the release group etc... I just cleared the log, and set logging to debug. Downloads are working fine for now, but I rebooted an hour ago. The problem duplicates itsel...

Hi Everyone, Long time user first time poster. I have noticed over the last 2 weeks(ish) nzb's added from sonarr start to download, then I get "write faild disk full" error. The disk is in a mirrored raid, and both disks are healthy. I can write files to the disk, read filed from the disk,...