-
[Support] omada-controller
I don't know what to say to that. "Probably"? The only thing I know is that I have the docker running since a year, updated the controller several times in the meantime and never had this problem before. So, where does this leave me now?
-
[Support] omada-controller
I updated this morning and just get a page for starting a new configuration when tryin to login to the Controller. Seems like for me all settings are still vanished. Haven't tried to set it up and load a saved config yet. Might work that way, still something is wrong with the update, I believe. EDIT: Even when I load a backup all the devices state "managed by others" and would have to be adapted again
-
[Support] omada-controller
Since an update today I cannot log into the controller anymore. Does anybody else have that problem? I am very sure that I am using the correct credentials.
-
Upgrade from 6.11.5 to 6.12 results in "Unmountable: Unsupported or no file system" of cache drive
And I thought I made a clean stick after my purchase 😟 I am sorry for the inconvenience and thanks a lot, that fixed it!
-
-
Upgrade from 6.11.5 to 6.12 results in "Unmountable: Unsupported or no file system" of cache drive
Hi, I started this topic yesterday already, but unfortunately it seems like it never went online. After upgrade from 6.11.5 to 6.12 my array did not start by itself. After manual start the disk where shown, but the cache disk says "Unmountable: Unsupported or no file system" (btfrs) on the main page. Dashboard says "active" and "healthy". I rebooted without any luck. Stopping and restarting he array resulted in having the array disks "unmountable" as well, but shares where shown. Rebooting the system then lead the array to be mounted, but the cache drive still not. Any quick fix for this? EDIT: I was using firefox, but tried reboot and restarting the array with chrome now as well. Filesystem check for the cache drive when having the array mounted in maintenance mode is: [1/7] checking root items [2/7] checking extents [3/7] checking free space tree [4/7] checking fs roots [5/7] checking only csums items (without verifying data) [6/7] checking root refs [7/7] checking quota groups skipped (not enabled on this FS) Opening filesystem to check... Checking filesystem on /dev/nvme0n1p1 UUID: bcc8c2c1-6a0e-4102-80fa-c016887e8f9b found 64720146432 bytes used, no error found total csum bytes: 62366748 total tree bytes: 367788032 total fs tree bytes: 168951808 total extent tree bytes: 108691456 btree space waste bytes: 73862023 file data blocks allocated: 180418424832 referenced 61422522368 trainstation-diagnostics-20230620-0948.zip
LotF
Members
-
Joined
-
Last visited