Squeeth

Thanks for the response @JorgeB ! I know 15 and 20 were some rando disks I pulled from a pile I had and may be on their way out overall, good call on memtest too...I hadn't thought about that one. I'll get going on checking the filesystem on those disks and report back. Thanks again for taking time to help :)

Hey everyone, I hope I'm just being over-cautious by posting here seeking advice. I had a similar issue a couple years back that I vaguely remember fixing, but I can't remember the steps I researched for the life of me, so I wanted to reach out to the community for guidance before proceeding just to get more clarity. My system had a sudden power loss a few days ago while I was out of state (go figure), and when I got home I noticed that I have two disks that are emulated and showing "Unmountable: wrong or no file system" in the array page. If I remember correctly, it should be checking and repairing the filesystem with the -L flag and the proceeding with a rebuild? To rebuild I believe it's stop array, unassign emulated disks, start without assigning, stop array, reassign, start array, let it rebuild? Sorry in advance for asking what I feel like is a silly question, I just get a little nervous when these things happen. I was shocked when I got home and went to do some work and noticed one of my shares being completely empty, so I'm just trying to proceed cautiously with guidance of minds smarter than mine. Thank you in advance for any help and taking the time to look at my diags to help me make sense of it all. EDIT: I forgot to mention that when I looked at my diags, I did notice disk 18 is shot. ethan-unraid-diagnostics-20251208-2030.zip

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.

I've seen some talk about with people who use HGST drives, but haven't seen much in the way of saying "Yeah, these are great and fantastic" or "They work, but I'd recommend something else". Anyone have any words of wisdom to share, personal experiences, etc.? Reason I ask is because I found some 10TB HGST Ultrastar SAS drives (HUH721010AL4200) I'm thinking about getting to replace my mixed 1,2,3TB WD, Seagate, Toshiba array in my 16 bay JBOD. They are used but have overwhelmingly positive reviews and purchases on eBay, with a 30 day warranty and testing 100%...and at $129 it seems like a steal that may be too good to be true. Should I steer clear, or pull the trigger?

Just curious as to if anyone else has been having issues with using Macinabox downloading High Sierra, as I have not had it working for me. I haven't seen much about High Sierra in this thread in quite some time, and it's understandable given being an out of date, unsupported, loss of security version of MacOS. I clear all images, templates, and remove from appdata before trying to restart the process. I've tried Method 1 and Method 2. Method 1 usually results in almost instantaneous ready notification, and boots without any issue to recovery menu...except only allows installing Monterey which I've seen is a result in previous posts on this topic. I've also seen that using Method 2 provides positive results for downloading the High Sierra image, however as I know it can take a long time (seen SpaceInvader One say his 490mbps speeds took over an hour), I have let it sit for almost 3 hours now with 500mbps and the file size in Krusader hasn't moved from 2GB. Reason I'm trying to get High Sierra over any newer versions is that I have a spare GT 1030 in my Unraid box that I'm trying to passthrough for the hardware acceleration. Strictly used for fiddling with MacOS and not be a daily driver, and to obviously learn about setting it up. I did successfully get Monterey setup and everything working as intended in the OS environment which was a long experience but rewarding at the end of the day, and now I'm itching for a new project to work on. Thanks in advance for anyone who might be able to point me in the right direction. Edit: I'm going to go on a hunch here and say it has to do with Apple servers? Edit2: Resolved after watching SIO's old tutorial covering installation of High Sierra and Mojave and not using the MIAB container

Update Server has been stable for 30 hours with the following changes made: XMP : Enabled C-State : Enabled Enable Intel Turbo/AMD Performance Boost? : Yes CPU Scaling Governor : Power Save Have since been able to install and configure a Windows 98, 2000, 7, and Server 2019 Standard VM. Also configured WDS in Server 2019 to have PXE boot on my network for Macrium Reflect recovery and Windows 7, 10, and 11 installation. Was able to confirm working by booting a new blank VM to PXE and was able to boot to Macrium and Windows Install on the WDS and install Windows from the Server VM to the new VM after injecting the VirtIO drivers to the appropriate wims. I'd like to think all is stable now! From here I know if it becomes unstable then I'll disable XMP first and then go from there....but I do believe for some strange reason the front panel connections I re-did were the culprits... Anyways, thanks again for all the help everyone! I do believe we can call this thread closed!

Just wanted to provide an update. Since the previous post changes have been made via BIOS and Tips and Tweaks plugin, the server has been stable for almost 48 hours and has had zero hiccups or issues along the way! I am going to try reverting those changes I made in BIOS and the plugin just to see what happens. One thing I should mention is that the case swap I did involved me redoing the front panel connections since it had the proprietary Intel chassis FP connection for their server boards and didn't match pin outs for consumer boards. When I first tried booting the system it wouldn't even POST, and after unplugging and removing all components except for CPU and one memory module... what solved it was removing the HDD LED connection and the Reset button connection. At that point it would then POST, and thought I had success until it was being unstable. However since this near 48 hour stability I have also removed the Power LED connection to the front panel...not sure why that would cause instability (if any) but it is now very much a possible suspect. In addition to stability for the past 48 hours I should add in that last night I was copying ~650GB of data from the array to my roommates local drive to remove his activity of working on projects directly from the array as a suspect. Additionally during that process I was able to run mover twice, install and configure multiple docker containers, and setup a Mac OSX and Windows 11 VM while the file transfer was running. I'd say that if I were to have any random instability issues still...they'd have peeked their ugly face last night when I was hammering the system 😂 I'll re-enable the settings and report back with updates. I'm sure you guys are probably tired of seeing me update this thread, but I just figured I'd keep this updated along the way until resolved Thanks once again for all the input everyone!

Web UI via VPN configured through separate firewall (Untangle installed on Sophos UPM320) was responsive today, however the dashboard was blank not showing anything besides the top tabs (Dashboard, Main, Shares, etc.) and was unable to access commands through terminal. Tried htop with no information reporting back, powerdown -r was also unresponsive. Main tab showed errors on every disk (16 disks in the array) which has never been present before except for <200 errors on disk 1 at times. Also was missing array options on the bottom of the page, so there was no ability to stop, check, spin up or down as would normally be present. Nobody was home today to even be putting any activity on the server either, so this appears to have been just a random occurrence. Unraid flash drive was in a USB 2.0 port, I also disabled Intel C-States in BIOS, and set CPU Scaling Governor to Power Save as well as Enable Intel Turbo/AMD Performance Boost to No in the Tips and Tweaks plugin. I'm grasping at straws here before downgrading Unraid OS to a previous version as mentioned above, and have attached todays syslog file as good measure in case anyone feels like taking a peek. As per usual, I will be reporting back with any good or (probably) bad news regarding stability. And as always, thanks again for all the help so far! syslog

I'll have to give that a go at some point too if this next thing I try doesn't solve my issues. I do remember a friend of mine once saying that I shouldn't be using the USB 3.0 port on my old board for my Unraid flash drive (that's a USB 3.0 drive), and that I should be using a USB 2.0 port. I don't remember what I plugged the flash drive into on this new config, but I'll be checking that when I get home and switching it from 3.0 to 2.0 if that's the case to see.

I didn't check and/or notice any issues with the server today, until my roommate messaged me while I was out for the day about it being down. I got home quite a few hours later and the GUI was unresponsive, and it was not accessible via the web UI. I did disable XMP yesterday, and I can't tell from the syslog if it was doing anything during its time of becoming unresponsive. I also don't know if he messaged me as soon as it happened or not. I looked through the syslog and nothing seems like a glaring issue besides the obvious errors on one of the hard drives in the array...however I don't think that would cause the entire system to become unresponsive. So at this point I can only assume that it is in fact some sort of hardware error. Hopefully there's something in the syslog I'm overlooking given my very limited knowledge, however I'm sadly thinking I'm not and it's time to start eliminating hardware in the system one at a time to find the possible culprit. Thanks again in advance for any help, as well as all the help that's been provided thus far! syslog (2)

That was a hunch I had but I'm glad someone else has the same hunch. I haven't tried with XMP disabled, I'll give that a go today and report back. I'll try running mover again to see if it restarts during that as a test, since that invoked a restart.