John_M

If it isn't the cables then it's the controller or the SSD itself. You still have a hardware problem, irrespective of what you've changed. Your syslog is absolutely full with messages like this, which makes it difficult to read: Jun 1 06:13:29 TOWER kernel: ata6.00: failed command: READ FPDMA QUEUED Jun 1 06:13:29 TOWER kernel: ata6.00: cmd 60/08:78:40:dc:5c/00:00:18:00:00/40 tag 15 ncq dma 4096 in Jun 1 06:13:29 TOWER kernel: res 41/84:08:40:dc:5c/00:00:18:00:00/00 Emask 0x410 (ATA bus error) <F> Jun 1 06:13:29 TOWER kernel: ata6.00: status: { DRDY ERR } Jun 1 06:13:29 TOWER kernel: ata6.00: error: { ICRC ABRT } Jun 1 06:13:29 TOWER kernel: ata6: hard resetting link Jun 1 06:13:29 TOWER kernel: ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 1 06:13:29 TOWER kernel: ata6.00: supports DRM functions and may not be fully accessible ### [PREVIOUS LINE REPEATED 1 TIMES] ### Is it a Marvell based controller? They are known to have problems and they seem to be getting worse with never kernels. If so you'll need to replace it. There are inexpensive dual port ASMedia SATA controllers that work well with Unraid.

Parentheses are ok but I'd avoid using slashes in filenames. If you call the folder F-X (1986) instead you'll be safe.

Which slot is each card in? Have you tried swapping them?

The .DS_Store file and files beginning with "._" are a consequence of you using macOS. They are harmless and can be ignored, though some people find them annoying, in which case they can be safely deleted.

I don't use downloaders myself but it seems not uncommon for people who do to have problems with the permissions or ownerships they are configured to use by default. You might find some information in the support thread for the particular docker that you're using.

You have a cable problem (or, much less likely, a controller problem) with your cache SSD. Shut down, replace the SATA cable, check the power cable and power up again.

You need to give more information. Go to Tools -> Diagnostics and attach the complete zip file to you next post. This will show what PCIe device you have at 05:00.0 and a load of other useful information. I'm guessing but is it an Nvidia graphics card? Are you passing it through to a VM? Have you tried Googling the error message? You'll find several hits and only one of them is this page.

I tried giving the unused port a static IP address but that didn't change anything. I want to try adding the port to the existing bond but today is scheduled parity check day so I'll leave it alone for now. I'll probably end up disabling the port in the BIOS.

I've installed the new version of the plugin by @kubed_zero on three servers and it's working fine on two of them, with Observium generating graphs. On the third I'm getting this error message repeatedly (every three seconds) in my syslog starting immediately after installing the plugin and Observium believes the server to be offline: May 31 18:16:30 Mandaue root: plugin: creating: /usr/local/emhttp/plugins/snmp/snmpd.conf - from INLINE content May 31 18:16:30 Mandaue root: plugin: running: anonymous ### [PREVIOUS LINE REPEATED 1 TIMES] ### May 31 18:16:30 Mandaue kernel: r8169 0000:05:00.0 eth2: Invalid ocp reg 2a3fe! May 31 18:16:30 Mandaue root: plugin: running: anonymous May 31 18:16:33 Mandaue kernel: r8169 0000:05:00.0 eth2: Invalid ocp reg 2a3fe! ### [PREVIOUS LINE REPEATED 439 TIMES] ### If I uninstall the plugin the error message continues until I reboot. If I don't install the plugin my syslog is clean. I Googled the error message but got nothing relevant - Google seems fixated by military uniforms, latching on to "ocp" and failing to find a match for everything else. The two major differences between this server and the other two: firstly, it's running Unraid 6.7.1-rc1 (as opposed to 6.7.0 on the others) as a test; secondly, eth2 is the onboard Realtek NIC, which is unconfigured and unused, though not disabled in the BIOS, with eth0 and eth1 forming a bond, while the other servers have no unused NICs. One of them has a single Realtek NIC, which is configured as eth0 and is in use. The other has two Broadcom NICs in a bond. Diagnostics attached. mandaue-diagnostics-20190531-1745.zip EDIT: I was only running Unraid 6.7.1-rc1 as a test. The server doesn't have an Intel processor and doesn't need the MDS mitigations but in the light of this comment by Tom, I thought it would be useful to test it. Anyway, I reverted to Unraid 6.7.0 on this server and the problem persists if I install the SNMP plugin. Attached diagnostics for Unraid 6.7.0. mandaue-diagnostics-20190531-1859.zip

It's an unusually long name. Can't you simply edit it to make it shorter? "HomeBridge-GUI" would surely fit.

To hide them completely you have to tell Windows not to display them. See the table below: Samba hide Samba show Windows hide Invisible Invisible Windows show Greyed out Visible I still maintain that I'm fundamentally opposed to the idea of configuring a file server to refuse to store certain files. It's much better to configure Macintosh clients not to create the annoying files on shared network storage in the first place. See here, for example: https://www.tekrevue.com/tip/stop-ds-store-files-mac-network/ defaults write com.apple.desktopservices DSDontWriteNetworkStores -bool TRUE

That's true and if you're living in isolation it does't really matter if you don't upgrade. But the reality is that it's a big bad world out there that has become bigger and badder since that previous release was new. But you're not living in isolation because you posted here, which means you're connected, which means you're vulnerable. You may not need the new features but you certainly need the security updates.

I'm reading that complete mitigation against the MDS flaw requires hyperthreading to be disabled, which will hit the performance of their higher end processors even harder, though Intel is playing it down.

ASMedia ASM1061 or ASM1062 based SATA cards work well with Linux and with SSDs.

I believe it's automatic if you have a wide enough display.

I don't know whether the Vega iGPU can be used to accelerate Plex transcoding. In theory it ought to be possible but only if Plex has been coded to make use of it. However, it's much more powerful than any Intel iGPU and I would like to see the driver included so that containers such as FoldingAtHome can make use of its OpenCL capabilities.

To anyone following this thread it would be useful to see if there's a correlation across the various motherboard brands. I'm interested to know if it's related to a particular AGESA version. You can help by posting your motherboard make and model, the BIOS version that broke your system and the latest version that fixes it. I have a personal interest in the Asus PRIME X470-Pro.

@rpj2 I backed up my flash and grabbed diagnostics, then upgraded the server with the Marvell 9235 card to Unraid 6.7.0. All disks were detected and there are no bad things in the syslog. Here's the snippet from lspci: 07:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller [1b4b:9235] (rev 11) DeviceName: Storage Controller Subsystem: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller [1b4b:9235] Kernel driver in use: ahci Kernel modules: ahci and I've attached my diagnostics for you to see for yourself that, for me at least, there's no problem with my Marvell controller and Unraid 6.7.0. So maybe there is something that affects the 9230 but not the 9235. northolt-diagnostics-20190513-0919.zip

The simple two and four port SATA controllers built around the Marvell 9230 or 9235 (or the 9220 or 9225) chip do indeed use the standard AHCI driver module. I had previously attributed my not having any problems with mine to that fact. The mvsas driver module is used by the eight-port SAS controllers that used to be popular amongst Unraid users - I have two that I can no longer use. So, to reiterate, Marvell makes both SATA and SAS controllers, based on different chips. The SATA controllers use the standard AHCI module and I've never had a problem with mine. The SAS controllers use the mvsas module and have been problematic for a few years. I haven't upgraded my server that uses the 9235 and it works fine with Unraid 6.6.7. I guess I'm going to have to bite the bullet and upgrade it to 6.7.0 to see if it's adversely affected. If it is, then our finding will agree. If it isn't then there's something else going on with your server.

If you want an 8-port card that fits in a long PCIe slot (x8) then there are several LSI-based cards to choose from. Used Dell Perc H310 cards pulled from servers are readily available on ebay and they represent good value for money, though they are usually set up in RAID mode and you need to cross-flash them with IT mode firmware. If you just want a 2-port card that fits in a short PCIe slot (x1) then look for one with an ASMedia chip, such as the ASM1061 or ASM1062. If you want a 4-port card with a PCIe x2 interface then you might well be out of luck. I haven't been able to find one other than those based on the Marvell 9230 or 9235.

I take it that you're being ironic, hence the italics, because there are already accompanying text descriptors. The text is there to help but you shouldn't need to read it. It's another visual clue, like colour and shape, but it's a final confirmation or a last resort in case the other two clues fail. If you need to take the time to read the text then the design of the icon has failed. It should be instantly and clearly recognisable. If you need to read the text in order to recognise the icon then there's no need for the icon, so you might as well take away the GUI and revert to pages of text with hyperlinks in them.

I notice that with the "white" theme the numbers on the disk usage bars are now quite difficult to read, especially on a red bar. EDIT: For comparison, here's how it looks under 6.6.7:

That's interesting. One of my servers has a SATA controller based on the similar Marvell 88SE9235 and it has never been any trouble. I had put that down to the fact that it uses the standard AHCI module rather than a driver specific to the chip but presumably the 9230 also uses the standard AHCI driver. The only difference I can see between the two chips is that the 9230 has hardware RAID capability while my 9235 doesn't. I think I would struggle to find a suitable replacement if I suddenly become unable to use my controller. The 923x has a x2 PCIe interface and provides four 6 Gb/s SATA ports. My particular card has two internal SATA ports and two eSATA ports and I don't know of any alternative that provides the same functionality. That said, I don't have IOMMU enabled on that server though I think I'll leave it on version 6.6.7 for a while longer until I've got time to experiment with it properly.

The thing about the indicators is that they were originally coloured balls of identical shape. Changing the shape of the red ball to a red cross was a positive move in that it made the shape distinctive while keeping the colour. That added information and helped everyone by increasing the number of visual cues. Changing application and configuration icons from coloured ones to monochrome ones has taken away information because they are now distinguishable only by their shape. Also, the new icons are less obvious in their meaning, being more simplistic and somewhat cryptic. I rather liked the skeuomorphic can of sardines VM Manager icon and it was very easy to spot on the Settings page but I'm sure I'll get used to the split-in-two monitor icon.

I agree and I mentioned the fact during the rc phase but it seems our preference for function over style puts us in a minority.