stealth82

I just wanted to say that I finally decided to install my first 6.20 beta, that is, beta 21. I didn't make any hardware changes since my early woes and lo and behold, it's stable now. So far, no problems whatsoeve. I'm starting feeling very, very, happy. Thanks unRAID staff for your hard work! Looking forward to seeing more magic happening

I noticed a strange behaviour. If I access the Settings > Docker page and all my disks are spun off before the page loads it makes all the disks spin up. I don't understand why. Besides, my docker image resides on the cache disk. Has anyone seen this before?

What do you need to execute after the torrent has finished?

I don't have the plugin. Is it the plugin that copies the log to the flash? How is it possibile that, in order to perform the most basic of the commands in the universe of Linux, you need an additional plugin to make it work?

I don't have any /flash(boot?)/logs folder

Agreed

I did issue a reboot command and happened to me just now: unRAID detected an unclean shutdown...

Besides the Xonar?

By the way, why would you want to pass the onboard audio through?

I mean that I'm quite sure it will still throw the error he's experiencing. As far as I could see the Xonar, PCI version in my case, won't share the vm with any other sound card. Either it alone or nothing. Anyway, I would be tremendously happy to be proved wrong regarding that.

If he does the VM simply won't start as it doesn't now.

Is your Xonar PCI or PCIe? Don't pass the AMD HDMI Audio. Still, if your VM finally boots successfully you MIGHT find yourself dealing with garbled audio from your Xonar and VM + unRAID severe lockups. Hope that doesn't happen to you and it's just my hardware to be unholy. If it is going to happen to you, also your hardware is unholy. Passing through PCI Sound Card http://lime-technology.com/forum/index.php?topic=44591

I'm just using cd and I guess it's the same thing through programs like WinSCP. I have 8GB of RAM and unRAID tells me only 20% is used. What I can do is to spin down the disk after it was spun up. I browse the folder again, launch a ls command and this time the disk doesn't spin up.

I did that but nothing changed. I didn't experience further freeze but it was just one short test, till I noticed that stuttering and garbled audio was there. For the moment I put things on hold: reinstated my old HTPC and moved the sound card back there. Hopefully things might change with the next update. I'd really love to hold my breath.

ssh

I've not read the whole thread, sorry, but the use of this plugin seems pretty straightforward to me. Either I'm misinterpreting its use or something is wrong. This is the configuration: Dec 28 21:20:05 Tower cache_dirs: ============================================== Dec 28 21:20:05 Tower cache_dirs: Starting cache_dirs: Dec 28 21:20:05 Tower cache_dirs: Arguments=-d 10 -e docker -e music -e torrents -e vm Dec 28 21:20:05 Tower cache_dirs: Cache Pressure=10 Dec 28 21:20:05 Tower cache_dirs: Max Scan Secs=10, Min Scan Secs=1 Dec 28 21:20:05 Tower cache_dirs: Max Scan Depth=10 Dec 28 21:20:05 Tower cache_dirs: Use Command='find -noleaf' Dec 28 21:20:05 Tower cache_dirs: Version=2.1.0 Dec 28 21:20:05 Tower cache_dirs: ---------- Caching Directories --------------- Dec 28 21:20:05 Tower cache_dirs: downloads Dec 28 21:20:05 Tower cache_dirs: home Dec 28 21:20:05 Tower cache_dirs: movies Dec 28 21:20:05 Tower cache_dirs: photos Dec 28 21:20:05 Tower cache_dirs: software Dec 28 21:20:05 Tower cache_dirs: tvshows Dec 28 21:20:05 Tower cache_dirs: videos Dec 28 21:20:05 Tower cache_dirs: ---------------------------------------------- Dec 28 21:20:05 Tower cache_dirs: cache_dirs process ID 12016 started and the process root 12016 1 0 Dec28 ? 00:06:39 /bin/bash /usr/local/emhttp/plugins/dynamix.cache.dirs/scripts/cache_dirs -d 10 -e docker -e music -e torrents -e vm This should cover a simple share browsing down to the following depth without spinning up a disk, right? /mnt/user/movies/1991/Fried Green Tomatoes (1991) But the disk having that folder is spinning up anyway. Where's my mistake?

Is still recreating the docker image the only solution to a say "rsync -a /mnt/cache/ mnt/user/backup/cache/" and return?

I have the PCI version and I'm experiencing instability issues. Movie playback is far from being flawless: every some random seconds or minutes the video stutters and the soundcard plays garbled audio. Sometimes, it can occur that the whole server freezes - not only the vm - and I am forced to hard reset everything. If I play audio only - Spotify for example - the playback sounds good but I'm still experiencing the entire lockup of the server. I'm really thinking the audio card is to blame at this point. I tried SeaBIOS and OMVF, Windows 8.1 and Windows 10, official driver and unixonar driver, but the result doesn't change. I guess the "Failed to setup INTx fd:" error message, when passing the whole video card - video and hdmi audio, has to do with the PCI being more rigid than the PCIe. I don't really know what to do as I don't want to spend some 200€ for having a PCIe version of the same card and still deal with the same problem. I guess everything is working well with you

Is your card PCI or PCIe?

All I can say is the cable had worked for a long time, and likely had worked before on a different disk as I tend to hoard them and only toss if proven faulty. If you have a brand new cable try that. I can confirm it definitively was the sata cable. I had 4 different sata cables and all of them proved to be unreliable, at least for a SATA 3.1 device. What was left was a couple of errors that, elsewhere in this forum, were considered negligible. However, since I was still on time to have the SSD replaced I swapped it for a SandDisk Extreme Pro. The log is now clean with this one.

If that had been possible I would surely have done it. I certainly have backups of what is vital but, still, running the parity check is mandatory and a PITA. It would already be something if one could just try out the VM without having to start the array. In that case, if the server froze, the data would still be safe and sound after the restart.

If I may say, that would depend on the importance of what else is running on the machine hosting it. The concept on the paper is good but if the catch is "with unholy hardware it may cause a heck of a complete freeze and say bye to unRAID and welcome to parity check" I would think twice before even thinking whether I want to endanger my data for the fun of it. I get it's not unRAID's fault, I guess complete "isolation" isn't achievable (yet?), but how can that be good for the product? It is nice but I can't say it is wise. If only good tested configs are allowed then this must be stated, and all the untested ones get the "experimental/run at your risk" label right where it's necessary to see it. I'm saying these things only because unRAID is freezing. I couldn't care less if it were just the VM to freeze.

OK, the errors were definitely caused by my 4 too old sata cables. Bought new 6gb certified ones and the speed is finally 6gb stable. I'm using xfs and the result is... I'm counting the 5 complete freeze since I started tinkering with virtualization. Next step will be removing the audio card and watching movies in complete silence. I still believe that the complete freeze of unRAID is simply UNACCEPTABLE.

Thanks for referring to the getbootstrap site. I do development in my free time and not employed by Limetech. Moving to a new concept even without reinventing the wheel will cost me considerable time. I am interested in this as a step forwards, but don't expect anything in short notice. I understand. Well, keep up the good work!

I like the unRAID interface but all the suggestions and "complaints" I'm reading could be better handled if unRAID adopted a responsive design and some forethought, which would really be about time considered we are in 2015. No need to reinvent the wheel. Why not take up bootstrap (http://getbootstrap.com) as foundation and start working from there? That is a question I've been asking myself for quite some time now.