January 2016 - openSUSE Users - openSUSE Mailing Lists

Aw: Re: Re: Re: [opensuse] system not booting
by Benjamin Draxlbauer 27 Jan '16

27 Jan '16

Gesendet: Dienstag, 26. Januar 2016 um 12:53 Uhr Von: "Bob Williams" <linux(a)karmasailing.uk> An: opensuse(a)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(a)gmail.com> > An: opensuse <opensuse(a)opensuse.org> > Betreff: Re: Re: [opensuse] system not booting > On Tue, Jan 26, 2016 at 11:13 AM, Benjamin Draxlbauer <Benjamin10(a)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(a)opensuse.org > To contact the owner, e-mail: opensuse+owner(a)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(a)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(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 3

RE: RE: Re: [opensuse] disabling wakeup when monitor sends hibernate message
by stakanov＠freenet.de 27 Jan '16

27 Jan '16

> -----Ursprüngliche Nachricht----- > Von: stakanov(a)freenet.de > Gesendet: Mi. 27.01.2016 09:54 > An: opensuse(a)opensuse.org > Betreff: RE: Re: [opensuse] disabling wakeup when monitor sends hibernate message > > > >> -----Ursprüngliche Nachricht----- >> Von: don fisher >> Gesendet: Mi. 27.01.2016 00:53 >> An: opensuse(a)opensuse.org >> Betreff: Re: [opensuse] disabling wakeup when monitor sends hibernate message >> >> On 01/25/2016 07:20 PM, don fisher wrote: >>> On 01/25/2016 06:20 PM, John Andersen wrote: >>>> On 01/25/2016 02:26 PM, don fisher wrote: >>>>> then the monitor offers a lost signal message, and the system unblanks-- > To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse+owner(a)opensuse.org > > > > -----Ursprüngliche Nachricht Ende----- Uttermost sorry for this empty reply, it is my freemailer again, really crappy. You may not have to buy a new computer. Think about these first: Use another cable, often the ones with clutches have issues (that give such a wake up signal). Try to change plug of the monitor. If it has a DVI and HDMI use the other one (maybe with an adapter) if available. If you find that the graphics card has another plug, try that first too. It could also be a mechanical problem. Before buying another monitory, try these first. Sure, cables are so expensive that they cost more than some monitors (I have noticed that mismatch and disproportionate prices for quite some time now). It is convenient to ask a friend for a spare first, maybe. --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

RE: Re: [opensuse] disabling wakeup when monitor sends hibernate message
by stakanov＠freenet.de 27 Jan '16

27 Jan '16

> -----Ursprüngliche Nachricht----- > Von: don fisher > Gesendet: Mi. 27.01.2016 00:53 > An: opensuse(a)opensuse.org > Betreff: Re: [opensuse] disabling wakeup when monitor sends hibernate message > > On 01/25/2016 07:20 PM, don fisher wrote: >> On 01/25/2016 06:20 PM, John Andersen wrote: >>> On 01/25/2016 02:26 PM, don fisher wrote: >>>> then the monitor offers a lost signal message, and the system unblanks-- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] chrome crashes kwin_x11 in plasma5 42.1
by tech＠reachthetribes.org 27 Jan '16

27 Jan '16

This has happened several times, but it does not always happen. If I use chrome (my preferred browser) to look at something in the course of my work, at some point suddenly kwin_x11 will crash and all my screen navigation in plasma5 will cease. The title bars disappear from all my open applications, and I am not able to switch desktops or navigate to a new application. This is what I do when it crashes like this. I hit ctrl-esc to open the resources monitor. Using that, I stop chrome (which has like 5 or 6 processes associated it, but one click kills it all in the resources monitor). On the resources monitor, the process for kwin_x11 says "stopped". I cannot kill it for some reason with the resources monitor. So then I hit alt-f2 and type in konsole. I do a > ps ax | grep kwin and find the pid for kwin_xll. I have to kill it with > kill -9 <pid> as kill all by itself won't do it. Then I hit alt-f2 again and type in kwin_x11 to restart it, and it restarts, and my desktop is back up and running, and I didn't have to exit out of all my applications. So it works, but it is a pain in the neck, and basically chrome is unusable. Anyone have any ideas? I haven't filed a bug report yet, because I think there may be something wrong with my system to troubleshoot first. -- George Box #1: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Box #2: 13.1 | KDE 4.12 | AMD Athlon X3 | 64 | 4GB Laptop #1: 13.1 | KDE 4.12 | Core i7-2620M | 64 | 8GB Laptop #2: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 7

[opensuse] Was there no security trouble of the linuxkernel for leap?
by cagsm 26 Jan '16

26 Jan '16

I see suse enterprise updates multitudes of kernel updates there in the recent days or even weeks. None for leap. What gives? Is leap so badly neglected that we dont deserve security? Or will we get newer 4.1.x release combined with the security fixage? Tia guys. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] systemd-sleep-grub debugging
by Bjoern Voigt 26 Jan '16

26 Jan '16

If my PC goes sleeping, systemd-sleep-grub does not call grub2-once any-more. This causes failing sleep mode entry (hibernate), if the running kernel is not the default kernel. I see, that /usr/bin/systemd-sleep-grub is a shell script and some logging can be found in Systemd journal. But logging is not very detailed. What is a good strategy to debug the script? Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 1

[opensuse] Boot fails to wait for a needed fstab NFS mount, fires a 'wicked nanny' error ("Failed to start Alias for NFS client.". Some systemd unit needs to wait longer?
by suse.dev＠fea.st 26 Jan '16

26 Jan '16

I'm booting a VM guest that needs to bring up an NFS mount. Right now on boot, something's out of order and it fails ... [ OK ] Started wicked network management service daemon. [ 23.805688] systemd[1]: Started wicked network management service daemon. [ 23.834962] systemd[1]: Starting wicked network nanny service... Starting wicked network nanny service... [FAILED] Failed to start Alias for NFS client. See "systemctl status nfs.service" for details. [ 23.876106] systemd[1]: Failed to start Alias for NFS client. [ OK ] Started System Logging Service. [ OK ] Started wicked network nanny service. ... Checking systemctl status nfs.service -l nfs.service - Alias for NFS client Loaded: loaded (/usr/lib/systemd/system/nfs.service; enabled) Drop-In: /run/systemd/generator/nfs.service.d └─50-insserv.conf-$remote_fs.conf Active: failed (Result: exit-code) since Tue 2016-01-26 07:16:26 PST; 52s ago Process: 738 ExecStop=/usr/bin/umount -aft nfs,nfs4 (code=exited, status=0/SUCCESS) Process: 727 ExecStartPost=/usr/bin/mount -at nfs,nfs4 (code=exited, status=32) Process: 705 ExecStart=/bin/true (code=exited, status=0/SUCCESS) Main PID: 705 (code=exited, status=0/SUCCESS) Jan 26 07:16:26 linux-u398 mount[727]: mount.nfs4: Failed to resolve server nfs01.example.com: Name or service not known That server's the mount defined in the guest's /etc/fstab cat /etc/fstab ... nfs01.example.com:/SEC/clients/client06 /sec/client06 nfs4 _netdev,tcp,ro,auto,soft,async,noexec,nosuid,bg,rsize=32768,wsize=32768 0 0 IIUC, fstab entries are translated by systemd-fstab-generator into native systemd units durint early boot, and it's systemd that controls the mounts & their dependencies. But, here, wicked's also involved as another layer. *Something* needs to wait longer on boot. I think just waiting for network to be online is good enough maybe? Question is -- what unit needs the additional dependency? Thanks. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Monitor Wakes Up Randomly
by SDM 26 Jan '16

26 Jan '16

Hi, On TW Snapshot 20160121, I have an issue on my desktop PC where my ASUS VH242 monitor wakes up at random times after it goes to sleep. I'll set it, for instance, to go to sleep after 5 minutes in the Energy Saving section of Plasma 5's System Settings. For multiple days straight, it will go to sleep and stay asleep. Then, for whatever reason, one day the monitor will wake up within minutes of going to sleep, go back to sleep again, and continue cycling on and off, so I eventually just press the power button but this poses a problem if I'm not present. Does this sound like a Linux driver issue or something wrong with the actual monitor? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] system not booting
by Benjamin Draxlbauer 26 Jan '16

26 Jan '16

Morning Guys! I have a serious problem with my system: Today I wanted to start my system but after the bootmanager menue this message showed up: Ignoring BGRT: invalid status 0 (expected 1) BTRFS (device sda3): parent transid verify failed on 35295068160 wanted 41939771539587072 found 2542 BTRFS (device sda3): parent transid verify failed on 35295068160 wanted 41939771539587072 found 2542 BTRFS: open_ctree failed Boot has failed. To debug this issue add "rd.shell rd.debug" to the kernel command line. I tried it a few times but it didn't help. Actually i can't remember doing anything on my laptop, not even an update yesterday… Best, Benjamin D. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 5

[opensuse] Bootup of Luks partitions not waiting long for Password
by John Andersen 26 Jan '16

26 Jan '16

I've got a 13.2 installation that for some reason some time ago started waiting a real short time for passwords on the Plymouth screen (or at least the Plymouth wallpaper) for a password for the Luks encrypted partition. I have to hover over the keyboard waiting for that prompt to come up and type it really quick or it boots without my home partition mounted. I thought it was /etc/crypttab where the delay was set, but this appears to be ignored. There are a few bug reports but they appear full of arguing back and forth and nobody has a clue. Has anyone else seen this, or have a solution? -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 37