johnodon

Let's here the arguments. I want to get an undated console for my boys (currently XBOX360). All they do is play games and really all they care about at the moment is playing Star Wars Battlefront. I understand that there are hardcore XBOX and PS4 fans, but let's try and leave "brand loyalty" out of this. FWIW...since we already have an XBOX360, the games we already have will play on the XBOX One. However, I have never owned a Sony product so I am kinda leaning toward the PS4 just for that reason. John

Did you even try passing through without using a BIOS? What are your symptoms? Do you get no video? Does it throw an exception? FYI...the site you posted is listed in the KVM section of the unraid Wiki: http://lime-technology.com/wiki/index.php/UnRAID_Manual_6#Assigning_Graphics_Devices_to_Virtual_Machines_.28GPU_Pass_Through.29

Don't know why I didn't ask before... What version of unraid? Assume you are using the Unassingned Devices plugin? Since this behavior seems to be limited to that shares via that plugin, you may get better support in that thread. John

Obviously, we have numerous choices now for syncing Kodi libraries and watch status (plexconnect, embyconnect, mysql). While I like the idea of using Plex or Emby for my Kodi library needs, the thing that has always bothered me is the fact that it is not instantaneous (like mysql). It writes the data locally and then syncs it. Correct? If so, I just see this process barfing too often. My other niggle is that I like to keep my Kodi (OpenELEC) instances as stock as possible. Having to install addons to perform a function that I can do via a couple of lines in advancedsettings.xml bothers me...more things that could break. Then again, mysql isn't exactly and Out-Of-the-Box, simple solution. And, upgrading presents its own challenges. Is my concern justified at all? Please be objective. I'm not looking for perspective that is completely tainted with brand loyalty. John

Everything I see om Google about that error talks about Linux exFAT partitions. Is that the case here? Here is one example... http://blog.marcelotmelo.com/linux/ubuntu/rsync-to-an-exfat-partition/

I have both, but rely on workgroup more. Thanks. I'll try. Just to be more clear... \\sun.workgroup if your workgroup name is actually workgroup.

Workgroup or domain? I do not have an explanation but I saw the same thing on my both of my WIN10 machines. What fixed it for me was to specify unraid.workgroup rather than just unraid. It let me right in and I only had to do it once. After that I could browse to just unraid without issue. John

I'm running this on one of my drives right now that had XFS corruption...16 hours to go but things look promising. I was at risk of losing 60+ lossless bdrips. Not a big deal as I can always get them back (eventually) but this sure would be a much shorter path. The BIGGER issue is the pics of my boys that I most certainly do not want to lose. Not sure if you are still around Tevian but how did you make out? John

TY. I think I am just going to start with a clean slate. John

Finally decided to bite the bullet and move to v6.2 and I am following the guide from the first beta announcement that explains the migration process. Since I knew that Docker and KVM would need some extra attention, I disabled both prior to shutting down the server. I formatted my flash drive since I had some corruption, installed 6.2rc3 on it, and restored the following: /config/disk,cfg /config/docker.cfg /config/domain.cfg /config/network.cfg /config/ident.cfg /config/Pro.key /config/super.dat /config/shares/* Booted unRAID without issue and I can access my shares. I continued to tweak a few settings and follow the guide when I ran into my first issue... This did not happen for me. The 'system' share was not created even though I have a cache drive. What should be my course of action? Do I need to manually create the 'system' share? Diagnostics are attached. John unraid-diagnostics-20160731-0937.zip

I think I have some corruption on my flash disk. I have 10 or so FSCK000x.REC files in the root. Also, all of the .key and .pub files in /boot/config/ssh are 0 bytes which I assume can't be right. I'll pull the flash drive, repair it and rebuild it. Probably a good time to move to 6.2 RC3 John

v6.1.9 Entire server is tunneling outside via VPN but this has never caused an issue in the past. All of a sudden I am not able to access my server via SSH (putty) from either of my WIN10 machines. I tried both name and IP and get the same error: Network error: Connection refused. Telnet works fine. Firewall on both WIN10 machines is turned off. I don't see any errors being thrown in the syslog. I have attached my diagnostics. The only change that I see on the unraid side is an update to the webui: Dynamix webGui v2016.07.27 Thoughts? John unraid-diagnostics-20160731-0821.zip

So, after browsing to \\unraid\workgroup and then rebooting, I am now able to browse to just \\unraid. Weird. I know I had rebooted numerous times since experiencing this issue and that never fixed. It was some combination of browsing the FQDN and rebooting that did it.

One more piece of info... if I browse to \\unraid.workgroup, I am able to access without issue. John

I can't say for sure that this is the root cause, but this all started when I temp upgraded to v6.2rc2 and downgraded back to 6.1.9. All of a sudden if I try to browse my shares via server name (\\unraid) in File Explorer, I am prompted for credentials. If I do the same with IP I am taken right in. However, I am able to open the webui via name without issue. Samba issue? Where can I begin to look? John

I decided to tuck my tail and just remove the problematic drive and create a new config. Running parity sync now. I think all that was at rick was tv shows and movies.

While I am waiting for this xfs_repair to complete, let me ask this... Is an easy way to get the contents of my shares back to exclude disk5 from each? Will that do the trick? John

I upgraded to v6.2 rc2 in hopes that the new version of xfs_repair will help me (v4.3 vs. v3.2.2 on 6.19). It's running now but I don't have high hopes.

xfs_repair version 4.3.0 TY richard. I guess I'll update to see if this version can correct the XFS corruption issue I am dealing with as the version on 6.1.9 (v3.2.2) isn't getting it done. John

Can someone who is running this RC tell me what version of xfs_repair is included? xfs_repair -V TIA! John

XFS repair finished and came back with this... ..Sorry, could not find valid secondary superblock Exiting now. According to the help I can run it with a -L switch as a last resort. Will that even help in this case? Or is my only option to format the drive as RFS and back to XFS? John

EDIT: I'll grab a syslog after the check is completed and I start the array again. I totally forgot to get it before I jumped. I was seeing a LOT of messages in my syslog telling me that XFS on disk5 had corruption. So, I stopped the array and restarted it in maintenance mode. I then clicked on disk5 and told it to run an xfs_repair -n which it is doing now. I'll let the check run until it is finished but the first thing that popped up was this message: Phase 1 - find and verify superblock... couldn't verify primary superblock - not enough secondary superblocks with matching geometry !!! attempting to find secondary superblock... Does this indicate that I am heading for dark times? FYI...one of the symptoms I am seeing is missing media (i.e. TV show episodes) and some of my shares show as empty even though I can see files/folders in them when I look at individual disks. Advice??? TIA! John John

How did you install it ? Same way I did in the OP. I am on unraid 6.2 rc2 i cant do what you did Unraid force me with only libreelec version 7.0 Don't use the template provided by LT. Create your own custom VM and following the instructions.

How did you install it ? Same way I did in the OP.

Thanks ue. However, when I change to the new cert and change my OVPN client to AES-128-CBC, port 1198, SHA1, I see this in the logs: Jul 13 06:29:34 openvpn 18216 WARNING: 'cipher' is used inconsistently, local='cipher AES-128-CBC', remote='cipher BF-CBC' Why is the remote side expecting BF? That being said, it does appear to be up and running and my unRAID box (which is using the tunnel) is able to update containers... Jul 13 06:29:37 openvpn 18216 Initialization Sequence Completed John