droopie

Voice 250712_145019.m4athe reason i was replacing disk9 is because that drive kept clicking but i dont think it was the drives fault now because i am noticing the same issues with its replacement. so could it be my power supply? i have like 1100 or 1300watts and i do have the powerdisable connector for most of those drives 8tb and all 14tb. i dont have any molex connected and was going to install more fans to molex. also, thanks @strike i set them to unassigned and see the contents for both thankfully. so starting like this, i do see errors again for serial 9JG49BVT but that aside, disk9 looks like its still the 8tb disk i originally had. so serial 9JG49BVT not been assigned to disk9 because i rather see whats causing the problem in hopes the original disk9 is actually fine and the problem is something else because that original disk didnt have any signs of death in the SMART. i could use this 14tb to replace another 14tb elsewhere so if i can save it i will but i was ready to use it in the array to replace 8tb. server-diagnostics-20250712-1515.zip

i swapped out the cable on the hda and fixed the filesystem for disk10 which gave me a long list. i also didnt see anymore connection issues. but when i started the array in without mounting the disks, i see the yellow icon on disk 10 and x icon on disk 9. i would like to verify that both disks 9 and 10 contents are being emulated before it gets written to especially disk10 as thats the same drive so if its not emulated i dont want to overwrite it. for disk9 i still have the original disk so yolo it if its blank. i could always put disk9 back but every now and then it just hangs. so, should i set the disk10 to unassigned and starting the array? server-diagnostics-20250712-1244.zip

i dont think i canceled i dont think anything actually started besides i guess assigning them? it wanted me to confirm starting the rebuild process for disk10 since that was disabled but unsure if the contents are in the array to actually rebuild or if its going to start fresh. very confusing i tell ya, i am reading online but i think in my case is that this happened right before replacing a drive so that just adds to it.

ima have to come back at this tomorrow. i think i fixed the parity but without even touching the rest i now have disk 4 acting up. i tried to do that check on disk 10 but it failed so tomorrow ill swap that cable for all the 4 connections to the hba server-diagnostics-20250711-2056.zip

appreciate it, will reconnect all these cables. the 9JG49BVT drive is the one i was going to replace disk 9 with when i turned off the array to remove disk 9 and install 9JG49BVT in its place, thats when all this happened. i am unsure how to continue after checking the filesystem if disk 9 was supposed to be rebuilt and now disk 10 being disabled. how likely is it that disk 10 will try to rebuild as if it was blank? thats what i fear so want to verify this somehow. so im not sure if i should put disk 9 back for now or of its too late now since i had selected the new disk when i started the array not knowing about the filesystem thing. i think it was just bad luck that i was attempting to replace the disk and do this check so dont know what to do...

i have a disk9 that was clicking so i wanted replace it with another disk. upon doing so, disk 10 got disabled. i fixed the cables for disk 10 but when i started the array i got Unmountable: wrong or no file system for both disks now. i noticed the icon where you typically browse the data on that disk is missing for both so i am afraid that if i start the array now, the unraid will ask me to checkmark to format this disk but if i format this, i fear that the array wont restore this data now. i just dont know why i am getting this Unmountable: wrong or no file system message now never seen it in like 6 years of using unraid. server-diagnostics-20250711-1801.zip

yea i should have backups but luckily i just unassigned the other disk and when i mount that disk, i was able to see the contents. but what caused this? i think i have a drive that causes the system to hang which disables some disks so every few months i rebuild the disk which i was prepared to do. just not sure why as soon as i started up (with auto start off) the array showed these two disks as unknown filesystem format or something like that causing them to be unmountable. just so i know for next time. still cant wrap my head around the fact that instead of data rebuild it just saw it as empty when just before the restart all the contents was fine. i even rebooted the server and reconnected those cables thinking maybe that was the issue since i thought maybe its just a new feature lol also, if these disks are now empty empty, whats the best way to just remove these off the array for now and keep what is working? i havent done that since like 2019

yea which i assumed that maybe with the new update was a confirmation of data rebuild so it would wipe and restore the data but as content isnt being emulated i am going to assume this drive is gone

i am not sure if this is a false alert but i upgraded my unraid to the latest version then on the restart two disks got disabled. i went to rebuild 1 but i am noticed that it asked to format the disk and on top of that both disks have emulated content with 0 files and both appear to be completely empty in the array view. it is really weird that both of these disks also show filesystem errors in the array view. please look at the log. server-diagnostics-20250705-1225.zip

Really appreciate the super quick reply. Yeah I have 2 LSI cards both should be identical and about 7 months ago (like November 2024 or October) I upgraded the power supply for more satas. Havnt touched it since but all of a sudden that disk 10 got disabled. Usually I see some smart and I document each drive but I don't have previous issues with them besides faulty connection due to that previous power supply. A general question. Just thinking here. Hypothetically, if i set 1 disk as 'none'm could I rebuild 1 of 2 disks? Is that a thing? If 2 disks are emulated can you rebuild another disk in this state or do both disks have to be rebuilt at the same time? I have had unRAID for like 7 years and thankfully haven't had 2 disks emulated let alone rebuild two at once.

Out of nowhere disk 10 got disabled but I don't see any of the normal disk dying errors. I reconnected it since that's usually the issue but when I tried a rebuild, disk 5 got disabled. I don't want to continue without some guides from you guys on what the issue could be. It's been working fine on the same hardware for like 7 months straight. From checking the disk log and googling the error I don't know of it's a power issue or the LSI needing an upgrade. It could be failing but I didn't see any smart issues. I'm going to start backing up those 2 disks just in case till I get some insight thanks. server-diagnostics-20250508-0810.zip

about 5 days ago, i re-added parity 1 because the disk was having weird issues. i swapped it out and readded parity 1. parity 2 has been working fine. then 4 days after having both dual parity up, parity 2 is now disabled. unsure why it keeps flipping between the two and disabling 1 or the other. server-diagnostics-20241121-0953.zip

1 of my disks had a reallocated sector count going up and up so i got a brand new 8tb to replace a 4tb that passed 3 preclears. the drive 3 was rebuilding fine but disk 5 has had error counts. i stopped the rebuild, reconnected the cables for disk 5, started up unraid again, and same thing. i was in the process of replacing parity 1 but after removing that disk and replacing it, i didnt want to start that with disk 3 those errors so i just left that unassigned and adding it after. i thought maybe its a power issue so i just unplugged parity 1 and started rebuilding again but same issue. im unsure what the problem is now. its a brand new drive with no issues preclearing. i ordered more of them blue cables for the hba but dont know if thats the issue and i hate changing those because ill have to mess with 3 other drives that are working fine so with my luck it can bring up more problems. i have an unassigned 14tb that i was going to also add at the end of fixing the array. i was going to unplug it to free up more power and try again. i can use it to replace a drive if needed and still have the 1st parity drive unused. unsure how to proceed. server-diagnostics-20241115-1246.zip

my problem was that after installing hub 9, i was never able to login to the admin panel. i thought maybe it was a reverse proxy issue as spaceinvader used something else. i am using swag and was able to set up the reverse proxy for the initial setup. but after all the apps started and the admin link popped up, was never able to access it. lost all hope. uninstalled or at least tried to. took me a while to remove all instances since trying to reinstall it left everything behind. i accidently removed all stopped dockers in the process but got them back.

i installed nextcloid aio but had issues and wanted to start over. when i reinstalled it, i noticed all the initial settings are saved somewhere in unraid but dont know where. anybody know what i can do to delete it and start fresh? i deleted all the docker images docker image prune -a and docker system prune -a but no luck. nvm using mc to go into /var/lib/docker/volumes and deleting the nextcloud aio and restarting dockerd worked.

This plugin hasn't been working for me. It never completes the backup and just stops. Is there an alternative? I got this code d68f7d91-3109-432a-8bf3-762e0ca9e535

the problem is getting worse. dockerd seems to randomly cause my unraid webui and all dockers to be unresponsive until i run docker stop $(docker ps -a -q) and to restart all i run /etc/rc.d/rc.docker restart which via ssh. also i dont think swapfile is running correctly because sometimes it says it on the bottom of the webui but the settings an X for "Control Actions". and this is a random thing. sometimes i can go 2 weeks, sometimes a few hours after a restart. i dont know what to do! server-diagnostics-20240619-1938.zip

I completely reset up most dockers fresh without using any backup. I even made a user script to restart dockerd and the problem still happens. My main issue is I have to go into ssh to stop the dockerd to make webui accessible again so I can safely restart the whole system. I'm out of ideas besides new cpu, mobo, ram.

thanks for the reply! i didnt know it reached that high since i have been using docker stats to see the cpu and ram used by dockers but i have never seen any docker use over 4gb of ram so its good that it did show that. any suggestions on what to do next?

yes just verified it does have the two dashes yes i also but weirdly i never actually see the ram in unraid go over 40% but when this happens its always the cpu at 100% even tho i have all the dockers to skip the first pin pairing and use the last 2 only. could it be faulty ram? i havnt had issues with OOM since building it in 2019

ive been getting these for like 6 months now and was sure a docker or dockerd was causing it because as soon as i killed random dockers OR simply restarted the docker service via ssh, everything starts working again. here is a list of things i have tried: -safe mode -cpu pinning to use only the last two on all dockers -Extra Parameters: -cpus=".5" --memory=4G on all dockers -deleted the docker image and setup all dockers manually again (not from a restore or using existing templates) -i also changed ipvlan in docker settings nothing seems to work and with this latest unraid update at least its telling me to post here with the diagnostics so hoping i get some sort of assistance server-diagnostics-20240419-1340.zip

i get that error 502 too when i open a docker webui. i was never able to find a fix. as soon as i restart ANY docker, everything gets updated to the latest running state like it hangs in the background. the cpu is also 100% during this time. i have tried running the absolute bare i can do not require any uptime like only rss stuff (radarr, sonarr, prowlarr, qbit, sabnzbd exactly) and not even running plex to keep it from doing this. i also was told by others to put all these apps to use only the last cores so in my case pair 4 but the cpu is still 100% for some reason. by any chance, are you running qbit? if so, how many torrents do you have if you dont mind me asking. ive also tried setting up a userscript to restart smaller apps like autoscan, and bazarr in hopes to randomly free up the cpu but i dont see it working. when i do a restart of any docker, my cpu is usually around 30% and everything works perfect so im not sure whats causing it to reach 100% and i strongly think its docker related.

it works on safemode and normally but after not using the webui at all, it still freezes and im able to see the logs without any of the php errors so those errors only show up when its freezing while im using webui. so now im thinking that its docker itself because when i am having issues loading unraid even waiting a few minutes to even login to unraid via ssh and another few minutes for it to run /etc/rc.d/rc.docker restart everything works for a few days again. i would hate to do this but is it possible and if so should i resetup the docker service with a new image and all that?

the nightmare doesnt stop unraids webui becomes unresponsive and all my dockers go down due to a flood of php-fpm[12015]: [WARNING] [pool www] child 4959 exited on signal 9 (SIGKILL) after 79.807463 seconds from start messages. i thought my phone was connecting to unraid and causing it to do this but after changing the login and only using webui on desktop and ssh on my phone, it just doesnt stop. im able to use it for about a day to three if im lucky before these messages appear. im noticing my cpu is also at 100% when this is happening. i dont know what to do anymore in short of not using docker as i believe it has something to do with docker because as soon as i start doing docker stop to ANY random container, it becomes responsive again at least enough to stop the array and restart. i also recently replaced the usb because it died so im unsure of while it was dying, some of the first symptoms are these errors already corrupt. while its unresponsive though, all other services like nfs and smb are fine. please look at the diag! server-diagnostics-20231116-1543.zip

so this stuck with me. i was monitoring on my phone via ssh the unraid logs and would see my phone say it was logging in via webui but i had no windows open. so after changing the password, and not logging in to the webui in days, i didnt see the warnings anymore. today i logged in the webui and monitored the log via, after an hour, i started seeing the warnings again. signed out of the webui and the warnings stopped. so it might be being logged into the webui for long period of time is causing this. im not looking into a dashboard/homepage that would let me start/stop dockers from a website and use iframes to open dockers webui in an iframe. organizr does great with iframe tabs but i cant control dockers to start/stop them so looking for alternatives. trying to minimize the logging into unraids webui.