glave

Is this working on 6.1 RC5? I installed the plugin while on unraid 6.01, I hit install in settings but noticed my tv card wasn't detected. I installed the 6.1 RC5 mediabuild kernels, and after rebooting the card is now detected, but the install button does not work and the plugin says it isn't installed. EDIT: I noticed that when I press the install button, at the bottom of the webpage I very briefly see this message before the webpage refreshes: sh: /usr/local/emhttp/etc/rc.d/rc.tvheadend: No such file or directory

Correct. When you click in the path box while creating a container, you get this:

Could I suggest the ability to browse for eligible to move folders, in the same fashion that you can browse paths when creating a new docker and choosing mount paths?

I've been slowly converting my drives this past week, going by the wiki: I've completed about 9 drive conversions, with 8 being left. I haven't gotten around to the last bit of changing drive include/excludes or doing new config. What happened was, I converted drive13 a few days back, having copied all of its contents to drive2, I changed it's format to xfs and then copied drive6 on it, etc, etc. That was a few days ago... Today drive 13 threw 4 errors and red balled out while I was rsync'ing from drive5 to drive3. Honestly, the last step in the process has confused me. Is my parity currently valid? I don't have exclusive drives, they are all available to all shares. If my parity is NOT valid, then how can I recover my now dead drive13?

I built my unraid exactly as the parts list went on the 20 drive beast,which gave me 4 gigs of ram (2x2gb). I'm looking now to increase that so I can start using VMs and docker more effciently, but finding the same ram or the sticks to max out the motherboard is proving to be a bit challenging. Has anyone else done this build and went with different ram other than the Kingston that was listed? I'm fine moving to a different brand, I'm just looking to max out the 16gb of udimm or maybe even the 32gb of rdimm. What few options I've seen have been kinda pricey, and made me question the possibility of getting a newer motherboard and upgrading it's memory instead. Thoughts?

Really? I tried it last night and it came up as 12.0. Is there a special variable to pass for it to go to 14.1? EDIT: Actually I just discovered I could tell it to check for an update and then do the update. I'm too used to docker apps not being able to do that.....

Does anyone have nzbget running 14.1 or higher? I was running needo's on 14.0 with no problem until I've hit a bug with nzbget getting stuck during a checking phase. Looks like it was fixed in 14.1, but I haven't had success getting 14.1 to run, and the EDGE svn needo's used only goes up to 14.0.

Over a few years I've installed several plugins and extensions as they developed along with unraid. Now my drive has leftover bits and pieces of uncleanly installed old plugins, and I'd like to start it over fresh. A pseudo 'format' of the flash drive I guess you'd say. How can I best erase my drive, drop my drive settings, config, usernames, pro key, etc back in place resulting in a pure 'stock' setup again?

With about 6 different containers using pretty much the same volume mappings, I was wondering about making a volume only container to keep setup a bit more simple. Has anyone else gave this a shot yet?

If I'm doing this in a less than optimal way, please offer better suggestions! My containers in unraid 6 are all using volumes which are nfs mounts back to my first unraid server. I'm trying to figure out how I can get the mounts to persist after a reboot of the unraid 6 server, and/or avoiding stale handles. I added a fstab into the config on the flash drive, and I edited the go script to copy the fstab over, but they still are not mounting when I reboot (nor does the fstab reflect that it is my modified one). Any suggestions?

I've been looking over the release notes, searching posts, and scratching my head for an hour. Is this missing now? Is there something I have to turn on?

I'd like to chime in. I just came to the forum looking for problems with this exact same issue. For years things have been fine, and now suddenly I'm seeing a lot of corrupt video files when they are copied over to unraid. Files are fine before being copied. Not much more info to report atm, but thought I'd just let it be known that you are not alone in this one.

Twice in the last month I've experienced a random reboot of my server. When I've went to check the logs, I've noticed that the log is reset on reboot. Is that normal behavior? Is there a way to preserve the log between reboots?

I'm looking for said link on the right, but I see nothing...?

Doing Utils->New Config will reset ALL drives to new though. Even from that page is a warning: "DO NOT USE THIS UTILITY THINKING IT WILL REBUILD A FAILED DRIVE - it will have the opposite effect of making it impossible to rebuild an existing failed drive - you have been warned!"

No, I don't have that option. Start will bring the array on-line and start Parity-Sync. That's all I have.

I've seen posts where I can use the trust array procedure, but I do not want to do a parity check. I need to trust it, start the array, and rebuild my 1 drive that failed. After the fact, I don't mind if I completely blow away parity and start it from scratch. I'm just hoping to get that one disk rebuilt first.

I had a scare last night as my parity drive just disappeared out from under me (http://lime-technology.com/forum/index.php?topic=25186.0). I powered the machine down, and slept on it. This morning I powered up and everything *seems* ok, but its re-enabled my parity disk, but has it marked as new and is going to do a parity sync. I'd like to tell it to trust the parity, and then try doing a data rebuild on the disk that still needs it. Currently my parity is marked with a blue ball, and the disk I replaced yesterday is still orange.

Things were going just fine during the data rebuild, but I just checked the web interface to see the parity drive is now disabled. Is there any hope? Anywhere unraid keeps a log of files on each drive? Perhaps I can at least see what I've lost on the drive that was being rebuilt. Log: http://pastebin.com/8CMY2WGn

Well, I got home and the monitor wouldn't come on at all. I listened closely, but from what I could tell, even though the activity light was light, there was no hdd activity at all on the new drive. I crossed my fingers and held my breath, and hit reset. She came back up just fine, as though I had just added the new drive back. I told her to do a data rebuild again, and so far so good. I did check the syslog, but it was completely empty of anything except the current booting up. Not sure what happened, but hopefully it was a fluke.

I've always been able to reconnect in the past as well. I can physically check it when I get home, but didn't have time this morning. I've had it take up to 24 hours in the past to do a full rebuild though.

Just tried a little further, doesn't respond to pings at all.

I had a drive die last week, I replaced it Monday, and the preclear finished last night. Last night I put it in the raid, clicked data rebuild, and went to bed. This morning I've been trying to get into the web interface, or telnet, but neither will respond. I did notice on my way out of the house this morning that from physically looking at the server, all the drives are spun up, and the new drive's activity light is blazing.... Should I be concerned yet?

Based on 2, and share's name is Movies, and its structure is HD/Aliens(1978)/files....then HD should be able to split across disks, but any folder created under it would be locked into that drive, correct?

Any more information I can provide? This is still plaguing me. I've also checked all of my other shares that are on disk2, and they do have minimum space requirements, and using cache as well.