BLKMGK

Members
  • Posts

    978
  • Joined

  • Last visited

Everything posted by BLKMGK

  1. RC3 hasn't been installed here yet but I'll try to do so today and report back. My password is under 25 chars in length. Edit: RC3 has the same behavior as RC1 with the added "benefit" that I can no longer go back to a working version of unRAID via the GUI. I've been able to edit the Go file from /boot/config to add my link file back to work around this for now. A parity check was triggered as well. Manual use of the emcmd against my drive resulted in a hang same as the other user, no output provided at the console from this command. minion-diagnostics-20191020-1613.zip
  2. @dlandon any thoughts on the diagnostic I posted the other day? Very curious as to what's going on
  3. I'm hoping Limetech will put the overlay module into their baseline kernel. If they can get to 5.4x we should see X570 chipset support too I believe.
  4. I have updated UD and will attempt to test tonight. Just so I'm clear, you want me to remove the link fix I've got now, allow it to fail, grab the diagnostic, and pop it up here? I will have to drop back to the old 6.7 RC that's weirdly onboard and then upgrade again to recover so I'm hoping these are the needed steps heh. Server is a touch busy right now but I'll try to do it ASAP so if there's something special you need and you're online drop it here and I'll hopefully spot it before doing this. P.S. Tom, could you guys please compile in the Overlay module for Docker going forward? I think it's the only thing preventing me from using Swarm with my server minion-diagnostics-20191016-0001.zip
  5. I posted it there as it appeared to be a bug in 6.8, I had missed the change in the release notes and it was pointed out. At that point I had assumed it was the plug-in not having been updated and thus asked here. I will follow this there if you would prefer but I wasn't attempting to seek solution in multiple places at once.
  6. Hopefully this has what you need! I'm currently running a link file in my Go so I'd have to break it to recreate but this isn't a long term fix obv. If you need me to do anything say the word and I'll work it as quick as I can to help out if there's an issue. minion-diagnostics-20191014-0132.zip
  7. Ah true, I use PFsense and DLink switches that are managed so that mihgt be possible if it doesn't need multiple NIC. Unfortunately it's not something I've ever messed with and I'm pretty ignorant about it. I'll wait and see how others fare and hopefully there's a solution that doesn't require this too. I should read up on this regardless, I've got some IP cameras I ought to better segment anyway. Thanks for the response!
  8. Seeing this too, it's amazing how fast my log is filling up! Looks like I may need an hourly cron job for this. Noting that as activity on the interface increases so does the speed with which the messages occur. Downloading a file via a container has got my log rolling so fast I can hardly follow it. Cron job to run hourly has been created! Edit: sadly this new board has only one NIC so I'd like to be able to share it.
  9. Thank you @Squid that looks to be exactly what's going on. I run both VM and multiple containers. I'll keep an eye on the log size! Happy to not be alone
  10. Allow me to actually answer the question. Converting from entering a passphrase to a keyfile is something I *just* had to do. The links above will tell you how to setup crypto just fine or even change passwords but you'll have to dig pretty good to find a way to easily go from passphrase to a file so I'll try to save you some trouble. In the end you need to have a file in the root of your ephemeral boot drive named keyfile that contains your passphrase. In my case I did this by creating a file on my USB stick and a line in my GO file to create a link to it as detailed below. Note that this is NOT SECURE if someone snatches your server. For me this is a temporary thing until I can go back to entering it by hand down the road. Others have come up with schemes to transfer the file in question via SFTP from other servers and it's also possible to use binary files like say a picture vs a text file - what I've detailed isn't that but you get the idea.
  11. Ah ha, I linked to root a keyfile stored on my USB (shiver) in the Go file and it's booted! I'm getting some ugliness in the logs though as it seems something is crashing. From the UI all appears normal for now and I'll let it roll. Appreciate the assist! Here's a link to a snippet of what I see in my logs currently and it began right after a container fired up (it's running fine). https://pastebin.com/HtKwsfx4
  12. Aw crap, I missed that! Well okay, that seems to have solved the mystery and explains the change in behaviour. Working as designed and anticipated it seems - d'oh! I suppose for now I can either save to a file or decrypt the drive, not sure which is yuckier lol
  13. 6.8.0 rc3 may have changed functionality that could be impacting Unassigned Drives. Specifically I have a drive outside of the array I mount using Unassigned Drives that is encrypted that fails to mount either manually or via AutoMount when I upgrade to 6.8.0 rc1. I can SSH into the array and display contents of all drives except the single Unassigned Drive I use for containers and VMs. Here's a link to the post in the prerelease area. Not clear yet where the issue lies but this worked fine in at least two previous releases and it seems behavior changed with the new 6.8 v1 release candidate. Edit: D'oh! There's a statement in the release notes that mentions they no longer save the decryption key to a file and that an API has been provided to allow Unassigned Drives to continue to function. Seems this is intentional, intended, and my use case was anticipated! Pretty please may I volunteer to test should that be needed assuming Unassigned Drives is updated?
  14. I use a passphrase that's entered at each boot, I am entering the passphrase in order to start the array. I am able to SSH in and see the contents of my protected drives without issue but SMB sharing is apparently not starting and I cannot see those shares from the network. I cannot see the unassigned drive as it never seems to mount. Under 6.7.2 and 6.7.3 rc4 this works. Now that it's not 1am pushing 4:30 am some clarity lol. My array consists or multiple drives that are all encrypted. My cache drive is also encrypted, my single drive outside of the array used for VM and container storage is also encrypted. When my system boots it requests a passcode before proceeding to mount drives and the Start button won't light without an entry. In the failure case I type in the password, the button lights, I hit start, and the interface eventually refreshes to show my drives up (no more dropdowns) but my Unassigned Drive outside of the array is failing to automount. As this is where VM and Container files are held this is "bad". When this occurs it appears that the normal sharing also fails and the rest of the array doesn't start. For those wondering - this encrypted drive outside of the array was created by temporarily making it my cache drive, formatting and encrypting it, and then returning my original encrypted cache drive to use. I then mount this drive like any other at boot with automount using Unassigned Drives. My entire array is encrypted as a result and has been since the feature was introduced (I lobbied for it for years). The drive outside the array was only recently encrypted, my thanks to u/Spaceinvaderone for the how-to on that trick just as I was upgrading cache and Container drives I could reverse this and decrypt that outside drive but it stores data I'd prefer to remain encrypted and it's worked well through multiple versions prior to this. Questions? Fire away, I'd love to solve this! This might be Unassigned Drives that needs a tweak, I'll hunt down the support thread for that as well, but something has most certainly changed somewhere in this "release candidate". So just to be clear I knew there was a risk here, am NOT upset, and simply want to help get to the bottom of this as there's a TON of fixes in this I'd love to obtain Much thanks to the NVIDIA guys for compiling against it too!
  15. By chance did you happen to find swarm modules enabled in this build already? I seem to recall you had managed to get that working previously. I have still not been able to test it on my test-bed but hope to soon with a friend's help. Would be lovely to have that functionality out of the box with a factory build!
  16. Crossposting from Reddit\6.8.0 RC1 thread - upgrade failed for me Some additional info: I have all disks encrypted including the disk with my containers on it using Unassigned drives. This is X570 hardware, 3700X. 6.7.2 (NVIDIA) ran fine for me other than issues we had all seen. When I boot the RC I see it seem to hang as mounting drives but I can SSH in and see everything except my flash and my unassigned SSD. There are two other SSD I don't automount but I don't think they're causing issues and could pull for troubleshooting if requested. Working my way back to 6.7.2 right now but from the looks of it I can test versions freely without trashing things and am willing to do so. If you need more info holler as I'd love to help, not sure what logs are best or safe to post! Edit: am on 6.73 RC4 running fine (so far) now. Let me know how I can help! ======== Just a heads up - this is NOT going well for my system so far. System is a TaiChi 3700X build. Docker isn't starting for some reason - NVIDIA build. I use encrypted disks but those seem to have mounted fine. Still troubleshooting and the logs look fine but no shares are showing despite mount showing a list and my being able to go into the shares via SSH. No containers are starting, VMs are down too. Screen says "mounting disks" and there it hangs. Am about to grab the standard version of this release and see if it does any better - bummer for me and I'll update as I learn more. u/sittingmongoose cross your fingers lol. Tempted to try a straight reboot first but I'll do the standard build and then try for NVIDIA. Hope I don't end up doing a parity! Edit: Doing a straight reboot first from the UI. Looks like it had to force shutdown - grr! coming up it says dirty and won't give the start button as it's waiting on Mounting disks Looks like I'll drop to the standard RC1 and if that fails back to 6.7.2 NVIDIA. Noticed it's not automounting my XFS encrypted drive for containers. Tried the Mount button and it's hanging. This disk isn't showing as mounted from SSH but the others are. Maybe this is the issue? Edit2: fun fact, cannot download another unRAID version to my USB while things won't mount. I may have to pull this from the rack. I'll try SFTP and hope I have a handy backup around SFTP gets me in at least but my share for Flash isn't showing dammit. Edit3: Normal unRAID upgrade tool had a backup version of 6.7.0 RC6 in it, guess it's been awhile since I used that Managed to boot it! For science sake I'll try the normal unRAID 6.8 RC1 and see if it works better using that tool. If not I at least have a working go-back and we'll know if this was NVIDIA or not. Edit4: nope same issue with normal 6.8 RC1 for me. It looks like my use of encrypted disks could be an issue? Possibly because I have an encrypted secondary disk using Unassigned devices - it's not clear to me but it looks like I can get back to 6.7.0 RC6. I will then use normal tool to get to 5.7.2 and then NVIDIA 6.7.2. Bummer, I really wanted this to work This is what I see when I try to manually mount my Lux encrypted container disk: Oct 14 01:28:59 Minion unassigned.devices: Adding disk '/dev/mapper/docker_vm'... Oct 14 01:28:59 Minion unassigned.devices: luksOpen: key file not found - using emcmd to mount. minion-diagnostics-20191014-0132.zip
  17. To be fair - I've hardly ever had to report bugs but I will happily do so and provide the diag log!
  18. Crossposting from Reddit - upgrade failed for me Some additional info: I have all disks encrypted including the disk with my containers on it using Unassigned drives. This is X570 hardware, 3700X. 6.7.2 (NVIDIA) ran fine for me other than issues we had all seen. When I boot the RC I see it seem to hang as mounting drives but I can SSH in and see everything except my flash and my unassigned SSD. There are two other SSD I don't automount but I don't think they're causing issues and could pull for troubleshooting if requested. Working my way back to 6.7.2 right now but from the looks of it I can test versions freely without trashing things and am willing to do so. If you need more info holler as I'd love to help, not sure what logs are best or safe to post! Edit: am on 6.73 RC4 running fine (so far) now. Let me know how I can help! ======== Just a heads up - this is NOT going well for my system so far. System is a TaiChi 3700X build. Docker isn't starting for some reason - NVIDIA build. I use encrypted disks but those seem to have mounted fine. Still troubleshooting and the logs look fine but no shares are showing despite mount showing a list and my being able to go into the shares via SSH. No containers are starting, VMs are down too. Screen says "mounting disks" and there it hangs. Am about to grab the standard version of this release and see if it does any better - bummer for me and I'll update as I learn more. u/sittingmongoose cross your fingers lol. Tempted to try a straight reboot first but I'll do the standard build and then try for NVIDIA. Hope I don't end up doing a parity! Edit: Doing a straight reboot first from the UI. Looks like it had to force shutdown - grr! coming up it says dirty and won't give the start button as it's waiting on Mounting disks Looks like I'll drop to the standard RC1 and if that fails back to 6.7.2 NVIDIA. Noticed it's not automounting my XFS encrypted drive for containers. Tried the Mount button and it's hanging. This disk isn't showing as mounted from SSH but the others are. Maybe this is the issue? Edit2: fun fact, cannot download another unRAID version to my USB while things won't mount. I may have to pull this from the rack. I'll try SFTP and hope I have a handy backup around SFTP gets me in at least but my share for Flash isn't showing dammit. Edit3: Normal unRAID upgrade tool had a backup version of 6.7.0 RC6 in it, guess it's been awhile since I used that Managed to boot it! For science sake I'll try the normal unRAID 6.8 RC1 and see if it works better using that tool. If not I at least have a working go-back and we'll know if this was NVIDIA or not. Edit4: nope same issue with normal 6.8 RC1 for me. It looks like my use of encrypted disks could be an issue? Possibly because I have an encrypted secondary disk using Unassigned devices - it's not clear to me but it looks like I can get back to 6.7.0 RC6. I will then use normal tool to get to 5.7.2 and then NVIDIA 6.7.2. Bummer, I really wanted this to work This is what I see when I try to manually mount my Lux encrypted container disk: Oct 14 01:28:59 Minion unassigned.devices: Adding disk '/dev/mapper/docker_vm'... Oct 14 01:28:59 Minion unassigned.devices: luksOpen: key file not found - using emcmd to mount.
  19. Heading over to post a bug, release was a no-go for me. So close and looking forward to the new kernel; and hardware support Edit: Not a bug, a feature! Unassigned Drives needs an update to continue to work with encrypted drives is all. A security update has changed the way you decrypt drives outside the array. Worked around it for now with a link file in my Go but it's not a long-term fix.
  20. Thanks, that's perfect I now have it up and running. Will test out swarm soon! If I can cluster with other machines in my home that will rock.
  21. Attempting to give your kernel a whirl! I attempted to compile my own for testing but ran into issues that I'm still trying to solve where GCC appears broken using your script. However when I use your kernel I get an error about an "incompatible md version". Which version of unRAID was your kernel built for? 6.7 hasn't worked for me and I'd really like to get this working! I now have an AMD processor in my server and swarm would be awesome with a project I'm working. If we can prove this out perhaps we can get Limetech onboard with the proper modules and it could trickle down to the NVIDIA guys Thanks!
  22. Okay, much to my surprise I'm able to access SATA drives via the U2 port, thank goodness! I am using a U2 cable to my SAS backplane on a Norco 24. I had to turn on the SATA vs U2 functionality in the BIOS with the new flash. Here's what I bought -> CableCreation Internal Mini SAS HD Cable, 1.6FT Mini SAS SFF-8643 to Mini SAS 36Pin SFF-8087 Cable, Mini SAS 36Pin to SFF-8643 Cable, 0.5M No go on the IPMI but I'll admit I've not tried to dork with it, I'm not sure where to begin with the damn thing. It does look like I'm using the Realtek NIC and so far it's been fine and found by Linux. With this U2 addition I might actually use this WKS board in my unRAID machine and a TaiChi in something else - anyone using the TaiChi? Thinking a 3700X, 32gig of memory, and a 4port SAS paired with a 2port to have enough slots and still run my 1050 for Plex
  23. I have the WKS board too albeit not in an unRAID system currently. I can confirm that it's U2 port doesn't work as a SAS with a breakout - despite being told so when I bought it. I'll be flashing mine in a moment and I'll try to test it with the breakout I've got buit I dooubt that a simple flash is going to bring functionality. This board was advertised as having "lights out" management and this special port, thus far both have proven to be useless. Knowing what I know now I wouldn't have bought it. My unRAID system is likely to get a TaiChi X570 instead - possibly this week. Wish I could find some 3900X processors
  24. @aterfax NVIDIA aside, were you able to get SWARM working?