Aw: Re: Re: Re: [opensuse] system not booting
Gesendet: Dienstag, 26. Januar 2016 um 12:53 Uhr Von: "Bob Williams" <linux@karmasailing.uk> An: opensuse@opensuse.org Betreff: Re: Aw: Re: Re: [opensuse] system not booting On 26/01/16 11:13, Benjamin Draxlbauer wrote:
Gesendet: Dienstag, 26. Januar 2016 um 11:37 Uhr Von: "Stanislav Baiduzhyi" <baiduzhyi.devel@gmail.com> An: opensuse <opensuse@opensuse.org> Betreff: Re: Re: [opensuse] system not booting On Tue, Jan 26, 2016 at 11:13 AM, Benjamin Draxlbauer <Benjamin10@gmx.at> wrote:
Thanks for the hint…Where should i add this line? I am not familiar on this type of stuff…
you can try that from rescue cd, gparted-live-cd is my personal favourite, and do something like this in terminal: sudo su - root mkdir /mnt/sda3 mount -t btrfs -o clear_cache /dev/sda3 /mnt/sda3
if that command succeeds then clearing cache helped and you can try rebooting to your main system. Otherwise you have different problem, maybe someone else will be able to advice something. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Okay, i tried it within a terminal in ubunut which is the second system i am running on my laptop…
sudo mount -t btrfs -o clear_cache /dev/sda3 /mnt/sda3 mount: Falscher Dateisystemtyp, ungültige Optionen, der Superblock von /dev/sda3 ist beschädigt, fehlende Kodierungsseite oder ein anderer Fehler Manchmal liefert das Systemprotokoll wertvolle Informationen, versuchen Sie »dmesg | tail« oder so
and dmesg tells the following:
dmesg | tail [ 514.164113] parent transid verify failed on 35295068160 wanted 41939771539587072 found 25424 [ 514.164117] BTRFS: failed to read chunk root on sda3 [ 514.182238] BTRFS: open_ctree failed [ 593.703113] BTRFS info (device sda3): force clearing of disk cache [ 593.703118] BTRFS info (device sda3): disk space caching is enabled [ 593.703120] BTRFS: has skinny extents [ 593.711602] parent transid verify failed on 35295068160 wanted 41939771539587072 found 25424 [ 593.723735] parent transid verify failed on 35295068160 wanted 41939771539587072 found 25424 [ 593.723742] BTRFS: failed to read chunk root on sda3 [ 593.741048] BTRFS: open_ctree failed
Almost the same as in my first mail…Any suggestions? This looks quite critical…and…i don't have a recent update!!!
You haven't mentioned which version of opensuse you are running, and more importantly, which kernel.
You'll probably get more help on the linux-btrfs@vger.kernel.org list. First question they'll ask is are you running an up to date kernel and an up to date version of btrfs-progs.
Bob -- Bob Williams System: Linux 4.1.13-5-default Distro: openSUSE 42.1 (x86_64) with KDE Development Platform: 4.14.10
Thanks for the hint… Here are my specs: System: Opensuse 42.1 Leap KDE Plasma: 5.4.3 Qt: 5.5.1 Kernel: 4.3.0-2-default unfortunately I have no access to my system, so I do not know which versions of btrfs-progs i have. But my system is up to date (lateste update 2 days ago). Thanks! (sorry Bob for sending you a private mail…was a mistake!) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 26.01.2016 um 13:55 schrieb Benjamin Draxlbauer:
Gesendet: Dienstag, 26. Januar 2016 um 12:53 Uhr Von: "Bob Williams"<linux@karmasailing.uk> An:opensuse@opensuse.org Betreff: Re: Aw: Re: Re: [opensuse] system not booting On 26/01/16 11:13, Benjamin Draxlbauer wrote:
Gesendet: Dienstag, 26. Januar 2016 um 11:37 Uhr Von: "Stanislav Baiduzhyi"<baiduzhyi.devel@gmail.com> An: opensuse<opensuse@opensuse.org> Betreff: Re: Re: [opensuse] system not booting On Tue, Jan 26, 2016 at 11:13 AM, Benjamin Draxlbauer<Benjamin10@gmx.at> wrote:
Thanks for the hint…Where should i add this line? I am not familiar on this type of stuff… you can try that from rescue cd, gparted-live-cd is my personal favourite, and do something like this in terminal: sudo su - root mkdir /mnt/sda3 mount -t btrfs -o clear_cache /dev/sda3 /mnt/sda3
if that command succeeds then clearing cache helped and you can try rebooting to your main system. Otherwise you have different problem, maybe someone else will be able to advice something. -- To unsubscribe, e-mail:opensuse+unsubscribe@opensuse.org To contact the owner, e-mail:opensuse+owner@opensuse.org
Okay, i tried it within a terminal in ubunut which is the second system i am running on my laptop…
sudo mount -t btrfs -o clear_cache /dev/sda3 /mnt/sda3 mount: Falscher Dateisystemtyp, ungültige Optionen, der Superblock von /dev/sda3 ist beschädigt, fehlende Kodierungsseite oder ein anderer Fehler Manchmal liefert das Systemprotokoll wertvolle Informationen, versuchen Sie »dmesg | tail« oder so
and dmesg tells the following:
dmesg | tail [ 514.164113] parent transid verify failed on 35295068160 wanted 41939771539587072 found 25424 [ 514.164117] BTRFS: failed to read chunk root on sda3 [ 514.182238] BTRFS: open_ctree failed [ 593.703113] BTRFS info (device sda3): force clearing of disk cache [ 593.703118] BTRFS info (device sda3): disk space caching is enabled [ 593.703120] BTRFS: has skinny extents [ 593.711602] parent transid verify failed on 35295068160 wanted 41939771539587072 found 25424 [ 593.723735] parent transid verify failed on 35295068160 wanted 41939771539587072 found 25424 [ 593.723742] BTRFS: failed to read chunk root on sda3 [ 593.741048] BTRFS: open_ctree failed
Almost the same as in my first mail…Any suggestions? This looks quite critical…and…i don't have a recent update!!!
You haven't mentioned which version of opensuse you are running, and more importantly, which kernel. You'll probably get more help on thelinux-btrfs@vger.kernel.org list. First question they'll ask is are you running an up to date kernel and an up to date version of btrfs-progs.
Bob -- Bob Williams System: Linux 4.1.13-5-default Distro: openSUSE 42.1 (x86_64) with KDE Development Platform: 4.14.10 Thanks for the hint… Here are my specs:
System: Opensuse 42.1 Leap KDE Plasma: 5.4.3 Qt: 5.5.1 Kernel: 4.3.0-2-default
unfortunately I have no access to my system, so I do not know which versions of btrfs-progs i have. But my system is up to date (lateste update 2 days ago). Thanks!
(sorry Bob for sending you a private mail…was a mistake!)
I do not know why, but it seems, that something has rotten my btrfs filesystem of my root partition (sda3)… I could solve the issue by running: See: http://askubuntu.com/questions/157917/how-do-i-recover-a-btrfs-partition-tha... I did: |btrfs-zero-log /dev/sda5| This made the partition mountable again. Thanks for hints! Best, Benjamin! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Jan 26, 2016 at 11:26 AM, Benjamin <benjamin10@gmx.at> wrote:
dmesg | tail [ 514.164113] parent transid verify failed on 35295068160 wanted 41939771539587072 found 25424 [ 514.164117] BTRFS: failed to read chunk root on sda3 [ 514.182238] BTRFS: open_ctree failed [ 593.703113] BTRFS info (device sda3): force clearing of disk cache [ 593.703118] BTRFS info (device sda3): disk space caching is enabled [ 593.703120] BTRFS: has skinny extents [ 593.711602] parent transid verify failed on 35295068160 wanted 41939771539587072 found 25424 [ 593.723735] parent transid verify failed on 35295068160 wanted 41939771539587072 found 25424 [ 593.723742] BTRFS: failed to read chunk root on sda3 [ 593.741048] BTRFS: open_ctree failed
I did:
|btrfs-zero-log /dev/sda5|
This made the partition mountable again.
The most serious message is about the chunk root. But I'm glad this worked, that's actually quite interesting because it's not the normal use case for btrfs rescue zero-log. For transid verify failed messages and failure to mount the first step is -o recovery. In order> use mount option recovery or ro,recovery; then try btrfs check (without --repair) and post to Btrfs upstream list with all kernel and user space tool version info; and then maybe depending on btrfs check output the fix is rescue zero-log or rescue super-recover or rescue chunk-recover or check --repair. Often check --repair is a last resort. So if you manage to get ro,recovery to work, immediately take the opportunity to fresh your backups before continuing with further repairs. -- Chris Murphy -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 26.01.2016 um 19:57 schrieb Chris Murphy:
On Tue, Jan 26, 2016 at 11:26 AM, Benjamin <benjamin10@gmx.at> wrote:
dmesg | tail [ 514.164113] parent transid verify failed on 35295068160 wanted 41939771539587072 found 25424 [ 514.164117] BTRFS: failed to read chunk root on sda3 [ 514.182238] BTRFS: open_ctree failed [ 593.703113] BTRFS info (device sda3): force clearing of disk cache [ 593.703118] BTRFS info (device sda3): disk space caching is enabled [ 593.703120] BTRFS: has skinny extents [ 593.711602] parent transid verify failed on 35295068160 wanted 41939771539587072 found 25424 [ 593.723735] parent transid verify failed on 35295068160 wanted 41939771539587072 found 25424 [ 593.723742] BTRFS: failed to read chunk root on sda3 [ 593.741048] BTRFS: open_ctree failed
I did:
|btrfs-zero-log /dev/sda5|
This made the partition mountable again.
The most serious message is about the chunk root. But I'm glad this worked, that's actually quite interesting because it's not the normal use case for btrfs rescue zero-log. For transid verify failed messages and failure to mount the first step is -o recovery.
In order> use mount option recovery or ro,recovery; then try btrfs check (without --repair) and post to Btrfs upstream list with all kernel and user space tool version info; and then maybe depending on btrfs check output the fix is rescue zero-log or rescue super-recover or rescue chunk-recover or check --repair. Often check --repair is a last resort. So if you manage to get ro,recovery to work, immediately take the opportunity to fresh your backups before continuing with further repairs.
Thanks for the descriptions…Still i do not know why this all happened (Maybe because i forget to umount a device properly???) …I tried to make it with btrfs -o recovery and btrfs ---check but that did not work, so had to carry on as it was described on the page I mentioned above. Beside…I noticed some problems while booting: The boot process is slower than before the problem and the system rebooted once within the boot process but then started regulary (but slower). Is there something I should check? Still it seems to my a unstable…but it works again… Lg Benjamin. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Benjamin -
Benjamin Draxlbauer
-
Chris Murphy