Squeeth

So I'm working on creating a way to synchronize my Launchbox config to all my computers on my network and saw that Syncthing was a good way to allow clients to update changes made to a specified folder. However (I feel so dumb for asking) I can't log into the WebUI, it asks for a username and password and I can't figure out what the default is. Any assistance is greatly appreciated 🙂

Thanks to the suggestion made by @JorgeB to rename the folders on the disks, it now works! I used Krusader to browse and rename on the disks, and afterwards confirmed that once adding in the "&" character, the share went back to "deleted" again. Interesting! Thanks again for the help!

Thanks for the response! I'll give the rename a go, hopefully it plays out well after renaming the share on disks 1-14 😅

Thanks for the reply JorgeB! I wonder if it's something to do with the most recent versions of Unraid? I never had it showing the deleted status previously; however while I can't pin point the time it started saying deleted, I do know it happened at some point after updating to rc4 (maybe even 6.10) If that character could possibly be the cause of the issues, what would the process be to rename it without that character and still maintain functionality of the share without interrupting any of the mappings I have set on devices? Or would I just need to remap devices as needed after creating a new share and moving all the data? Thanks in advance for the all help and input!

Thanks for the response trurl! The share .cfg file is named "Launchbox ROMS & ISO's.cfg", and matches the same (I can assume) in the Shares tab by showing "Launchbox... ISO's". The confusion continues with the fact that when I click the link for that share in the Shares tab, it shows the screenshot in my original post with the name "Launchbox ROMS". If I go to any computer in my home network and type in my Unraid systems IP address, it does show the full share name "Launchbox ROMS & ISO's" (matching the shares .cfg) with all the folders and files present inside of the share.

Friendly bump in hopes to get help resolving. I took a look on my Unraid flash drive to verify the share still exists, and sure enough it still does. I cross checked the .cfg file of this share with my other shares in /boot/config/shares and sure enough everything is the same. Quite boggled by this one.

Hey all, had a weird issue occur at some point recently (I can't pin-point the day) where I got this weird message when trying to view a share. Not quite sure how or why this happened, and it's the only share that I have with this message. I can't seem to find much information regarding this error on the forums, or a solution for that matter. It's still accessible on my computers as a mapped drive, which has me very confused as to what this error is and what it means. I did try to restart the system a few times, but no luck getting rid of that message. Thanks in advance for any help, and let me know what other information might be needed. ethan-unraid-diagnostics-20220429-0821.zip

Thanks for the info clearing that up, I had a bad feeling that would have some issues with it but I did also try to accept the possible loses. Overnight only a few more errors occurred while rebuilding one of the disabled disks, so before I left work this morning I swapped out the disk with errors and started a rebuild on that and will monitor it throughout the day. Once I get home if everything is completed properly then I'll swap the other disabled disk as well. Hoping nothing crazy has gotten lost throughout this, I've been trying to limp along with 2nd hand refurb drives until I can afford new replacements.

Hey all, looking to get a bit of guidance/reassurance with this process. I'm about to swap out a couple disabled disks in my server and then replace a few smaller drives as well. I just want to be sure that I won't be losing any data during this as I had a drive failure and auto parity rebuild cost some data loss when I wasn't paying close attention. As far as I know (and I could be wrong) it should be as simple as stopping the array, shutting everything down, replacing one disk, turning back on, assigning drive, and letting the rebuild take place? Or do I have to do a parity sync/backup first and then replace and rebuild? I'm just making sure I'm thinking straight. I have my diags attached as well if needed. I have a few other things to figure out as well like why my 16-bay hot swap enclosure has issues actually hot swapping with my my raid controller and Unraid...but I digress. Thanks in advance everyone! ethan-unraid-diagnostics-20220327-1352.zip

Moving to solved. Couldn't dump my cards VBios on my own, tried the old school and the SIO script...no joy. Did add the video=efifb:off to the append line in syslinux, and switched my boards BIOS to boot Legacy. 980 TI successfully started working in passthrough after that.

Thanks Ghost! Yes it is the Streaming VM and I'm excited to give it another shot. How you see everything is how I left it after my 6th or 7th attempt, hence why multifunction was off and my own vbios wasn't dumped. Adding that into my syslinux config was something I didn't do, so hopefully that was the missing piece of the puzzle!

I've been trying to configure a Windows 10 VM for the last two days to utilize my 980 TI, but I can not for the life of me get it to passthrough to the VM properly. I've followed every video SpaceInvader One has out there about GPU passthrough, followed multiple suggestions on here about starting with VNC and trying to install drivers, letting that fail, shutdown, add GPU, and finish driver install, SeaBios and OVMF, Q35 and i440fx...but all to no successful outcomes. I've done the XML edit for multifunction, stubbing the card, using a no VBIOS dump, untouched dump, modded dump per SIOs tutorials...I'm just at a loss here now. Wondering if anyone has a helping hand to try and help resolve this, or a current config similar with their setup that can point me in the right direction. Thanks in advance! ethan-unraid-diagnostics-20220116-2245.zip

I keep receiving messages from my log saying that it is having a write error due to file being too large? This just recently started happening and can not figure out what changes I have made that could have caused these to appear. I've browsed through the diags myself, however I'll admit that there is far smarter and more knowledgeable minds out there that will probably be able to tell what's going on. Jan 16 21:17:29 ETHAN-UNRAID rsyslogd: file '/boot/logs/syslog'[6] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: File too large [v8.2002.0 try https://www.rsyslog.com/e/2027 ] Jan 16 21:17:29 ETHAN-UNRAID rsyslogd: action 'action-1-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2002.0 try https://www.rsyslog.com/e/2027 ] ethan-unraid-diagnostics-20220116-2245.zip

Thanks for the input, I greatly appreciate it! I'm hoping that with the chassis they would be going in not having any additional hardware besides the PSU's and an HBA with five pretty decent 80mm fans, that it won't be too big of difference and possibly cause any issues. I think the skeptical part of me just sees "used" and combines it with the seemingly sparse amount of peoples experience with those specific drives and thinks, "Okay...the price is good, but it's probably because I'll have issues." 😅

Thanks for your response! If you know and don't mind sharing, what temp was it at compared to the other drives and what kind of cooling/chassis were they in? I'd be installing mine into a Chenbro RM41416 that has 5x80mm fans behind the drives and my existing drives sit around 32-35c. I'm just trying to gauge the temp difference and if I should maybe also consider ordering new and better fans along with the drives.