damonwilson24

I am having issues with my macs opening up smb folders that are very large (specifically my photo backups). It will eventually open, but it takes a very long time and makes my photos share unusable from my mac. My windows pc opens it right up. I do not have any issue opening up smaller SMB shares from the mac. Aside from creating a lot of subfolders for my pictures, are they any other options? Is this a known limitation? For the record I am running Yosemite.

You are correct. This morning I was chatting to my coworker who had a similar problem with memory and then it dawned on me that maybe its just using the 512GB drive for parity and only leaving me with the smaller 64GB drive (even though it said I had 129GB remaining). Once I broke the pool, removed the smaller drive, and moved my data back to it, everything seems to be working fine. If that changes, I will let you know. I want to thank everyone for their input to get me through this. The unraid forums are some of the best around and I appreciate all the assistance.

I have a 500 and 64GB cache pool with 219GB free. So unless the pool is not working right, it is something else. I just looked through the VM log and the unraid log on the dashboard and I am seeing errors. I am new to unraid, but I would guess these errors are not good. This is not all of it, but they both seem to repeat the same errors so I just pasted part of it: VM log: 2015-08-19 23:50:26.966+0000: starting up libvirt version: 1.2.15, qemu version: 2.3.0 Domain id=30 is tainted: high-privileges Domain id=30 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) qemu: terminating on signal 15 from pid 15552 2015-08-20 00:45:58.223+0000: shutting down 2015-08-20 00:46:00.953+0000: starting up libvirt version: 1.2.15, qemu version: 2.3.0 Domain id=31 is tainted: high-privileges Domain id=31 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) Dashboard log: Aug 19 21:03:21 unraid kernel: blk_update_request: I/O error, dev loop0, sector 9251096 Aug 19 21:03:21 unraid kernel: BTRFS: bdev /dev/loop0 errs: wr 6454, rd 0, flush 0, corrupt 0, gen 0 Aug 19 21:03:22 unraid kernel: loop: Write error at byte offset 4736688128, length 4096. Aug 19 21:03:22 unraid kernel: blk_update_request: I/O error, dev loop0, sector 9251344 Aug 19 21:03:22 unraid kernel: BTRFS: bdev /dev/loop0 errs: wr 6455, rd 0, flush 0, corrupt 0, gen 0 Aug 19 21:03:22 unraid kernel: loop: Write error at byte offset 4736696320, length 4096. Aug 19 21:03:22 unraid kernel: blk_update_request: I/O error, dev loop0, sector 9251360 Aug 19 21:03:22 unraid kernel: BTRFS: bdev /dev/loop0 errs: wr 6456, rd 0, flush 0, corrupt 0, gen 0 Aug 19 21:03:22 unraid kernel: loop: Write error at byte offset 4736823296, length 4096. Aug 19 21:03:22 unraid kernel: blk_update_request: I/O error, dev loop0, sector 9251608 Aug 19 21:03:22 unraid kernel: BTRFS: bdev /dev/loop0 errs: wr 6457, rd 0, flush 0, corrupt 0, gen 0 Aug 19 21:03:22 unraid kernel: loop: Write error at byte offset 4736950272, length 4096. Aug 19 21:03:22 unraid kernel: blk_update_request: I/O error, dev loop0, sector 9251856 Aug 19 21:03:22 unraid kernel: BTRFS: bdev /dev/loop0 errs: wr 6458, rd 0, flush 0, corrupt 0, gen 0

One of these machines is a windows 7 machine and it has been running fine since I built it 2 weeks ago. Today I was connected to it from work doing a download and it just dropped me. When I got back home I saw it was in a paused state. I have started it up 3x since and it keeps pausing.

All of a sudden my 2 VM machines go into paused mode without notice. It does not let me resume them and the only way to get them out of it is to do a force stop. It just started happening and does it within minutes of booting them up. Any ideas where to start looking? I was just about to start building out my home lab. Thanks!

I went barebones and it is much much faster now. I also don't have the ssd cache issue anymore because the passthrough was not working properly. I may run it like this for a while to see if it makes more sense to stay like this and virtualize my esxi. I don't have lots of free time to tinker like I used to so maybe using going barebones makes more sense. We will see though as I still need a vm environment for my home lab. I appreciate all the help!

Thanks guys. I will take a look at that thread. I built this server on the recommendation of a coworker who has the the same setup as me. He just has a 4 year old system and never had issues with it (even though even he said it is not officially supported). He has since switched to bare metal just for the heck of it. He suggested I stay on esxi and a virtual unraid just to get used to esxi management (as we use it at work). I can always run the esxi virtually if I need to. I would be more than happy to test it bare metal just to confirm its not an issue with unraid. BRiT. If you still want the diagnostic file, I can upload it. I just was not sure if its the whole diagnostics folder, or a specific portion within it you wanted to look at

Hey guys, I am new to Unraid. My server build has been a work in progress these last few months. It is up and running on a esxi server but acting very slow to respond through the web gui. Sometimes I have to wait a few min to even get to the webpage upon booting. Once up, it can take 20-30 seconds to switch between tabs (but not always). I cannot find any rhyme or reason for it, but it is extremely frustrating. I am afraid to move my data to it because it just seems like its not stable. I have redone my usb stick, but that did not help at all. Any ideas? Thanks ps. I have a few other issues but I will do one post at a time syslog-2.txt