I just updated to Unraid v 6.12.4 and now a whole lot of my containers will not start.

 

On server reboot I see a lot of these in the log:

Oct 26 09:18:35 storeStep kernel: br-7f14e4841fe4: port 7(vethd64225f) entered blocking state

Oct 26 09:18:35 storeStep kernel: br-7f14e4841fe4: port 7(vethd64225f) entered disabled state

Oct 26 09:18:35 storeStep kernel: device vethd64225f entered promiscuous mode

Oct 26 09:18:52 storeStep kernel: vethf21ecfb: renamed from eth0

 

From the logs of some containers that won't start, it seems the file system is read only:

Zigbee2MQTT:error 2023-10-26 08:14:14: Failed to write state to '/app/data/state.json' (EROFS: read-only file system, open '/app/data/state.json')

 

Any idea what's going on here and how to fix it?

storestep-diagnostics-20231026-0928.zip

UPDATE:
Also, all the containers that do start can't find their container data. It's like they're starting for the first time, asking to set them up and configure them.

UPDATE:
I am just now seeing that my cache disk is not recognized. In the main tab under Cache it simply says:

Not installed

 

There's no cache device assigned, check connections.

Hi @JorgeB

 

I turned off the server to check all connections. They seemed fine, however I thought I would create a disk image of the disk (as a backup) before rebooting, however I could not initialize the disk in windows..

 

Re-connecting the disk and booting up the server gives this result (which seems fine):

 

Starting the array however, results in this error: Unmountable: Unsupported or no file system

 

Also:
The disk is listed under "Historical Devices" as well

 

Under Fix Common Problems I get this error:

Where I fall into the latter category (If the disk is listed as being unmountable, and it has data on it, whatever you do do not hit the format button. Seek assistance HERE).

and it also lists a bunch of warnings, all referencing "non existent pool cache".

 

 

And so that's where I'm stuck right now.

Any and all suggestions are very welcome ❤️ 

Edited October 26, 20232 yr by tTownTom
Added "Historical Devices" and "Fix common problems"

 

This means the SSD failed, typical issue with multiple models based on the same controller, you will need to replace it.

Just now, JorgeB said:

 

This means the SSD failed, typical issue with multiple models based on the same controller, you will need to replace it.

Thank you for your reply!

 

When replacing it, will I have to set every container up from scratch? 😬

If you don't have a backup or can recover the current appdata you will to.

12 minutes ago, JorgeB said:

If you don't have a backup or can recover the current appdata you will to.

..sure hope those weekly backups actually did their job 🙃

 

Would having multiple cache drives solve this in the future? Or is that not how cache pools work?

11 minutes ago, tTownTom said:

Would having multiple cache drives solve this in the future?

Yes, as long has just one of them failed.