Support Forum

After updating the kernel, it is working again and showing the actual free space! Thanks!

Oh that's great news. I am on the affected kernel version 5.15.0-102.112. I will check if 5.15.0-105.115 is available for me to update! Thanks!

sander wrote: ↑April 18th, 2024, 1:56 am check out the other thread in which you posted ... full explanation & howto

i tried but i didnt get it

if Sab can't get the free space, is there anyway to tell sab to ignore that and just download there anyway? i did try changing the 1G setting on the incomplete folder in sab to nothing but it didn't help

i also applied some OS patches, so maybe that did something. anything i can try running like Sab checks for free space? seems like something made the free space info stop working on the smb share maybe.

just as a test i tried moving the sab complete and incomplete paths to a local ubuntu drive path with 86GB free. sab shows expected 86GB free. now it can download, but it's now failing to move from complete folder to the smb share. however i can copy by hand to the smb destination no issue, so i don...

this is what the sab log shows for anything i try : 2024-04-17 20:51:35,905::INFO::[notifier:142] Sending notification: Warning - Too little diskspace forcing PAUSE (type=warning, job_cat=None) 2024-04-17 20:51:35,905::WARNING::[assembler:155] Too little diskspace forcing PAUSE 2024-04-17 20:51:35,9...

since upgrading, it shows i have 0 B free space even though i have plenty and other download tools to the same mounted smb share work fine. sabnzbd on ubuntu 20.04 mounted to a windows smb share seems to have started this problem only after upgrading to sab 4.2.3 i can browse the files on teh mounte...

i have the same issue out of nowhere it shows i have 0 B free space even though i have plenty and other download tools to the same mounted smb share work fine. sabnzbd on ubuntu 20.04 mounted to a windows smb share seems to have started this problem only after upgrading to sab 4.2.3 hope someone can...

Sadly the setting made no difference. It's still happening =(

Yes I probably did a long time ago since the description of that settings made me think it's safer to not enable it. But strange that I've only recently started having this video problem? I enabled it and keeping my fingers crossed! Thanks!

No, folder rename is not enabled.

Did another test. Just dropped the nzb file manually into sabnzbd web ui on ubuntu and let it download to sabnzbd completed folder then it was automatically moved to plex folders by sonarr. checksum is different than all the others but it plays without issue doing this test. So not sure what's going...

Ok, I installed nzbget on a new windows 11 virtual machine. configured it with same news server. Grabbed the same nzb file that was used for the video that my sabnzbd used. Played the file downloaded from nzbget and no issue at all playing. Checked sha256 of each file and the size in bytes is exactl...

No I'm not sure about the source. So, maybe I can try setting up SAB on some other system to try one of the videos I see this with. But it's many different sources, not just one. So unlikley