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.

Unraid 7.3.0 after configuring boot partition- Can't start array: cache - too many wrong or missing devices

Featured Replies

So, I've used 2 of my cache devices to be selected as boot + data partition. They where at "cache" pool, so set all devices from "cache" to unassigned (no device) and started the wizard. Choose 16GB, and it ask for a name for the data partition that I set "cacheta". After restart the boot partition works great, but I could not start the array as "cache - too many wrong or missing devices ".

Tried to click on "cache", ERASE POOL, proceed, nothing happen, logs shows this red message:

May 25 01:00:39 LeitoaNas kernel: read_file: error 2 opening /boot/config/super.dat

Full log after pressing the ERASE POOL

May 25 01:01:59 LeitoaNas emhttpd: update_pool_cfg: 30 cache 0

May 25 01:01:59 LeitoaNas kernel: md: unRAID driver removed

May 25 01:01:59 LeitoaNas emhttpd: shcmd (282): /sbin/modprobe md-mod super=/boot/config/super.dat

May 25 01:01:59 LeitoaNas kernel: md: unRAID driver 2.9.40 installed

May 25 01:01:59 LeitoaNas kernel: read_file: error 2 opening /boot/config/super.dat

May 25 01:01:59 LeitoaNas kernel: md: could not read superblock from /boot/config/super.dat

May 25 01:01:59 LeitoaNas kernel: md: initializing superblock

May 25 01:01:59 LeitoaNas kernel: mdcmd (1): import 0 sda 64 3907018532 0 WDC_WD40EFPX-68C6CN0_WD-WX22DC391VED

May 25 01:01:59 LeitoaNas kernel: md: import disk0: (sda) WDC_WD40EFPX-68C6CN0_WD-WX22DC391VED size: 3907018532

May 25 01:01:59 LeitoaNas kernel: md: disk0 new disk

May 25 01:01:59 LeitoaNas kernel: mdcmd (2): import 29

May 25 01:01:59 LeitoaNas kernel: mdcmd (3): import 1 sdc 64 1953514552 0 WDC_WD20EFPX-68C4TN0_WD-WX52DA3ACDT7

May 25 01:01:59 LeitoaNas kernel: md: import disk1: (sdc) WDC_WD20EFPX-68C4TN0_WD-WX52DA3ACDT7 size: 1953514552

May 25 01:01:59 LeitoaNas kernel: md: disk1 new disk

May 25 01:01:59 LeitoaNas kernel: mdcmd (4): import 2

May 25 01:01:59 LeitoaNas kernel: mdcmd (5): import 3

May 25 01:01:59 LeitoaNas kernel: mdcmd (6): import 4

May 25 01:01:59 LeitoaNas kernel: mdcmd (7): import 5

May 25 01:01:59 LeitoaNas kernel: mdcmd (8): import 6

May 25 01:01:59 LeitoaNas kernel: mdcmd (9): import 7

May 25 01:01:59 LeitoaNas kernel: mdcmd (10): import 8

May 25 01:01:59 LeitoaNas kernel: mdcmd (11): import 9

May 25 01:01:59 LeitoaNas kernel: mdcmd (12): import 10

May 25 01:01:59 LeitoaNas kernel: mdcmd (13): import 11

May 25 01:01:59 LeitoaNas kernel: mdcmd (14): import 12

May 25 01:01:59 LeitoaNas kernel: mdcmd (15): import 13

May 25 01:01:59 LeitoaNas kernel: mdcmd (16): import 14

May 25 01:01:59 LeitoaNas kernel: mdcmd (17): import 15

May 25 01:01:59 LeitoaNas kernel: mdcmd (18): import 16

May 25 01:01:59 LeitoaNas kernel: mdcmd (19): import 17

May 25 01:01:59 LeitoaNas kernel: mdcmd (20): import 18

May 25 01:01:59 LeitoaNas kernel: mdcmd (21): import 19

May 25 01:01:59 LeitoaNas kernel: mdcmd (22): import 20

May 25 01:01:59 LeitoaNas kernel: mdcmd (23): import 21

May 25 01:01:59 LeitoaNas kernel: mdcmd (24): import 22

May 25 01:01:59 LeitoaNas kernel: mdcmd (25): import 23

May 25 01:01:59 LeitoaNas kernel: mdcmd (26): import 24

May 25 01:01:59 LeitoaNas kernel: mdcmd (27): import 25

May 25 01:01:59 LeitoaNas kernel: mdcmd (28): import 26

May 25 01:01:59 LeitoaNas kernel: mdcmd (29): import 27

May 25 01:01:59 LeitoaNas kernel: mdcmd (30): import 28

May 25 01:01:59 LeitoaNas emhttpd: import 30 pool device: no device

May 25 01:01:59 LeitoaNas emhttpd: import 31 pool device: no device

May 25 01:01:59 LeitoaNas emhttpd: import 32 pool device: (nvme0n1) Samsung_SSD_970_EVO_Plus_1TB_S59ANM0W542695L

May 25 01:01:59 LeitoaNas emhttpd: import 33 pool device: (nvme1n1) Samsung_SSD_970_EVO_Plus_1TB_S4EWNJ0N421679T

May 25 01:01:59 LeitoaNas emhttpd: import 34 pool device: (sdb) Samsung_SSD_850_EVO_500GB_S2RBNX0J120136A

May 25 01:01:59 LeitoaNas emhttpd: flash: zfs assign devices

May 25 01:01:59 LeitoaNas emhttpd: import boot device: 35 (nvme0n1p3)

May 25 01:01:59 LeitoaNas emhttpd: import boot device: 36 (nvme1n1p3)

May 25 01:01:59 LeitoaNas emhttpd: update_pool_cfg: 30 cache 0

May 25 01:01:59 LeitoaNas emhttpd: update_pool_cfg: 32 cacheta 0

May 25 01:01:59 LeitoaNas emhttpd: update_pool_cfg: 34 tempcache 0

So, deleting the pool doesn't work, I can't start the pool also.

Tried to unassign from "cacheta" to the old one also doesn't work as it looks that needs the previous one.

Tried to delete /boot/config/pools/cache.cfg but it got recreated as soon as I ask to delete again (as it appears again at the Main).

Tried to recreate a New config and selected "ALL" for "Preserve current assignments". The problematic "cache" partition was recreated.

Tried to again to recreate a New Config, but now it says: "Array has been Reset (please configure)"

So I'm in a catch-22 situation. I can't reconfigure as it asks for this reference of the old (non partitioned device). Can't create a New Config. Delete the new pool doesn't work. Set pool size to 0 doesn't work (it only shows 2).

I'm adding a screenshot, please let me know if you have any suggestion as my array can't be started.

image.png

Solved by JorgeB

  • Community Expert
  • Solution

Type

mv /boot/config/pools/cache.cfg /boot/config/pools/cache.bak

Then reboot

  • Author

That solved my problem!!! Thank you very much!

Just wanted to add that I had the same issue as vessosa. Whilst my cache name was different (in my instance it was nvme500g - which makes sense as that was what the pool was previously called) the above syntax worked for me by renaming the file and rebooting so it regenerated it.

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.