DaveHavok

Same here! The ITE-IT87 Driver install fixed my fan detection for my motherboard: Gigabyte X99P-SLI-CF. Many thanks for the Developer - XOXO!

Thanks @dlandon! I reverted my SMB extras configuration back to this with all the fruit settings removed and it eliminated the synthetic_pathref errors that were generating previously: #unassigned_devices_start #Unassigned devices share includes include = /tmp/unassigned.devices/smb-settings.conf #unassigned_devices_end [global] spotlight backend = tracker [system] path = /mnt/user/system veto files = /._*/.DS_Store/ delete veto files = yes spotlight = yes I'll take a look the /etc/samba/smb-fruit.conf steps you mentioned from a previous post. Cheers.

Same issues here with 6.11.1 My logs are flooded with this error: Oct 17 12:15:15 OrigamiNET smbd[17095]: [2022/10/17 12:15:15.334182, 0] ../../source3/smbd/files.c:1193(synthetic_pathref) Oct 17 12:15:15 OrigamiNET smbd[17095]: synthetic_pathref: opening [filepath/file:AFP_AfpInfo] failed Here is my Samba extra configuration: [global] vfs objects = catia fruit streams_xattr fruit:nfs_aces = no fruit:zero_file_id = yes fruit:metadata = stream fruit:encoding = native spotlight backend = tracker [system] path = /mnt/user/system veto files = /._*/.DS_Store/ delete veto files = yes spotlight = yes Would appreciate any guidance here as it's dragging my server operations down. Also - my foolish mistake here, but does anyone have a copy of the default unRAID Samba extra configuration so I can revert back to defaults for testing purposes? Thank you.

That is a valid point. Hmmm. If anything - Maybe I'll replace the fans on the existing ones I have to improve cooling, noise levels, and get a new fan in there.

Thanks for the feedback @Whaler_99 and @kizer! Such a tricky situation. I love my 5-in-3 Icy Docks with trays, but wanted to try something new. The loose fit with the hard drives in trayless cages seem to be the common complaint and drive vibration being a concern. Hmmm. Such a tough call before grabbing 4 for a new case build out.

Has anyone tried the newer iStar ISTAR BPN-DE350HD 5-in-3 cages yet? I'm curious on the build quality and if the fans needs to be replaced. Appreciate any feedback before buying 4 of these. I've been using Icy Dock for YEARS now, but wanted to try something new (more silent, better cooling, etc.)

Spotted this Antec 1200 (Refurbished) - I can't vouch for the vendor: https://www.priceblaze.com/CAP1200V3-Antec-Power-Supply?ref=gshp I was interested in an Antec 1200 myself, but it's just way too heavy of a case for me. Good luck!

Many thanks for the information @BlinkerFluidand @ChatNoir!

Hello fellow Data Horders! I had a question about Server Rack Mounts as I'm looking at building out a new setup for my UnRAID server and have been looking at these 24 hard drive bay cases like as seen here: https://www.amazon.com/Norco-Mount-Hot-Swappable-Server-RPC-4224/dp/B00BQY3916 Questions: 1.) Is it possible to have multiple Server Rack Mounts connected to a single instance of UnRAID? I know there is currently a 30 drive limited under the Pro license, but I'm thinking for down the road should this limit be increased. 2.) If it is possible to connect multiple racks, how would this be accomplished? 3.) Any recommended brands for a 24-bay hard drive Server Rack mount case? 4.) Any other gotchas I should be aware of from switching from a mid tower case to a server rack mount setup? Thank you for any assistance you can provide! Cheers!

Hello @paloooz! Some quick questions - I'm looking at doing a rebuild of my server for increased hard drive storage and was curious what the drive capacity of yours is. Also, are you using hard drive cages? What's holding your hard drives in this setup! Thank you for any info you can provide! Cheers! UPDATE: I may have answered my own question looking at these: https://www.amazon.com/Rosewill-Rackmount-Computer-Pre-Installed-RSV-R4000/dp/B00N9CXGSO?th=1

Thanks for the quick response on this @JorgeB! I've been looking for an excuse to do some UNRAID server upgrades

https://myaccount.google.com/apppasswords This will instantly solve your problems.

So you can't have spaces in the path name? That makes no sense at all since all my other Dockers have no issues with spaces. I've been at this for hours and stuck with this error message: Warning: SimpleXMLElement::addChild(): unterminated entity reference Comics =/= eComics =/ in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 211 Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="ubooquity" --net="bridge" -e TZ="America/Los_Angeles" -e HOST_OS="unRAID" -e "MAXMEM"="512" -e "PUID"="99" -e "PGID"="100" -p 2202:2202/tcp -p 2203:2203/tcp -v "":"/books":ro -v "":"/comics":ro -v "/mnt/user/appdata/ubooquity":"/config":rw linuxserver/ubooquity /usr/bin/docker: Error response from daemon: Invalid volume spec ":/comics:ro": Invalid volume specification: ':/comics:ro'. See '/usr/bin/docker run --help'. The command failed.

This plugin saved my ass!!! THANK YOU! THANK YOU! OMG THANK YOU!!!!

Awesome! Thanks johnnie!

Is it possible to use an External HDD Enclosure via USB3 connection in place of a HDD Backplate Cage that has a bad slot in order to restore the array into a protected state again? Looking to do this as a temporary fix until the replacement HDD Backplate Cage arrives.

And I spoke too soon... sigh. After some extensive hardware testing, I've confirmed that the backplate is the issue here as it's having problems reading the drive from time to time. Bypassing the backplate confirms this issue. Unfortunately, the Icy Dock HDD cages are a pain in the ass to track down right now... some sort of shortage it looks like as the pricing is very inflated on the MB155SP-B. In the mean time, is it OK to plug the drive into an external SATA enclosure so I can keep the array protected until I can find a replacement HDD cage? Basically putting the drive back into the array using an external SATA enclosure since the bay that the drive was in is bad. Thanks!

Hi John! Looks like I'm still good to go. No errors at all. As for the IOMMU, I don't currently have a need for it as this server is purely running the Dockers I have listed in my sig. However, if unRAID gave me the ability to setup a HyperSpin Docker instance, I could see the potential need for hardware pass-through for game system emulators, and reading the USB slots for Bluetooth dongles and game controllers. Thanks again!

Well I'll be damned! No errors since the change! It's been about 9 hours with nothing weird at all! I'm heading to bed to give it some more time before declaring all good, but I'm just surprised that it was just that single BIOS adjustment to fix this! Thanks for the second set of eyes on this John! Much appreciated.

I'm not really seeing any of the errors that's mentioned in that thread, well nothing that's a solid match for my problem. I'm running the newest firmware for the card also: 4.0.0.1812 UPDATE: I take that back John, I do believe I am seeing what you're taking about with the IOMMU and Marvell chipset cards. So far, I'm just seeing this same error going back and forth between ATA7 and ATA8. They switch out for hours at a time on being reported. - Finished another extended SMARTCheck on the drive. Passed - Parity Check completed and No Errors Found (Array is up and Protected) However, I'm still seeing a few of these popping up every now and then: Dec 12 06:14:01 OrigamiNET kernel: ata8.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen Dec 12 06:14:01 OrigamiNET kernel: ata8.00: irq_stat 0x08000002, interface fatal error Dec 12 06:14:01 OrigamiNET kernel: ata8: SError: { UnrecovData 10B8B BadCRC } Dec 12 06:14:01 OrigamiNET kernel: ata8.00: failed command: SMART Dec 12 06:14:01 OrigamiNET kernel: ata8.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 4 pio 512 in Dec 12 06:14:01 OrigamiNET kernel: res 50/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Dec 12 06:14:01 OrigamiNET kernel: ata8.00: status: { DRDY } Dec 12 06:14:01 OrigamiNET kernel: ata8: hard resetting link Dec 12 06:14:02 OrigamiNET kernel: ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Dec 12 06:14:02 OrigamiNET kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359) Dec 12 06:14:02 OrigamiNET kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT1.SPT3._GTF] (Node ffff88082f523bb8), AE_NOT_FOUND (20150930/psparse-542) Dec 12 06:14:02 OrigamiNET kernel: ata8.00: supports DRM functions and may not be fully accessible Dec 12 06:14:02 OrigamiNET kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359) Dec 12 06:14:02 OrigamiNET kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT1.SPT3._GTF] (Node ffff88082f523bb8), AE_NOT_FOUND (20150930/psparse-542) Dec 12 06:14:02 OrigamiNET kernel: ata8.00: supports DRM functions and may not be fully accessible Dec 12 06:14:02 OrigamiNET kernel: ata8.00: configured for UDMA/33 Dec 12 06:14:02 OrigamiNET kernel: ata8: EH complete Dec 12 02:00:47 OrigamiNET kernel: ata7.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen Dec 12 02:00:47 OrigamiNET kernel: ata7.00: irq_stat 0x08000000, interface fatal error Dec 12 02:00:47 OrigamiNET kernel: ata7: SError: { UnrecovData 10B8B BadCRC } Dec 12 02:00:47 OrigamiNET kernel: ata7.00: failed command: READ DMA EXT Dec 12 02:00:47 OrigamiNET kernel: ata7.00: cmd 25/00:40:00:35:33/00:05:c0:00:00/e0 tag 0 dma 688128 in Dec 12 02:00:47 OrigamiNET kernel: res 50/00:00:37:62:16/00:00:75:00:00/e0 Emask 0x10 (ATA bus error) Dec 12 02:00:47 OrigamiNET kernel: ata7.00: status: { DRDY } Dec 12 02:00:47 OrigamiNET kernel: ata7: hard resetting link Dec 12 02:00:48 OrigamiNET kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Dec 12 02:00:48 OrigamiNET kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359) Dec 12 02:00:48 OrigamiNET kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT1.SPT2._GTF] (Node ffff88082f523b40), AE_NOT_FOUND (20150930/psparse-542) Dec 12 02:00:49 OrigamiNET kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359) Dec 12 02:00:49 OrigamiNET kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT1.SPT2._GTF] (Node ffff88082f523b40), AE_NOT_FOUND (20150930/psparse-542) Dec 12 02:00:49 OrigamiNET kernel: ata7.00: configured for UDMA/133 Dec 12 02:00:49 OrigamiNET kernel: ata7: EH complete

Thanks for taking a look John. I just finished the Disk Rebuild on the drive and the array is back up and running again in protected state. -The next step is to do a Parity Check with the "Make Corrections to Parity Drive" unchecked. -Fix the ACPI Exception with this http://lime-technology.com/forum/index.php?topic=45920.0 However, I noticed in the Sys Log that the reported errors went from ATA8 to ATA7 about half way through the rebuild process. The IOMMU is a new one on me and will have to review the provided thread and follow up with you. origaminet-diagnostics-20161211-1856.zip

Quick question - Could dust or a slightly loose connection cause this error: Dec 11 13:36:00 OrigamiNET kernel: ata8.00: supports DRM functions and may not be fully accessible Dec 11 13:36:00 OrigamiNET kernel: ata8.00: configured for UDMA/33 Dec 11 13:36:00 OrigamiNET kernel: ata8: EH complete Dec 11 13:36:33 OrigamiNET kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x880000 action 0x6 frozen Dec 11 13:36:33 OrigamiNET kernel: ata8: SError: { 10B8B LinkSeq } Dec 11 13:36:33 OrigamiNET kernel: ata8.00: failed command: WRITE DMA EXT Dec 11 13:36:33 OrigamiNET kernel: ata8.00: cmd 35/00:40:a0:a0:97/00:05:a4:00:00/e0 tag 2 dma 688128 out Dec 11 13:36:33 OrigamiNET kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 11 13:36:33 OrigamiNET kernel: ata8.00: status: { DRDY } Dec 11 13:36:33 OrigamiNET kernel: ata8: hard resetting link Dec 11 13:36:34 OrigamiNET kernel: ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310) I'm just seeing the SError: { 10B8B LinkSeq } issue now instead of the previous { UnrecovData HostInt 10B8B BadCRC } UPDATE: Attaching full Sys Log incase I'm missing something origaminet-syslog-20161211-1355.zip

Well that sucks Looks like the Icy Dock MB455SPF-B is no longer manufactured, and the few units for sale are at super mark up prices. Looks like I'm in the market for a new case that can hold 15+ drives and has good cable management. Any suggestions or recommendations? UPDATE: I might just swap out the defective dock for the newer version: Icy Dock FatCage MB155SP-B

UPDATE: - Replaced my AOC-SASLP-MV8 with a AOC-SAS2LP-MV8 - Replaced all cables The issue with Drive 5 continues. The drive itself appears to be fine, but it intermittently appears and disappears from the BIOS hardware listing when rebooting. - Move the SATA cable for Drive 5 to a different port. No change and the issue continues with intermittently detecting the drive. - Swapped drives out just to humor myself and the same behavior continues with the swapped drive. At this point, I suspect that the Icy Dock bay itself is going bad. Bypassing the Icy Dock bay and doing a direct connection to the drive would confirm that. Just seems so odd that the Icy Dock itself is starting to go bad. Maybe I should just replace the entire case and forgo the Icy Dock bays all together and get something that allows for easier motherboard access for cable management. Back at it again. Sigh.