Nach online update opensuse 12.3 startet nicht mehr

Hallo,

kernel BUG at fs/btrfs/extent-tree.c:6185!
>>> http://comments.gmane.org/gman….file-systems.btrfs/23020

Zitat

I had to use btrfs-zero-log before it could mount again.

Btrfs Problem FAQ
>>> https://btrfs.wiki.kernel.org/index.php/Problem_FAQ

Zitat

You will need to build and run the btrfs-zero-log tool: get a recent copy of the user-space tools, and build them:

Code

$ make
$ make btrfs-zero-log

Then, run it as root, but BEFORE YOU DO THIS, PLEASE RUN btrfs-image

Code

gandalfthegreat:~# btrfs-image -c 9 -t 8 /dev/mapper/root /var/tmp/fs_image 
 gandalfthegreat:~# btrfs-zero-log /dev/mapper/root                                                        
 Check tree block failed, want=4268204032, have=2075122916315869932                                        
 Check tree block failed, want=4268204032, have=2075122916315869932                                        
 Check tree block failed, want=4268204032, have=12746175583536274708                                       
 Check tree block failed, want=4268204032, have=2075122916315869932                                        
 Check tree block failed, want=4268204032, have=2075122916315869932                                        
 read block failed check_tree_block                                                                        
 gandalfthegreat:~# btrfs-zero-log /dev/mapper/root                                                        
 gandalfthegreat:~#

(replacing /dev/mapper/root with whatever device(s) your FS resides on). Please Email the btrfs list, explain the problem, and offer your filesystem image to a developer.

Running btrfs-zero-log on a filesystem with any other kind of mount problem will most likely not fix it, and may make recovering it harder. If in doubt, check with the developers on IRC or the mailing list first.

Alles anzeigen

Da Du btrfs verwendest

Zitat von Btrfs wiki

It is still in heavy development and marked as unstable.

können wir davon ausgehen dass Du weisst wie damit umgehen

Gruss,
Roland

Aber in Deinem Splash sehe ich zuunterst:

Zitat

Code

...
...exiting to /bin/sh

???

Ansonsten: Vielleicht von einem Life-Linux booten und dann mit "chroot" weitermachen?

-/-