John_M

There's Apple Screen Sharing that's built into macOS. It works well between Macs but I don't know if there's a Windows client.

Since upgrading to Unraid 6.8-rc series I'm seeing the weekly scheduled integrity check abort with exit status 126: Oct 27 06:00:01 Mandaue crond[1772]: exit status 126 from user root /boot/config/plugins/dynamix.file.integrity/integrity-check.sh &> /dev/null @bonienl Likely a consequence of the permissions change on the boot flash device that now prevents scripts from being executed directly from the flash?

Cool. Thank you so much. That's good to know.

Do you have to take any special precautions to make sure they never both transcode at the same time, or it is simply not an issue?

Here's mine, if it helps. It's unedited by me - any changes have been made by the system itself. It seems to consist mostly of comments. sshd_config

Yes, it's pretty impressive, really. My favourite example is a five member RAID10.

It would be useful if the original post could be updated to insert the missing linefeeds.

That looks good now. The view you had mid-balance showed that some of the metadata had been converted to RAID1, while some remained as single, pending conversion.

One the Home page, click on the "cache" device to open its window. Scroll down to the Balance Status section and to the right of the Balance button enter the following -dconvert=raid1 -mconvert=raid1 then click the Balance button.

I recall it being mentioned somewhere before and being confirming as a bug. If you're worried that the healthy members of your cache pool might be overwritten by the bad data on your once missing, now returned disk you can wipe it. You should see it under the Unassigned devices heading on the Main page. Make a note of its device name, sdX. In a terminal window type wipefs /dev/sdX and double, triple check before you press RETURN that you're wiping the correct disk. Then reassign it to its rightful slot in the cache pool and let the system format it and rebalance the pool.

One of the disks in your cache pool dropped offline: Oct 13 10:56:02 Tower kernel: BTRFS warning (device sdr1): devid 3 uuid 1d8f16d9-c1d4-4ba2-8a87-729545783443 is missing probably due to a cable problem. You ought to have grabbed diagnostics at that point (Tools -> Diagnostics) and posted the resulting zip file. Syslog fragments are of very limited use - in this case it showed what happened, but not why. When Unraid notices a disk missing from the cache pool it will rebalance the pool to protect the data on the remaining disk(s) in the pool as much as it can. If I understand correctly, the missing disk has now reappeared after a reboot and you want to add it back to the pool? Before you do, I recommend shutting down, checking its cables, then rebooting and grabbing diagnostics. If the disk is properly recognised and in good health then you can re-allocate it to its former slot and it will be reformatted and the pool will be rebalanced again. When it has completed rebalancing everything should be as it was before. That's the meaning of the message that the disk will be overwritten - it will be overwritten with data from the remaining healthy members of the pool, which is exactly what you want.

I'm not trying to set this up right now but I'm trying to follow the discussion. What is the significance of the 10.253.0.0/24 subnet, which is used but not explained? Is it used by the tunnel?

There are longstanding problems with Marvell controllers and as newer Linux kernels are introduced the problems just get worse. Just Google "unraid marvell" and see for yourself. You can get second hand Dell H310s on Ebay. They are mostly pulled from servers and they are great value for money. That's what a lot of Unraid users are using now. The only nuisance is that they don't work "out of the box" as they generally come configured with RAID firmware. There are guides on this forum and elsewhere (they are popular with FreeNAS users and Serve The Home subscribers too) for crossflashing them to LSI IT firmware. The ASMedia ASM1062 is a simple two-port SATA card that works well (plug and play) with Unraid if you connect the disks to it directly, without a port multiplier.

It was recognised but it has dropped off line. Is it connected to a SATA port multiplier? Oct 11 21:18:23 Tower kernel: ata9: softreset failed (1st FIS failed) Oct 11 21:18:23 Tower kernel: ata9: limiting SATA link speed to 3.0 Gbps Oct 11 21:18:28 Tower kernel: ata9: softreset failed (device not ready) Oct 11 21:18:28 Tower kernel: ata9: reset failed, giving up Oct 11 21:18:28 Tower kernel: ata9.00: disabled Oct 11 21:18:28 Tower kernel: sdk: detected capacity change from 8001563222016 to 0

It's a lost cause - I realised that when I was told that icons aren't intended to be functional, just eye candy. I've given up whining and moved on.

I agree with Squid - those are virtual network ports. If you do have a problem that syslog snippet doesn't show it. Post your full diagnostics zip if you think there's some issue. The Mover doesn't use the network so it would be unaffected by a network problem anyway.

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.

@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