zachamo

Update: printer stopped working after a docker image update and I had to update the driver in CUPS to get it working again (the new driver name was identical except Gutenprint 5.3.4 vs. 5.3.5). I also noticed network discovery stopped working at some point. Fortunately the printer can be manually added via IPP.. Not a universal fix as MacOS didn't like anything /after/the/port and my kid's school Chromebook wants to hit the local network via external proxy, but other devices accepted it as a manually added IPP printer at [IP.of.UnraidServer]:631/printers/[CUPSprintername]. This matches the URL of the printer's config page, so opening the CUPS-Airprint WebUI from the Unraid web interface then navigating to your printer will provide the necessary IPP connection string (if your printer's config is available at http://123.456.789:631/printers/awesomeprinter, the IPP printer address is 123.456.789:631/printers/awesomeprinter). Not sure what broke network discovery - could have been the docker image update, Unraid 7 (suspected), or a router update.. Looking like this will be a tough one to troubleshoot - network issues are rarely easy, and obscure protocols don't help. CUPS documentation seems to focus on connecting to network printers rather than getting network devices connected to CUPS.. Does a great job of communicating with old printers, but it seems to miss the mark on making them readily available. Kudos to the devs of this fork for trying to bridge the gap - hope to get things working smoothly some day.

This was a lifesaver for an old Canon MX870 printer! No longer supported by Canon, not a 'plug-and-play' printer for most devices, and what drivers can be found are a nuisance for anything but Windows. A few quick notes from my experience: In the end I was able to add it as an lpd network printer using the included Gutenprint driver and this connection string: lpd://[IP.Address.Here]/queue Will play around a bit to see if I can get another protocol working, but getting this working is a huge improvement! I wasn't able to use bonjour discovery via the web UI nor console's 'lpinfo --include-schemes dnssd -v' for some reason. Had to add Root to the lpadmin group to get around a permission error, but no results listed once I got around this issue.. Adding root to lpadmin: adduser root lpadmin

That's the point -- I didn't come across other instances of people discussing this specific error in relation to a PCI-E slot's use.. It isn't like the SATA slots were disabled; the disks were still available, they just started misbehaving. Nothing in the manual that clearly lays out this kind of limitation so far as I can see. I did include my mobo in the post btw:

Hey All! tldr; adding a GPU in PCI-E slot 3 of my Motherboard causes my array hard drives to throw UDMA CRC errors. Not expressly looking for support, but wanted to share my experience as I wasn't able to find other posts on this sort of issue.. I'd rather not have to rebuild parity again if I can avoid it and don't want to risk any data loss. A second GPU is a nice-to-have in my case, but I can live without it. I recently picked up an older GPU (AMD 7870) and had an even older GPU thrown in for free.. After adding the new GPU and booting unraid, I started getting UDMA CRC errors on my array drives within an hour - this caused issues with parity.. After some troubleshooting I figured out that it was the GPU, so I swapped the 7870 for the second older GPU figuring I got a dud.. Same thing happened again - more UDMA CRC errors.. Never encountered these errors before, and after removing the second GPU I haven't seen them again.. UDMA CRC seems to typically be related to bad SATA connections or cables, but this clearly isn't the issue here. After some reading I discovered that the lower PCIE SLOT is connected to the southbridge chipset, not the CPU directly.. I'm guessing I either have a defective motherboard (issues specific to this PCI slot) or the combination of 4 SATA devices, an M.2, and a GPU is too much for the chipset. Motherboard: ASUS TUF GAMING X570-PLUS (WI-FI) BIOS 4602 CPU: Ryzen 3900x 1000w power supply 1 x M.2 3 x SATA 7200 3.5" HDs 1 x SATA SSD