eraser1320

Hello! Thanks so much for the excellent update! I'd just like to confirm my understanding is correct here. I'm trying to migrate to internal boot. I've run the migration wizard, which said it worked moving to my new internal drives. I saw the waring about switching the boot order, which I didn't change. So now I have the warning "Internal Boot Available". I'm assuming this means I'm still booting from my original USB. Do I just need to change the boot order in my BIOS? Will the fact that I've been running for 24 hours on the USB after the migration cause any issues?

Is it possible to backup the current config and roll back to it if something happens to go wrong? Thanks!

I was wondering the correct process to remove the array and keep my existing zfs pools using a new config. I know you have to create a new config with the array stopped. I currently have just a USB stick with nothing on it that's my array. I have 3 zfs pool, 2 of them are encrypted. Appreciate the help in the proper steps to avoid data loss.

Same thing happened to me, turned out it was something had happened to docker. Deleted it and reinstalled everything, now all is well again.

I ended up deleting my image, changing to overlay2 and reinstalling everything. So far so good.

It looks like it was something related to by docker. I deleted my image, changed to overlay2 and reinstalled everything.

The browser debug gives me this: unraid-components.client-_93nHWRM.js:78 [GraphQL error] Object (anonymous) @ unraid-components.client-_93nHWRM.js:78 unraid-components.client-_93nHWRM.js:84 [serverStateQuery] error ApolloError: Error message not found. at new tee (unraid-components.cl…3nHWRM.js:78:217857) at unraid-components.cl…3nHWRM.js:78:305533 at nee (unraid-components.cl…3nHWRM.js:78:209243) at unraid-components.cl…3nHWRM.js:78:209141 at new Promise (<anonymous>) at Object.then (unraid-components.cl…3nHWRM.js:78:209103) at Object.next (unraid-components.cl…3nHWRM.js:78:209261) at Yqe (unraid-components.cl…3nHWRM.js:78:202137) at qqe (unraid-components.cl…3nHWRM.js:78:202725) at tee.next (unraid-components.cl…3nHWRM.js:78:203320) unraid-components.client-_93nHWRM.js:78 [setError] Object unraid-components.client-_93nHWRM.js:78 Uncaught (in promise) ApolloError: Error message not found. at new tee (unraid-components.cl…3nHWRM.js:78:217857) at unraid-components.cl…3nHWRM.js:78:305533 at nee (unraid-components.cl…3nHWRM.js:78:209243) at unraid-components.cl…3nHWRM.js:78:209141 at new Promise (<anonymous>) at Object.then (unraid-components.cl…3nHWRM.js:78:209103) at Object.next (unraid-components.cl…3nHWRM.js:78:209261) at Yqe (unraid-components.cl…3nHWRM.js:78:202137) at qqe (unraid-components.cl…3nHWRM.js:78:202725) at tee.next (unraid-components.cl…3nHWRM.js:78:203320) And then then repeating over and over again: unraid-components.client-_93nHWRM.js:78 WebSocket connection to 'ws://xxx.xxx.xxx.x/graphql' failed: (anonymous) @ unraid-components.client-_93nHWRM.js:78 unraid-components.client-_93nHWRM.js:78 WebSocket connection to 'ws://xxx.xxx.xxx.x/graphql' failed: (anonymous) @ unraid-components.client-_93nHWRM.js:78 unraid-components.client-_93nHWRM.js:78 WebSocket connection to 'ws://xxx.xxx.xxx.x/graphql' failed: (anonymous) @ unraid-components.client-_93nHWRM.js:78

It happens on Brave and Firefox, and after I've cleared cache and cookies. But interestingly it doesn't happen on Brave on Android mobile. I've also been getting an "Unraid API is currently offline" waring this whole time, but when I click on go to connect it says online. Not to sure if it's related.

Here are the latest diagnostics. Interestingly when I just logged in everything was back to normal, but then I clicked off the unraid tab, and when I went back to it, the gui was back to the half dead state as described in this issue. Thanks! tiger-diagnostics-20250501-0722.zip

It was yes, I'll grab another set today.

I have a strange issue that's just cropped up. Unraid seems to be working just fine, array docker VMs start and all run fine. However, the web gui stops updating any real time information. The Dashboard tab becomes static. The main tab goes to starting and listing everything fine, to nothing listed besides the array operations. All shares and users are there are fully accessible. When I go to update a plugin, it just bounces and nothing ever read out in the box, but when refreshed it's updated just fine. Same with creating a diagnostic file, it just bounces in the window with no test every updating, but the files are created just fine. I've attached one. PS - This started happening on 7.0.1. I updated to 7.1.0rc3 to see of that made a difference, same exact behavior. Thanks! tiger-diagnostics-20250430-1637.zip

I'll need to try again later because my first attempt didn't work. After making sure nothing would auto start, and a fresh reboot of unraid, docker started up, and the problem container was in a "dead" state. I assumed I should start all containers I want to keep so the prune doesn't delete them. The prune didn't find the problem container to delete, and when I checked the docker tab again, the problem container was back the in the "removal in process" state. Is there any way to directly delete the offending image form the array before docker is started? Thanks for the help!

Adding --volumes got rid of some old unrelated stuff, but didn't not get rid of the Removal in Process container. Thanks though.

One of my docker containers seems to have bugged out. At first it wouldn't start up anymore, I didn't really care about the container, so I ignored it. After a while docker it's self started to get really laggy, so I stopped and restarted the docker service, but docker wouldn't start up again. I did a bunch of searching, there weren't any terminals open or anything like that, it seemed tied to the one container being busy. I tried to restart unraid, I always shut down the array first manually first, but it even got stuck shutting down the array because of the busy container. I rebooted unraid and everything come back up fine, tried to delete the problem container, and now it's stuck in a "Removal in Progress" state. I've tried to search a bunch of CLI ways how to kill it, but none of the solutions I've found have worked so far. Attached are the diagnostics. I don't care about the container in question at all, just want to get rid of it without messing anything else up. Thanks for the help! tiger-diagnostics-20250426-1052.zip

Same..