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.

docker take to long to start

Featured Replies

hi, guys, need some help, problem i have started in the last hour,  docker containers are taking to long time to start, this happen after trying to manually update a container then server got stuck, so i did a restart then the array did not want to come back or having problem to start, so i entered in safe mode and disabled docker then array started as normal, now i started docker and all docker containers taking forever to start , any help please, i am with almost 2 hours and still not all containers started

Ulogs.txt

Edited by Danuel
logs

  • Author

now after all this restarting and trying to understand what happens i see a container that i  dont know what it is, i dont remember installing it, this just showed up

unknown.png

  • Author

just happen to notice that sometimes server shut down itself when trying to start a container,  it  take like 5 minutes

anyway does take long time to start or stop a container

Edited by Danuel
edited

  • Author

ZFS 100%  ?

can that be the problem ?

 

zfs.png

Edited by Danuel

1 hour ago, Danuel said:

ZFS 100%  ?

can that be the problem ?

No.   That is the ZFS ARC and it is expected to be that sort of value in normal running.

  • Author

from what is see, is behaving like a slow system, even with docker off, Unraid homepage still take a bit to refresh or load

 

i wonder if is a corrupted docker image ?

and downgrading to 6.12.4 does not help, another thing i noticed is that sometime when i am trying to start a container i get execution error, or takes up to 5 min to start a container 

Edited by Danuel

  • Author

any news regarding those diagnostics ?

  • Author

Is there any way or tool that i can check for hardware faults ? I dont know what is with my server, sometimes work ok, sometimes work like a very old system or freezes, need some help please some ideas on what to try

  • Author

those are the latest logs, i dont know what happen, but i came back and unraid UI and started again to have a parity and all containers were off

now i see something regarding CPU not supported

seven-diagnostics-20231231-1207.zip

  • Author

what i see, if i manage to start 1-2 containers the 3 one will spin and if i try to acces log from UI i have blank 

also sometime after a fresh boot when i navigate on UI TOOLS tabs, or settings it takes time to load

  • Author

is this regarding to VM ?

 

Dec 31 14:37:13 Seven kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Dec 31 14:37:13 Seven kernel: ACPI: \_PR_.C000: Found 2 idle states
Dec 31 14:37:13 Seven kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Dec 31 14:37:13 Seven kernel: ACPI: \_PR_.C002: Found 2 idle states
Dec 31 14:37:13 Seven kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Dec 31 14:37:13 Seven kernel: ACPI: \_PR_.C004: Found 2 idle states
Dec 31 14:37:13 Seven kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Dec 31 14:37:13 Seven kernel: ACPI: \_PR_.C006: Found 2 idle states
Dec 31 14:37:13 Seven kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Dec 31 14:37:13 Seven kernel: ACPI: \_PR_.C001: Found 2 idle states
Dec 31 14:37:13 Seven kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Dec 31 14:37:13 Seven kernel: ACPI: \_PR_.C003: Found 2 idle states
Dec 31 14:37:13 Seven kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Dec 31 14:37:13 Seven kernel: ACPI: \_PR_.C005: Found 2 idle states
Dec 31 14:37:13 Seven kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Dec 31 14:37:13 Seven kernel: ACPI: \_PR_.C007: Found 2 idle states

  • Author

i wonder if this is CPU related

 

i wanted to install older RAM and the CPu did not recoqnize them, took me 1 h for the older ram to work again

 

both sets of RAM that i have tested they are fine, anyone any thoughts ?

 

or is it possible top be the flash drive ?

Edited by Danuel
edited

  • Author

so i did a roll back to  6.12.3 and the problem is still  there now is start to crash after a while

Looks like you are having multiple issue, I would first try to fix the crashing and only after that look at the docker issues, you can boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

  • Author
17 minutes ago, JorgeB said:

Looks like you are having multiple issue, I would first try to fix the crashing and only after that look at the docker issues, you can boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

multiple issue that pointing to what ?

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.