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.

Array will not start after being stopped, only starts on reboot.

Featured Replies

Trying to pin down some issues I have been developing on my device.

This is a small issue but seems to have been replicated in a few posts:
https://forums.unraid.net/bug-reports/stable-releases/722-array-wont-start-after-being-stopped-emhttpd-cmdstart-already-starting-logs-r4227/
https://forums.unraid.net/topic/197199-array-wont-start-after-stopping/

This was discovered while I try and address a cache issue that has returned. In an unrelated reddit post someone noted a bad cache pool might prevent the array from starting. As this was in the middle of troubleshooting the cache issue I just deleted the pool and still had the issue. I also had an update to apply so figured perhaps it would be addressed in the update. Updated to current and still have the issue.

Attached are dags. Please call out any other issues you spot.

For context to my overall issue that led up to this - cache pool on 2 nvme drives (raid 1/btrfs) will drop one drive when under heavy i/o. This occurred on a pair of TeamGroup 512GB drives. Somehow these drives became misaligned (I didn't know this could even happen with Raid 1) and the drives would end up with 2 different sets of data on them.
I ended up deleting the pool, replacing the drives with Western Digital 4TB drives, everything seemed better but now I find myself in the same situation. This tells me the issue is deeper than the drives and I have started looking at the board/pcie bridge and OS (however I don't have a strong indication yet from unraid being the casue) f4-424-diagnostics-20260709-1245.zip

Solved by JorgeB

  • Community Expert
  • Solution

Jul 9 11:21:41 F4-424 emhttpd: cmdStart: already starting

This is typically a plugin issue; see if it happens in safe mode.

  • Author

Oh nice. I'll give that a go. Any tips on how to narrow the plugin down after confirming this is the cause via safe mode or is it more of a "whats the last thing you installed" game of wack-a-mole?

  • Author

Hate to open a new thread just to ask but - is this new from 7.2 - 7.3?
I didn't have this "Status" on the cache/drives before. Only now that I have recreated the pool do I have this - but I also did a OS update between the action as well.

image.png

  • Community Expert
1 hour ago, Catch_22_ said:

Hate to open a new thread just to ask but - is this new from 7.2 - 7.3?
I didn't have this "Status" on the cache/drives before. Only now that I have recreated the pool do I have this - but I also did a OS update between the action as well.

image.png

It is new yes.

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.