Hey,

So i was having some issues with transmission docker, actually i accidentally deleted my watch and download folders so i restored them from recycle bin but transmission was still giving me some errors so decided i stop my unraid array and start it again to see whether it will  fix it or not but the moment i hit start i got some errors reported by fix common problems plugin.

Error No1.

Cache Floor Size (calculated to 2048000000 bytes) is larger than your cache drive (1945759744 bytes)

Error No2.

Call Traces found on your server

 

If anyone knows how fix these errors then please help.

unraid-diagnostics-20170419-1737.zip

You have configured things a little differently than what I'm used to seeing. No parity, no cache, 2 data disks as btrfs.

 

Since you don't have cache, the cache floor size error must be a false report from FCP.

 

The Call Traces seems to be associated with btrfs, but not sure if it is referring to one of your disks. There are some things in your syslog about loop0, your docker.img, which is also btrfs. However, I don't see that device (or indeed your actual disks) in df.

 

Do you have docker enabled?

 

Are you having any actual problems?

 

 

12 minutes ago, trurl said:

You have configured things a little differently than what I'm used to seeing. No parity, no cache, 2 data disks as btrfs.

 

Since you don't have cache, the cache floor size error must be a false report from FCP.

 

The Call Traces seems to be associated with btrfs, but not sure if it is referring to one of your disks. There are some things in your syslog about loop0, your docker.img, which is also btrfs. However, I don't see that device (or indeed your actual disks) in df.

 

Do you have docker enabled?

 

Are you having any actual problems?

 

 

yeah as im new to unraid i decided to go with new stuff which is BTRFS. As for the parity drive im going add it next month until then i won't be putting any critical data on it and as for cache drive i don't need it for now as im already getting real good speeds i guess its because im not having any parity drive (no parity drive = no parity calculations = better speeds, correct me if im wrong).

Actually after posting those error i rebooted my unraid server and after that its not reporting any error as of now. 

Unfortunately im having way some actual problems too.

Like with plex server docker --- not running schdule tasks.

with transmission Docker --- Download speeds are real slow.

with deluge Docker --- Not downloading anything, all my torrents are entering some kind of error state.

openvpn docker  --- webui not working.

And i also noticed i more little thing that while im installing any kind of docker, the unraid web gui stops responding in other tabs but as soon as its done with installing part its back again.

So preety good amount Actual Problems.

I think you would be better off to start over and include a cache disk and a parity disk. As you said, the reason you have good speed is because you have no parity to write. You will not want parity writing all the time due to dockers writing their appdata.

 

As for all the other things, you should take things more slowly. Get your array working reliably before tackling dockers. Get one docker working well before adding another. If you do have a specific problem, start a thread about that specific problem and we can work on it before adding other problems to troubleshoot.

10 minutes ago, trurl said:

I think you would be better off to start over and include a cache disk and a parity disk. As you said, the reason you have good speed is because you have no parity to write. You will not want parity writing all the time due to dockers writing their appdata.

 

As for all the other things, you should take things more slowly. Get your array working reliably before tackling dockers. Get one docker working well before adding another. If you do have a specific problem, start a thread about that specific problem and we can work on it before adding other problems to troubleshoot.

i will add them both in the next month but i really dont get it, why are you recommending me to add  them now and start over again cause one of the main reason behind going with unraid was its ability to add drives later as well. i know that after adding parity drive speeds will be low, as you have also stated in your post too.(You will not want parity writing all the time due to dockers writing their appdata) 

So basically i just wanna know that is their any special reason behind you recommending to start over with parity and cache drives which i don't know about?

It's OK as it is for now. When you get a cache disk, the shares you have that need to be on cache will get moved to cache anyway.

 

I still recommend tackling one problem at a time though.

 

Don't know if you have a problem with btrfs or not. Most have only been using it with cache pools and using XFS on their array disks.

1 hour ago, trurl said:

Since you don't have cache, the cache floor size error must be a false report from FCP.

Yes and no.

 

The thing is that for the error to be generated, /mnt/cache has to exist.  (The cache disk size listed in the OP is going to be the size of the RAM give or take).

 

A docker template is odds on referencing /mnt/cache/appdata/.... which since the drive doesn't actually exist winds up creating it in RAM.

24 minutes ago, Squid said:

A docker template is odds on referencing /mnt/cache/appdata/.... which since the drive doesn't actually exist winds up creating it in RAM.

I wonder if the loop0 issues aren't similar.

 

Max,

where did you tell it to create docker.img?

10 minutes ago, trurl said:

Max,

where did you tell it to create docker.img?

If im getting your question right then the answer will be through that Community Applications plugin.

Just now, Max said:

If im getting your question right then the answer will be through that Community Applications plugin.

Not at all.

 

In Settings - Docker, where you enable the docker service, you had to tell it where and what size to create docker.img.

1 minute ago, trurl said:

Not at all.

 

OOops,

Answer will be in pic im going to attach with this post.

As far as i remember never touched anything in docker service settings of course except enabling docker service.

 

That looks OK.

 

In your diagnostics, logs/syslog.txt has some of this:

Apr 19 13:29:06 Unraid kernel: BTRFS error (device loop0): parent transid verify failed on 1008975872 wanted 3840 found 1550
...

then later this:

Apr 19 17:22:11 Unraid emhttp: shcmd (7178): umount /var/lib/docker |& logger
Apr 19 17:22:11 Unraid kernel: ------------[ cut here ]------------
Apr 19 17:22:11 Unraid kernel: WARNING: CPU: 1 PID: 25995 at fs/btrfs/extent-tree.c:134 btrfs_put_block_group+0x42/0x59
Apr 19 17:22:11 Unraid kernel: Modules linked in: xt_nat veth xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables tun ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod bonding x86_pkg_temp_thermal coretemp i2c_i801 i2c_smbus ahci i2c_core libahci e1000e ptp pps_core video backlight [last unloaded: vhost]
Apr 19 17:22:11 Unraid kernel: CPU: 1 PID: 25995 Comm: umount Not tainted 4.9.19-unRAID #1
Apr 19 17:22:11 Unraid kernel: Hardware name: To be filled by O.E.M. To be filled by O.E.M./O.E.M, BIOS 4.6.5 08/20/2012
Apr 19 17:22:11 Unraid kernel: ffffc90009a77d20 ffffffff813a3bf2 0000000000000000 ffffffff81969034
Apr 19 17:22:11 Unraid kernel: ffffc90009a77d60 ffffffff8104d04c 0000008609a77d00 ffff880139249c00
Apr 19 17:22:11 Unraid kernel: ffff880139249ce8 ffff880136ec4090 ffff880139249c00 ffff880136ec40a0
Apr 19 17:22:11 Unraid kernel: Call Trace:

You might try stopping the docker service, deleting then recreating docker.img. and adding your dockers back from Community Applications - Previous Apps

 

Still don't understand why your diagnostics has nothing for loop0 or your disks in system/df.txt. Maybe you should check your disks filesystems but I don't have any experience with btrfs in the array.

 

Maybe @johnnie.black will come to the rescue.

12 minutes ago, trurl said:

You might try stopping the docker service, deleting then recreating docker.img. and adding your dockers back from Community Applications - Previous Apps

About Dockers, 

For now i have deleted all dockers except plex and now im trying qbittorrent docker for torrents, as this the only docker which is giving at least some kind of acceptable speeds.

but still it nothing compared to what im getting with same qbittorrent software on windows. Now, how come same piece of software is performing better on windows is beyond my understanding.

1 hour ago, trurl said:

Still don't understand why your diagnostics has nothing for loop0 or your disks in system/df.txt. Maybe you should check your disks filesystems but I don't have any experience with btrfs in the array.

 

That's because the diags were grabbed with the array stopped, only see issues with the docker image and like trurl said it should be deleted and recreated.

1 hour ago, johnnie.black said:

 

That's because the diags were grabbed with the array stopped, only see issues with the docker image and like trurl said it should be deleted and recreated.

Thanks guys, @trurl @Squid @johnnie.black thanks everything.

Two last things that i would like to ask for now.

1.) How that docker image got corrupted did i did something wrong.

2.) How come Everytime when im installing a new docker web gui becomes unaccessible and after it's done installing docker i can access the web gui back again.

21 minutes ago, Max said:

How come Everytime when im installing a new docker web gui becomes unaccessible and after it's done installing docker i can access the web gui back again.

Perfectly normal and affects everyone.  Its because of how the UI operates -> only one task at a time.  6.4 when released is supposed to be switching to a new web engine (nginx) that should alleviate that problem.

@trurl @Squid @johnnie.black hey

As you all suggested me to delete the docker image so today, to do the same when i the turned my unraid server on and hit start to start array i got some error 349 on disk 1 and then when i hit stop to stop the array disk 1 went completely missing.

So i just gave a push to all cables connected to my hdd and it came back alive.

So my question is could it be all because of some loose cable connection and as for Dockers i would like to know what would be the best way to delete docker. Img in your opinion.

2 hours ago, Max said:

i would like to know what would be the best way to delete docker. Img in your opinion.

Settings - Docker. Disable docker and you can delete docker.img from that same page, then recreate it from that page.

 

After recreating it you can get your containers back by installing them from Community Applications - Previous Apps.

10 minutes ago, trurl said:

Settings - Docker. Disable docker and you can delete docker.img from that same page, then recreate it from that page.

 

After recreating it you can get your containers back by installing them from Community Applications - Previous Apps.

Okay i did exactly like u said but after deleting docker image, docker page wasn't loading properly and i noticed that if i turn down my array it will load fine.

So i ended up reformatting my drives (still Btrfs) so now docker page is loading fine but now i realized that all the data that I'm writing to window share is only going in disk 1, disk 2 is just empty

Each user share has settings which control how it uses the disks. Go to any user shares page and turn on Help. Allocation method defaults to High Water, which is a good compromise between balancing your data across disks, without the need to constantly switch disks when reading and writing.

10 minutes ago, trurl said:

Each user share has settings which control how it uses the disks. Go to any user shares page and turn on Help. Allocation method defaults to High Water, which is a good compromise between balancing your data across disks, without the need to constantly switch disks when reading and writing.

its already set on high water. thats why i feel its  a bit weird cause earlier it was writing to both of my drives.

11 minutes ago, Max said:

its already set on high water. thats why i feel its  a bit weird cause earlier it was writing to both of my drives.

Sounds like it's working OK now.

4 minutes ago, trurl said:

Sounds like it's working OK now.

Hmm 

Okay if u say so.

4 minutes ago, Max said:

Hmm 

Okay if u say so.

If you haven't filled the first drive to the high water mark then it won't write to another drive, simple as that.

 

I can't speculate on how you got anything on another disk before, there are many ways to make that happen intentionally or by accident.

 

2 minutes ago, trurl said:

If you haven't filled the first drive to the high water mark then it won't write to another drive, simple as that.

 

I can't speculate on how you got anything on another disk before, there are many ways to make that happen intentionally or by accident.

 

Great a minutes ago i was thinking that it's wired that now it's not writing to both of my drive and now I'm thinking earlier it writing to both my drive way actually the wired part. ?