Bushibot

I don't see this in the app repository for unraid? Is there working setup guide for unraid? I'm looking to kick flickr and this seems to have a nice public type view. All the other apps seem to only want to manage my photo's rather than share them :p. Alsu curious about the long file name issue. I down loaded my flickr archive and that dose liek to rename everything with their hash (anoying), so all long files names :p.

okay, well that was defaults. I didn't change anything there. that said - However still like to know, can I change the Docker data-root: to file system to prevent this? Will this happen gracefully, or do I then need to manually/reinstall everything? - Is there a good method to explore the image size? I'm guessing something is getting cached there that shouldn't because 20gig's seems a given the current container size it's still growing a bit...

Is files on the array bad? I'm not clear how that relates? Docker vDisk location: /mnt/user/system/docker/docker.img Default appdata storage location: /mnt/user/appdata/

Adjusting the docker size fixed the problem. It was not obvious to do that through the UI since when it's running it does not show any options about in settings docker.nas-mass-diagnostics-20230918-2339.zip - However still like to know, can I change the Docker data-root: to file system to prevent this? Will this happen gracefully, or do I then need to manually/reinstall everything? - Is there a good method to explore the image size? I'm guessing something is getting cached there that shouldn't because 20gig's seems a given the current container size it's still growing a bit...

So I figured out how to stop the image and see if I can resize it now. - However can I change the Docker data-root: to file system to prevent this? Will this happen gracefully, or do I then need to manually/reinstall everything? - Is there a good method to explore the image size? I'm guessing something is getting cached there that shouldn't because 20gig's seems a given the current container sizes.

Could be, I do see error stating Docker critical image disk utilization. How do I make that bigger? I didn't do anything to restrict it that I'm aware of.

I'm getting out of spare errors on app update but I can't figure out why. I seem to ahve plenty of space on cache and certainly on the arrary... Error: failed to register layer: ApplyLayer exit status 1 stdout: stderr: write /usr/lib/libpcre2-16.a: no space left on device I don't think I set any growth limits, I'm not sure why I'm hitting this.

I reran new permission tool on the shares. I had tried this before with zero change (several times, including the disk) but today when I did it worked for whatever reason and now I can mount the folders. Ambiguity in system behavior makes my skin itch, but I guess I'm good for now. post run pre run drwsrwsrwt 1 nobody users postrun -rw-rwSrwT 1 nobody users 4294939196 Feb 19 201 I'm not really clear on the difference between the two or what the cap S and T mean or which value is significant here. I assume it will come back but as long the tool actually works I guess I'll just file it as dumb work around. If nothing else I guess it show it is some sort of underlying permission issue or ownership thing.

nas-mass-diagnostics-20230912-1540.zip

So a little more on this. I thought it was only related to migrated data, but this is not the case. It's popping up all over with new folders now created through containers. What I have found is it seems related ownership. I can't access from windows/mac sub folders owned by nobody. I can access top level shares though and they are owned by nobody. I can access folders owned by root or griffon from windows/mac. Can't access windows/mac: drwsrwsrwt 1 nobody users 74 Sep 10 12:10 folder1/ Can access: drwsrwsrwt 1 griffon users 160 Sep 7 02:30 folder2/ Can access: drwxr-xr-x 1 root root 4096 Sep 8 23:43 folder 3/ I thought ok let me just change the ownership... but that didn't fix it either, folders taken by root still remain inaccessible right next to ones that are.

Is there a way through the unraid UI to set docker boot order a dependency check? For example to containers that should not come up until the DB container has finished starting. If it's not glaringly obvious I'm pretty ne to docker.

THAT did the trick, thank you.

Photoprism docker. I'm trying to replace flickr. Dose this support a public read only view. I looks like you have send out share links... I want to have a read only folder and stream view for anyone much like flickr...?

Thanks l’ll try that l

I plugged in a usb drive to get some data off it but it dose not seem to mount. I feel like I'm missing a step but I'm not sure what? I can see the drive and the share in unassigned devices but it does not seem to be accessible.

I see on LycheeOrg/Lychee-Docker SQL lite is included and you don't need a extra db container? Is that something we could have on the unraid lychee container too?

having some trouble getting remote access to work port for container was showing up as ???? so I added one. but I must have something wrong. Forwarded correctly on my router. Plex is claiming it's happy now but actually moving any data Command executiondocker run -d --name='binhex-plexpass' --net='host' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="nas-mass" -e HOST_CONTAINERNAME="binhex-plexpass" -e 'TRANS_DIR'='/config/transcode' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'NVIDIA_VISIBLE_DEVICES'='' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -e 'TCP_PORT_32400'='32400' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:32400]/web/index.html' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/plex-icon.png' -v '/mnt/user/datapool/':'/media':'rw' -v '/mnt/user/appdata/binhex-plexpass':'/config':'rw' 'binhex/arch-plexpass' 989a41b1eb395e113afb1f947f7d96db0317b90190e0d512bd3d69054d474fe8 Not seeing any errors though in plex log: 2023-09-09 13:58:03,390 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-09-09 13:58:17,690 DEBG 'plexmediaserver' stdout output: Critical: libusb_init failed 2023-09-09 14:13:22,155 DEBG 'plexmediaserver' stderr output: Jobs: Exec of /config/Plex Media Server/Codecs/EasyAudioEncoder-1847-linux-x86_64/EasyAudioEncoder/EasyAudioEncoder failed. (13) Was on old nas. Unraid plex works on LAN fine.

I'm going to test this, but I have moved so much stuff by hand I have to go back and setup a new broken one :p. I want to say my first rsync was just -r but I can't quite be sure.

Yeah, filebot isn’t actually doing anything. I just set it up to use to try and merge the folders. The duplicates occurred before filebot was even installed.

Duplicate folder issue It looks like Sonarr (I think) is creating duplicate media folders, helpfully with correct capitalization. The original folder structure was all lower case... I thought I could just CP them together, but SSH only shows the new folders Ashoka vs ashoka for example. I'm not quite sure how make the existing folder structure play nice...? The new downloads are going into the new directory's old ones have the legacy data. Argh filebot won't show the duplicates. So much for easy button.

Never mind I had missed the tiny format check box. Not super intuitive to not have the option on the drive or cache views :p.

text error warn system array login Sep 7 10:40:42 nas-mass kernel: ata2: SATA max UDMA/133 abar m2048@0xf7216000 port 0xf7216180 irq 34 Sep 7 10:40:42 nas-mass kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Sep 7 10:40:42 nas-mass kernel: ata2.00: supports DRM functions and may not be fully accessible Sep 7 10:40:42 nas-mass kernel: ata2.00: ATA-11: Samsung SSD 870 QVO 2TB, SVQ02B6Q, max UDMA/133 Sep 7 10:40:42 nas-mass kernel: ata2.00: 3907029168 sectors, multi 1: LBA48 NCQ (depth 32), AA Sep 7 10:40:42 nas-mass kernel: ata2.00: Features: Trust Dev-Sleep NCQ-sndrcv Sep 7 10:40:42 nas-mass kernel: ata2.00: supports DRM functions and may not be fully accessible Sep 7 10:40:42 nas-mass kernel: ata2.00: configured for UDMA/133 Sep 7 10:40:42 nas-mass kernel: ata2.00: Enabling discard_zeroes_data Sep 7 10:40:42 nas-mass kernel: sd 3:0:0:0: [sdg] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB) Sep 7 10:40:42 nas-mass kernel: sd 3:0:0:0: [sdg] Write Protect is off Sep 7 10:40:42 nas-mass kernel: sd 3:0:0:0: [sdg] Mode Sense: 00 3a 00 00 Sep 7 10:40:42 nas-mass kernel: sd 3:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Sep 7 10:40:42 nas-mass kernel: sd 3:0:0:0: [sdg] Preferred minimum I/O size 512 bytes Sep 7 10:40:42 nas-mass kernel: ata2.00: Enabling discard_zeroes_data Sep 7 10:40:42 nas-mass kernel: sdg: sdg1 sdg2 Sep 7 10:40:42 nas-mass kernel: sd 3:0:0:0: [sdg] Attached SCSI disk Sep 7 10:40:55 nas-mass emhttpd: Samsung_SSD_870_QVO_2TB_S6R4NJ0R701417P (sdg) 512 3907029168 Sep 7 10:40:55 nas-mass emhttpd: read SMART /dev/sdg Sep 7 10:49:45 nas-mass emhttpd: Samsung_SSD_870_QVO_2TB_S6R4NJ0R701417P (sdg) 512 3907029168 Sep 7 10:49:45 nas-mass emhttpd: import 30 cache device: (sdg) Samsung_SSD_870_QVO_2TB_S6R4NJ0R701417P Sep 7 10:49:45 nas-mass emhttpd: read SMART /dev/sdg Sep 7 10:49:54 nas-mass emhttpd: Samsung_SSD_870_QVO_2TB_S6R4NJ0R701417P (sdg) 512 3907029168 Sep 7 10:49:54 nas-mass emhttpd: import 30 cache device: (sdg) Samsung_SSD_870_QVO_2TB_S6R4NJ0R701417P Sep 7 10:49:54 nas-mass emhttpd: read SMART /dev/sdg Sep 7 10:50:24 nas-mass emhttpd: shcmd (600): /usr/sbin/cryptsetup luksErase /dev/sdg1 Sep 7 10:50:24 nas-mass root: Device /dev/sdg1 is not a valid LUKS device. Sep 7 10:50:24 nas-mass emhttpd: shcmd (601): /sbin/wipefs -a /dev/sdg1 Sep 7 10:50:24 nas-mass emhttpd: shcmd (602): /sbin/wipefs -a /dev/sdg Sep 7 10:50:24 nas-mass kernel: ata2.00: Enabling discard_zeroes_data Sep 7 10:50:24 nas-mass root: /dev/sdg: 8 bytes were erased at offset 0x00000200 (gpt): 45 46 49 20 50 41 52 54 Sep 7 10:50:24 nas-mass root: /dev/sdg: 8 bytes were erased at offset 0x1d1c1115e00 (gpt): 45 46 49 20 50 41 52 54 Sep 7 10:50:24 nas-mass root: /dev/sdg: 2 bytes were erased at offset 0x000001fe (PMBR): 55 aa Sep 7 10:50:24 nas-mass root: /dev/sdg: calling ioctl to re-read partition table: Success Sep 7 10:50:26 nas-mass emhttpd: Samsung_SSD_870_QVO_2TB_S6R4NJ0R701417P (sdg) 512 3907029168 Sep 7 10:50:26 nas-mass emhttpd: import 30 cache device: (sdg) Samsung_SSD_870_QVO_2TB_S6R4NJ0R701417P Sep 7 10:50:26 nas-mass emhttpd: read SMART /dev/sdg Sep 7 11:02:19 nas-mass emhttpd: /sbin/btrfs filesystem show /dev/sdg1 2>&1 Sep 7 11:02:19 nas-mass emhttpd: ERROR: not a valid btrfs filesystem: /dev/sdg1 Sep 7 11:02:19 nas-mass emhttpd: /usr/sbin/zpool import -d /dev/sdg1 2>&1 Sep 7 11:05:47 nas-mass emhttpd: read SMART /dev/sdg Sep 7 11:05:56 nas-mass emhttpd: Samsung_SSD_870_QVO_2TB_S6R4NJ0R701417P (sdg) 512 3907029168 Sep 7 11:05:56 nas-mass emhttpd: import 30 cache device: (sdg) Samsung_SSD_870_QVO_2TB_S6R4NJ0R701417P Sep 7 11:05:56 nas-mass emhttpd: read SMART /dev/sdg Sep 7 11:07:04 nas-mass emhttpd: Samsung_SSD_870_QVO_2TB_S6R4NJ0R701417P (sdg) 512 3907029168 Sep 7 11:07:04 nas-mass emhttpd: read SMART /dev/sdg Sep 7 11:07:06 nas-mass emhttpd: Samsung_SSD_870_QVO_2TB_S6R4NJ0R701417P (sdg) 512 3907029168 Sep 7 11:07:06 nas-mass emhttpd: read SMART /dev/sdg Sep 7 11:07:27 nas-mass emhttpd: Samsung_SSD_870_QVO_2TB_S6R4NJ0R701417P (sdg) 512 3907029168 Sep 7 11:07:27 nas-mass emhttpd: read SMART /dev/sdg Sep 7 11:07:36 nas-mass emhttpd: Samsung_SSD_870_QVO_2TB_S6R4NJ0R701417P (sdg) 512 3907029168 Sep 7 11:07:36 nas-mass emhttpd: read SMART /dev/sdg Sep 7 11:07:41 nas-mass emhttpd: Samsung_SSD_870_QVO_2TB_S6R4NJ0R701417P (sdg) 512 3907029168 Sep 7 11:07:41 nas-mass emhttpd: import 30 cache device: (sdg) Samsung_SSD_870_QVO_2TB_S6R4NJ0R701417P Sep 7 11:07:41 nas-mass emhttpd: read SMART /dev/sdg Sep 7 11:07:44 nas-mass emhttpd: Samsung_SSD_870_QVO_2TB_S6R4NJ0R701417P (sdg) 512 3907029168 Sep 7 11:07:44 nas-mass emhttpd: import 30 cache device: (sdg) Samsung_SSD_870_QVO_2TB_S6R4NJ0R701417P Sep 7 11:07:44 nas-mass emhttpd: read SMART /dev/sdg Sep 7 11:08:32 nas-mass emhttpd: /sbin/btrfs filesystem show /dev/sdg1 2>&1 Sep 7 11:08:33 nas-mass emhttpd: ERROR: not a valid btrfs filesystem: /dev/sdg1 Sep 7 11:08:33 nas-mass emhttpd: /usr/sbin/zpool import -d /dev/sdg1 2>&1

Trying to upgrade my cahe, swapped in a 2T SSD but now getting. Unmountable: Unsupported or no file system on both drives. I erased them through the unraid UI. I guess I messed up order of operations somehow, how do I recover and get the cache pool up?

I don't know either but it even if it's something on the source data side (WD PR2100 raid0) that is funky, though I can't imagine what since the old nas works fine, then it's still in how unraid is handling the data since it only presents back out to other devices.

This problem is nuts. I'm now having to hand move large chunks of data and baby sit it since unraid seems to be changing a bit somewhere making sub folders copied in accessible to external devices.