craig_read

Hi, Just trying to understand what has happened here.. The machine is up and running but I am now missing two (correction... it's not just NFS) shares, most other shares are there.. One of the shares that's down is appdata.. so that will explain Docker... I've gone in via command lines... if I navigate to mnt/diskx then I can see the folders for the shares.. and all the data is there.. currently I am copying it off to another location... however if i navigate to mnt/user and I try to open the share folder there.. this fails.. with.. "bash: cd: Data: Input/output errorinput/out" I've left the machine running at the moment.. any idea what's happened? Don't want to reboot till I've got the data off.. it's no vital.. just inconvenient if I lose it.. Thanks Craig tower-diagnostics-20221124-0738.zip

Ok... it's back... I can trace all this to a few operations I think... so I'll just complete the tidy up operations and then go from there now...

Ok I have ran this now, after I don't see anything coming from the log that looks bad. I'll do a reboot now and go back into maintenance mode to see if it mounts properly. Is there a memory tester built in to UNRaid?

Phase 1 - find and verify superblock... - block cache size set to 720104 entries Phase 2 -using internal log -zero log... Log inconsistent (didn't find previous header) empty log check failed zero_log: cannot find log head/tail (xlog_find_tail=5) ERROR: The log head and/or tail cannot be discovered. Attempt to mount the filesystem to replay the log or use the -L option to destroy the log and attempt a repair. is it safe to run again from the GUI with "-L" in the options box next to CHECK?

Sorry I saw this too late.. apologies.

Diagnostics attached. tower-diagnostics-20220427-1544.zip

Yes I did, I'm just in the process of rebooting (which weirdly fixed the same issue with the cache drive) but disk 6 is still in the same condition.

I'm trying to run; xfs_repair -v /dev/md6 But I am getting the following failure; xfs_repair: cannot open /dev/md6: Device or resource busy

Ok.. it has happened again... Attached is the results of the check... not sure what I am looking at if I am honest.. Disk Check.txt

Please close this as I have sorted it now...

Hi, I've had a lot of problems lately some of which I am unsure whether or not have actually gone away. But I am happy with the data on the disks, I do not want to do a rebuild. How do I get the array to accept the data on the disks and stop the re-build process? I basically want to setup my array, re-introduce a partiy disk again and get it to build parity based on what's there.... Thanks Craig

Ok so I've definitely lost anything that was on disk 6? Oh well.. you live and learn I guess.. I've gone through and anything that was important I still have.. the rest is pretty incidental. I guess I learned a good lesson quite lightly! Also important stuff is backed up in multiple places so again.. incidental really... Out of interest.. what should I have done?

Here is the diagnostics. tower-diagnostics-20220425-1422.zip

Haha...... yeah I figured... I can still see all my "emulated" data... so there is a way I can "copy" it back? If not.... that's life

Ok.. so I am having a problem. I recently replaced a drive with a new one, and the parity re-build process completed but the drive was showing as unmountable. I (unsure if this was the right thing to do or not) formatted the drive in MAIN, and then it showed as empty but active in the array. I paniced... shut down the array... took the drive offline again.. formatted it... and put it back into the array and it's now rebuilding again. The drive is showing as 41.9GB used and nearly 6TB free, this is incorrect. The original drive had a lot more data on it than this. I'm looking at my shares and I can see that they're emulated, so I am assuming parity is maintaining those. I'm not sure what to do, I am concerned I'm about to loose a whole bunch of data from the array once re-build completes. Can someone advise me on the best approach to take here?

In that case I have my replacement arriving in a few hours, I'll swap out this drive, RMA and probably use the replaced drive to upgrade one of the smaller drives in the system. I've attached the report, but Unraid is saying "Self-test execution status 121 The previous self-test completed having the read element of the test failed." I'd say that's not looking good... The drive is in warranty so I'll package it up and send it back for replacement. I'm using an encrypted array so I am assuming I don't need to blank it to return it, my data is protected and unreadable? ST6000VN001-2BB186_ZR10DJK6-20220424-1245.txt

Yeah this has only just happened, I have a replacement drive already ordered so I can swap it out if necessary very quickly. I ran a test yesterday and there was no change. I'm running another one now. Perhaps keep using it for another day keeping a close eye and if anything changes do the swap out right away? I have a Reallocated sector count of 1200, and Reported uncorrect at 162 as well.

Hi, Not being super familiar with HDD health stats, I have a HDD with this showing; 197 Current pending sector = 32 198 Offline uncorrectable = 32 Is this suitably bad for a warranty claim? Thanks Craig

Ok so I just did a server restart and now Plex is working.... not sure why this is happening....

Hello, I'm having a problem with my Plex today, it appears to no longer be starting. This is the error I get in the logs; "PMS: failure detected. Read/write access is required for path: /config/Plex Media Server" And the docker command is as follows, and executes successfully. root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-plexpass' --net='host' --cpuset-cpus='0,1' -e TZ="Europe/London" -e HOST_OS="Unraid" -e HOST_HOSTNAME="tower" -e HOST_CONTAINERNAME="binhex-plexpass" -e 'TRANS_DIR'='/config/transcode' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -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/Media/':'/media':'rw' -v '/mnt/user/appdata/binhex-plexpass':'/config':'rw' 'binhex/arch-plexpass' The complete log is here; Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2022-04-23 12:27:33.039632 [info] Host is running unRAID 2022-04-23 12:27:33.069862 [info] System information Linux tower 5.15.30-Unraid #1 SMP Sat Mar 19 08:42:03 PDT 2022 x86_64 GNU/Linux 2022-04-23 12:27:33.110278 [info] OS_ARCH defined as 'x86-64' 2022-04-23 12:27:33.150647 [info] PUID defined as '99' 2022-04-23 12:27:33.243654 [info] PGID defined as '100' 2022-04-23 12:27:33.328836 [info] UMASK defined as '000' 2022-04-23 12:27:33.359542 [info] Permissions already set for '/config' 2022-04-23 12:27:33.399324 [info] Deleting files in /tmp (non recursive)... 2022-04-23 12:27:33.438181 [info] TRANS_DIR defined as '/config/transcode' 2022-04-23 12:27:33.521726 [info] Starting Supervisor... 2022-04-23 12:27:34,038 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing 2022-04-23 12:27:34,038 INFO Set uid to user 0 succeeded 2022-04-23 12:27:34,043 INFO supervisord started with pid 7 2022-04-23 12:27:35,046 INFO spawned: 'plexmediaserver' with pid 71 2022-04-23 12:27:35,048 INFO spawned: 'shutdown-script' with pid 72 2022-04-23 12:27:35,049 INFO reaped unknown pid 8 (exit status 0) 2022-04-23 12:27:35,319 DEBG 'plexmediaserver' stderr output: PMS: failure detected. Read/write access is required for path: /config/Plex Media Server 2022-04-23 12:27:35,320 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2022-04-23 12:27:35,321 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22964515171456 for <Subprocess at 22964515167328 with name plexmediaserver in state STARTING> (stdout)> 2022-04-23 12:27:35,322 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22964515171888 for <Subprocess at 22964515167328 with name plexmediaserver in state STARTING> (stderr)> 2022-04-23 12:27:35,322 INFO exited: plexmediaserver (exit status 1; not expected) 2022-04-23 12:27:35,322 DEBG received SIGCHLD indicating a child quit 2022-04-23 12:27:36,325 INFO spawned: 'plexmediaserver' with pid 76 2022-04-23 12:27:36,350 DEBG 'plexmediaserver' stderr output: PMS: failure detected. Read/write access is required for path: /config/Plex Media Server 2022-04-23 12:27:36,352 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22964515172368 for <Subprocess at 22964515167328 with name plexmediaserver in state STARTING> (stdout)> 2022-04-23 12:27:36,352 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 22964515172416 for <Subprocess at 22964515167328 with name plexmediaserver in state STARTING> (stderr)> 2022-04-23 12:27:36,352 INFO exited: plexmediaserver (exit status 1; not expected) 2022-04-23 12:27:36,353 DEBG received SIGCHLD indicating a child quit 2022-04-23 12:27:38,357 INFO spawned: 'plexmediaserver' with pid 79 2022-04-23 12:27:38,386 DEBG 'plexmediaserver' stderr output: PMS: failure detected. Read/write access is required for path: /config/Plex Media Server 2022-04-23 12:27:38,388 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22964515172176 for <Subprocess at 22964515167328 with name plexmediaserver in state STARTING> (stdout)> 2022-04-23 12:27:38,388 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 22964515167424 for <Subprocess at 22964515167328 with name plexmediaserver in state STARTING> (stderr)> 2022-04-23 12:27:38,389 INFO exited: plexmediaserver (exit status 1; not expected) 2022-04-23 12:27:38,389 DEBG received SIGCHLD indicating a child quit 2022-04-23 12:27:41,395 INFO spawned: 'plexmediaserver' with pid 82 2022-04-23 12:27:41,426 DEBG 'plexmediaserver' stderr output: PMS: failure detected. Read/write access is required for path: /config/Plex Media Server 2022-04-23 12:27:41,428 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22964515168192 for <Subprocess at 22964515167328 with name plexmediaserver in state STARTING> (stdout)> 2022-04-23 12:27:41,428 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 22964515172320 for <Subprocess at 22964515167328 with name plexmediaserver in state STARTING> (stderr)> 2022-04-23 12:27:41,429 INFO exited: plexmediaserver (exit status 1; not expected) 2022-04-23 12:27:41,429 DEBG received SIGCHLD indicating a child quit 2022-04-23 12:27:42,430 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly Is anyone able to point me to where I might look to rectify this? Thanks Craig

I did a search for my printer for PPD files. I found a PPD file for it online, however when I installed this it would not work. I did some further searching and found that the printer I am using HL4150CDN from Brother will actually work with a another printer driver that was already available in the list built in to this CUPS build. I tried that driver and it worked just fine. Perhaps find a driver that's compatible but already within that list if you're having a problem.

Figured this out now using the operational policy.. all is well

I'm able to print documents now from iphone, ipad with this container. The only thing I'm trying to sort out now is a weird setting where the print is paused till I get to the printer nad press "Go" on the printer itself. It then prints without problem. On the pi version I made of this, I don't have to do this, is there some setting somewhere I can flip to prevent this that anyone knows about? Not really a CUPS problem but wondered if someone knew. Thanks

Hi, It's ok I have sorted it now thanks, for some reason it needed to use a different driver and after some config changes it appears to be working Please ignore!

Hi, I have been looking for this very thing for ages! I've got a similar query to Twinkie... I'm connecting to a network printer and want to serve this printer to devices in the house via wifi etc... the reason being the printer isn't Apple Air Print compatible and CUPS is a nice way of bridging that gap. I've actually created a pi build that does this with CUPS and works but I wanted to use a container on my "always on" Unraid box... I've got the printer installed, I've collected a PPD file for it from the manufacturer CUPS sees the printer. I've also managed to sent print jobs to it from network machines so I know CUPS is receiving the print jobs and processing them. However it appears the printer isn't doing anything. The jobs just sit in the job list and never complete, is there anything I could try?