mathomas3

check network settings... perhaps you gateway IP has changed... you might try setting the server up via DHCP and making it's new IP static via your router

I would backup your usb now... Kinda feels like it might be going bad... Have you been using this USB for a while?

You might try accessing the webconsole via IP and using private/incognito mode... and also running the following command in CMD is a good idea 'ipconfig /flushdns'

two things that I would suggest here... update the OS(folks here dont like troubleshooting outdated software) and post Diags... it's possible that the IP address has changed due to a new nic and DHCP providing a different IP... have you validated that you have the correct IP via the console(using an external monitor connected to the server)?

You and I worked on an issue a few months back... and let me thank you for your continued support and efforts for the community... you are quick and responsive... Thank You My system is healthy... except for some lag when a docker prevents emby or the unraid interface to update/work... another issue for another time when im tired of it... Backups? no... irreplaceable... no... A few photos or what not... but nothing critical... I watch this system daily... It's my baby... I hope to preserve the media that I have collected for the future... I have been building this system for 12 years now and modified it many times... I have a feeling that my unraid UI is unique ATM(lack of features) vs screenshots of fresh builds... overall... I think adding the extra DAS is a good idea... balancing Cost to Risk... but again... if someone know of a better deal/idea I am all ears

Do you think that jumping to 14tb drives now is worth the addl cost? Adding a disk shelf doesnt add much to the cost of the build... and having that added drive bays does make sense on a certain level...

I have no disk warnings. Nothing to be concerned about on that end. The problem is that I can only add 2 HHD to the current setup before I am out of space. If I were to switch to 14tb drives, it would be easier now vs later, thus this post. Yes I am running dual parity tower-diagnostics-20221226-1725.zip

Hello, I am trying to decide the next expansion of my setup... Currently I am running 17 HDDs in the Array, 2 disk pools and a spare HHD if one should fail. The majority of the disks are 8tb. The current DAS that I am using only has 2 spare slots left. My concerns are measuring cost and risk. Granted the more disks that you have, the more likely that one or more will fail. Replacing 114tb with newer(even used) drives with the cheapest drives that I can find(14tb for $148) would run $450 just to expand the array for the first time(to increase parity and replacing the 8tb drives would only increase array size by 6tb)... I have found another DAS that could be delivered for $250 and would allow me to continue to expand using 8tb drives($55 each) for a reasonable cost... I favor buying the additional DAS due to my experience with 8tb SAS drives. Before moving to these drives, I had numerous drive failures(2,3,5tb) and since running the 8tb drives, I havent had a single failure. What do you think? Do you have better ideas? Thank you for your time

tower-diagnostics-20221206-1622.zip

Another update has failed again... This time after partially downloading 2 files, setup stopped the containing and proceeded to 'successfully' update the container. Which it was not

no comment?

This is when updating from the docker page. I went ahead and updated the rest of my containers and there was no error except for tubearchivist-es and zoneminder(never used it thus far... doesnt even work as far as I know). They both completed normally but still show an update is ready. The container that I had issues with today was readarr tower-diagnostics-20221201-1117.zip

Another example that happened a few days ago... After the failed update the container was 'orphaned' I had to go to the app store to reinstall the container. I have not attempted to update that one since

Oh, one other thing that I noticed after each failed update is that the container ID will change

After downloading(and failing to completely DL and extract), the update attempts to stop the container. After about 15 seconds, the text changes to error and continues to the next stop of removing the container.

Hello, I have been having issues updating docker containers after updating to unraid 6.11.5. Here is what is happening... 1. Incomplete downloads 2. Error when stopping a container 3. Completes the update but the container is still the old version 4. Still says that there is an update pending after returning to the docker page On my third try, it finally finished downloading the files and extracted them. It worked. Suggestions? Is anyone else having this issue?

Ended up finding out the problem... I recently started recording live videos using emby... and for some reason after telling emby to use a custom DIR for the recordings, it decided to use the default DIR and thus recording to the 2 ssd array I had setup... Had to create a new share that mirrored the default path to the larger array... yea... not happy about that one... Thanks for the help JorgeB

I personally used paypal... and they have been in my array for 6 months... Im happy

Hello, I have a 2 disk 256gb ssd disk pool that has only 10gb of space left and for the life of me I cant find out why. I have checked the sizes of every folder (using Mint file browser) which added up to about 120gb... I have checked the size of the entire share 135gb used. So where does the extra 110gb come from?

We had some shifty power that day... hoping that was all that it was... Ordered a much larger UPS the same day

That's odd Orca... I too also have a parity and data disk drop from the array over night... I rebuilt both of them with some spare disks that I have... Both of the disks SMART report looks ok... Im not going to say that this might be bug unless more reports come up... but timing between your failure and mine is odd tower-diagnostics-20220916-1203.ziptower-diagnostics-20220915-0800.zip

it was in the logs that it couldnt find ES... I noticed that when after an update/reboot sometimes the IP for that docker would get changed as I have them in bridged mode... I guess I could sidestep that by using host IPs but...

I will make a small note here... While 100ish days to compete a rebuild is on the extreme... I wonder what the numbers will be now that you have shutdown dockers... read/writes have a huge impact on parity, but too this extreme slow speed, seems very unusual... what I would suggest is KISS... Keep It Simple Stupid... means that your rig seems a little complex given the notes in this thread... Disconnect/disable unused/required hardware for unraid to function... and try a parity check while monitoring system usage/load... there is a bottleneck that is preventing disk1 rebuild and limiting the variables is a good thing to do... But do please note... I am not an expert on unraid(been a user for 10+ years) but I would suggest limiting activity on the system and ensuring that IO is good would be a good first step... thus the parity check would be a good benchmark for the rebuild

NM. Figured it out... after the update some of the IPs for the different dockers changed and after updating those I was able to get things back to square...

I am having some issues... It was about 5 days ago there was an update for tubearchivist that broke it... it fails to start even after waiting a few days for a new update... I have since uninstalled the docker and reinstalled it... and still fails to start... dies within a second or so... anyone else having this happen? where in this docker or what commands should I run to collect logs... I am a bit lost when it comes to dockers