[[SOLVED] Parity Swap Procedure - Asking to Copy Again]

Unraid driver crashed, you will need to reboot, having just pariry2 should not be a problem.

[3x Drives keep throwing errors...randomly, whilst SMART tests say they are all good.]

But it's spamming the log, if it still does it after a reboot post new diags.

[3x Drives keep throwing errors...randomly, whilst SMART tests say they are all good.]

Those look similar, reboot to clear the logs and post new diags as soon as there are issues logged with the cache device.

[How should I proceed? - Two drives failed during a network transfer, crashed unraid, caused unclean shutdown.]

Both disks dropping offline at the same time suggests a power/connection issue, see if they share something, like a power splitter.

 

Then and since the emulated disks are mounting, and assuming contents look correct, you can rebuild on top.

 

 

[3x Drives keep throwing errors...randomly, whilst SMART tests say they are all good.]

Diags don't show the start of the problem, they show constant errors for sdd, but there' no SMART for sdd, any idea which device is that?

[How should I proceed? - Two drives failed during a network transfer, crashed unraid, caused unclean shutdown.]

Diags are after rebooting so we can't see what happened, if you don't have pre reboot diags post new ones after array start.

[Entire folder directories become unresponsive]

Syslog in the diags is empty, try

cp /var/log/syslog /boot/syslog.txt

 

then attach it here.

[Server crashed - unclear of the reason]

Call trace is zfs related, there could be some hardware issue like bad RAM, and/or that zfs filesystem is corrupt.

[Brand new server rebooting during parity or SMART tests]

80C is not overheating, and overheating should not make the PC reboot, at worse it should shutdown, so likely there's some other hardware issue, try with just one stick of RAM, if the same try the other one, that will basically rule out the RAM.

[6.13 Beta question "Hybrid ZFS pools" - what does it mean?]

5 hours ago, jortan said:

Just wanted to check if this is a supported configuration in 6.13?

This is currently not supported, and AFAIK there no plans for the near future, only one zfs partition per device is supported.

[Crashing (Followed Normal Troubleshooting)]

Server rebooting on its own is almost always a hardware issue, but can be caused by different components, start by running memtest, but note that memtest is only definitive if it finds errors, if you have multiple sticks you can also try with just one, if the same try with a different one, that will basically rule out bad RAM, next suspects after that would be PSU, board, CPU.
 

[Secure boot issue - how to repair usb?]

8 hours ago, Crystal420 said:

what's more the secure boot options are not all greyed out.

Try enabling CSM/legacy boot, some BIOS don't let you disable secure boot if only UEFI boot is enabled.

[Unraid 6 Keeps Crashing every 24-48 hours]

Unfortunately there's nothing relevant logged, this can be a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

[Data Loss Mitigation Help]

Running on the sd device will not update parity, click on the disk, set the filesystem to xfs, try running it again using the GUI and post the results.

[Moving cache to different drive]

You can use this:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=511923

 

[New User, New Build. System not staying up for more than a couple hours]

14 hours ago, skittlebean said:

I can't imagine that "servo/seek failure" is possible on a healthy drive.

It's never a good sign.

[ZFS integrity during 2 disk resilver]

Additionally, and if you have enough SATA ports to have all disks connected, you could do a manual replacement, so the old disks could still be read (except for the bad parts).

[Unraid can't get IP address after motherboard swap]

May 11 11:56:19 [1449]: br0: checksum failure from 192.168.1.1
May 11 11:56:34 [1449]: br0: checksum failure from 192.168.1.1
May 11 11:57:06 [1449]: br0: checksum failure from 192.168.1.1
May 11 11:58:09 [1449]: br0: checksum failure from 192.168.1.1
May 11 11:59:13 [1449]: br0: checksum failure from 192.168.1.1

 

Maybe a router issue? Try rebooting it.

[Server is restarting every 1-2 days]

17 hours ago, mainframe.admin said:

The governor is set to performance so i’m not sure why it’s scaling up and down rather than staying at 4.8GHz.

This is normal, it will just scale up earlier than the other options.

 

When you say the server is restarting do you mean it's rebooting on its own?

 

 

[Backup solution for Home NAS]

Correct 

[6.12.10 I broke setup upgrading cache drive! Any advise?]

It's fine to leave in place, you will be using the free OpenDNS servers for DNS, and it also suggests an issue with your router/ISP DNS server.

[Parity check not finishing]

18 hours ago, loady said:

time to start testing the RAM sticks ?

 That's a good place to start, start by running memtest, but note that memtest is only definitive if it finds errors, if you have multiple sticks you can also try with just one, if the same try with a different one, that will basically rule out bad RAM, next suspects after that would be PSU, board, CPU.

[Machine Check Event Triggered after upgrade to AMD Ryzen Processor/Motherboard]

19 hours ago, sgrangers said:

it rebooted abruptly

Server rebooting on its own is almost always a hardware issue, but can be caused by different components, since you are re-using the RAM, the next suspects after that would be PSU, board, CPU.

[Interesting Video: The Birth, Boom and Bust of the Hard Disk Drive]

 

[SMART “Completed: Electrical Failure”]

Not an error that I remember seeing before, but a SMART test failing to complete is reason enough top replace a drive