[SOLVED]Re: Partition unreadable [was: Re: Debian Stretch broken !]

Le 09/04/2020 20:11, Greg Wooledge a écrit : On Thu, Apr 09, 2020 at 08:04:31PM +0200, Bernard wrote: [ 15541.577] (EE) AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so failed (/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so: cannot open shared object file: No such file or dir

Re: Partition unreadable [was: Re: Debian Stretch broken !]

On Thu, Apr 09, 2020 at 08:04:31PM +0200, Bernard wrote: > [ 15541.577] (EE) AIGLX error: dlopen of > /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so failed > (/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so: cannot open shared object > file: No such file or directory) You're missing the libgl1-mesa-dri

Re: Partition unreadable [was: Re: Debian Stretch broken !]

Le 09/04/2020 16:44, Greg Wooledge a écrit : On Thu, Apr 09, 2020 at 04:32:10PM +0200, Bernard wrote: If you're trying to debug X, start simple. Install a traditional window manager, and just name it on the startx command to override the system defaults. $ startx invariably leads to .

Re: Partition unreadable [was: Re: Debian Stretch broken !]

On Thu, Apr 9, 2020 at 9:32 AM Bernard wrote: > > > Le 09/04/2020 15:45, Kent West a écrit : > > > > > > On Thu, Apr 9, 2020 at 8:29 AM Bernard > > wrote: > > > > > > > > I just realized that in that Debian Stretch system, > > > > I HAVE NO /home//.gconf director

Re: Partition unreadable [was: Re: Debian Stretch broken !]

On Thu, Apr 09, 2020 at 04:32:10PM +0200, Bernard wrote: > # tasksel > > a graphical window opens and proposes a choice between Debian Desktop > environment, GNOME, KDE, xfce, MATE... I alternatively chose most of these > including Gnome Desktop env, GNOME, KDE, xfce, MATE. So we don't even known

Re: Partition unreadable [was: Re: Debian Stretch broken !]

Le 09/04/2020 15:45, Kent West a écrit : On Thu, Apr 9, 2020 at 8:29 AM Bernard mailto:bdebr...@free.fr>> wrote: I just realized that in that Debian Stretch system, I HAVE NO /home//.gconf directory ! It'll rebuild itself when it's needed. The lack of a .gconf directory is p

Re: Partition unreadable [was: Re: Debian Stretch broken !]

On Thu, Apr 9, 2020 at 8:29 AM Bernard wrote: > > > I just realized that in that Debian Stretch system, > > I HAVE NO /home//.gconf directory ! > > [ While I have one my laptop using Ubuntu 14.04, also on my old desktop > running Debian Lenny] > > but it didn't rebuild itself so far ! > > What sh

Re: Partition unreadable [was: Re: Debian Stretch broken !]

On Thu, Apr 09, 2020 at 03:28:43PM +0200, Bernard wrote: > I just realized that in that Debian Stretch system, > > I HAVE NO /home//.gconf directory ! Uh... yay? > but it didn't rebuild itself so far ! > > What should I do to get it rebuilt ? Run something that uses it. Or, if you don't run a

Re: Partition unreadable [was: Re: Debian Stretch broken !]

Hi Tom, Alexei, Kent and Everyone else, Le 05/04/2020 03:25, Tom Dial a écrit : From the various postings it seems somewhat clear that the system, as such, is not broken. The initial message indicates, I think Felix Miata noted, that there is a problem with gdm starting (probably) gnome.

Re: Debian Stretch broken !

Andrei POPESCU composed on 2020-04-06 15:12 (UTC+0300): >> 214] (EE) AIGLX error: dlopen of >> /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so failed >> (/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so: cannot open shared object >> file: file or directory) >> 214] (EE) AIGLX: reverting to software re

Re: Debian Stretch broken !

On Lu, 06 apr 20, 14:51:18, Andrei POPESCU wrote: > On Lu, 06 apr 20, 12:30:06, Bernard wrote: > > Le 06/04/2020 09:46, Andrei POPESCU a écrit : > > > > > > Please attach the file /home/bd/.local/share/xorg/Xorg.0.log. It should > > > be small enough to be accepted by the list. > > > > Here is th

Re: Debian Stretch broken !

On Lu, 06 apr 20, 12:30:06, Bernard wrote: > Le 06/04/2020 09:46, Andrei POPESCU a écrit : > > > > Please attach the file /home/bd/.local/share/xorg/Xorg.0.log. It should > > be small enough to be accepted by the list. > > Here is the file. > > Bernard 214] (EE) AIGLX error: dlopen of /usr/lib/

Re: Debian Stretch broken !

Le 06/04/2020 09:08, Felix Miata a écrit : [quote] You are in rescue mode. After logging in, type "journalctl -xb" to view system logs[/quote] Did you do this? I did it a few posts ago ; in the end of it were three identical red lines saying that there was a bad block on sda2... But, at t

Re: Debian Stretch broken !

Le 06/04/2020 02:07, Kent West a écrit : You can log in as a normal user! Excellent! Can you ping something by address? by name? e.g. ping 8.8.8.8 ping google.com (Just trying to see how "normal" your system is.) ping 8.8.8.8 displays things related to time or somet

Re: Debian Stretch broken !

Le 05/04/2020 16:35, Kent West a écrit : No, again, I think I've been mistaken. Seeing a different thread dealing with this same problem, I realize that /dev/sda2 is likely the "container" for extended partitions; trying to mount it would likely result in an error; so I'm back to thinkin

Re: Debian Stretch broken !

What windows manager are you using. That has not been removed by mistake has it? On Mon, Apr 6, 2020 at 11:30 AM Bernard wrote: > > > Le 06/04/2020 09:46, Andrei POPESCU a écrit : > > On Du, 05 apr 20, 23:35:45, Bernard wrote: > >> > >> Le 05/04/2020 08:24, Andrei POPESCU a écrit : > >>> > >>>

Re: Debian Stretch broken !

Le 06/04/2020 09:46, Andrei POPESCU a écrit : On Du, 05 apr 20, 23:35:45, Bernard wrote: Le 05/04/2020 08:24, Andrei POPESCU a écrit : Log in with your normal user and try running 'startx' from the console. In case it stops with some error messages we need those. The on screen results of

Re: Debian Stretch broken !

On Du, 05 apr 20, 23:35:45, Bernard wrote: > > Le 05/04/2020 08:24, Andrei POPESCU a écrit : > > > > Log in with your normal user and try running 'startx' from the console. > > In case it stops with some error messages we need those. > > The on screen results of such trials have been photographi

Re: Debian Stretch broken !

Bernard composed on 2020-04-04 01:13 (UTC+0200): > http://bdebreil.free.fr/IMG_0901.jpg [quote] You are in rescue mode. After logging in, type "journalctl -xb" to view system logs[/quote] Did you do this? It should provide clues what needs to be done and/or what is going wrong. If journalctl -xb

Re: Debian Stretch broken !

On Sun, Apr 5, 2020 at 4:36 PM Bernard wrote: > > > Le 05/04/2020 08:24, Andrei POPESCU a écrit : > > On Vi, 03 apr 20, 20:41:06, Bernard wrote: > > >> But : "Oh no, something has gone wrong..." > >> > > > > > and then boot "normally" (this time in text mode). > > > > Log i

Re: Debian Stretch broken !

Le 05/04/2020 08:24, Andrei POPESCU a écrit : On Vi, 03 apr 20, 20:41:06, Bernard wrote: Hi to Everyone, Having done some minor resettings on alsamixer with no results, I thought I had to reboot. But : "Oh no, something has gone wrong..." Apparently I missed this on

Re: Debian Stretch broken !

On Sun, Apr 5, 2020 at 9:28 AM Kent West wrote: > > > On Sun, Apr 5, 2020 at 9:23 AM Kent West wrote: > >> >> Next I typed 'journalctl -xb' to view system logs : a dozen of pages >>> which I will shoot later, one thing I have noticed in it all, printed in >>> red characters : >>> >>> EXT4-fs (sd

Re: Debian Stretch broken !

On Sun, Apr 5, 2020 at 9:23 AM Kent West wrote: > > Next I typed 'journalctl -xb' to view system logs : a dozen of pages >> which I will shoot later, one thing I have noticed in it all, printed in >> red characters : >> >> EXT4-fs (sda2): unable to read superblock >> >> this repeated three times

Re: Debian Stretch broken !

Things are looking a bit more promising now... On Fri, Apr 3, 2020 at 6:14 PM Bernard wrote: > > > Le 03/04/2020 21:05, Kent West a écrit : > > > > > > On Fri, Apr 3, 2020 at 1:41 PM Bernard > > wrote: > > > > > > Having done some minor resettings on alsamixer with

Re: Debian Stretch broken !

On Vi, 03 apr 20, 20:41:06, Bernard wrote: > Hi to Everyone, > Having done some minor resettings on alsamixer with no results, I thought I > had to reboot. > > But : "Oh no, something has gone wrong..." > > So, I am writing this message from my other laptop running Ubuntu 14.04 > > I tried to re

Re: Partition unreadable [was: Re: Debian Stretch broken !]

On 4/4/20 11:57, Bernard wrote: > Le 04/04/2020 18:16, Andrei POPESCU a écrit : >> On Sb, 04 apr 20, 11:00:06, Bernard wrote: >>> Thanks a lot for this reply >>> >>> The output of the proposed tests are shown on the following screen >>> picture : >>> >>> http://bdebreil.free.fr/IMG_0906.jpg >>>

Re: Partition unreadable [was: Re: Debian Stretch broken !]

On 2020-04-04 10:57, Bernard wrote: Le 04/04/2020 18:16, Andrei POPESCU a écrit : On Sb, 04 apr 20, 11:00:06, Bernard wrote: Thanks a lot for this reply The output of the proposed tests are shown on the following screen picture : http://bdebreil.free.fr/IMG_0906.jpg

Re: Partition unreadable [was: Re: Debian Stretch broken !]

Le 04/04/2020 18:16, Andrei POPESCU a écrit : On Sb, 04 apr 20, 11:00:06, Bernard wrote: Thanks a lot for this reply The output of the proposed tests are shown on the following screen picture : http://bdebreil.free.fr/IMG_0906.jpg .. Please post also the contents of

Re: Partition unreadable [was: Re: Debian Stretch broken !]

On Sb, 04 apr 20, 11:00:06, Bernard wrote: > Thanks a lot for this reply > > The output of the proposed tests are shown on the following screen picture : > > http://bdebreil.free.fr/IMG_0906.jpg > > As for partition sda2 : I don't remember having created this partition when > installing Stretch

Re: Partition unreadable [was: Re: Debian Stretch broken !]

Thanks a lot for this reply The output of the proposed tests are shown on the following screen picture : http://bdebreil.free.fr/IMG_0906.jpg As for partition sda2 : I don't remember having created this partition when installing Stretch on this then newly bought desktop (2 years ago). Isn'it

Partition unreadable [was: Re: Debian Stretch broken !]

On Sb, 04 apr 20, 01:13:35, Bernard wrote: > > Next I typed 'journalctl -xb' to view system logs : a dozen of pages which I > will shoot later, one thing I have noticed in it all, printed in red > characters : > > EXT4-fs (sda2): unable to read superblock > > this repeated three times ! This *c

Re: Debian Stretch broken !

Le 03/04/2020 21:05, Kent West a écrit : On Fri, Apr 3, 2020 at 1:41 PM Bernard mailto:bdebr...@free.fr>> wrote: Having done some minor resettings on alsamixer with no results, I thought I had to reboot. But : "Oh no, something has gone wrong..." So, I am writing this mes

Re: Debian Stretch broken !

Bernard composed on 2020-04-03 20:41 (UTC+0200): > "Oh no, something has gone wrong..." That message is issued when GDM cannot start. How to fix I don't know, as I never use GDM, but when that happens you should be able to switch to any of the vttys GDM doesn't run on to find a text login prompt.

Re: Debian Stretch broken !

On Fri, Apr 3, 2020 at 1:41 PM Bernard wrote: > > Having done some minor resettings on alsamixer with no results, I > thought I had to reboot. > > But : "Oh no, something has gone wrong..." > > So, I am writing this message from my other laptop running Ubuntu 14.04 > > I tried to reboot in rescue

Re: Debian Stretch broken !

On Fri, Apr 3, 2020, 14:41 Bernard wrote: > Hi to Everyone, > Having done some minor resettings on alsamixer with no results, I > thought I had to reboot. > > But : "Oh no, something has gone wrong..." > > So, I am writing this message from my other laptop running Ubuntu 14.04 > > I tried to rebo

Debian Stretch broken !

Hi to Everyone, Having done some minor resettings on alsamixer with no results, I thought I had to reboot. But : "Oh no, something has gone wrong..." So, I am writing this message from my other laptop running Ubuntu 14.04 I tried to reboot in rescue mode, but I don't know what to do from the