ok...1 ram module has gone....now everything seems to be ok!!!
i can mark as solved this thread but i still have debug log problem...
QuickCheck OK - RAR Corrupt [debian] [SOLVED]
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: QuickCheck OK - RAR Corrupt [debian] [SOLVED]
I'm a bit reluctant to help further: this was (and is?) a hardware problem. Maybe your disk is faulty too. Google "linux check disk health".
Furthermore, with your broken RAM your OS / filesystem can be broken too. So I would start with a fresh install of your OS. And then install Ubuntu, as it's easier.
Furthermore, with your broken RAM your OS / filesystem can be broken too. So I would start with a fresh install of your OS. And then install Ubuntu, as it's easier.
Re: QuickCheck OK - RAR Corrupt [debian] [SOLVED]
ok...only for info, this is the result of disk check in /home partition:
root@debian:/dev# /sbin/e2fsck -pvcf /dev/nvme0n1p1
/dev/nvme0n1p1: Updating bad block inode.
/dev/nvme0n1p1: Inode 3407884 extent tree (at level 2) could be narrower. IGNORED.
/dev/nvme0n1p1: Inode 3408129 extent tree (at level 2) could be narrower. IGNORED.
/dev/nvme0n1p1: Inode 3408137 extent tree (at level 2) could be narrower. IGNORED.
/dev/nvme0n1p1: Inode 3408142 extent tree (at level 2) could be narrower. IGNORED.
/dev/nvme0n1p1: Inode 3539875 extent tree (at level 2) could be narrower. IGNORED.
/dev/nvme0n1p1: Inode 3670018 extent tree (at level 1) could be narrower. IGNORED.
/dev/nvme0n1p1: Inode 3670020 extent tree (at level 1) could be narrower. IGNORED.
8321 inodes used (0.03%, out of 30466048)v
28 non-contiguous files (0.3%)
3 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 8293/15/5
21184807 blocks used (17.39%, out of 121850368)
0 bad blocks
9 large files
7491 regular files
821 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
------------
8312 files
Also / partition is clean and every installed sosftware works fine. I can survie without log.file but i very would like to understad if there is a reason why i can get a complete log file launching sabnzbd by CLI and not launching it as a service... i understand that it is not the right thread, maybe can i open a new topic and see if anyone other has the same issues?
root@debian:/dev# /sbin/e2fsck -pvcf /dev/nvme0n1p1
/dev/nvme0n1p1: Updating bad block inode.
/dev/nvme0n1p1: Inode 3407884 extent tree (at level 2) could be narrower. IGNORED.
/dev/nvme0n1p1: Inode 3408129 extent tree (at level 2) could be narrower. IGNORED.
/dev/nvme0n1p1: Inode 3408137 extent tree (at level 2) could be narrower. IGNORED.
/dev/nvme0n1p1: Inode 3408142 extent tree (at level 2) could be narrower. IGNORED.
/dev/nvme0n1p1: Inode 3539875 extent tree (at level 2) could be narrower. IGNORED.
/dev/nvme0n1p1: Inode 3670018 extent tree (at level 1) could be narrower. IGNORED.
/dev/nvme0n1p1: Inode 3670020 extent tree (at level 1) could be narrower. IGNORED.
8321 inodes used (0.03%, out of 30466048)v
28 non-contiguous files (0.3%)
3 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 8293/15/5
21184807 blocks used (17.39%, out of 121850368)
0 bad blocks
9 large files
7491 regular files
821 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
------------
8312 files
Also / partition is clean and every installed sosftware works fine. I can survie without log.file but i very would like to understad if there is a reason why i can get a complete log file launching sabnzbd by CLI and not launching it as a service... i understand that it is not the right thread, maybe can i open a new topic and see if anyone other has the same issues?