CasaP

I noticed last week that one of my appcache drives is showing 8 errors, but I am checking the SMART (short & long test) and all is good. How do I clear these error or actually see what they are?

I agree, just a set of bad coincidences. I find UnRaid bullet proof, you nearly need to go out of your way to break it. I do a monthly parity check, when the June one is finished, I'm going to look into the internal boot, these USB sticks are way too fragile.

Same issue, had a heart stopping moment, the upgrade went fine, stable for a few days, but I had to do a reboot (dead network switch) I didn't know was dead until I did the hard reset. Then, server name changed, still had the same IP, dropped me two nvme appcache drives. Once I stopped the array and changed the pool back to normal, all was good. But, I have the old GUI, not the fancy 7.3 one. All my dockers seem to be working, so I don't really care.

PermissionError: [Errno 13] Permission denied: '/invokeai_root/invokeai.example.yaml' Just doesn't work. Every time I fix permissions, it overwrites them.

That was exactly the problem, the new PSU was extremely picky about what cable was used. Crazy stuff. Even the main PSU to CPU cable wouldn't work until I changed it of the one that came in the box. Also, as you guessed I am dealing with the "lost+found" issue now, manually moving things back in place. Is there a faster way to do this? I am using Krusader synchroniser to get things back to normal, it's taking forever.

Well that was exciting. So what happened was that when replacing the power supply 3 WD drives had their fuses blown (apparently quite a common thing). I brought them into my friendly Polish electronics repair shop and they brought them back to life by replacing the barely visible SMD fuses. Popped them back into the server, they mounted without issue. The next problem was the two drives I mistakenly started to rebuild (before I realised the power supply was dying), the repair finished and they were both marked "unmountable". I followed the Disk Repair Procedure using the GUI and they both had a "zero log" error. They refused to mount, so I just cleared the log with the GUI and ran another file check, which both drives passed. All back up and running. I'm going to swap those WD's out for 3 new Toshiba 18Tb drives in the next few days and finally power up the Zimacube Pro backup box I bought, which I am going to install unRaid onto. unRaid really is a sublime piece of software that really keep data safe no matter what we throw at it. I learned a big lesson, relax and analyse the problem before pushing buttons. Thanks @trurl for your attention.

I think I'm inn the territory;

How do I do file system repair. I just replaced my power supply (a great 1000w PSU with 6x SATA lanes), the disks that went AWOL are now showing, but 3 x WD 12tb are now missing. Mind boggling. It's not cables, not power, just FS errors now I would say. I want to get these drives back again before doing anything. I did a clean shut down, so no idea why these just decided to die, as you can note, I have 6 of these WD 12tb, 3 died. Jesus this new PSU id noisy.

Thanks Trurl, I think it's a power issue. I was lazy when I expanded my array from 12 to 16 drives. Just opened her up and I have splitter cables everywhere. I'm going to the local PC store tomorrow to buy some 8 pin to 2 x Molex, and a couple of 6 pin to 2x Molex. I always have issues at start up / parity sync, so only when all drives are fired up. I'll swap out the cables and report back. I am going to put less drives on a string, I just looked and I had 8 drives running off a splitter, problem drives 5, 6 & 7. Lesson learned #1. I need to have a proper backup. Time to set up the Zima Cube I bought. Lesson learned #2. Think about power supply to drives, especially when they all spin up together.

Everything working fine, today my server decides to have multiple dis failures. So I had a power issue a day or so ago, got the "unclean shutdown" error despite NUT server doing it's thing, all disks were asleep, the cache (SSD) was the only drive in use. Did a parity rebuild going fine, then unRaid decided 2 disks were bad, so I started to rebuild them, then it decided another disk is bad, then another, then another. Now I have an unbelievable 4 disks bad. Crazy. Is this a bad HBA? Any ideas? I think Disk 7 is genuinely bad, the rest are ok. I just stopped the server, because I am fuming right now.

If anyone is looking to get NUT running with MacOS, there is a great app called "UPS Power Monitor" (€8.99) which you install on one Mac in your network, then you install a separate helper "server" agent on each Mac (free / open source). See here Power Guard The app connects to your unRaid NUT server instance, then can shutdown your Macs depending on battery remaining, time on battery or battery percentage. Very handy little app. I only looked into all of this because I had an iMac power supply blow due to a power failure recently, all wired machines are now on some form of UPS, with the main one that was already on the unRaid machine doing the heavy lifting.

That's basically what I did. I will set up a backup schedule for the USB now.

I remember seeing those, is that a bad thing, i.e. USB on the way out, or should I ignore? It's a high quality SANdisk USB, one of those tiny ones. At least if someone else has the same issue, they know there is a fix, due to how rock solid Unraid is.

So after a good bit of digging, I realised there was an issue inside my /config folder of the Unraid boot USB. The "go" file was blank and the "ident.cfg" file was blank. I downloaded a fresh zip of version 7, and copied these two files across and once I rebooted, I got the GUI. The next problem was I had to reassign the Apache and another download pool. Starting the array took some time, but all appears to be up and running now. I will restart a few times to make sure everything is stable.

So even when I boot up in GUI mode, I get an error trying to log into https://localhost directly on the machine, it says "unable to connect".