DivideBy0

How about this setup? AsRock Rack E3C252D4U paired with an Intel® Xeon® E-2388G Processor

I do not have "Parity Check Tuning" installed.

So this statement is not accurate then? " The array should now stop successfully (This issue was resolved with 6.12.3)" I mean what is done is done, but folks should know the issue is not fixed and manual interaction is still required, just to be on the safe side?

That is an easy fix and I wish I knew. My assumption was that is fixed in 6.12.3 but I guess is still not fixed. If the system is currently running 6.12.0 - 6.12.2, we're going to suggest that you stop the array at this point. If it gets stuck on "Retry unmounting shares", open a web terminal and type: umount /var/lib/docker The array should now stop successfully (This issue was resolved with 6.12.3)

OK, so then how do we explain this unwanted behavior? Obviously when an upgrade is done and a reboot is required I would expect some checks and balances in the upgrade / reboot process? Can't just blindly upgrade and then blindly reboot, hoping that everything is gonna turn ok? I am extremely confused here. Do we need to worry every time we do a simple upgrade now? Very few dockers running in this system:

Not sure why this was moved to 6.12.3 Unclean Shutdown as I believe will be misleading for the folks here. This is a symptom of my upgrade from 6.12.3 to 6.12.4 and have nothing to do with an intentional shutdown or reboot. All this happened after the upgrade took place and is asking for a reboot and that is exactly what I did. Not sure where the confusion. I do have another UnRaid system due for 6.12.4 which I will not upgrade as I am concerned with the same behavior.

I sure can Sir. Please see attached nas-unraid-2-diagnostics-20230904-0854.zip

Thank you Sir, that should do the trick then.

Fixing to completely swap all hardware on my current UnRaid 8 bay system. The only things I plan to keep from the original system are the original USB boot drive, the HBA LSI controller in IT mode with its associated array and parity hard drives. If I wire the HBA controller and the hard drives in the same order as original system, would the USB config boot recognize my drives and keep the array intact? I would hate to move data manually.

Again is absolutely SILLY that a system can't actually unmount the darn mounts and just reboot normally 🙂 I had nothing going on the background and this is a very basic, primitive system. Sep 4 08:54:23 NAS-UNRAID-2 emhttpd: Unmounting disks... Sep 4 08:54:23 NAS-UNRAID-2 emhttpd: shcmd (299477): umount /mnt/cache Sep 4 08:54:23 NAS-UNRAID-2 root: umount: /mnt/cache: target is busy. Sep 4 08:54:23 NAS-UNRAID-2 emhttpd: shcmd (299477): exit status: 32 Sep 4 08:54:23 NAS-UNRAID-2 emhttpd: Retry unmounting disk share(s)... Sep 4 08:54:28 NAS-UNRAID-2 emhttpd: Unmounting disks... Sep 4 08:54:28 NAS-UNRAID-2 emhttpd: shcmd (299478): umount /mnt/cache Sep 4 08:54:28 NAS-UNRAID-2 root: umount: /mnt/cache: target is busy. Sep 4 08:54:28 NAS-UNRAID-2 emhttpd: shcmd (299478): exit status: 32 Sep 4 08:54:28 NAS-UNRAID-2 emhttpd: Retry unmounting disk share(s)... Sep 4 08:54:29 NAS-UNRAID-2 root: Status of all loop devices Sep 4 08:54:29 NAS-UNRAID-2 root: /dev/loop1: [2049]:12 (/boot/previous/bzfirmware) Sep 4 08:54:29 NAS-UNRAID-2 root: /dev/loop2: [0043]:260 (/mnt/cache/system/docker/docker.img) Sep 4 08:54:29 NAS-UNRAID-2 root: /dev/loop0: [2049]:10 (/boot/previous/bzmodules) Sep 4 08:54:29 NAS-UNRAID-2 root: Active pids left on /mnt/* Sep 4 08:54:29 NAS-UNRAID-2 root: USER PID ACCESS COMMAND Sep 4 08:54:29 NAS-UNRAID-2 root: /mnt/addons: root kernel mount /mnt/addons Sep 4 08:54:29 NAS-UNRAID-2 root: /mnt/cache: root kernel mount /mnt/cache Sep 4 08:54:29 NAS-UNRAID-2 root: /mnt/disks: root kernel mount /mnt/disks Sep 4 08:54:29 NAS-UNRAID-2 root: /mnt/remotes: root kernel mount /mnt/remotes Sep 4 08:54:29 NAS-UNRAID-2 root: /mnt/rootshare: root kernel mount /mnt/rootshare Sep 4 08:54:29 NAS-UNRAID-2 root: Active pids left on /dev/md* Sep 4 08:54:29 NAS-UNRAID-2 root: Generating diagnostics...

Well is doing parity check and can't touch it. Looking at my IPMI log file it was a forced shutdown? Say is collecting a diagnostic file Where can I find the diagnostic file so I can upload it here?

I have a pretty simple system. Upgrade went OK but when back it started a parity check? That's not cool and I am simply annoyed I have a second UnRaid that I am debating if I should upgrade given this experience

I am consolidating my 2 x NAS to a rack mount type case. What would the entire system fetch me? Had it for about 2 years give or take, rock solid, very low power consumption. All is for sale except the 8 drives that I use for the Array and Parity. The 2 x Internal SSD (500GB) can stay for the cache. You can see all the specs on the first image. I will include the UnRaid USB boot disk as well to preserve the configuration.

I absolutely give up on UnRAID SMB with Macs starting with the TimeMachine. Good luck but UnRAID does a terrible job at SMB when it comes to Macs. Not sure if Unraid or Apple fault but I just give up. My Windows and Linux boxes works fine except the Apple gear.

I got this for a project that I never finished and I keep buying the wrong parts. Anyway my loss is your gain as I will let this go for $140 including shipping via USPS in all US states. I am PayPal verified. Shipping or local pickup

LOL they don''t know what vi is I grew up with vi

To switch to SimonF's IPMI and NUT do I have uninstall the unsupported versions first and then install SimonF's? Would the configurations stay or I have to re-configure everything all over again after the SimonF versions install?

I have this nice Supermicro X10SRM-TF Motherboard Micro ATX Socket LGA-2011 paired with an E5- 2620V4 and 32 Megs RAM, I used for my backup UnRaid NAS but there is catch. Somehow after upgrading my BIOS, both embedded 10G network LAN eproms got corrupted and I really don't have the knowledge to fix these. I know is possible to re-flash the eeproms if you have the know how and patience. I believe SuperMicro can provide privately the appropriate flash files. You could also RMA this in as per my conversation with SuperMicro support and they will do it for you at no cost, just shipping. Priced accordingly for the corrupted 2 x 10G LAN eprom interfaces - $250 + Shipping for entire package. I am PayPal verified.

Sorry I was traveling. Just got back. Messaged you back just now

Correct. That was the cleanest way to do a fresh install and no previous baggage.

I had data in one of my remote machine NextDoor folder so when I logged in it synced everything back into the server On the server side I blew everything off including the data folder and its content

yes everything

I just blew it all up and re-did it from scratch. What a waste of my time man

Now I get this. I am SO EFFING annoyed by this shit man. Can I just re-install over? Or remove NextCloud and add it back? I am at the point where I rather re-do everything than trying to fix. Absolutely effing ridiculous

Guys offer solutions and not criticism and make stupid assumptions like we don't know what we're doing here. I maintain my versions religiously and I wasn't behind 2 or 3 major versions. Is so freaking easy to point fingers rather than actually helping.