emmcee

Rebuild has completed successfully. A reboot has fixed the Array Operations tab too. Maybe it’s time for an update. thanks again for your help!

It’s happening with Safari too. Not to worry. It’s 75% of the way through the rebuild so we’re looking good. Thanks for your help @JorgeB!

yeah, I've done that now and it's rebuilding. The Array operaions tab has only 3 buttons and the main tab still has dropdowns, even though it's doing a rebuild. Is that as expected?

OK, I stopped, restarted with P2 unselected, stopped again, reslected P2 and started. It was rebuilding parity this morning, but I just checked it and it has write errors in the logs, and it says it's paused at 1.7% of a parity check. In the Array Operations tab I only have reboot, shutdown and sleep. Whast my best course of action here? Can I reboot, and then deselct P2? Will it need to rebuild parity on P1? I'd be happy with single parity for now if it gets me up and running. tower-diagnostics-20231123-1420.zip

A few months ago I swapped my SATA cards for a HBA as I had been getting UDMA CRC errors. Everyting has been fine since, but I had to shutdown the server today for the first time and on restart, one of my parity drives is disabled. SMART looks OK to me (but I'm not an expert). Is there anything to be concerned about here? Do I just need to rebuidl parity? tower-diagnostics-20231120-1107.zip

Rebooted and everything is back again. Note to self: now is a good time to backup my flash drive.

I sat down to Plex this evening and none of my Libraries are showing. So I had a look on the server and all of my shares have disapeared, except, frunnily enough, Plex - which has my Plex metadata. I had issues after a hardware change last week where one of my cache droves was missing from the RAID 0 pool (though the pool seemed fully functional and reported the full size). I moved everything off the SSD, recreated the pool and moved it back again, like you would when doing an SSD upgrade. Everything seemed fine after that (approx 4 days ago). I tried to stop and restart the array, but it's stuck at "Array Stopping•Retry unmounting user share(s)..." Looking at the discs it seems like everything is there. Diagnostics attached. Please help. tower-diagnostics-20200923-2046.zip

You should exclude your cache drive in the plugin settings. 47deg is usually fine for an SSD. Mine ran constantly when I got new SSD's until I excluded my cache pool.

I love the fact that I have lost a few drives over the years, but I haven’t lost any data. I’d love if fan control was Automatic and supported multiple fans.

FWIW, my KP issues were down to BIOS version. I updated to the latest Gigabyte BIOS and it ran fine for the past 3 years.

I thought I might post this here as it's taken me a while to piece it all together and it may help someone else get Fan Auto Control working. I have a Gigabute Z390 Aorus Elite board. Unraid can't support the fan PWM controler out of the box. I spent a couple of evenigns playing with sensors-detect btu noting was recognised. Then I found this page: https://github.com/a1wong/it87/issues/1 Essentially, you go to Main -> Boot Devices ->Flash -> Syslinux Configuration -> Unraid OS Change the second line from: append initrd=/bzroot to: append initrd=/bzroot acpi_enforce_resources=lax Then add this line to your /boot/config/go file: modprobe it87 force_id=0x8628 Reboot and Fan Auto Control should see your PWM fan.

Cool. At least it's one of my older drives.

I rebuilt parity overnight, and just as it was ending, Parity2 threw some read errors. Is my best option here just to replace Parity2? tower-diagnostics-20191108-1605.zip

You’ve saved my bacon yet again Johnnie! Many thanks.

Update: system, log has this after mounting the FS again: Nov 7 19:19:13 Tower kernel: XFS (md3): Corruption warning: Metadata has LSN (5:1567790) ahead of current LSN (5:1566498). Please unmount and run xfs_repair (>= v4.3) to resolve. Nov 7 19:19:13 Tower kernel: XFS (md3): log mount/recovery failed: error -22 Nov 7 19:19:13 Tower kernel: XFS (md3): log mount failed Nov 7 19:19:13 Tower root: mount: /mnt/disk3: wrong fs type, bad option, bad superblock on /dev/md3, missing codepage or helper program, or other error. Nov 7 19:19:13 Tower emhttpd: shcmd (268): exit status: 32 Nov 7 19:19:13 Tower emhttpd: /mnt/disk3 mount error: No file system