JorgeB

Parity2 is also showing as new, can't have 3 invalid disks.

There's a lot of crashes but nothing that points to the cause for me, you can try running the server in safe mode without any dockers/VMs for a couple of days, if it still crashes running as a basic NAS most likely there's some hardware issue, if it doesn't start turning on the services one by one.

It's somewhat of a mystery but some users see a very large performance difference using user shares vs disk shares, some overhead is normal, but not so much, best bet is to use disk shares when possible.

I have some of those, measured power use at about 9w.

One of them is bound to vfio-pci so it's not available for Unraid.

Yes, it should be 255 to disable, not 0, my mistake. Never tried that, it won't hurt.

Yes, under /mnt/disks

Yes, hdparm -B 0 /dev/sdX to make it disable or hdparm -B 254 /dev/sdX for maximum performance, either should achieve desired results. Yes, look at the user scripts plugin, good for that.

Since the SMART test passed disk is OK for now, but the error is logged as a disk issue, also keep an eye on this attribute: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 1 If it keeps increasing most likely there will me more errors soon.

It should work with v6.9-rc2 Unraid doesn't support wifi.

Jan 11 08:37:03 storage kernel: ata15.00: HPA detected: current 3907027055, native 3907029168 Jan 11 08:37:03 storage kernel: ata15.00: ATA-9: WDC WD20EFRX-68AX9N0, WD-WMC300660429, 80.00A80, max UDMA/133 See here:

Please post the diagnostics: Tools -> Diagnostics

2.5" drives usually have much more aggressive power saving enable, you can limit or disable that by lowering or disabling the APM level, you can do that with hdparm -B, will need to be re-applied after a reboot wit a user script or by using the go file.

Please don't crosspost.

Depends on the SAS controller.

NICs are found but fail to load the driver because of an error: Jan 10 14:02:06 dstore kernel: bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 1.712.30-0 (2014/02/10) Jan 10 14:02:06 dstore kernel: bnx2x 0000:03:00.0: msix capability found Jan 10 14:02:06 dstore kernel: bnx2x: PCI device error, probably due to fan failure, aborting Jan 10 14:02:06 dstore kernel: bnx2x 0000:03:00.1: msix capability found Jan 10 14:02:06 dstore kernel: bnx2x: PCI device error, probably due to fan failure, aborting So this is a Linux or hardware issue, maybe look for a firmware update.

Note that unless there's a serious hardware issue most transfers should be 100% OK, since most pathways are protected, like Ethernet and disks (and RAM if you're using ECC), but it's still good to have checksums and they can come in handy for some situations if there are ever any doubts, I use Corz, you can easily generate checksums by folder and then check them by folder (or the complete share) on the destination if needed.

Clearly there's a LAN problem.

Like mentioned errors on multiple disks still happening, possibvly a power problem, try with another PSU if available, also change onboard SATA from IDE to AHCI.

Again the array is started, I though you couldn't start the array?

Syslog doesn't show any disk errors, based on SMART disk7 look OK, cache has some reallocated sectors, but nothing critical showing, you can run extended SMART tests or post new diags after there are errors.

No need, no write error = successful rewrite.

This is a hardware issue, you can try a CMOS reset and/or BIOS update, if that doesn't help you'd need to replace the board or use an add-on NIC.

Yes, in the first diags the NIC is there, it's completely missing on the second ones, like if it's disable or doesn't exist.

Because there weren't any write errors, if a read error is found Unraid uses parity and the other disks to calculate what should be there and re-writes that block to the offending disk, if there's a write error the disk will be disable.