Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Everything gets broken after upgrade to 1.3.1-1 #151

Open
ProtocolNebula opened this issue Jan 7, 2025 · 7 comments
Open

Everything gets broken after upgrade to 1.3.1-1 #151

ProtocolNebula opened this issue Jan 7, 2025 · 7 comments

Comments

@ProtocolNebula
Copy link

Hi,

After struggling with the updates (I left the topics open so can be fixed), I had to reboot twice the NAS, and, after that, this is what I found:

  • No GPU detected
  • No Dockers detected
  • If a monitor is attached, the main screen is trying to load something but is continously refreshing
  • Dockers are running

I guess ZimaOS is not for me at this development stage or I have enough bad luck to get all bugs 😢


Dashboard (without apps/dockers)

image


The main screen when boots

IMG_5176.mov

Dockers running

IMG_5177

@LinkLeong
Copy link
Contributor

I'm sorry for this problem, I'm not aware of any update failures at the moment, so there's no need to panic. First of all, our system is two partitions, so you can manually switch to the normal partition (keep pressing the up and down keys on your keyboard while zimaos is booting to see the interface for switching partitions.) You can start by reverting to the situation before the update, 然后你可以发送邮件到link@icewhale.org邮箱你的远程操作方式 and we will look at the issue remotely.

@R0GGER
Copy link

R0GGER commented Jan 9, 2025

Updating from 1.3.0-2 to 1.3.1-1 on Zimablade ☹️
What now?
upgrade

@R0GGER
Copy link

R0GGER commented Jan 9, 2025

The update made changes to the BIOS, altering the boot order.

  1. Windows Boot manager
  2. MMC
  3. EUFI OS (MMC)

Changed the order... and it boots again.
afbeelding

@Fralmar
Copy link

Fralmar commented Jan 10, 2025

So, ZimaOS is Stable then? I am doubting to install it to have nextcloud on it and access remote via.

@LinkLeong
Copy link
Contributor

The update made changes to the BIOS, altering the boot order.该更新对 BIOS 进行了更改,改变了启动顺序。

  1. Windows Boot manager  Windows 启动管理器
  2. MMC
  3. EUFI OS (MMC)  EUFI 操作系统 (MMC)

Changed the order... and it boots again.更改顺序...然后它再次启动。 afbeelding

System updates can't modify the boot order of the bios, the operating system doesn't have that privilege. As to what caused the change would require more information from you, such as what other actions were done.

@R0GGER
Copy link

R0GGER commented Jan 16, 2025

After updating ZimaOS, the system needed to be restarted. This is where it went wrong. I received the message “Reboot and select proper Boot device.” I’ve never had issues with updating before, but this time I did.

@LinkLeong What should I look at, and what information do you need?

@ProtocolNebula
Copy link
Author

ProtocolNebula commented Jan 17, 2025

I'm sorry for this problem, I'm not aware of any update failures at the moment, so there's no need to panic. First of all, our system is two partitions, so you can manually switch to the normal partition (keep pressing the up and down keys on your keyboard while zimaos is booting to see the interface for switching partitions.) You can start by reverting to the situation before the update, 然后你可以发送邮件到link@icewhale.org邮箱你的远程操作方式 and we will look at the issue remotely.

Thanks for the information,

It took me 15 minutes to boot with the previous installation, it had the last version but still a bit buggy, now I'm not sure what to do, my Zima is off since then, thinking if wait more time or migrate to a clean OS. It's a pain in the ass, I don't want to leave Zima OS but I have no time to struggle with erros everytime it updates (the server will be in a difficult access zone away from my home).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants