write error disk full

[905jay]

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, move and copy around without issue.
There is over 800GB on that raid array.

If i reboot, and re-add the same nzb files, they download fine, and a few hours later (today I rebooted at 1pm, and had to reboot again at 11pm -- time of this post).

I uninstalled sabnzb, removed all registry entries etc.., and reinstalled /reconfigured sabnzbd, however the issue persists.

Again, I have confirmed the issue is not hardware related.

Edit: I have just cleared the logs, and set to debug mode. I will update this post tomorrow with the log results

[sander]

Post the exact error message, plus surrounding lines from sabnzbd.log.
What kind of OS?
What kind of filesystem is on your disks.
How large are the downloads?
Can you download this: http://nzbindex.com/download/149652132/ ... 742-MB.nzb

[905jay]

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 itself every day for the last week and a bit, however I don't know exactly when it pops up.
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.

Just to reiterate, a reboot fixes it immediately (for an unspecified duration of time).

[sander]

What is the exact error? Is is 'Unpacking failed, write error or disk is full?'

I have confirmed the issue is not hardware related.

How have you confirmed that?

[905jay]

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.
The drive(s) that are used by SABNZBd to write to, is a media related RAID 1. There is lots of writing happening on these disks, and this is the only place where I can see any errors, which leads me to believe it is software related, but I have been wrong before!!

[sander]

and my other question?

[905jay]

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 patience and help

[sander]

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 patience and help

Please be 100% correct with the error message; there is a big difference between

'write error disk full' (like in your subect)

and

'Unpacking failed, write error or disk is full?'

The last message contains an "or" (which is essential), and a question mark.

[905jay]

ive got the log, sorry for the delay. i will pop it on my google drive

https://drive.google.com/open?id=0B1rYN ... 3R0MGhNdXM


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) changes to 127.0.0.1 instead of 192.168.1.100 that i assign it. When this happens the skin also changes back to plush gold.

[safihre]

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 used. These are used again when restarting.

[sander]

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.

[905jay]

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 used. These are used again when restarting.

Thanks for the info. I have not added any additional parameters that I am aware, and in the course of troubleshooting the issue, I uninstalled SAB completely, and set up cleanly. Can you offer some advice of removing these parameters as it appears uninstalling didn't do the trick.
Could this be why, also, when restarting the application itself, or rebooting the server, it always reverts back to "Plush Gold" and 127.0.0.1 Host IP instead of what I have changed it to?

[905jay]

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 you to view. There is also a screenshot in there of the error as I see it in SAB (just in case it helps somehow).

I don't have access to that machine at the moment, so if you can please try the link again. The log is in-and-around 3mb.

[sander]

In the JPG, I only see "ERROR: write error". Correct?

On your Windows, open a CMD (DOS) box, and type

Code: Select all

wmic logicaldisk get name,filesystem

and post the output here.

Example output:

Code: Select all

wmic logicaldisk get name,filesystem

FileSystem  Name
NTFS        C:
            D:
FAT         E:
NTFS        G:
NTFS        H:
NTFS        M:
NTFS        Q:
NTFS        X:

[905jay]

In the JPG, I only see "ERROR: write error". Correct?

On your Windows, open a CMD (DOS) box, and type

Code: Select all

wmic logicaldisk get name,filesystem

and post the output here.

Example output:

Code: Select all

wmic logicaldisk get name,filesystem

FileSystem  Name
NTFS        C:
            D:
FAT         E:
NTFS        G:
NTFS        H:
NTFS        M:
NTFS        Q:
NTFS        X:

Sure thing Sander, here you are:

Code: Select all

C:\Users\jay>wmic logicaldisk get name,filesystem
FileSystem  Name
NTFS        A:
NTFS        C:
NTFS        D:
NTFS        E:
NTFS        P:
NTFS        Y:
NTFS        Z: