January 19, 20251 yr Hi, I've removed a device from the cache pool, and now the GUI can't start after server restart. I can SSH into the server, and the syslog shows the following errors: Jan 19 01:41:06 Unraid emhttpd: import 30 pool device: (sdf) CT1000MX500SSD1_ Jan 19 01:41:06 Unraid emhttpd: import 31 pool device: (sdg) CT1000MX500SSD1_ Jan 19 01:41:06 Unraid emhttpd: pool_state_btrfs 3166 rdevStatus.32 not found I've manually mounted the Btrfs pool and removed the missing device, but it didn't help. root@Unraid:~# btrfs filesystem show Label: none uuid: XXX-XXX-XXX Total devices 2 FS bytes used 300.16GiB devid 1 size 931.51GiB used 303.03GiB path /dev/sdf1 devid 3 size 931.51GiB used 304.03GiB path /dev/sdg1 Do you have any ideas on how to fix this? Edited January 19, 20251 yr by marcins
January 19, 20251 yr Community Expert Reimporting the pool should correct that: on main click on the first device for that pool and then "remove pool" back on main, create a new pool with the same name and number of slots assign the pool device(s), leave the filesystem set to auto start the array to import the pool
January 19, 20251 yr Author The problem is that I don't have access to the GUI. The emhttp service, which handles the GUI, won't start. Even when I boot Unraid in safe mode, the GUI still doesn't work. I can only SSH into the server and use commands.
January 19, 20251 yr Author Solution I've fixed the issue by resetting the disk configuration. I had to delete the /boot/config/super.dat file, which contains the disk assignments, and the /boot/config/pool/<pool_name>.cfg, which was my cache pool configuration. This resolved the issue, and the GUI now starts. I had to assign the disk in the array and manually create a new cache pool, as JorgeB mentioned. Everything seems fine now. It looks like a bug to me. When a device in a pool is not present, it prevents the GUI (emhttp) from starting.
January 19, 20251 yr Community Expert You should remove the pool device using the GUI, that way it won't cause issues.
January 19, 20251 yr Author I removed the device using the GUI, left one of the three slots empty, and then restarted the server. I suppose missing device and the empty slot is the cause of the issue.
January 19, 20251 yr Community Expert 31 minutes ago, marcins said: I removed the device using the GUI, left one of the three slots empty, and then restarted the server. You need to start the array first so that the device can be removed from the pool and the cfg file updated.
May 8, 20251 yr On 1/19/2025 at 3:41 AM, marcins said: I've fixed the issue by resetting the disk configuration. I had to delete the /boot/config/super.dat file, which contains the disk assignments, and the /boot/config/pool/<pool_name>.cfg, which was my cache pool configuration. This resolved the issue, and the GUI now starts. I had to assign the disk in the array and manually create a new cache pool, as JorgeB mentioned. Everything seems fine now. It looks like a bug to me. When a device in a pool is not present, it prevents the GUI (emhttp) from starting. For weeks I have been trying to solve the same problem. Deleting /boot/config/pool/cache.cfg was it. THANK YOU!
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.