Uptime was just a couple of hours short of reaching 6 days, which would have been the first time it reached that threshold instead of its usual freezing or rebooting sometime during the 5th day. Alas, once more it did not make it, but this time it did damage. All temperatures were normal, cpu & RAM usage were low, no external power dip occurred, TW [20171125] had been behaving beautifully. Until…
…i needed to go to bed, so i went to Suspend TW. It did not respond. I tried again, thinking my click had not registered. It gave a warning message that a suspend job was already queued [not those exact words], but otherwise ignored me again. Fearing that this was the beginning of another crash, i began closing all my open docs & pgms, preparatory to doing a full shutdown. Each respective window duly closed, but KSysGuard showed their processes still ran & would not be manually killed when i tried therein]. I tried the Shutdown widget, initially which seemed to work, but then a TTY appeared instead of the desktop, & proceeded to fill with continuous error messages, mentioning that the write job was being ignored due to the read-only file system. Oh noooooooo, not that rotten problem *yet again!
*
After 15’ those errors just continued streaming along in TTY, so i did REISUB, to which it did respond. Upon the reboot all looked normal until i reached the passphrase screen to decrypt my /dev/sda3 & mount my /home. It accepted my passphrase, but almost immediately gave simply a blank screen with blinking top lhs cursor. This was repeatable. Groan.
Remembering the last time this [read-only filesystem] occurred, & what solved it, https://forums.opensuse.org/showthread.php/527390-BtrFS-has-gone-ReadOnly-again?p=2840121#post2840121, i attempted the same rescue… booted Tower from my Krypton USB, & tried the btrfs repair. It was not a good outcome this time:
linux@localhost:~> **sudo blkid**
/dev/sdc3: LABEL="hybrid" UUID="f232076a-c63b-424b-af27-a7a23b07a49a" TYPE="ext4" PARTUUID="c0bef442-03"
/dev/sdc2: UUID="2017-07-10-10-52-11-00" LABEL="\"openSUSE Krypton Stable\"" TYPE="iso9660" PARTUUID="c0bef442-02"
/dev/loop0: TYPE="squashfs"
/dev/sdb1: UUID="1be44f1e-8593-460e-91ab-c6132245f640" TYPE="crypto_LUKS" PARTUUID="00060756-01"
/dev/sda1: SEC_TYPE="msdos" UUID="DFF3-1AD7" TYPE="vfat" PARTLABEL="primary" PARTUUID="bde1c356-f603-4a7e-ad42-c399c35f9750"
/dev/sda2: LABEL="root" UUID="f3e11c85-7f1a-4e9e-8585-5b6a61e4ea8c" UUID_SUB="65ee96ef-42d9-4fe4-b96c-c57e868cc214" TYPE="btrfs" PARTLABEL="primary" PARTUUID="b56c2d68-cc5f-48e7-bbd0-2b981a6c602a"
/dev/sda3: UUID="a3869823-41e7-498d-abe7-84438db8f4af" TYPE="crypto_LUKS" PARTLABEL="primary" PARTUUID="d2fc8cea-af0e-446f-8a59-264cc59a1451"
/dev/sdb2: LABEL="SeagateSpare" UUID="f4ae6a8c-a541-4bbd-b086-6358872a3962" TYPE="xfs" PARTUUID="00060756-02"
/dev/sdb3: LABEL="Seagate" UUID="23927deb-03f4-4b7b-9599-9e44c9f86919" TYPE="ext4" PARTUUID="00060756-03"
/dev/sdc1: SEC_TYPE="msdos" LABEL="BOOT" UUID="BA91-72AD" TYPE="vfat" PARTUUID="c0bef442-01"
linux@localhost:~> **sudo btrfs check --repair /dev/sda2**
enabling repair mode
incorrect offsets 12731 12987
Checking filesystem on /dev/sda2
UUID: f3e11c85-7f1a-4e9e-8585-5b6a61e4ea8c
checking extents
incorrect offsets 12731 12987
incorrect offsets 12731 12987
Unable to find block group for 0
extent-tree.c:287: find_search_start: Warning: assertion `1` failed, value 1
btrfs(btrfs_reserve_extent+0x637)[0x55fbb2672527]
btrfs(btrfs_alloc_free_block+0x5f)[0x55fbb2672bbf]
btrfs(__btrfs_cow_block+0x182)[0x55fbb26632a2]
btrfs(btrfs_cow_block+0x10a)[0x55fbb2663aaa]
btrfs(btrfs_search_slot+0x2d3)[0x55fbb2666683]
btrfs(+0x1b000)[0x55fbb265e000]
btrfs(+0x1c275)[0x55fbb265f275]
btrfs(+0x1c8b9)[0x55fbb265f8b9]
btrfs(cmd_check+0xaf3)[0x55fbb26a77b3]
btrfs(main+0x84)[0x55fbb2661e34]
/lib64/libc.so.6(__libc_start_main+0xea)[0x7f39ca2f346a]
btrfs(_start+0x2a)[0x55fbb2661f4a]
Unable to find block group for 0
extent-tree.c:287: find_search_start: Warning: assertion `1` failed, value 1
btrfs(btrfs_reserve_extent+0x637)[0x55fbb2672527]
btrfs(btrfs_alloc_free_block+0x5f)[0x55fbb2672bbf]
btrfs(__btrfs_cow_block+0x182)[0x55fbb26632a2]
btrfs(btrfs_cow_block+0x10a)[0x55fbb2663aaa]
btrfs(btrfs_search_slot+0x2d3)[0x55fbb2666683]
btrfs(+0x1b000)[0x55fbb265e000]
btrfs(+0x1c275)[0x55fbb265f275]
btrfs(+0x1c8b9)[0x55fbb265f8b9]
btrfs(cmd_check+0xaf3)[0x55fbb26a77b3]
btrfs(main+0x84)[0x55fbb2661e34]
/lib64/libc.so.6(__libc_start_main+0xea)[0x7f39ca2f346a]
btrfs(_start+0x2a)[0x55fbb2661f4a]
Unable to find block group for 0
extent-tree.c:287: find_search_start: Warning: assertion `1` failed, value 1
btrfs(btrfs_reserve_extent+0x637)[0x55fbb2672527]
btrfs(btrfs_alloc_free_block+0x5f)[0x55fbb2672bbf]
btrfs(__btrfs_cow_block+0x182)[0x55fbb26632a2]
btrfs(btrfs_cow_block+0x10a)[0x55fbb2663aaa]
btrfs(btrfs_search_slot+0x2d3)[0x55fbb2666683]
btrfs(+0x1b000)[0x55fbb265e000]
btrfs(+0x1c275)[0x55fbb265f275]
btrfs(+0x1c8b9)[0x55fbb265f8b9]
btrfs(cmd_check+0xaf3)[0x55fbb26a77b3]
btrfs(main+0x84)[0x55fbb2661e34]
/lib64/libc.so.6(__libc_start_main+0xea)[0x7f39ca2f346a]
btrfs(_start+0x2a)[0x55fbb2661f4a]
extent-tree.c:2696: btrfs_reserve_extent: BUG_ON `ret` triggered, value -28
btrfs(+0x2a5f6)[0x55fbb266d5f6]
btrfs(btrfs_reserve_extent+0x94b)[0x55fbb267283b]
btrfs(btrfs_alloc_free_block+0x5f)[0x55fbb2672bbf]
btrfs(__btrfs_cow_block+0x182)[0x55fbb26632a2]
btrfs(btrfs_cow_block+0x10a)[0x55fbb2663aaa]
btrfs(btrfs_search_slot+0x2d3)[0x55fbb2666683]
btrfs(+0x1b000)[0x55fbb265e000]
btrfs(+0x1c275)[0x55fbb265f275]
btrfs(+0x1c8b9)[0x55fbb265f8b9]
btrfs(cmd_check+0xaf3)[0x55fbb26a77b3]
btrfs(main+0x84)[0x55fbb2661e34]
/lib64/libc.so.6(__libc_start_main+0xea)[0x7f39ca2f346a]
btrfs(_start+0x2a)[0x55fbb2661f4a]
Aborted
linux@localhost:~>
The only bit of good fortune i had this time, was the surprise discovery that Krypton actually gave me access to my encrypted /home. It was literally as simple as navigating to that partition in Dolphin, clicking on it, & entering my passphrase into the resultant popup dialog box. Thank goodness!. So i have therefore been able to copy all my data to “/dev/sdb2: LABEL=“SeagateSpare”” temporarily, & am now [3:10am] going to bed.
Unless something happens in my dreams to change my mind, tomorrow i shall be ending my five month Tumbleweed dalliance. On both my Tower & Laptop there’s just been too many of these stressful serious incidents. TW’s Plasma5 runs superbly for a while, then out of the blue has a meltdown & gives me apoplexy, then the pattern repeats. My laptop stopped being TW two weeks ago after its last catastrophe, which lost all data [https://forums.opensuse.org/showthread.php/528173-Laptop-cpu-suddenly-went-to-99-now-can-boot-but-not-login?p=2845862#post2845862]. Tomorrow i regretfully think TW will be over too, for Tower. It’s sad.