dboonthego

I'm seeing these errors for the first time (or noticing for first time) on two different servers running 6.12.3 and 6.12.4. I haven't noticed any negative impact though, but I do have GUI tabs and browser terminal sessions open to both servers. Is the thought that leaving the terminal session open is what causes this error? Or a tab to the Unraid GUI? Or both?

Destination host unreachable means there is no route to the destination which is different from a timeout where the route is there, but nothing responded. Probably a dumb question, but have you rebooted the Win10 machine? Something is awry with that device or your networking equipment. Not being able to ping the Win10 machine isn't totally alarming as anti-virus / firewall could block incoming icmp packets. Disable any anti-virus / firewall too.

It's another black-on-black redaction.

Good luck!

That works too. I suppose the diskpart route is native to Windows if someone wanted to avoid use of 3rd party tools.

In Windows, they call this the Blue Screen of Death (BSOD). That's basically what the MCE is. Your system has a hardware problem. Have you tried clearing the CPU fan/heatsink of dust? It could be caused by poor cooling. Maybe open the case and point a fan in there? It sounds like you're on the right track of elimination. If you're positive your PSU and RAM are good and you've disconnected non-essentials, then I'd start suspecting the CPU or main board. Does the system fail at this point every boot? I believe MCE errors that are correctable are written to /var/log/mcelog; otherwise the system halts and reboots. With Unraid, that log is probably empty regardless because the OS runs in RAM and logs aren't retained between reboots.

A flash stick that is greater than 32GB can be partitioned down to 32GB (or less) and used with Unraid. You forfeit the additional storage capacity, but you weren't going to use it anyway... Hopefully this helps someone in the future. From Windows, open cmd.exe As Administrator. This will wipe the contents of the flash drive and create a 32GB partition. diskpart list disk select disk x (where x equals the flash device # from list disk output) clean create partition primary size 32768 format fs=fat32 label=UNRAID active exit Copy the Unraid .zip contents to the flash and execute make_bootable.bat and you're golden.

In addition to Frank's comments, what does "ipconfig /all" show for both windows 10/11 machines? This sounds like a network routing issue and less of Unraid itself. Have you power cycled your equipment?Turn everything off and bring up modem, router, switches in that order and wait 3-5 minutes between each power up.

No, don't guess! Do you have a recent diagnostics .zip? You can assign all of your drives as data drives without assigning a parity. The one showing unformatted is the parity disk. After identifying the parity disk, do a new config and assign the parity slot.

No. You'd need an 8TB to support 2nd parity. You can still add the 4TB disks without having 2nd parity. You can't add 2nd parity with anything less than 8TB because you have a data disk that is 8TB. You can turn one of your 8TB data disks into the 2nd parity and add the 2 4TB to the array. You will still end up with 16TB capacity.

Explains why I'm on 27 now. Good to know. Thanks.

That's cool. Since when? It wasn't that long ago I was manually updating.

Selecting "apply update" next to the docker you wish to update is all that is necessary for most dockers. For Nextcloud specifically, updating the docker container does not update the Nextcloud app version. You need to login as Admin and select Administration Settings-->Overview and update from there. In my experience, each update required manual tweaks to complete and wasn't seamless. Here's the Nextcloud upgrade reference material.

Yes. Some apps such as Nextcloud may also require additional steps to upgrade the app version.

If someone has a flash larger than 32GB, it can be partitioned to 32GB or less and additional space discarded, correct?

Agree with Frank. I use the Fractal-Design Define R5 and I couldn't be happier. Extremely well engineered. Quiet. Excellent cable management. Holds (2) 2.5hdd on backside of mobo. (8) easily removable bays (not hot swap) for 3.5hdd. (2) 5.25 bays for cdrom or other HDD with conversion kit. Dust management is awesome. Has removable screens that act like a typical dryer lint screen. Inside of my case stays relatively clean. Worth every penny.

Yes! It can be done now, but it's not baked into the OS. It took me 10 years to reach this point so not likely very common, but would be nice for those needing to shrink.

Built-in option to permanently remove a data disk and maintain parity. Reduce physical disk count.

This looks like it reached the end of the disk. Is "no space left on device" normal output? root@Tower:~# dd bs=1M if=/dev/zero of=/dev/md2p1 status=progress 2000357949440 bytes (2.0 TB, 1.8 TiB) copied, 23160 s, 86.4 MB/s dd: error writing '/dev/md2p1': No space left on device 1907730+0 records in 1907729+0 records out 2000398901248 bytes (2.0 TB, 1.8 TiB) copied, 23160.8 s, 86.4 MB/s root@Tower:~#

I had rebooted before posting. I agree it doesn't make sense. I might have unassigned/reassigned disk 2 in the same slot before changing the FS, but most definitely disk 2 started a clear which was unexpected.

I emptied Disk 2. I replaced parity with a larger disk and allowed parity sync to complete. I converted Disk 2 to XFS Encrypted. When the array started, it began to clear Disk 2, but I cancelled it. I formatted and started array and everything looked normal. I stopped the array and assigned the old parity to Disk 6. Started array and the clear process began on 6. I let that finish. Do I need to do something with Disk 2? Or re-run parity sync?

Yeah, also normal. I tend to focus on the main tab vs dashboard. Main vs. Dashboard. I guess the dashboard has more room to scare you. 😊

Navigate to https://unraid.net/download and click "Manual Install method." These two links return 404 error due to extra "changing-the-flash-device/" in the path. They work fine if navigating from the https://docs.unraid.net menu tree. Alternatively, if you are using a Linux system or if the USB Flash Creator tool is not working for some reason, please use the legacy method. Prepare a new flash device using the procedure documented in the Getting Started guide.

Parity invalid is normal for a new drive assignment until parity sync has completed. I think you're fine.

The cert needs to be signed by a CA the browser trusts. Your options (to avoid seeing warning) are to turn off SSL or you can apply for a free myunraid.net Let's Encrypt certificate. In your present configuration, the connection is still encrypted, just not trusted.