polishprocessors

I'm never seeing my BigSur/Monterey (tried both) disks upon first reboot after the initial config and disk erase/reconfig - only getting macOS Base System, macOS Installer, Recovery, UEFI Shell, and reset NVRAM. Before this newest version I was able to see the new BigSur disk I created. If I pick either of the first two options it takes me back through the initial install process but my BigSur disk is already formatted. I'm using default settings otherwise and I've tried deleting the scripts, docker, and deleting the appdata twice and retrying, but with the same results...

late responding to this, but yes, I was able to rename the file in /boot from Media to media with no issues. I backed it up to be safe and it took a reboot to apply, but it worked.

Having similar issues-no matter what I pick (option 1 or 2) I end up with Monterey and then, no matter what I do, once I try to change the EFI settings it will no longer boot. I guess Spaceinvaderone needs to update the docker/scripts to support Monterey (or allow us to select an older version again), but in the meantime I guess we're dead in the water for new installs...

Actually I said I'd try by preclearing the drive, but I get those same blk_update_request: I/O error messages when I try that and, when I try to unmount the drive, I get the following error: Dec 7 15:25:27 unRaid unassigned.devices: Remove partition failed: 'Warning: Error fsyncing/closing /dev/sdh1: Input/output error Warning: Error fsyncing/closing /dev/sdh: Input/output error Warning: Error fsyncing/closing /dev/sdh1: Input/output error Error: /dev/sdh: unrecognised disk label Warning: Error fsyncing/closing /dev/sdh: Input/output error '.

Per title, trying to remove a 4TB drive from the array, move a 10TB parity into the array and replace the 10TB with a 14TB. However, when I start the 'copy' procedure, I get the following errors in the logs: Dec 7 15:17:48 unRaid kernel: sd 9:0:0:0: [sdh] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s Dec 7 15:17:48 unRaid kernel: sd 9:0:0:0: [sdh] tag#22 CDB: opcode=0x8a 8a 00 00 00 00 00 10 0b 23 88 00 00 00 a8 00 00 Dec 7 15:17:48 unRaid kernel: blk_update_request: I/O error, dev sdh, sector 269165448 op 0x1:(WRITE) flags 0x104000 phys_seg 168 prio class 0 Dec 7 15:17:48 unRaid kernel: sd 9:0:0:0: [sdh] tag#23 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s Dec 7 15:17:48 unRaid kernel: sd 9:0:0:0: [sdh] tag#23 CDB: opcode=0x8a 8a 00 00 00 00 00 10 0b 24 30 00 00 00 a8 00 00 Dec 7 15:17:48 unRaid kernel: blk_update_request: I/O error, dev sdh, sector 269165616 op 0x1:(WRITE) flags 0x104000 phys_seg 168 prio class 0 Dec 7 15:17:48 unRaid kernel: sd 9:0:0:0: [sdh] tag#31 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s Dec 7 15:17:48 unRaid kernel: sd 9:0:0:0: [sdh] tag#31 CDB: opcode=0x8a 8a 00 00 00 00 00 10 0b 24 d8 00 00 00 a8 00 00 Dec 7 15:17:48 unRaid kernel: blk_update_request: I/O error, dev sdh, sector 269165784 op 0x1:(WRITE) flags 0x104000 phys_seg 168 prio class 0 Dec 7 15:17:48 unRaid kernel: sd 9:0:0:0: [sdh] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s Dec 7 15:17:48 unRaid kernel: sd 9:0:0:0: [sdh] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 10 0b 25 80 00 00 00 a8 00 00 Dec 7 15:17:48 unRaid kernel: blk_update_request: I/O error, dev sdh, sector 269165952 op 0x1:(WRITE) flags 0x104000 phys_seg 168 prio class 0 Dec 7 15:17:48 unRaid kernel: sd 9:0:0:0: [sdh] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s Dec 7 15:17:48 unRaid kernel: sd 9:0:0:0: [sdh] tag#1 CDB: opcode=0x8a 8a 00 00 00 00 00 10 0b 26 28 00 00 00 a8 00 00 Dec 7 15:17:48 unRaid kernel: blk_update_request: I/O error, dev sdh, sector 269166120 op 0x1:(WRITE) flags 0x104000 phys_seg 168 prio class 0 sdh is the new 14TB drive. I have stopped the copy and restored the array as before and am running a preclear on the new drive, but should I be worried the new drive is already bad? Additionally, when I opened the case and swapped out the 4TB for the 14TB, on restarting the array I got this error on the 10TB drive: Warning [UNRAID] - udma crc error count is 2 Just want to make sure I don't have any drives that are about to fail before I swap them over...

Actually I had renamed my Media folder to media but it shows up in /boot/config/shares as Media.cfg Think it’s safe to rename that to media.cfg ?

Ahh, yes, I changed my media folder to lower-case m to avoid issues elsewhere. Where can I adjust the config file to fix this…?

Hey there! I have this plugin installed and set to run the mover at 60% cache utilization with a run frequency of every 3 hours. However, my cache keeps getting over 60% and failing to move. If I run the mover manually it works fine so I changed the 'move now button follows plugin fliters’ option to ‘yes’ and ran it again. Here’s my output: Sep 27 19:05:59 unRaid root: mvlogger: *********************************MOVER START******************************* Sep 27 19:05:59 unRaid root: mvlogger: Age supplied Sep 27 19:05:59 unRaid root: mvlogger: Size supplied Sep 27 19:05:59 unRaid root: mvlogger: Sparness supplied Sep 27 19:05:59 unRaid root: mvlogger: No Skipfiles Argument Supplied Sep 27 19:05:59 unRaid root: mvlogger: No Skipfiles Argument Supplied Sep 27 19:05:59 unRaid root: mvlogger: No Before Script Argument Supplied Sep 27 19:05:59 unRaid root: mvlogger: No After Script Argument Supplied Sep 27 19:05:59 unRaid root: mvlogger: CTIME Argument: no Sep 27 19:05:59 unRaid root: mvlogger: CACHE THRESH to Move all Cache-Yes shares to array: 65 Sep 27 19:05:59 unRaid root: mvlogger: No Test Mode Argument Supplied Sep 27 19:05:59 unRaid root: mvlogger: No Ignore Hidden Files Argument Supplied Sep 27 19:05:59 unRaid root: mover: started Sep 27 19:05:59 unRaid root: mvlogger: No Script to Run. Sep 27 19:05:59 unRaid root: mvlogger: CACHETHRESH: 65 Sep 27 19:05:59 unRaid root: mvlogger: Checking to see if we should all files from share. Sep 27 19:05:59 unRaid root: mvlogger: Move All Cache Threshold: 65 Sep 27 19:05:59 unRaid root: mvlogger: /mnt/cache PCT USED: 85 Sep 27 19:05:59 unRaid root: mvlogger: Pool /mnt/cache is above 'move all' percentage, moving all cache-yes shares to array Sep 27 19:05:59 unRaid root: mvlogger: Not in Test mode Sep 27 19:05:59 unRaid root: find: unknown predicate `-depth+= | /usr/local/sbin/move -d 1' Sep 27 19:05:59 unRaid root: mvlogger: Complete Mover Command: find /mnt/cache/media -depth Sep 27 19:05:59 unRaid root: mvlogger: Done checking Move All from Share Sep 27 19:05:59 unRaid root: mvlogger: Share Name Only: Media Sep 27 19:05:59 unRaid root: mvlogger: Cache Pool Name: cache Sep 27 19:05:59 unRaid root: mvlogger: cache Threshold Pct: Sep 27 19:05:59 unRaid root: mvlogger: OVERALL Threshold: 60 Sep 27 19:05:59 unRaid root: mvlogger: Share Path: /mnt/cache/Media Sep 27 19:05:59 unRaid root: mvlogger: Pool Pct Used: 85 % Sep 27 19:05:59 unRaid root: mvlogger: DFTPCT LIMIT USED FOR SETTING: 60 Sep 27 19:05:59 unRaid root: mvlogger: Threshold Used: 60 Sep 27 19:05:59 unRaid root: mvlogger: Adding Age Sep 27 19:05:59 unRaid root: mvlogger: Age 1 Sep 27 19:05:59 unRaid root: mvlogger: Skipfiletypes string: find "/mnt/cache/Media" -depth -mtime +1 Sep 27 19:05:59 unRaid root: mvlogger: Not in Test mode Sep 27 19:05:59 unRaid root: mvlogger: Complete Mover Command: find "/mnt/cache/Media" -depth -mtime +1 Sep 27 19:05:59 unRaid root: find: '/mnt/cache/Media': No such file or directory Sep 27 19:05:59 unRaid root: mover: finished Sep 27 19:05:59 unRaid root: mvlogger: No After Script to Run. and some settings for reference: Any thoughts on what might be happening?

I've noticed in this version of MariaDB it seems the following are set to Swedish: collation_databaselatin1_swedish_ci collation_serverlatin1_swedish_ci Is it possible to either switch this to something unicode or manually change the defaults ourselves, as this is causing some issues with some of my other containers trying to use databases. I presume those devs can also hard-code their collation choice, but it'd be nice to change it at this level, too..

Ok, something of an update: it might actually just be the specific RAW filetype (Fuji .raf) isn't properly handled by DarkTable and instead needs to be processed by RawTherapee. I've created an issue to have the devs force Fuji .raf files to be processed by RawTherapee instead... https://github.com/photoprism/photoprism/issues/1362

The devs, due to the errors, think it might be a metadata string issue: -Looks like the photo location can't be created properly due to a broken metadata string. Need to know what it is specifically to provide a fix if needed. -Might be related to the location details, which our backend returns... so it would be good to test as guessing takes a lot of time I'll send you a PM with a RAW file, but any idea what metadata strings might be broken?

To be specific (and I’m also chatting with the devs) I’ve done the following: started from scratch, ran the purge script, deleted the docker, dropped the database, and re-installed from the start (in Unraid) and it looks like the final verdict is: all RAW files of mine (from two separate cameras) appear to be broken. PP appears to process it, save it as a .jpeg, and stack it with the original, but then doesn’t display it. I see nothing obvious that should be blocking my permissions and the files themselves, if I ‘Download’ them from PP, look fine, so I’m guessing it’s a thumbnail issue? Errors in the logs when indexing completes but before I view anything are mostly: time="2021-06-07T00:34:44+02:00" level=error msg="location: record not found (find cell s2:14cab798d68c)"
time="2021-06-07T00:34:45+02:00" level=error msg="location: Error 1366: Incorrect string value: '\xC5\x9Fikta...' for column photoprism.places.place_city at row 1 (create place s2:14cab7b3667c)"
time="2021-06-07T00:34:45+02:00" level=error msg="location: Error 1366: Incorrect string value: '\xC4\x9F\xC4\xB1' for column photoprism.cells.cell_name at row 1 (create cell s2:14cab7b3667c)" But once I pull up PP and try to browse any RAW files I see the following errors in the logs: time="2021-06-07T01:54:24+02:00" level=error msg="thumbs: thumbnail not cached"
time="2021-06-07T01:54:24+02:00" level=error msg="thumbs: thumbnail not cached" all my permissions in the container are for photoprism:users except /photoprism/storage/config, which is photoprism:root drwxr-xr-x 1 photoprism users 44 Jun 6 21:39 albums drwxr-xr-x 1 photoprism users 54 Jun 6 11:34 cache drwxr-xr-x 1 photoprism root 38 Jun 6 11:35 config drwxr-xr-x 1 photoprism users 444 Jun 6 18:37 sidecar

Reached out via chat and they pointed me here: https://github.com/photoprism/photoprism/issues/411 It *was* working, at least in large part, but seems to have taken a turn for the worse. At startup it often took ages (10+ minutes) to load, and the team said that was because it was running usermod, at which point they recommended I set PHOTOPRISM_DISABLE_CHOWN = true, which did speed up the start of the program but may have started some of my issues, though I'm not sure. I've completely removed PP, dropped the table in MariaDB, and deleted the storage path and reinstalled it, but had the same issue, primarily with .jpeg files working fine but some (though not all) RAW files not displaying. They're quite convinced it's a permissions issue and suggested I try changing the user it runs as, but given it *was* working on your defaults (plus a manual MariaDB config) I'm inclined to believe it's not the user itself...

Has anyone seen issues with PhotoPrism (running MariaDB) processing pictures (especially RAW ones), adding them to the library, but then showing a broken image icon instead? If I download either the .jpeg or the original RAW the image looks fine, it just seems like PhotoPrism isn't displaying them correctly. I've reached out to the dev team and they seem to think it's a permissions issue. I'm running UID/GID of 99:100...

Think I figured it out-need to have swag and any containers I want to kick it to on the same virtual network in docker

Ok, solved my issue to an extent. Whilst I have no idea why it's failing, I found this note in the SWAG proxy documentation: So I changed the $upstream_app to read, instead of the name of the container, the IP of the NAT'd IP of Docker. It works fine, but does anyone know why I have to do this and how to run it as default?

Hey all! So I thought I had this up and running - got LetsEncrypt to work, got some subdomains setup, changed my DNS entries to point the right way and redirected my FW appropriately. But now I'm getting the following errors in my nginx log: 2021/05/14 18:18:06 [error] 476#476: send() failed (111: Connection refused) while resolving, resolver: 127.0.0.11:53 2021/05/14 18:18:11 [error] 476#476: send() failed (111: Connection refused) while resolving, resolver: 127.0.0.11:53 2021/05/14 18:18:11 [error] 476#476: send() failed (111: Connection refused) while resolving, resolver: 127.0.0.11:53 I've seen this elsewhere in the thread but no one's answered what's going on. It seems to me like the local docker resolver isn't working but I don't know whether this is from me changing something or just something broken in my config. I've confirmed I can ping 127.0.0.11 so it just seems like it's being rejected. I've tried running the container as a host but all my requests come back with a 502 error, presumably because it's not on the same docker subnet as the other containers, but once I put it back on 'bridge' with the rest of the containers I get these resolve errors as above again. I've tried restarting docker and my whole unraid box, to no avail-does anyone have any thoughts?

Still no luck-if I try after clearing out the Plex Token I get a spinning wheel, but once I add the token that stops I just get no choices under Servers:

I’m running my Plex docker on the same IP (host mode) and, while I’m able to log into my Plex account when prompted to the (local) IP of my sever, but then I never see any servers populate. I am using secure connections for my Plex but not forcing it but I’ve tried both to no avail. No obvious errors in my log, either. Any suggestions? I’ve tried to log into plex multiple times and remove the plugin and reinstall it, but I never see a server and the plugin just says “Please make sure you have setup the plugin first”

/dev/bus/usb doesn't support any by-id options-nothing obvious in there that should, hence the flightradar@ symlink, but that doesn't seem to work...

Hey there-I've tried to reproduce this for my FlightAware USB device and I keep getting the following error: rtlsdr: error querying device #0: No such file or directory I think I've got it configured properly, as here's the lsusb/dev output: root@unRaid:/dev# ls -l flightradar lrwxrwxrwx 1 root root 15 Jan 4 16:50 flightradar -> bus/usb/001/023 root@unRaid:/dev# lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive Bus 001 Device 023: ID 0bda:2832 Realtek Semiconductor Corp. RTL2832U DVB-T Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bus 001 Device 004: ID 0b05:1872 ASUSTek Computer, Inc. AURA LED Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub But the FW24 docker container won't start with /dev/flightaware as its RTL-SDR Device. I have the following script configured to run hourly: #!/bin/bash # copy persistent script from usb drive to drive at startup cp /boot/config/rules.d/99-usb-rules.rules /etc/udev/rules.d/ chmod 644 /etc/udev/rules.d/99-usb-rules.rules # udav has likely run before the copy completes so udev needs its rules refreshed udevadm control --reload-rules # a reset of the device is needed so the rules just copied can take hold udevadm trigger --attr-match=subsystem=usb Off this .rules config: root@unRaid:/etc/udev/rules.d# more 99-usb-rules.rules SUBSYSTEM=="usb", ATTRS{idVendor}=="0bda", ATTRS{idProduct}=="2832", ATTRS{serial}=="00001000", SYMLINK+="flightradar" Can anyone help point me in the right direction? I just don't seem able to to get this to work, even though it looks like it should be just fine to me...

Does anyone else have issues with unraid changing the USB device ID regularly? I keep getting notifications from FlightAware because my RTL device is moving around between devices on one USB bus. This occurs if I plug anything into another USB port or, sometimes, when I don’t. Is there a way to lock a device to a specific ID within unraid/the OS? Edit: found this which fixed it: