Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

anyone experience like Lockout Process Stuck Loop on 6.12.13 but i can ping it cant access

Featured Replies

recently i upgraded to 6.12.13  but i noticed  server  is like hanging  stuck  or stuck in a loop... the hard drive light for overal is going soild... but the individual hard drives are not...  i can ping my server.. but i cant ssh   i cant access any vms  no dockers...    i upgraded a few days ago.. and noticed it been hanging like this last few days too.. Home assistant stops working as a vm...  my ubuntus stop working...   i cant get a diagnostic  as i have to hit the reset button as you cant access the gui page or ssh in... 

 i just curious if anyone else experiencing the same and i updated all dockers and plugins..

 

just wondering if its just me or if others experiencing same issues

 

 i running on

Asus X570 Strix Gaming   64Gb ram ECC ram  x5800  also noticed my fans dont match anymore like in 6.12.11   so fan speed doesnt wanna work right   like fan4 is fan2  and cant detect fan4 right etc.... 

 

i didnt upgrade my other servers   my other unraids are still running 6.12.11

Edited by comet424

Yep. Upgraded to the beta and got this behaviour so downgraded and I’m still getting this issue. 
 

everything is down except Plex, that’s still up but playback fails. So I suspect it’s something to do with the main array.  I can see the shares but trying to access them crashes explorer. Accessing docker containers that don’t have the main array mounted works fine. 
 

I’ve got portainer installed and I can access the webui but as soon as it tries to connect to the docker socket it crashes.

I can ping but I get errors trying to ssh.

 

Trying to log on via the server itself gives me timeout errors. So I can’t log in to do any diagnostics etc. I’m currently away from home so can’t do a hard reset. But I have a pikvm so can try other things. 

  • Author

ah ok ya what i do for my server i use TP link plugs  wifi and i can just tell kasa app to turn on off so i can force the server power off and on.. comes in handy for the dsl modem and pfsense box time to time.....   but ya i know i was able to see diagnostics    some time out thing  but they were warnings  didnt make much sense then not long  i lost all access... i dont think i upgraded to a beta version i thought  6.12.13 was stable.  but ill downgrade.. but i have to do it tommorow  as now array doing parity check and that always takes 25 hours   72tb and 2 parity disks.. and still slow lol even with cache drives...

 

but it is frustrating cuz i notice last night home assistant was down all night  and it had crashed i was able to vnc to see...  i guess unraid went nuts or took 100% cpu  last night released it kinda by morning...   but then did it again... and had to hit reset button...  hopefully it doesnt try to delete the files  this weirdness.. i working on transfering files to 2 backup servers of unraid  so i have 3 copies of files..  dont need it deleting due to wonkieness

It’s plugged into an ups so can’t use the smart plugs. I’m going to get the atx power control for the pikvm.

 

i moved my home assistant to a dedicated machine for these exact reasons. My other half doesn’t mind Plex going down because she’ll just watch Netflix but if she can’t turn the lights off I’m up all night diagnosing it.  
 

I think I’m going to downgrade back to 6.11.11 when I’m home again. 

  • Author

ah ya for me i have the smart plug  plugged in the ups.. so the ups keeps the computer on  but i can still reboot the computer  with the cell phone app when i connect to the network.. so it helps that way..  so i go ups  ---> smart plug ---> unraid box 

 

but ya i thinking going raspberry pi maybe for HA  i use 1 but its jjust to run a sump pump... but  ya  i just letting it do its parity  and downgrade.. i did check  6.12.13 is a stable release i thought i might have downloaded a beta by accident.. but apparently its stable..  so it shouldnt be glichty....  gonna wait till 6.12.14  ...    what you use for your dedicated HA

So being away from home

mea t I couldn’t reboot the server and it came back up after a couple of days. 
 

it was a weird issue, half of my containers were still up, I could watch Plex, access gitea, Immich but others I couldn’t. I have been having separate issues with authentik so anything that was proxies through that I couldn’t access. 
 

I couldn’t log on via ssh or via the physical server (via pikvm) 

 

but now it’s come back up I had to restart docker with the rc.d command as all the containers had been stopped and have a system error if I tried to start them from the webui. 
 

bit I was able to get the diagnostics which may help get down to the root of the issue.

storageserver-diagnostics-20240831-0717.zip

  • Author

i did leave my 1 server running the latest.. and i get all these errors 

she glitchy as hell

ep  1 09:23:55 Tardis php-fpm[12953]: [WARNING] [pool www] child 25971 exited on signal 9 (SIGKILL) after 21.084949 seconds from start
Sep  1 09:24:14 Tardis php-fpm[12953]: [WARNING] [pool www] child 25972 exited on signal 9 (SIGKILL) after 40.885417 seconds from start
Sep  1 09:24:38 Tardis php-fpm[12953]: [WARNING] [pool www] child 27165 exited on signal 9 (SIGKILL) after 24.018489 seconds from start
Sep  1 09:25:01 Tardis php-fpm[12953]: [WARNING] [pool www] child 27974 exited on signal 9 (SIGKILL) after 23.044698 seconds from start
Sep  1 09:25:39 Tardis unassigned.devices: Warning: shell_exec(/bin/lsblk -b -n -o NAME,SIZE,TYPE | /bin/awk '$3 == 'disk' {print $1 ',' $2}' 2</dev/null) took longer than 0s!
Sep  1 09:25:55 Tardis php-fpm[12953]: [WARNING] [pool www] child 29392 exited on signal 9 (SIGKILL) after 26.722472 seconds from start
Sep  1 09:25:57 Tardis php-fpm[12953]: [WARNING] [pool www] child 29460 exited on signal 9 (SIGKILL) after 28.007264 seconds from start
Sep  1 09:26:13 Tardis php-fpm[12953]: [WARNING] [pool www] child 28672 exited on signal 9 (SIGKILL) after 71.674685 seconds from start
Sep  1 09:26:17 Tardis php-fpm[12953]: [WARNING] [pool www] child 30225 exited on signal 9 (SIGKILL) after 19.778683 seconds from start
Sep  1 09:26:19 Tardis php-fpm[12953]: [WARNING] [pool www] child 30242 exited on signal 9 (SIGKILL) after 21.155927 seconds from start
Sep  1 09:26:30 Tardis php-fpm[12953]: [WARNING] [pool www] child 30860 exited on signal 9 (SIGKILL) after 12.227188 seconds from start
Sep  1 09:27:08 Tardis php-fpm[12953]: [WARNING] [pool www] child 30881 exited on signal 9 (SIGKILL) after 49.048186 seconds from start
Sep  1 09:27:10 Tardis php-fpm[12953]: [WARNING] [pool www] child 31133 exited on signal 9 (SIGKILL) after 28.466605 seconds from start
Sep  1 09:27:39 Tardis php-fpm[12953]: [WARNING] [pool www] child 761 exited on signal 9 (SIGKILL) after 29.191487 seconds from start
Sep  1 09:27:49 Tardis php-fpm[12953]: [WARNING] [pool www] child 3400 exited on signal 9 (SIGKILL) after 21.934981 seconds from start

 

tardis-diagnostics-20240902-0737.zip

  • 2 weeks later...

I’ve resolved my issues now. I thought it was a bad usb stick but it was actually a bad stick of ram. I thought I’d do a contest to rule it out, there was no errors until the first pass got to about 80% and then there were thousands. 
 

I’ve since replaced and upgraded my ram (32gb to 64gb) and my server has been stable ever since. 

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.