Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #220837 > unrolled thread

Debian Stretch broken !

Back to article view | Back to linux.debian.user

Contents

  Debian Stretch broken ! Bernard <bdebreil@free.fr> - 2020-04-03 20:50 +0200
    Re: Debian Stretch broken ! Kent West <westk@acu.edu> - 2020-04-03 21:10 +0200
      Re: Debian Stretch broken ! Bernard <bdebreil@free.fr> - 2020-04-04 01:20 +0200
        Partition unreadable [was: Re: Debian Stretch broken !] Andrei POPESCU <andreimpopescu@gmail.com> - 2020-04-04 08:30 +0200
          Re: Partition unreadable [was: Re: Debian Stretch broken !] Bernard <bdebreil@free.fr> - 2020-04-04 11:10 +0200
            Re: Partition unreadable Felix Miata <mrmazda@earthlink.net> - 2020-04-04 12:00 +0200
            Re: Partition unreadable [was: Re: Debian Stretch broken !] Andrei POPESCU <andreimpopescu@gmail.com> - 2020-04-04 18:20 +0200
              Re: Partition unreadable [was: Re: Debian Stretch broken !] Bernard <bdebreil@free.fr> - 2020-04-04 20:00 +0200
                Re: Partition unreadable [was: Re: Debian Stretch broken !] David Christensen <dpchrist@holgerdanske.com> - 2020-04-05 01:10 +0200
                Re: Partition unreadable [was: Re: Debian Stretch broken !] Tom Dial <tddial@comcast.net> - 2020-04-05 03:50 +0200
                  Re: Partition unreadable [was: Re: Debian Stretch broken !] Bernard <bdebreil@free.fr> - 2020-04-09 15:30 +0200
                    Re: Partition unreadable [was: Re: Debian Stretch broken !] Greg Wooledge <wooledg@eeg.ccf.org> - 2020-04-09 15:40 +0200
                    Re: Partition unreadable [was: Re: Debian Stretch broken !] Kent West <westk@acu.edu> - 2020-04-09 15:50 +0200
                      Re: Partition unreadable [was: Re: Debian Stretch broken !] Bernard <bdebreil@free.fr> - 2020-04-09 16:40 +0200
                        Re: Partition unreadable [was: Re: Debian Stretch broken !] Greg Wooledge <wooledg@eeg.ccf.org> - 2020-04-09 16:50 +0200
                          Re: Partition unreadable [was: Re: Debian Stretch broken !] Bernard <bdebreil@free.fr> - 2020-04-09 20:10 +0200
                            Re: Partition unreadable [was: Re: Debian Stretch broken !] Greg Wooledge <wooledg@eeg.ccf.org> - 2020-04-09 20:20 +0200
                              [SOLVED]Re: Partition unreadable [was: Re: Debian Stretch broken  !] Bernard <bdebreil@free.fr> - 2020-04-10 14:50 +0200
                        Re: Partition unreadable [was: Re: Debian Stretch broken !] Kent West <westk@acu.edu> - 2020-04-09 17:00 +0200
        Re: Debian Stretch broken ! Kent West <westk@acu.edu> - 2020-04-05 16:30 +0200
          Re: Debian Stretch broken ! Kent West <westk@acu.edu> - 2020-04-05 16:40 +0200
            Re: Debian Stretch broken ! Bernard <bdebreil@free.fr> - 2020-04-06 13:30 +0200
        Re: Debian Stretch broken ! Kent West <westk@acu.edu> - 2020-04-05 16:30 +0200
        Re: Debian Stretch broken ! Felix Miata <mrmazda@earthlink.net> - 2020-04-06 09:10 +0200
          Re: Debian Stretch broken ! Bernard <bdebreil@free.fr> - 2020-04-06 14:00 +0200
    Re: Debian Stretch broken ! Default User <hunguponcontent@gmail.com> - 2020-04-03 21:10 +0200
    Re: Debian Stretch broken ! Felix Miata <mrmazda@earthlink.net> - 2020-04-03 21:30 +0200
    Re: Debian Stretch broken ! Andrei POPESCU <andreimpopescu@gmail.com> - 2020-04-05 08:30 +0200
      Re: Debian Stretch broken ! Bernard <bdebreil@free.fr> - 2020-04-05 23:40 +0200
        Re: Debian Stretch broken ! Kent West <westk@acu.edu> - 2020-04-06 02:10 +0200
          Re: Debian Stretch broken ! Bernard <bdebreil@free.fr> - 2020-04-06 13:40 +0200
        Re: Debian Stretch broken ! Andrei POPESCU <andreimpopescu@gmail.com> - 2020-04-06 09:50 +0200
          Re: Debian Stretch broken ! Bernard <bdebreil@free.fr> - 2020-04-06 12:40 +0200
            Re: Debian Stretch broken ! Daniel Harris <mail.dharris@googlemail.com> - 2020-04-06 13:10 +0200
            Re: Debian Stretch broken ! Andrei POPESCU <andreimpopescu@gmail.com> - 2020-04-06 14:00 +0200
              Re: Debian Stretch broken ! Andrei POPESCU <andreimpopescu@gmail.com> - 2020-04-06 14:20 +0200
                Re: Debian Stretch broken ! Felix Miata <mrmazda@earthlink.net> - 2020-04-06 14:30 +0200

Page 1 of 2  [1] 2  Next page →

#220837 — 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 
there. 'startx' says that it doesn't have the proper files to launch 
startx as root.

login
bd

says : wrong login (doesn't even ask a pswd)

I remember a few years back on older versions, I had used 'System Rescue 
CD', but this said CD, provided that I find it, would probably no work 
on this system


Thanks in advance for your help so that I can expect to boot my system 
without loss of data

By the way: not only did I reset alsamixer prior to rebooting, also I 
had accepted an automatic system upgrade this morning.

Bernard

[toc] | [next] | [standalone]

#220838

[Multipart message — attachments visible in raw view] — view raw

On Fri, Apr 3, 2020 at 1:41 PM Bernard <bdebreil@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 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
> there. 'startx' says that it doesn't have the proper files to launch
> startx as root.
>
> login
> bd
>
> says : wrong login (doesn't even ask a pswd)
>

It's unclear how far you're getting.

Can you boot normally and get to a login prompt on a text-only screen?

-- 
Kent

[toc] | [prev] | [next] | [standalone]

#220847

Le 03/04/2020 21:05, Kent West a écrit :
>
>
> On Fri, Apr 3, 2020 at 1:41 PM Bernard <bdebreil@free.fr
> <mailto:bdebreil@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 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
>     there. 'startx' says that it doesn't have the proper files to launch
>     startx as root.
>
>     login
>     bd
>
>     says : wrong login (doesn't even ask a pswd)
>
>
> It's unclear how far you're getting.
>
> Can you boot normally and get to a login prompt on a text-only screen?
>
> --
> Kent
>
Thanks for your reply. To get login prompt and text screen, I had to 
take pictures with a camera, since the caracters are so small. Reading 
back those images, I will say this :

upon booting, a number of screen messages do appear and scroll down 
fast. I could only see that 'OK' was on most or all of them. In the end, 
a screen with smaller characters appear for 2-3 sec, that I have 
photographied.It has two lines as follows :

/dev/sda1: clean, 408719/60530688 files, 116865639/242103552 blocks
[    8.436046] nouveau 0000:01:00.0: priv: HUB0: 085014 ffffffff (1e70820b)

Those two lines only appear for 2-3 sec, so I had a hard time to 
photography them on the screen, and I am just coping them by hand, Links 
for photos are as follows :

http://bdebreil.free.fr/IMG_0900.jpg
http://bdebreil.free.fr/IMG_0901.jpg
http://bdebreil.free.fr/IMG_0902.jpg
http://bdebreil.free.fr/IMG_0903.jpg
http://bdebreil.free.fr/IMG_0904.jpg

After those 2-3 sec, another screen appears saying (translated from 
French to English)

"Oops, something went wront. A problem has occured and the system cannot 
recuperate. Please disconnect and try again"

Countless trials have all lead to the same behaviour.

Now, if I reboot on rescue mode, a lot of fast moving messages do 
appear, I only could see that most or all of them bore the mention 'OK', 
as said before. In the end, smaller characters do remain on screen, 
waiting till I submit the root pasword. Then :

You are in rescue mode. After logging in, type "journalctl -xb" to view 
system logs, "systemctlreboot" to reboot, "systemctldefault" or ?D to 
boot into default mode

Give the superuser pswd (or press CTRL-D) to continue : [    9.315865] 
[TTM] Zone kernel: A

Available graphic memory: 2097152 kiB

[   9.316077 [TTM] Initializing DMA pool allocator
[ nouveau ..... DRM:
......
etc ...

When typing 'ls -l' home directories do not appear (see pictures)

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 !

Thanks in advance for your comments and advises.

Bernard

[toc] | [prev] | [next] | [standalone]

#220856 — Partition unreadable [was: Re: Debian Stretch broken !]

[Multipart message — attachments visible in raw view] — view raw

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 *could* indicate a serious problem and attempts to fix it *could* 
make it worse. It could also be a minor issue that is easily fixed.

Do you have an *empty* spare drive to copy your data to? Ideally you 
should use 'dd' to take a complete image of sda and work on that 
instead.

    dd if=/dev/sda of=/dev/<spare drive> bs=1M status=progress

Warning: this will overwrite your data on the spare drive!

For this to work properly the spare drive should be same size (to the 
byte!) or bigger than sda.

Before any recovery attempts let's try to find out how your drives are 
partitioned.

Please post the output of following commands from the rescue console.

LANG=C lsblk -f
LANG=C fdisk -l

These are read-only commands so should be safe.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#220864 — 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 funny that it shows the exact same size as that of the swap 
partition sda5 ?

I doubt that I would have willingly created such a small partition... 
maybe the install program created it...

Whether it did exist or not in my working system, one thing remains :

     on the rescue mode, I cannot find my /home directory

Waiting for your advice and recommendations,

Bernard

Please post the output of following commands from the rescue console.
 >
 > LANG=C lsblk -f
 > LANG=C fdisk -l
 >

Le 04/04/2020 08:28, Andrei POPESCU a écrit :
> 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 *could* indicate a serious problem and attempts to fix it *could*
> make it worse. It could also be a minor issue that is easily fixed.
>
> Do you have an *empty* spare drive to copy your data to? Ideally you
> should use 'dd' to take a complete image of sda and work on that
> instead.
>
>      dd if=/dev/sda of=/dev/<spare drive> bs=1M status=progress
>
> Warning: this will overwrite your data on the spare drive!
>
> For this to work properly the spare drive should be same size (to the
> byte!) or bigger than sda.
>
> Before any recovery attempts let's try to find out how your drives are
> partitioned.
>
> Please post the output of following commands from the rescue console.
>
> LANG=C lsblk -f
> LANG=C fdisk -l
>
> These are read-only commands so should be safe.
>
> Kind regards,
> Andrei
>

[toc] | [prev] | [next] | [standalone]

#220868 — Re: Partition unreadable

Bernard composed on 2020-04-04 11:00 (UTC+0200):

> 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 funny that it shows the exact same size as that of the swap 
> partition sda5 ?

Rather than a filesystem (or LVM) container, which is what your sda1 and sda5 are,
sda2 is a logical partition container, labeled extended. Creating it as a separate
partitioning step is an anachronism which in practical terms serves no purpose but
to confuse those uninitiated with legacy/MBR partitioning.

> I doubt that I would have willingly created such a small partition... 
> maybe the install program created it...
The smarter partitioning programs don't "create it", because it is nothing but an
envelope within which partitions that can contain filesystems may be created.
These smarter ones do create it, but they do so automatically without making any
mention of it, automatically making them the size required to contain the
partitions within that they contain. It occupies a partition table entry that is
nothing but a definition of the size of the container, plus a pointer to the first
partition that it contains. Thus if only one partition is contained, it may
virtually match the size of that which it contains, the difference being the size
allocated to the definition itself.

The gap in numbers is because the MBR partition table only has space for 4
entries. That makes 5 the first available number for a logical partition contained
by the extended "partition" definition. Logical is the name given defined by the
extended's table entry, plus each in the chain of additional entries at the start
of each that is defined beyond that which is labeled #5.
-- 
Evolution as taught in public schools is religion, not science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#220885 — Re: Partition unreadable [was: Re: Debian Stretch broken !]

[Multipart message — attachments visible in raw view] — view raw

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 on this then newly bought desktop (2 years ago). Isn'it
> funny that it shows the exact same size as that of the swap partition sda5 ?
> 
> I doubt that I would have willingly created such a small partition... maybe
> the install program created it...

Felix Miata already answered to this much better than I could have done.
 
> Whether it did exist or not in my working system, one thing remains :
> 
>     on the rescue mode, I cannot find my /home directory
> 
> Waiting for your advice and recommendations,

Please post also the contents of /etc/fstab.

It's curious that fdisk shows sdb has no partition at all. Is this 
expected or does sdb contain your /home?

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#220893 — 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 /etc/fstab.

http://bdebreil.free.fr/IMG_0907.jpg

>
> It's curious that fdisk shows sdb has no partition at all. Is this
> expected or does sdb contain your /home?

There is no mystery about sdb ; I should have mentioned it before. This 
is an additional disk ; my desktop has two hard drives. This extra one 
had no part in the install process, I only used it later on as an 
extension to save files, I mount it manually every time I want to use 
it. I didn't see any point to partition it. I successfully mounted it in 
my recovery boot, and everything seemed to be OK at first sight.

Regards,

Bernard

[toc] | [prev] | [next] | [standalone]

#220901 — 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
>>>
> ......................
>>
>> Please post also the contents of /etc/fstab.
> 
> http://bdebreil.free.fr/IMG_0907.jpg
> 
>>
>> It's curious that fdisk shows sdb has no partition at all. Is this
>> expected or does sdb contain your /home?
> 
> There is no mystery about sdb ; I should have mentioned it before. This 
> is an additional disk ; my desktop has two hard drives. This extra one 
> had no part in the install process, I only used it later on as an 
> extension to save files, I mount it manually every time I want to use 
> it. I didn't see any point to partition it. I successfully mounted it in 
> my recovery boot, and everything seemed to be OK at first sight.
> 
> Regards,
> 
> Bernard

To be blunt, if you just want to use video conferencing and not learn 
how video conferencing works (or does not work) on Linux, I would use 
Windows or macOS.


As for the broken Debian computer, I would back up the data, install a 
small SSD, install Debian, wipe the 1 TB drives, create an md mirror, 
create an ext4 file system, restore the data, install Samba, and share 
the data.


It is useful to have a USB flash drive with Debian installed on it, to 
use as tool for working on other computers.


It is useful to maintain a folder in a version control system for each 
host, with an administrator journal (plain text file), system 
configuration files, and anything else useful for setup, configuration, 
and maintenance.  I use Vim and CVS over SSH.


David

[toc] | [prev] | [next] | [standalone]

#220902 — 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
>>>
> ......................
>>
>> Please post also the contents of /etc/fstab.
> 
> http://bdebreil.free.fr/IMG_0907.jpg
> 

>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. It
also indicates that the boot completed almost normally (or almost
completed normally).

There is no obvious problem with the disks or partitions. It is unusual
to put a file system on an entire raw disk, as with /dev/sdb, but I do
not know of a reason it would not work, or that one should not do it if
the entire disk is to be used for a single file system.

As for /dev/sda: /sda1 is the partition containing everything, including
/boot and / (the root file system which, in this case contains all files
that are not on /dev/sdb, including /home). There is nothing
fundamentally wrong with this either; I find it increasingly hard to
justify to myself my old custom of putting /boot, /, /usr, /var, /tmp,
and /home on separate partitions. As Felix Miata also noted, sda2 is the
"extended" partition, and sda5 is the swap partition, created during
installation.

By the indications given, both disks are healthy, or considered so by
the Linux kernel.

The message string does not say directly whether you received a login
widget, and then the "Oh, no ..." after trying to log in. That would
indicate that GDM (or the display manager was in use, maybe lightdm)
worked, but gnome could not start.

I have seen a similar problem with gdm/gnome on occasion, but do not
remember the exact problem or its solution. It appeared to have
something to do with corruption in one of the files under
/home/<user>/.gconf. I think my answer might have been to throw away
that directory and let it rebuild as it liked. There are times when I
have little patience with files for which I have trouble finding
detailed documentation and which were created as side effects of
application or subsystem operation. I haven't burned myself yet, but
hesitated to recommend it for others where I have no skin in the game.

Others (almost everyone here) who know more than I about the innards of
the display manager and gnome may provide useful information, but
worrying about the disk looks to me like missing the mark.


>>
>> It's curious that fdisk shows sdb has no partition at all. Is this
>> expected or does sdb contain your /home?
> 
> There is no mystery about sdb ; I should have mentioned it before. This
> is an additional disk ; my desktop has two hard drives. This extra one
> had no part in the install process, I only used it later on as an
> extension to save files, I mount it manually every time I want to use
> it. I didn't see any point to partition it. I successfully mounted it in
> my recovery boot, and everything seemed to be OK at first sight.
> 
> Regards,
> 
> Bernard

Regards,

Tom Dial

[toc] | [prev] | [next] | [standalone]

#221124 — 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. It
> also indicates that the boot completed almost normally (or almost
> completed normally).
>
> There is no obvious problem with the disks or partitions.
>
 >
> By the indications given, both disks are healthy, or considered so by
> the Linux kernel.
>
> The message string does not say directly whether you received a login
> widget,
"Oh, no ..."

no login widget, the "Oh, no ..." displayed after about 1 minute.

  That would
> indicate that GDM (or the display manager was in use, maybe lightdm)
> worked, but gnome could not start.
>
> I have seen a similar problem with gdm/gnome on occasion, but do not
> remember the exact problem or its solution. It appeared to have
> something to do with corruption in one of the files under
> /home/<user>/.gconf. I think my answer might have been to throw away
> that directory and let it rebuild as it liked.
> Tom Dial

I just realized that in that Debian Stretch system,

I HAVE NO /home/<user>/.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 should I do to get it rebuilt ?

Bernard


>
>

[toc] | [prev] | [next] | [standalone]

#221126 — 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/<user>/.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 anything that uses it,
rejoice that you don't need it.

It's not exactly bleeding edge stuff...

unicorn:~$ ls -lart .gconf
total 64
-rw-------   1 greg greg     0 Jun 28  2002 %gconf.xml
drwx------   2 greg greg  4096 Mar 12  2011 %gconf-xml-backend.lock/
drwx------   7 greg greg  4096 Apr 22  2015 apps/
drwx------   3 greg greg  4096 Apr 22  2015 desktop/
drwx------   3 greg greg  4096 Apr 22  2015 schemas/
drwx------   6 greg greg  4096 Jan 11  2017 ./
drwxr-xr-x 218 greg greg 40960 Apr  9 08:24 ../
unicorn:~$ ls -lart .gconf/apps/
total 28
-rw------- 1 greg greg    0 Jun 28  2002 %gconf.xml
drwx------ 7 greg greg 4096 Apr 22  2015 evolution/
drwx------ 5 greg greg 4096 Apr 22  2015 file-roller/
drwx------ 9 greg greg 4096 Apr 22  2015 galeon/
drwx------ 3 greg greg 4096 Apr 22  2015 panel/
drwx------ 2 greg greg 4096 Apr 22  2015 totem/
drwx------ 7 greg greg 4096 Apr 22  2015 ./
drwx------ 6 greg greg 4096 Jan 11  2017 ../
unicorn:~$ 

[toc] | [prev] | [next] | [standalone]

#221127 — Re: Partition unreadable [was: Re: Debian Stretch broken !]

[Multipart message — attachments visible in raw view] — view raw

On Thu, Apr 9, 2020 at 8:29 AM Bernard <bdebreil@free.fr> wrote:

>
>
> I just realized that in that Debian Stretch system,
>
> I HAVE NO /home/<user>/.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 should I do to get it rebuilt ?
>
> Bernard
>
>
It'll rebuild itself when it's needed. The lack of a .gconf directory is
probably not causing your problem; rather, your problem is causing the lack
of a .gconf directory.

What happened when you tried running tasskel and installing a simpler
Windowing setup?

-- 
Kent

[toc] | [prev] | [next] | [standalone]

#221128 — 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 <bdebreil@free.fr
> <mailto:bdebreil@free.fr>> wrote:
>
>
>
>     I just realized that in that Debian Stretch system,
>
>     I HAVE NO /home/<user>/.gconf directory !
>

>
> It'll rebuild itself when it's needed. The lack of a .gconf directory is
> probably not causing your problem; rather, your problem is causing the
> lack of a .gconf directory.
>
> What happened when you tried running tasskel and installing a simpler
> Windowing setup?

# 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.

$ startx

invariably leads to

.......................
connexion to X server lost

==

Another time, I attempted to run

# evolution

unable to init server, connexion refused
failed to initiate gtk+  could not open display

Does that mean that I should re-install the gtk library ?

Bernard

[toc] | [prev] | [next] | [standalone]

#221131 — 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 which one you're currently trying to use.  That
makes debugging a lot harder, don't you think?

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
> 
> .......................
> connexion to X server lost

At that point, you look for errors in ~/.xsession-errors or, more usefully,
in the X log file.  Which, for stretch-and-later, on most hardware, will
be in ~/.local/share/xorg/.  Or if for some reason your X server still runs
as root, it might be in the /var/log/ directory.

> Another time, I attempted to run
> 
> # evolution
> 
> unable to init server, connexion refused
> failed to initiate gtk+  could not open display
> 
> Does that mean that I should re-install the gtk library ?

No, it means you tried to run it outside of an X session.  Obviously
that's not going to work.

Start with the basics.  Can X run *at all*?

Make sure xterm is installed, and try

startx xterm

That should give you the barest possible X session.  If it works, you'll
have a mostly empty screen, but with an xterm in the upper left corner.
You'll be able to move the mouse pointer around, and if the mouse cursor
is inside the xterm window area, you'll be able to type in the terminal.
Do that, and type "exit" or Ctrl-D in the xterm to get out.

If it DOESN'T work, try to figure out why, by reading the X log file.

Also useful would be:

Which video chipset is in use?  lspci -nn

Which firmware files are loaded, and which are missing?
dmesg | grep -i firmware

And, possibly, if you can, the *important* lines from the X log file.
But figuring out which lines are important, out of that gargantuan
log file, is an art form.

[toc] | [prev] | [next] | [standalone]

#221136 — 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
>>
>> .......................
>> connexion to X server lost
>
> At that point, you look for errors in ~/.xsession-errors or, more usefully,
> in the X log file.  Which, for stretch-and-later, on most hardware, will
> be in ~/.local/share/xorg/.  Or if for some reason your X server still runs
> as root, it might be in the /var/log/ directory.

Here are a few meaningful lines extracted from the Xorg.0.log


Starting line 48/515 :

[ 15541.358] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_33
[ 15541.360] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 15541.361] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 
paused 0
[ 15541.363] (--) PCI:*(0:1:0:0) 10de:128b:1458:36f8 rev 161, Mem @ 
0xee000000/16777216, 0xe0000000/134217728, 0xe8000000/33554432, I/O @ 
0x0000e000/128, BIOS @ 0x????????/131072
[ 15541.363] (II) LoadModule: "glx"
[ 15541.363] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 15541.366] (II) Module glx: vendor="X.Org Foundation"
[ 15541.366]    compiled for 1.19.2, module version = 1.0.0
[ 15541.366]    ABI class: X.Org Server Extension, version 10.0
[ 15541.366] (==) Matched nouveau as autoconfigured driver 0
[ 15541.366] (==) Matched nv as autoconfigured driver 1
[ 15541.366] (==) Matched nouveau as autoconfigured driver 2
[ 15541.366] (==) Matched nv as autoconfigured driver 3
[ 15541.366] (==) Matched modesetting as autoconfigured driver 4
[ 15541.366] (==) Matched fbdev as autoconfigured driver 5
[ 15541.366] (==) Matched vesa as autoconfigured driver 6
[ 15541.366] (==) Assigned the driver to the xf86ConfigLayout
[ 15541.366] (II) LoadModule: "nouveau"
[ 15541.366] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[ 15541.367] (II) Module nouveau: vendor="X.Org Foundation"
[ 15541.367]    compiled for 1.19.3, module version = 1.0.13
[ 15541.367]    Module class: X.Org Video Driver
[ 15541.367]    ABI class: X.Org Video Driver, version 23.0
[ 15541.367] (II) LoadModule: "nv"
[ 15541.367] (WW) Warning, couldn't open module nv
[ 15541.367] (II) UnloadModule: "nv"
[ 15541.367] (II) Unloading nv

from line 375

[ 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)
[ 15541.577] (EE) AIGLX: reverting to software rendering
[ 15541.577] (EE) AIGLX error: dlopen of 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so failed 
(/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so: cannot open shared object 
file: No such file or directory)
[ 15541.577] (EE) GLX: could not load software renderer
[ 15541.577] (II) GLX: no usable GL providers found for screen 0
[ 15541.580] (II) NOUVEAU(0): NVEnterVT is called.
[ 15541.610] (II) NOUVEAU(0): Setting screen physical size to 508 x 285
[ 15541.610] resize called 1920 1080
[ 15541.629] (II) config/udev: Adding input device Power Button 
(/dev/input/event4)
[ 15541.629] (**) Power Button: Applying InputClass "libinput keyboard 
catchall"
[ 15541.629] (II) LoadModule: "libinput"
[ 15541.629] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[ 15541.630] (II) Module libinput: vendor="X.Org Foundation"
[ 15541.630]    compiled for 1.19.0, module version = 0.23.0
[ 15541.630]    Module class: X.Org XInput Driver
[ 15541.630]    ABI class: X.Org XInput driver, version 24.1
[ 15541.630] (II) Using input driver 'libinput' for 'Power Button'
[ 15541.630] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 
19 paused 0

The whole text file can be downloaded at

http://bdebreil.free.fr/Xorg.0.log

>
>
>
> Start with the basics.  Can X run *at all*?
>
> Make sure xterm is installed, and try
>
> startx xterm


That works !  This is the only graphic thing that I have been able to 
launch since the crash
>
> That should give you the barest possible X session.  If it works, you'll
> have a mostly empty screen, but with an xterm in the upper left corner.
> You'll be able to move the mouse pointer around, and if the mouse cursor
> is inside the xterm window area, you'll be able to type in the terminal.
> Do that, and type "exit" or Ctrl-D in the xterm to get out.
>
> If it DOESN'T work, try to figure out why, by reading the X log file.
>
> Also useful would be:
>
> Which video chipset is in use?  lspci -nn

00:00.0 Host bridge [0600]: Intel Corporation Device [8086:590f] (rev 05)
00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller 
(x16) [8086:1901] (rev 05)
00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 
xHCI Controller [8086:a12f] (rev 31)
00:16.0 Communication controller [0780]: Intel Corporation Sunrise 
Point-H CSME HECI #1 [8086:a13a] (rev 31)
00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-H SATA 
controller [AHCI mode] [8086:a102] (rev 31)
00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express 
Root Port #5 [8086:a114] (rev f1)
00:1c.5 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express 
Root Port #6 [8086:a115] (rev f1)
00:1c.6 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express 
Root Port #7 [8086:a116] (rev f1)
00:1c.7 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express 
Root Port #8 [8086:a117] (rev f1)
00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express 
Root Port #9 [8086:a118] (rev f1)
00:1d.1 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express 
Root Port #10 [8086:a119] (rev f1)
00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-H LPC 
Controller [8086:a143] (rev 31)
00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-H PMC 
[8086:a121] (rev 31)
00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-H HD Audio 
[8086:a170] (rev 31)
00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-H SMBus 
[8086:a123] (rev 31)
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK208 
[GeForce GT 710B] [10de:128b] (rev a1)
01:00.1 Audio device [0403]: NVIDIA Corporation GK208 HDMI/DP Audio 
Controller [10de:0e0f] (rev a1)
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] 
(rev 0c)


>
> Which firmware files are loaded, and which are missing?
> dmesg | grep -i firmware


[    0.168357] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[  293.533132] r8169 0000:02:00.0: firmware: direct-loading firmware 
rtl_nic/rtl8168g-2.fw
>

Thanks for your help

Bernard

[toc] | [prev] | [next] | [standalone]

#221137 — 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 package (or it's partly installed, or
corrupted...).  In any case, try reinstalling libgl1-mesa-dri.

> [ 15541.577] (EE) AIGLX: reverting to software rendering
> [ 15541.577] (EE) AIGLX error: dlopen of
> /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so failed
> (/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so: cannot open shared object
> file: No such file or directory)

Same package.

> > startx xterm
> 
> That works !  This is the only graphic thing that I have been able to launch
> since the crash

*nod* xterm doesn't need 3d rendering.  Some desktop environments do.

> 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK208 [GeForce
> GT 710B] [10de:128b] (rev a1)

> [    0.168357] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
> [  293.533132] r8169 0000:02:00.0: firmware: direct-loading firmware
> rtl_nic/rtl8168g-2.fw

Looks like your video chipset doesn't require firmware, so that's fine.

[toc] | [prev] | [next] | [standalone]

#221150 — [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 directory)
>
> You're missing the libgl1-mesa-dri package (or it's partly installed, or
> corrupted...).  In any case, try reinstalling libgl1-mesa-dri.

That did the trick !! After that package reinstalled, a return to user 
mode and

$ startx

did boot to the gnome desktop I'd lost 6 days ago, everything was there 
working all right. I logged out and booted again the usual way: 
everything was fine. I will never know how that driver got damaged.

Thanks a lot to you and to everyone who helped me solving that problem.

Bernard

[toc] | [prev] | [next] | [standalone]

#221132 — Re: Partition unreadable [was: Re: Debian Stretch broken !]

[Multipart message — attachments visible in raw view] — view raw

On Thu, Apr 9, 2020 at 9:32 AM Bernard <bdebreil@free.fr> wrote:

>
>
> Le 09/04/2020 15:45, Kent West a écrit :
> >
> >
> > On Thu, Apr 9, 2020 at 8:29 AM Bernard <bdebreil@free.fr
> > <mailto:bdebreil@free.fr>> wrote:
> >
> >
> >
> >     I just realized that in that Debian Stretch system,
> >
> >     I HAVE NO /home/<user>/.gconf directory !
> >
>
> >
> > It'll rebuild itself when it's needed. The lack of a .gconf directory is
> > probably not causing your problem; rather, your problem is causing the
> > lack of a .gconf directory.
> >
> > What happened when you tried running tasskel and installing a simpler
> > Windowing setup?
>
> # 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.
>

During the install, did you get any errors?

What happens if you do:

# sudo aptitude update

and

# sudo aptitude full-upgrade

Errors?



> $ startx
>
> invariably leads to
>
> .......................
> connexion to X server lost
>
>

So something is wrong with your X server setup; thus my suggestion to try a
simpler windowing system, and my suggestion to update/upgrade.


==
>
> Another time, I attempted to run
>
> # evolution
>
> unable to init server, connexion refused
> failed to initiate gtk+  could not open display
>
>
This is probably simply because X is not running; X-based apps aren't going
to be able to run if X is not first running.
I see that for startx, you're writing a "$" prompt (normal user, in most
cases - good), but or evolution, you're writing a "#" prompt (superuser
(root), in most cases - not good).

As a test, create an ~/.xinitrc file with the single line

/usr/bin/X11/xterm


If X can start, this should start only an xterm window ("exit" should shut
down X). (Don't forget to delete/modify/restore this file after this test
so your system works normally.)

-- 
Kent West                    <")))><
Westing Peacefully - http://kentwest.blogspot.com

[toc] | [prev] | [next] | [standalone]

#220927

[Multipart message — attachments visible in raw view] — view raw

On Sun, Apr 5, 2020 at 9:23 AM Kent West <westk@acu.edu> 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 looks a bit worrisome, but it may not actually be; it depends on what
> device is at sda2 (it might be a second (unformatted, unused) hard drive,
> or a USB thumb drive, or a CD/DVD drive, or ...).
>

No it can't be; I wasn't thinking straight. This is a second partition, not
a second drive.

This is almost certainly your problem. The next question is if it's a
hardware, formatting, or mounting problem. I'd run "cfdisk" and see what
that shows me.


-- 
Kent West                    <")))><
Westing Peacefully - http://kentwest.blogspot.com

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web