May 25May 25 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.datFull log after pressing the ERASE POOLMay 25 01:01:59 LeitoaNas emhttpd: update_pool_cfg: 30 cache 0May 25 01:01:59 LeitoaNas kernel: md: unRAID driver removedMay 25 01:01:59 LeitoaNas emhttpd: shcmd (282): /sbin/modprobe md-mod super=/boot/config/super.datMay 25 01:01:59 LeitoaNas kernel: md: unRAID driver 2.9.40 installedMay 25 01:01:59 LeitoaNas kernel: read_file: error 2 opening /boot/config/super.datMay 25 01:01:59 LeitoaNas kernel: md: could not read superblock from /boot/config/super.datMay 25 01:01:59 LeitoaNas kernel: md: initializing superblockMay 25 01:01:59 LeitoaNas kernel: mdcmd (1): import 0 sda 64 3907018532 0 WDC_WD40EFPX-68C6CN0_WD-WX22DC391VEDMay 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 diskMay 25 01:01:59 LeitoaNas kernel: mdcmd (2): import 29May 25 01:01:59 LeitoaNas kernel: mdcmd (3): import 1 sdc 64 1953514552 0 WDC_WD20EFPX-68C4TN0_WD-WX52DA3ACDT7May 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 diskMay 25 01:01:59 LeitoaNas kernel: mdcmd (4): import 2May 25 01:01:59 LeitoaNas kernel: mdcmd (5): import 3May 25 01:01:59 LeitoaNas kernel: mdcmd (6): import 4May 25 01:01:59 LeitoaNas kernel: mdcmd (7): import 5May 25 01:01:59 LeitoaNas kernel: mdcmd (8): import 6May 25 01:01:59 LeitoaNas kernel: mdcmd (9): import 7May 25 01:01:59 LeitoaNas kernel: mdcmd (10): import 8May 25 01:01:59 LeitoaNas kernel: mdcmd (11): import 9May 25 01:01:59 LeitoaNas kernel: mdcmd (12): import 10May 25 01:01:59 LeitoaNas kernel: mdcmd (13): import 11May 25 01:01:59 LeitoaNas kernel: mdcmd (14): import 12May 25 01:01:59 LeitoaNas kernel: mdcmd (15): import 13May 25 01:01:59 LeitoaNas kernel: mdcmd (16): import 14May 25 01:01:59 LeitoaNas kernel: mdcmd (17): import 15May 25 01:01:59 LeitoaNas kernel: mdcmd (18): import 16May 25 01:01:59 LeitoaNas kernel: mdcmd (19): import 17May 25 01:01:59 LeitoaNas kernel: mdcmd (20): import 18May 25 01:01:59 LeitoaNas kernel: mdcmd (21): import 19May 25 01:01:59 LeitoaNas kernel: mdcmd (22): import 20May 25 01:01:59 LeitoaNas kernel: mdcmd (23): import 21May 25 01:01:59 LeitoaNas kernel: mdcmd (24): import 22May 25 01:01:59 LeitoaNas kernel: mdcmd (25): import 23May 25 01:01:59 LeitoaNas kernel: mdcmd (26): import 24May 25 01:01:59 LeitoaNas kernel: mdcmd (27): import 25May 25 01:01:59 LeitoaNas kernel: mdcmd (28): import 26May 25 01:01:59 LeitoaNas kernel: mdcmd (29): import 27May 25 01:01:59 LeitoaNas kernel: mdcmd (30): import 28May 25 01:01:59 LeitoaNas emhttpd: import 30 pool device: no deviceMay 25 01:01:59 LeitoaNas emhttpd: import 31 pool device: no deviceMay 25 01:01:59 LeitoaNas emhttpd: import 32 pool device: (nvme0n1) Samsung_SSD_970_EVO_Plus_1TB_S59ANM0W542695LMay 25 01:01:59 LeitoaNas emhttpd: import 33 pool device: (nvme1n1) Samsung_SSD_970_EVO_Plus_1TB_S4EWNJ0N421679TMay 25 01:01:59 LeitoaNas emhttpd: import 34 pool device: (sdb) Samsung_SSD_850_EVO_500GB_S2RBNX0J120136AMay 25 01:01:59 LeitoaNas emhttpd: flash: zfs assign devicesMay 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 0May 25 01:01:59 LeitoaNas emhttpd: update_pool_cfg: 32 cacheta 0May 25 01:01:59 LeitoaNas emhttpd: update_pool_cfg: 34 tempcache 0So, 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.
May 25May 25 Community Expert Solution Typemv /boot/config/pools/cache.cfg /boot/config/pools/cache.bakThen reboot
May 27May 27 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.