emmcee

Members
  • Posts

    115
  • Joined

  • Last visited

Everything posted by emmcee

  1. 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!
  2. 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!
  3. 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?
  4. 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
  5. 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
  6. Rebooted and everything is back again. Note to self: now is a good time to backup my flash drive.
  7. 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
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. Cool. At least it's one of my older drives.
  13. 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
  14. You’ve saved my bacon yet again Johnnie! Many thanks.
  15. 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
  16. OK - I did that and it says: Is it OK to use -L?
  17. OK, I had the brianwave of pulling all the drives/flash and putting them in my gaming PC. After some fiddling I got all drives to show. The good news is that there are no ATA errors in the log. The bad news is that drive 3 is showing as unmountable. That drive is 4.5 years old and was due for replacement. I have a spare. Is it worth rebuilding that onto a new drive. If so, there is no issues replacing a 3TB unmountable with an 8TB? New diagnostics attached tower-diagnostics-20191107-1858.zip
  18. Yes - just spotted that. I have an option of a Gigabyte X299 AORUS Gaming 3 for that CPU - post edited
  19. My old PSU seems to have bitten the dust, but I'm thinking of using the opportunity of future proofing my server for the next few years, but it's been a while since Iv'e built any hardware and I'm not up to speed on the latest CPUs. Currently my thoughts are as follows: - Motherboard: Gigayte Z390 Aorus Elite or Gigabyte X299 AORUS Gaming 3 - RAM: 2x Kingston KCP424NS8/8 (already have one stick of this) - PSU: Seasonic FOCUS Plus Platinum 550W (just ordered this to replace my old one) - Cooler: I need some suggestions. It needs to be something quiet as it's goign to be in my office. There is plenty of space in case for a large heatsink. Not sure I care about water cooling. - CPU: i5-9600K or i7-9800x - data/cache dries to be recycled from current system This will mainly be used as a Plex server but I also run a couple of VM's and have considered moving my GPU from my gaming rig and consolidating into one machine. I can source either of the CPU's cheaply, but I'm torn between QuickSync on the i5 and 16 threads on the i7. My current thoughts are that QuickSync for transcoding isn't really worth it due to inferior quality, and with 8 cores on the i7, it will not have any issues coping. I'm also thinking that the i7 is likely to be better able to mange future needs. Can someone give me some input before I spend my euros?
  20. Yeah. The error moved to ata7 when I did this which points to the PSU. It’s only a year old but has a 3 year warranty so I’ll RMA it. I have a gaming PC so I can pull the PSU from that I’n the meantime. I hope I have enough SATA power cables...
  21. Cables and card look OK to me. I'm not sure how to proceed though. Parity2 is connected to the motherboard, but there are 6 drives in total on the motherboard and 2 on a PCI card. Is it worth swaping parity2 over to a spare port on the card? I have a spare 8TB drive I can swap in for parity 2, but there seems to be an error on ata4 also. Looking at the disk attribites, there are UDMA CRC errors on disk1, disk2, disk3.
  22. Agreed. I’ll shutdown later and check my cables and card. I’m already looking at new hardware - I’ve been looking for an excuse for a while.
  23. Is it worth running a parity check again. I’m thinking if something happened during the parity check then it may not actually be a problem with the disks parity.
  24. Oops - diagnostics attached. tower-diagnostics-20191106-1230.zip
  25. I had a scheduled monthly parity check at the weekend and it has reported 4536 errors. I'm runing a UPS and haven't had any outages (uptime is 69 days). The main page is showing zero errors on all of my drives. The syslog is showing these errors from when the check was running: Nov 3 00:31:03 Tower kernel: ata1: SError: { PHYRdyChg 10B8B DevExch } Nov 3 00:31:03 Tower kernel: ata1.00: failed command: WRITE DMA EXT Nov 3 00:31:03 Tower kernel: ata1.00: cmd 35/00:40:18:7b:1e/00:05:b0:02:00/e0 tag 12 dma 688128 out Nov 3 00:31:03 Tower kernel: res 50/00:00:c7:88:1c/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Nov 3 00:31:03 Tower kernel: ata1.00: status: { DRDY } Nov 3 00:31:03 Tower kernel: ata1: hard resetting link Nov 3 00:31:04 Tower sSMTP[20039]: Sent mail for [email protected] (221 2.0.0 closing connection p18sm17796971wmi.42 - gsmtp) uid=0 username=xxx outbytes=684 Nov 3 00:31:09 Tower kernel: ata3: link is slow to respond, please be patient (ready=0) Nov 3 00:31:09 Tower kernel: ata1: link is slow to respond, please be patient (ready=0) Nov 3 00:31:09 Tower kernel: ata4: link is slow to respond, please be patient (ready=0) Nov 3 00:31:13 Tower kernel: ata3: COMRESET failed (errno=-16) Nov 3 00:31:13 Tower kernel: ata3: hard resetting link Nov 3 00:31:13 Tower kernel: ata1: COMRESET failed (errno=-16) Nov 3 00:31:13 Tower kernel: ata1: hard resetting link Nov 3 00:31:13 Tower kernel: ata4: COMRESET failed (errno=-16) Nov 3 00:31:13 Tower kernel: ata4: hard resetting link Nov 3 00:31:13 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 3 00:31:13 Tower kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 3 00:31:13 Tower kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 3 00:31:13 Tower kernel: ata3.00: configured for UDMA/133 Nov 3 00:31:13 Tower kernel: ata3: EH complete Nov 3 00:31:14 Tower kernel: ata1.00: configured for UDMA/133 Nov 3 00:31:14 Tower kernel: ata1: EH complete Nov 3 00:31:14 Tower kernel: ata4.00: configured for UDMA/133 Nov 3 00:31:14 Tower kernel: ata4: EH complete Nov 3 00:33:13 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x4090000 action 0xe frozen Nov 3 00:33:13 Tower kernel: ata1.00: irq_stat 0x00400040, connection status changed Nov 3 00:33:13 Tower kernel: ata1: SError: { PHYRdyChg 10B8B DevExch } Nov 3 00:33:13 Tower kernel: ata1.00: failed command: READ DMA Nov 3 00:33:13 Tower kernel: ata1.00: cmd c8/00:f0:58:07:53/00:00:00:00:00/e0 tag 27 dma 122880 in Nov 3 00:33:13 Tower kernel: res 50/00:00:57:07:53/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Nov 3 00:33:13 Tower kernel: ata1.00: status: { DRDY } Nov 3 00:33:13 Tower kernel: ata1: hard resetting link Nov 3 00:33:13 Tower kernel: ata4.00: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen Nov 3 00:33:13 Tower kernel: ata4.00: irq_stat 0x00400040, connection status changed Nov 3 00:33:13 Tower kernel: ata4: SError: { HostInt PHYRdyChg 10B8B DevExch } Nov 3 00:33:13 Tower kernel: ata4.00: failed command: READ DMA EXT Nov 3 00:33:13 Tower kernel: ata4.00: cmd 25/00:40:18:c8:94/00:05:b0:02:00/e0 tag 13 dma 688128 in Nov 3 00:33:13 Tower kernel: res 50/00:00:5f:04:53/00:00:00:00:00/40 Emask 0x50 (ATA bus error) Nov 3 00:33:13 Tower kernel: ata4.00: status: { DRDY } Nov 3 00:33:13 Tower kernel: ata4: hard resetting link Nov 3 00:33:19 Tower kernel: ata4: link is slow to respond, please be patient (ready=0) Nov 3 00:33:19 Tower kernel: ata1: link is slow to respond, please be patient (ready=0) Nov 3 00:33:23 Tower kernel: ata4: COMRESET failed (errno=-16) Nov 3 00:33:23 Tower kernel: ata4: hard resetting link Nov 3 00:33:23 Tower kernel: ata1: COMRESET failed (errno=-16) Nov 3 00:33:23 Tower kernel: ata1: hard resetting link Nov 3 00:33:24 Tower kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 3 00:33:24 Tower kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 3 00:33:24 Tower kernel: ata1.00: configured for UDMA/133 Nov 3 00:33:24 Tower kernel: ata1: EH complete Nov 3 00:33:24 Tower kernel: ata4.00: configured for UDMA/133 Nov 3 00:33:24 Tower kernel: ata4: EH complete The machine is still running. Any suggestions as to how I should proceed?