On 02/16/2015 04:19 PM, John Andersen wrote:

Right now I'm running on my rescue CD on my Linux Laptop. I was right in the middle of posting to this list when the machine just locked up flashed the keyboard lights, fell back to a console display full of scary messages.

Booting again, same result, and the messages suggest btrfs has bitten the dust. Booting from a read only snapshot, same result.

The best I could do is take phone pics of the screen, and now I'm in recovery mode (which seems to work fine) and am about to try some btrfs diagnostics and see what I can find out without doing any more damage.

Opensuse 13.2 x86_64.

Any suggestions would be welcome.

Well that was fun. Apparently, the best I can determine by looking at my camera shots, is that the root file system became corrupted, systemd died, machine panicked and left we with a machine with blinking caps/num lock lights. I booted recovery with the CDROM and (reading man pages from the web on another machine) I did: btrfs check /dev/sda2 Saw a bunch of errors talking about corrupt extent records, backref parents not found in extent tree, and similar obscure references. So I did btrfs check --repair /dev/sda2 and it said it was fixing things. When that was done I did the btrfs check again and it seemed to have no problem on the partition. So I mounted it under /mnt (of the recover system) and peeked at enough things to convince me it would probably boot. but while I had it mounted I ran btrfs scrub start -B /dev/sda2 and it only took 144 seconds and said it fixed some things, (I forgot to take pictures of the screen, and had no other way to save these messages). I rebooted and everything came up just fine. I have no clue what caused it, but I've read about problems with Btrfs on this kernel suddenly being mounted read-only in response to problems, which leads to crashes. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org