http://bugzilla.opensuse.org/show_bug.cgi?id=1205445 Bug ID: 1205445 Summary: transactional-update breaks system after some time. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs@opensuse.org Reporter: samcon@protonmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- dear experts, I've been running MicroOS headless on multiple raspberry-pi 3bs with single service (excl. system services) and/or as container host. After some time, the devices no longer boots correctly, I am unable to ssh or ping device. Since I didn't have extra monitor, I would do clean install of MicroOS (with Combustion). Doing this multiple times over the past months, I assumed maybe the SD cards were corrupt so I used another SD card, unfortunately, after sometime same happened. I got my hands on dell inspiron tower, I installed MicroOS last week. This time disabling transactional-update.timer. Everything was working fine until I enabled transactional-update.timer last week Wednesday, yesterday (Monday) I attempted to ssh into machine and found it was no longer reachable. I now have a monitor, plugged it in and am welcomed by blank screen (no login prompt). After force rebooting machine I am welcomed with: "Notice ��� Hard drive self monitoring system has reported that a parameter has exceeded its normal operating range. Dell recommends that you back up your data regularly. A parameter out of range may or may not indicate a potential hard drive problem Press F2 to Resume" Pressing F2, then waiting ... I eventually I see underscore cursor flashing and nothing happens. Where do I go from here? I am unable to get to bootloader to log into device to check logs or to perform btrfs rollback. Kind regards, Sam -- You are receiving this mail because: You are on the CC list for the bug.