Can't roll back after 3.8.0 upgrade

#1

Hey! Thanks for this! I have some other issue. My laptop with the endless 3.8.0 keep freezing and the only way to go on using is restart it with the power off button. I managed to restart it with the previous version of endless( 7.8), but I can’t change it back as you described. The error is:Commit dd7c0a54a0c6303e7eea425dd4e11cf37ebb99ed55d84881ce8308a950fc28ee: Commit has collection ID ‘com.endlessm.Os’ in collection binding metadata, while the remote it came from has collection ID ‘com.endlessm.Demo.Os’.

What else can I do about it?
Thanks for helping me!.

By the way, with the new version the hexadecimal sting looks like this:51610f7af0cc1d2e0880024e634d00883a0f61bbdf00656f384aa7fb647f5789.0 (pending)

Release | Endless OS 3.8.0
#2

I think the instructions you were referring to were these from @egrath which I moved to a different thread:

For the record, we have a built-in eos-rollback command to do this in one step.

The error message you give above is interesting because it refers to com.endlessm.Demo.Os. Had you previously switched to the beta channel? Can you get a diagnostics file by following these instructions, and attach it here?

#3

Heyeos-diagnostic-200507_222559_UTC 0200.txt|attachment (780,7 kB)

Here is my file. I think I might have switched to a beta version trying to fix the bugs at the first place. Thanks for help!

#4

eos-diagnostic-200507_222559_UTC 0200.txt (780,7 kB)

#5

Please forgive the slow response.

[remote "eos"]
url=https://ostree.endlessm.com/staging/demo/eos-amd64
branches=os/eos/amd64/eos3a;
xa.disable=true
collection-id=com.endlessm.Demo.Os

Yep, you’re on the beta channel.

You should be able to switch back to the previous deployment with:

pkexec eos-rollback

However, you may want to try upgrading to 3.8.1 which was released yesterday. If you’re not already on it, try booting to 3.7.8 then running:

pkexec eos-stage-ostree prod
eos-updater-ctl update

This release includes some firmware that was missing from the 3.8.0 release, and has been reported to fix issues on some other Wi-Fi devices too. It would be interesting to know whether it fixes your case. (Your log shows your device uses the nl80211 driver.)

#6

excuse me…i did exactly what you said, but this happened. what’s wrong?

image
image1366×768 94.5 KB

eos-diagnostic-200601_013400_UTC 0800.txt (2.4 MB)

#7

@Maurice_Lenard_Cempr

Jun 01 01:34:11 endless kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jun 01 01:34:11 endless kernel: ata1.00: configured for UDMA/133
Jun 01 01:34:11 endless kernel: sd 0:0:0:0: [sda] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jun 01 01:34:11 endless kernel: sd 0:0:0:0: [sda] tag#5 Sense Key : Medium Error [current] 
Jun 01 01:34:11 endless kernel: sd 0:0:0:0: [sda] tag#5 Add. Sense: Unrecovered read error - auto reallocate failed
Jun 01 01:34:11 endless kernel: sd 0:0:0:0: [sda] tag#5 CDB: Read(10) 28 00 1c 43 05 68 00 00 08 00
Jun 01 01:34:11 endless kernel: blk_update_request: I/O error, dev sda, sector 474154344 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
Jun 01 01:34:11 endless kernel: EXT4-fs warning (device sda3): htree_dirblock_to_tree:997: inode #14811792: lblock 93: comm ThreadPoolForeg: error -5 reading directory block
Jun 01 01:34:11 endless kernel: ata1: EH complete
Jun 01 01:34:12 endless polkitd[2450]: Unregistered Authentication Agent for unix-process:8230:72204 (system bus name :1.456, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Jun 01 01:34:14 endless kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x50000 action 0x0
Jun 01 01:34:14 endless kernel: ata1.00: irq_stat 0x40000001
Jun 01 01:34:14 endless kernel: ata1: SError: { PHYRdyChg CommWake }
Jun 01 01:34:14 endless kernel: ata1.00: failed command: READ DMA EXT
Jun 01 01:34:14 endless kernel: ata1.00: cmd 25/00:08:68:05:43/00:00:1c:00:00/e0 tag 3 dma 4096 in
                                         res 51/40:00:68:05:43/00:00:1c:00:00/00 Emask 0x9 (media error)
Jun 01 01:34:14 endless kernel: ata1.00: status: { DRDY ERR }
Jun 01 01:34:14 endless kernel: ata1.00: error: { UNC }
Jun 01 01:34:14 endless kernel: ata1: hard resetting link

This pattern of messages is repeated over and over in your journal. I think your hard disk is failing or there is another physical problem with your device – I suggest you back up your data as soon as possible, then contact the computer manufacturer.

#8

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.