Fail to update to 1.7.0

Endymion · July 29, 2026, 9:24pm

Hello everyone, and thank you for your work.
I’m having a problem with the recent update to 1.7.0: updating from the GUI or via SSH fails.
I have generic hardware with an N150 CPU.
I’m looking for help.

Bin · July 30, 2026, 3:00am

@Endymion It would be better if you could give us some logs or error messages for us to analyze.

Endymion · July 30, 2026, 6:01am

After fail update via GUI i try:

root@ZimaOS:/root ➜ # curl -fsSL ‘https://ota.zimaos.com/’ | sh

[INFO] ZimaOS upgrade script starting…

[INFO] Current version: 1.6.2

[INFO] Current channel: stable

[INFO] Getting latest version for channel: stable

[INFO] Target version: 1.7.0

[INFO] Starting system upgrade…

[INFO] Attempting download (try 1): zimaos-x86_64-1.7.0.raucb

######################################################################## 100.0%

[SUCCESS] Download successful: zimaos-x86_64-1.7.0.raucb

[INFO] Installing zimaos-x86_64-1.7.0.raucb…

installing

0% Installing

0% Determining slot states

10% Determining slot states done.

10% Checking bundle

10% Verifying signature

20% Verifying signature done.

20% Checking bundle done.

20% Checking manifest contents

30% Checking manifest contents done.

30% Determining target install group

40% Determining target install group done.

40% Updating slots

40% Checking slot boot.0

42% Checking slot boot.0 done.

42% Copying image to boot.0

60% Copying image to boot.0 done.

60% Checking slot kernel.0 (A)

62% Checking slot kernel.0 (A) done.

62% Copying image to kernel.0

[cut]

80% Copying image to kernel.0 done.

80% Checking slot rootfs.0

82% Checking slot rootfs.0 done.

82% Copying image to rootfs.0

[cut]

99% Copying image to rootfs.0

99% Copying image to rootfs.0 failed.

99% Updating slots failed.

100% Installing failed.

LastError: Installation error: Failed updating slot rootfs.0: Syncing content to disk failed: Input/output error

Installing `/tmp/zimaos_upgrade/zimaos-x86_64-1.7.0.raucb` failed

[ERROR] Upgrade failed

[INFO] Cleaning up temporary files…

so i checck rauc statuss

rauc status=== System Info ===Compatible: zimaos-zimacubeVariant: Booted from: kernel.1 (B)=== Bootloader ===Activated: kernel.1 (B)=== Slot States === [boot.0] (/dev/disk/by-partlabel/casaos-boot, vfat, inactive)○ [kernel.0] (/dev/disk/by-partlabel/casaos-kernel0, raw, inactive) bootname: A boot status: bad [rootfs.0] (/dev/disk/by-partlabel/casaos-system0, raw, inactive) [kernel.1] (/dev/disk/by-partlabel/casaos-kernel1, raw, booted) bootname: B boot status: good [rootfs.1] (/dev/disk/by-partlabel/casaos-system1, raw, active)

Endymion · July 31, 2026, 7:55pm

No help?

Zima-Jerry · August 3, 2026, 8:20am

Regarding your question, we suspect that there may be an error with the system’s disk configuration. You can use the root account in ZimaOS to execute the following command, and then report the results to us. This will help us identify the specific issue.

curl -fsSL https://get.casaos.io/check-disk-health.sh | sh -s -- --read-scan

Endymion · August 3, 2026, 5:15pm

thks hera my result…

root@ZimaOS:/root ➜ # curl -fsSL https://get.casaos.io/check-disk-health.sh | sh -s – --read-scan
ZimaOS disk health check
Time: 2026-08-03T17:13:50Z
Mode: read-only diagnostics
[INFO] System disk: /dev/sdb

=== Disk /dev/sdb ===
sdb 476.9G 0 sata Firebat FSTC30A-512G
[PASS] /dev/sdb is writable at the block-device layer.
SMART/NVMe health:
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
SMART overall-health self-assessment test result: PASSED
Current Temperature: 40 Celsius
Power Cycle Min/Max Temperature: 40/40 Celsius
Lifetime Min/Max Temperature: 23/40 Celsius
Specified Max Operating Temperature: 100 Celsius
[PASS] /dev/sdb reports a passing SMART health status.
[FAIL] /dev/sdb returned SMART failure status (smartctl exit code 4).

=== Kernel log ===
[FAIL] Kernel storage errors were found during the current boot:
Aug 02 00:05:26 ZimaOS kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Aug 02 00:05:26 ZimaOS kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Aug 02 00:05:26 ZimaOS kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Aug 02 00:05:26 ZimaOS kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Aug 02 00:05:26 ZimaOS kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Aug 02 00:05:26 ZimaOS kernel: ata2.00: failed command: READ FPDMA QUEUED
Aug 02 00:05:26 ZimaOS kernel: ata2.00: failed command: READ FPDMA QUEUED
Aug 02 00:05:26 ZimaOS kernel: ata2.00: failed command: READ FPDMA QUEUED
Aug 02 00:05:26 ZimaOS kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Aug 02 00:05:26 ZimaOS kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Aug 02 00:05:26 ZimaOS kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Aug 02 00:05:26 ZimaOS kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Aug 02 00:05:26 ZimaOS kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Aug 02 00:05:26 ZimaOS kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Aug 02 00:05:26 ZimaOS kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Aug 02 00:05:26 ZimaOS kernel: ata2: hard resetting link
Aug 02 00:05:26 ZimaOS kernel: I/O error, dev sdb, sector 387344384 op 0x1:(WRITE) flags 0x0 phys_seg 65 prio class 2
Aug 02 00:05:26 ZimaOS kernel: EXT4-fs warning (device sdb8): ext4_end_bio:368: I/O error 10 writing to inode 15472783 starting block 48418048)
Aug 02 00:05:26 ZimaOS kernel: Buffer I/O error on device sdb8, logical block 45223936
Aug 02 00:05:26 ZimaOS kernel: I/O error, dev sdb, sector 315612416 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2
Aug 02 00:05:26 ZimaOS kernel: Buffer I/O error on device sdb8, logical block 45223937
Aug 02 00:05:26 ZimaOS kernel: Buffer I/O error on device sdb8, logical block 45223938
Aug 02 00:05:26 ZimaOS kernel: Buffer I/O error on device sdb8, logical block 45223939
Aug 02 00:05:26 ZimaOS kernel: Buffer I/O error on device sdb8, logical block 45223940
Aug 02 00:05:26 ZimaOS kernel: Buffer I/O error on device sdb8, logical block 45223941
Aug 02 00:05:26 ZimaOS kernel: Buffer I/O error on device sdb8, logical block 45223942
Aug 02 00:05:26 ZimaOS kernel: Buffer I/O error on device sdb8, logical block 45223943
Aug 02 00:05:26 ZimaOS kernel: Buffer I/O error on device sdb8, logical block 45223944
Aug 02 00:05:26 ZimaOS kernel: Buffer I/O error on device sdb8, logical block 45223945
Aug 02 00:05:26 ZimaOS kernel: I/O error, dev sdb, sector 315612672 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2

=== Read scan /dev/sdb3 ===
[INFO] Reading the complete system slot. This may take several minutes; no data will be written.

[PASS] The complete /dev/sdb3 slot was read without an I/O error.

=== Result ===
UNHEALTHY: disk or storage I/O errors were detected. Back up data before retrying an upgrade.
Note: a passing result reduces risk but cannot guarantee that a disk will not fail.

Zima-Jerry · August 4, 2026, 2:33am

Based on the diagnostic output, the issue is very likely related to the /dev/sdb storage device or its SATA connection, rather than the OTA package, signature, or RAUC configuration.

The most important errors are:

ata2.00: failed command: WRITE FPDMA QUEUED
ata2.00: failed command: READ FPDMA QUEUED
ata2: hard resetting link
I/O error, dev sdb
Buffer I/O error on device sdb8

These messages show that the SATA device encountered low-level read/write failures and that the kernel had to reset the SATA link. During an OTA update, RAUC continuously writes the inactive system slot and then flushes the data to disk. This kind of storage failure can directly cause:

Syncing content to disk failed: Input/output error

Therefore, the previous RAUC update failure was most likely caused by the same underlying storage problem.

Although SMART reports:

SMART overall-health self-assessment test result: PASSED

this does not guarantee that the device is healthy. SMART only reports whether the drive has reached its vendor-defined failure thresholds. It may not detect an intermittent SATA cable, power, connector, controller, or sustained-write problem.

The script also reported:

smartctl exit code 4

This code alone does not necessarily mean that the SSD has failed; it can indicate that a SMART command could not be completed successfully. However, combined with the kernel’s repeated read/write errors and SATA link reset, the storage path must be treated as unreliable.

Recommended actions:

Back up /DATA and all important data immediately. Do not repeatedly retry the OTA update.
Shut the system down completely and disconnect power.
Reseat the SATA data and power cables. If possible, replace the SATA cable and use another SATA port.
Check that the drive is firmly installed and that the power connection is stable.

After rebooting, collect the full SMART and error logs:

smartctl -x /dev/sdb
smartctl -l error /dev/sdb
smartctl -l selftest /dev/sdb

If READ FPDMA QUEUED, WRITE FPDMA QUEUED, hard resetting link, or I/O error messages continue after changing the cable and port, replace the SSD. If the same problem occurs with a new SSD, the SATA controller, motherboard, or power supply should be investigated.

Only retry the system upgrade after the storage problem has been resolved and the important data has been backed up. Do not manually mark the failed RAUC slot as good, and do not force the system to boot from an incompletely updated slot.