Re: What sets LC_TIME?

[Anssi Saari]

Greg Wooledge  writes:

> On Fri, Feb 16, 2024 at 03:34:12PM +0200, Anssi Saari wrote:
>> Yah. It was ssh passing through all that. On serial console, locale
>> settings are as expected:
>> 
>> $ locale
>> LANG=en_US.UTF-8
>> LANGUAGE=en_US:en
>> LC_CTYPE="en_US.UTF-8"
>> LC_NUMERIC="en_US.UTF-8"
>> LC_TIME="en_US.UTF-8"
> [...]
>
> Well then, that just changes the mystery from "happens on the Debian
> system I ssh into" to "happens on my ssh client".  For some reason,
> your ssh client has all of those LC_* variables set in its environment,
> which is still quite unusual.

Not at all, I know perfectly well where that comes from. I'd be upset if
I didn't. I set all that in my shell config. It's a kind of a legacy
contamination from remote shell machines. As I don't have root on all
the shell machines I use, I have traditionally configured locales in
shell init there. And at some point, I've copied those locale settings
to my home desktop, possibly other machines too.

I guess one of these days I'll run update-locale and clean up my shell
config.

Re: f3tools vs Silicon Power 4T drive

[Jeffrey Walton]

On Sat, Feb 17, 2024 at 12:47 AM gene heskett  wrote:
>
> On 2/16/24 21:13, Andy Smith wrote:
> > [...]
> > Sure, but we still don't know what Gene is trying to do or why
> > partition names would be useful to him so I am kind of sceptical
> > that this leads anywhere.
> >
> That part if the ^%$ drives ever get here, I just looked at the front
> deck and it has 2" of fresh white stuff on it.

Lol... More irrelevant chatter. Andy asked what you are trying to
accomplish, and you replied with your weather. It would be brilliant
comedy if it was not so sad to watch this thread torture the folks who
are trying to help you.

Painting with a broad brush, there are two types of people in the
world - those who listen, and those who wait to talk. I am pretty sure
you are one of those who wait to talk. It would behoove you to listen
more, talk less, and answer the questions that are asked of you. If
you don't, then folks like Andy, David and Max are not going to help
you.

Jeff

Re: partition reporting full, but not

[tomas]

On Sat, Feb 17, 2024 at 03:44:49PM +1100, Keith Bainbridge wrote:

[...]

> df -h
> Filesystem  Size  Used Avail Use% Mounted on
> udev7.2G 0  7.2G   0% /dev
> tmpfs   1.5G  1.9M  1.5G   1% /run
> /dev/nvme0n1p2   63G   27G   35G  44% /
> tmpfs   7.3G   84M  7.2G   2% /dev/shm
> tmpfs   5.0M   16K  5.0M   1% /run/lock
> /dev/nvme0n1p2   63G   27G   35G  44% /home

[...]

> Yes the / partitions are btrfs
> > 
> The annoying habit of listing /home at df seems to be part of btrfs standard
> practice which I dislike [...]

Oh, wait! This is btrfs. It seems to be able to put more than one file
system in a partition (so no, it's not "standard practice": you have
two different file systems there, which df duly reports, but they seem
to co-habitate one partition)

This being btrfs... quite possibly the missing space is used up in
one or more snapshots?

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: partition reporting full, but not

[Felix Miata]

Keith Bainbridge composed on 2024-02-17 15:44 (UTC+1100):

> Yes the / partitions are btrfs

df was not designed for the task you gave it. You need to use

btrfs filesystem 

commands:
https://btrfs.readthedocs.io/en/latest/btrfs-filesystem.html
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

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

Felix Miata

Re: partition reporting full, but not

[tomas]

On Fri, Feb 16, 2024 at 09:52:22PM -0500, Greg Wooledge wrote:
> On Sat, Feb 17, 2024 at 01:38:56PM +1100, Keith Bainbridge wrote:
> >   >> sudo df -h /
> > Filesystem  Size  Used Avail Use% Mounted on
> > /dev/sda336G   35G  100M 100% /
> 
> First off: you don't need sudo for this, ever.
> 
> Second: what kind of file system is this?
> 
> > sudo du -hPx --max-depth=1 /
> > 0   /mnt
> > 181M/boot
> > 15M /etc
> > 0   /media
> > 236M/opt
> > 336K/root
> > 0   /srv
> > 4.0K/tmp
> > 8.1G/usr
> > 726M/var
> > 9.2G/
> 
> So I guess the question is "Where's the rest of that 35 G used data?"
> 
> Conspicuously missing from this output is /home.  Is that a separate
> file system?  If so, you *could* have data inside the /home directory
> of the root file system, which is hidden by the /home file system that's
> mounted over it.  You'd need to unmount /home to check.  It's not a
> super probable situation, but it's worth checking.

Absolutely. What I miss, too, is lost+found (not every file system has
that,i though).

> The same applies to any other directory that's got a file system mounted
> on it.

Yes, looking "under" the mounts is a very good idea.

> Or... it could be some bizarre btrfs crap.  If this is a btrfs.

We're all curious :-)

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: What sets LC_TIME?

[tomas]

On Fri, Feb 16, 2024 at 05:19:10PM -0600, David Wright wrote:
> On Fri 16 Feb 2024 at 16:25:05 (-0500), Greg Wooledge wrote:

[...]

> > At this point we have no idea whether the ssh client is even a Unix/Linux
> > system.  It could be anything.  It could be a literal toaster.
> 
> More likely an æbleskiver pan?

But we know that all toasters run Unix, since a well-known company
got burnt by that recall they had to do.

On pans... I'm out of my depth, sorry.

;-)

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: "I: update-initramfs is disabled (live system is running on read-only media)" ...

[tomas]

On Fri, Feb 16, 2024 at 06:43:19PM -0600, Albretch Mueller wrote:
> On 2/16/24, to...@tuxteam.de  wrote:
> > On Fri, Feb 16, 2024 at 01:44:22PM -0600, Albretch Mueller wrote:

[...]

> > What is a "simple page" and what does "pixelation" mean in this
> > context? Or is that irrelevant?
> 
>  A relatively simple, js-based web page  I meant to say.

Ah. A browser trying to render some thing from "out there". I see.

> >> have searched and found out is that I will have to un/repack initramfs
> >> ..., but I haven't found a relatively safe, complete procedure.
> >>
> >> How can you update the initramfs on read-only media?
> >
> > You can't. Initramfs resides in the boot medium. To update it,
> > you have to write to said medium.
> 
>  Right on the Debian Kernel Handbook they tell you you may use
> "initramfs hooks" for such things:
> 
>  
> https://kernel-team.pages.debian.net/kernel-handbook/ch-update-hooks.html#s-initramfs-hooks
> 
>  even though I couldn't find exactly the
> "/etc/initramfs/post-update.d/" directory used by  update-initramfs
> for post update hook options, I notice what seems to be a bunch of
> those in:
> 
>  /usr/share/initramfs-tools/hooks/

AFAIK, those are rather to modify the result of the initramfs
build in various ways (e.g. include additional software in the
image, configure things in a different way, etc.). They are
invoked at different steps in the build process.

What you need, as others have said, is to rebuild your write-only
medium. You can tell mkinitramfs to deposit its result in a regular
file (option -o, the man page). How it goes to that read-only
medium is left as an exercise to the reader (unless you tell us
how you build that in the first place, that is :-)

Usually it goes to somewhere /boot/initramfs.img, if /boot is mounted
properly.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: f3tools vs Silicon Power 4T drive

[gene heskett]

On 2/16/24 21:13, Andy Smith wrote:

Hello,

On Fri, Feb 16, 2024 at 02:02:59PM -0600, David Wright wrote:

On Fri 16 Feb 2024 at 14:48:12 (+), Andy Smith wrote:

No, because it's a filesystem label for the ext4 fs created on
/dev/sdz1. If sdz1 is turned into an LVM Physical Volume, there
won't be an ext4 filesystem on it any more. If sdz1 is turned into a
member of an MD array, there won't be an ext4 filesystem on it any
more. The labels go with the filesystem.


It isn't a filesystem LABEL.


Oh dear, I am lost. I don't use gparted but at least one person in
this thread has said that Gene created a filesystem label not a
partition name, and Gene doesn't know which he created, so I've gone
from guessing partition name to fs label and now back to partition
name again.

I'm totally willing to believe that you know what you've created
there though, so fair enough.


You've not yet been clear about what you want, but from what little
information you have provided you've been told multiple times by
multiple people that filesystem labels won't help.

↑

… which would be moot if only Gene could create partition PARTLABELs
successfully.


Sure, but we still don't know what Gene is trying to do or why
partition names would be useful to him so I am kind of sceptical
that this leads anywhere.

That part if the ^%$ drives ever get here, I just looked at the front 
deck and it has 2" of fresh white stuff on it.


To describe what I am building, this is a 5 slot bare drive cage. You 
could throw tom cats thru it from most angles so I printed pretty sides 
for it.


I've printed drawers to fill those slots.  The top slot has a bpi-m5 in 
it, the bottom slot has a 5 volt 10 amp psu in it. slot 2 will have 2 of 
those nearly 4T SSD's in a 2 drive adapter, with full disk partitions on 
them, so obviously I should name the top one as "si-pwr-s2t". the bottom 
one then s/b si-pwr-s2b

slot-3 then s/b si-pwr-s3t and si-pwr-s3b.
slot-4 then is giga-s4t1 and giga-s4t2. ditto for the bottom one. named 
giga-s4b1 and giga-s4b2.  1 partition to hold amanda's database and one 
to serve as amanda's holding disk.


Whats so meaningless to you that you can't see the utility in that? 
That has not been explained, so please educate me as to why you think 
its worthless?

Thanks,
Andy



Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis

Re: f3tools vs Silicon Power 4T drive

[tomas]

On Fri, Feb 16, 2024 at 03:46:54PM -0500, Stefan Monnier wrote:

[...]

> FWIW, my crystal ball says "30s => software timeout rather than hardware
> problem"

and whithin that, a network thingy. Ah, were it 90s, it'd be a DNS thingy.
But 30s...

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: f3tools vs Silicon Power 4T drive

[tomas]

On Fri, Feb 16, 2024 at 12:12:06PM -0800, David Christensen wrote:
> On 2/15/24 17:44, gene heskett wrote:

[...]

> >  Other than that the gui access delay (30+ seconds) problems I have did
> > NOT go away when I moved /home off the raid to another SSD [...]

I think at this point few are surprised by that. Last round of debugging
we pretty much eliminated disk access as likey cause of those delays.

The most hopeful cause for a candidate, IIRC, was some thingy deep in the DE
trying to access an unavailable resource.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: partition reporting full, but not

[Keith Bainbridge]

On 17/2/24 13:55, Gremlin wrote:

On 2/16/24 21:38, Keith Bainbridge wrote:

Good afternoon All

I have just rebooted this laptop to ensure it is 'fresh'

/ is reporting full.

Trying to locate where I ran

sudo du -hPx --max-depth=1 /
0    /mnt
181M    /boot
15M    /etc
0    /media
236M    /opt
336K    /root
0    /srv
4.0K    /tmp
8.1G    /usr
726M    /var
9.2G    /
keith@dell0 $

  Sat 17Feb2024@13:33:29
  :~


  But:
   >> sudo df -h /
Filesystem  Size  Used Avail Use% Mounted on
/dev/sda3    36G   35G  100M 100% /
keith@dell0 $

  Sat 17Feb2024@13:33:39
  :~

Where do I start locating the conflicting information please?



Do you have any nfs mounts?






No nfs mounts

Thankyou

--
All the best

Keith Bainbridge

keith.bainbridge.3...@gmail.com
+61 (0)447 667 468

UTC + 10:00

Re: partition reporting full, but not

[Keith Bainbridge]

On 17/2/24 13:52, Greg Wooledge wrote:

On Sat, Feb 17, 2024 at 01:38:56PM +1100, Keith Bainbridge wrote:

   >> sudo df -h /
Filesystem  Size  Used Avail Use% Mounted on
/dev/sda336G   35G  100M 100% /


First off: you don't need sudo for this, ever.

Second: what kind of file system is this?


sudo du -hPx --max-depth=1 /
0   /mnt
181M/boot
15M /etc
0   /media
236M/opt
336K/root
0   /srv
4.0K/tmp
8.1G/usr
726M/var
9.2G/


So I guess the question is "Where's the rest of that 35 G used data?"

My wife is often telling me I'm not clear (obtuse). Thank you for 
clarifying the question



Conspicuously missing from this output is /home.  Is that a separate
file system?  If so, you *could* have data inside the /home directory
of the root file system, which is hidden by the /home file system that's
mounted over it.  You'd need to unmount /home to check.  It's not a
super probable situation, but it's worth checking.


I had wondered why /home was missing and concluded that as it's listed if I

df -h /home/
Filesystem  Size  Used Avail Use% 
Mounted on
/dev/sda3 ===same partiton as /   36G   35G  100M 100% /home
keith@dell0 $

Then
>> sudo du -hPx --max-depth=1  /home/
[sudo] password for root:
2.2G/home/keith
2.2G/home/
keith@dell0 $

So, part of the missing 35G, but nothing significant

I checked my daily driver - lenv0, and I have the same situation -

sudo du -hPx --max-depth=1 /
[sudo] password for root:
265M/boot
18M /etc
0   /media
947M/opt
1.5M/root
0   /srv
du: cannot access '/tmp/.mount_Espansr8ZHig': Permission denied
12M /tmp
9.6G/usr
1.8G/var
13G /

  >> sudo du -hPx --max-depth=1 /home/
3.0M/home/ke1th
3.0M/home/
keith@lenv0 $

df -h
Filesystem  Size  Used Avail Use% Mounted on
udev7.2G 0  7.2G   0% /dev
tmpfs   1.5G  1.9M  1.5G   1% /run
/dev/nvme0n1p2   63G   27G   35G  44% /
tmpfs   7.3G   84M  7.2G   2% /dev/shm
tmpfs   5.0M   16K  5.0M   1% /run/lock
/dev/nvme0n1p2   63G   27G   35G  44% /home

In this case /home/keith is a sym link to another partition.

But still 14GB difference between the 2 reporting processes.





The same applies to any other directory that's got a file system mounted
on it.


I have had data written to /mnt/someDisk when the partition was NOT 
mounted. I get that suggestion. Those instances showed up in du though.


Or... it could be some bizarre btrfs crap.  If this is a btrfs.


Yes the / partitions are btrfs


The annoying habit of listing /home at df seems to be part of btrfs 
standard practice which I dislike.   So far the ability to create 
timeshift and BackInTime snapshots in the proverbial blink of an eye are 
VERY good points for btrfs.Seems I need to allow for more more 
'slack' space as well?   du is reporting my timeshift directory as 0, 
and the internal subdir that lists save file as 108K. This tells me that 
btrfs is doing something magic.

Guess I'll be contemplating reinstalling onto ext4 in my sleep tonight.

To answer another question - no NFS

Thanks All

--
All the best

Keith Bainbridge

keith.bainbridge.3...@gmail.com
+61 (0)447 667 468

UTC + 10:00

Re: f3tools vs Silicon Power 4T drive

[David Wright]

On Sat 17 Feb 2024 at 02:12:49 (+), Andy Smith wrote:
> On Fri, Feb 16, 2024 at 02:02:59PM -0600, David Wright wrote:
> > … which would be moot if only Gene could create partition PARTLABELs
> > successfully.
> 
> Sure, but we still don't know what Gene is trying to do or why
> partition names would be useful to him so I am kind of sceptical
> that this leads anywhere.

  https://lists.debian.org/debian-user/2024/02/msg00604.html

I think Gene was nonplussed¹ by the "wall of HEX numbers" in that
post, where he gives the impression that the by-id/ string has to
be copied into the PARTLABEL field, and looks for meaning in a list
of /dev/disk/ symlinks without their targets.

I would sympathise with the view that by-id/ names are not very
memorable, or easy to transcribe if that's ever required. And,
of course, we've seen that they're not always unique. That may be
a reason to use PARTLABELs instead.

But I don't try to keep up with reports of what Gene's trying to do,
interspersed as they are with stories of He cylinders and Lead-acid
batteries.

¹ British meaning.

Cheers,
David.

Re: Does "LC_ALL=C" work on all shells?

[Max Nikulin]

On 16/02/2024 23:35, Franco Martelli wrote:

On 16/02/24 at 03:03, Max Nikulin wrote:

 LC_ALL=C.UTF-8 LANGUAGE=it aptitude why firefox-esr


here seems to override, tested twice with "it" and "it_IT.UTF-8":

~# env LC_ALL=C LANGUAGE=it script -T ~/test.time -a ~/test.script


You tested with LC_ALL=C, not with LC_ALL=C.UTF-8. It has been discussed 
that behavior of gettext in respect to LANGUAGE is different.


I am against "C" locale in Debian official docs since it may mangle 
output. I have posted it already:


LC_ALL=C ls /tmp/it/
''$'\303\250'

LC_ALL=C.UTF-8 ls /tmp/it/
è

root@itek:~# env LC_ALL=C LANGUAGE=it_IT.UTF-8 script -T ~/test.time -a 
~/test.script


Again, LANGUAGE value is a list of *languages*, not a locale like for 
LANG or LC_*. LANGUAGE can be it:en_US:en, while this value is invalid 
for LC_ALL. Do not confuse these variables.


Try to add "export LC_ALL=it_IT.UTF-8" to .bashrc and e.g."date" in 
the script session.


Yes, the messages are localized to it_IT.UTF-8 into the "script" 
session, however users that have set LC_ALL variable into .bashrc I 
suppose already know what are they doing.


They just noticed that such variable exists and added to their configs. 
My colleague was bitten by LC_ALL. Is was a surprise when a database 
started to use "," instead of "." as decimal separator and it took 
enough time to find what caused drastic lost of precision. LC_ALL was 
set by the system administrator in ~/.bashrc.


I like the idea to *suggest* people to use English locale for upgrades 
if they are comfortable with it. It will help for searching web and 
during discussions. However I believe that a UTF-8 locale is safer and 
better nowadays. I hope, there is no mistakes any more:


LC_ALL=C.UTF-8; LANGUAGE=; export LC_ALL LANGUAGE

or its equivalent for user shell executed inside "script" session. I am 
unsure if locale of "script" command can be an issue.

Re: partition reporting full, but not

[Gremlin]

On 2/16/24 21:38, Keith Bainbridge wrote:

Good afternoon All

I have just rebooted this laptop to ensure it is 'fresh'

/ is reporting full.

Trying to locate where I ran

sudo du -hPx --max-depth=1 /
0    /mnt
181M    /boot
15M    /etc
0    /media
236M    /opt
336K    /root
0    /srv
4.0K    /tmp
8.1G    /usr
726M    /var
9.2G    /
keith@dell0 $

  Sat 17Feb2024@13:33:29
  :~


  But:
   >> sudo df -h /
Filesystem  Size  Used Avail Use% Mounted on
/dev/sda3    36G   35G  100M 100% /
keith@dell0 $

  Sat 17Feb2024@13:33:39
  :~

Where do I start locating the conflicting information please?



Do you have any nfs mounts?

Re: partition reporting full, but not

[Greg Wooledge]

On Sat, Feb 17, 2024 at 01:38:56PM +1100, Keith Bainbridge wrote:
>   >> sudo df -h /
> Filesystem  Size  Used Avail Use% Mounted on
> /dev/sda336G   35G  100M 100% /

First off: you don't need sudo for this, ever.

Second: what kind of file system is this?

> sudo du -hPx --max-depth=1 /
> 0 /mnt
> 181M  /boot
> 15M   /etc
> 0 /media
> 236M  /opt
> 336K  /root
> 0 /srv
> 4.0K  /tmp
> 8.1G  /usr
> 726M  /var
> 9.2G  /

So I guess the question is "Where's the rest of that 35 G used data?"

Conspicuously missing from this output is /home.  Is that a separate
file system?  If so, you *could* have data inside the /home directory
of the root file system, which is hidden by the /home file system that's
mounted over it.  You'd need to unmount /home to check.  It's not a
super probable situation, but it's worth checking.

The same applies to any other directory that's got a file system mounted
on it.

Or... it could be some bizarre btrfs crap.  If this is a btrfs.

Re: partition reporting full, but not

[David Wright]

On Sat 17 Feb 2024 at 13:38:56 (+1100), Keith Bainbridge wrote:
> I have just rebooted this laptop to ensure it is 'fresh'
> 
> / is reporting full.
> 
> Trying to locate where I ran
> 
> sudo du -hPx --max-depth=1 /
> 0 /mnt
> 181M  /boot
> 15M   /etc
> 0 /media
> 236M  /opt
> 336K  /root
> 0 /srv
> 4.0K  /tmp
> 8.1G  /usr
> 726M  /var
> 9.2G  /
> keith@dell0 $
> 
>  Sat 17Feb2024@13:33:29
>  :~
> 
> 
>  But:
>   >> sudo df -h /
> Filesystem  Size  Used Avail Use% Mounted on
> /dev/sda336G   35G  100M 100% /
> keith@dell0 $
> 
>  Sat 17Feb2024@13:33:39
>  :~
> 
> Where do I start locating the conflicting information please?

Typically some space is reserved for root, so that you have a little
headroom to extricate yourself from this situation. It looks like it's
the 5% shown below (from an installer screen):

  ┌┤ [!!] Partition disks ├─┐   
  │ │   
  │ You are editing partition #3 of /dev/nvme0n1. This partition is │   
  │ formatted with the Ext4 journaling file system. All data in it WILL │   
  │ BE DESTROYED!   │   
  │ │   
  │ Partition settings: │   
  │ │   
  │  Name:  Umbo-B  │   
  │  Use as:Ext4 journaling file system │   
  │ │   
  │  Format the partition:  yes, format it  │   
  │  Mount point:   /   │   
  │  Mount options: defaults│   
  │  Label: umbo03  │   
  │  Reserved blocks:   5%  │   
  │  Typical usage: standard│   
  │  Bootable flag: off │   
  │ │   
  │  Resize the partition (currently 31.5 GB)   │   
  │  Erase data on this partition   │   
  │  Delete the partition   │   
  │  Done setting up the partition  │   
  │ │   
  ││   
  │ │   
  └─┘   

Cheers,
David.

partition reporting full, but not

[Keith Bainbridge]

Good afternoon All

I have just rebooted this laptop to ensure it is 'fresh'

/ is reporting full.

Trying to locate where I ran

sudo du -hPx --max-depth=1 /
0   /mnt
181M/boot
15M /etc
0   /media
236M/opt
336K/root
0   /srv
4.0K/tmp
8.1G/usr
726M/var
9.2G/
keith@dell0 $

 Sat 17Feb2024@13:33:29
 :~


 But:
  >> sudo df -h /
Filesystem  Size  Used Avail Use% Mounted on
/dev/sda336G   35G  100M 100% /
keith@dell0 $

 Sat 17Feb2024@13:33:39
 :~

Where do I start locating the conflicting information please?

--
All the best

Keith Bainbridge

keith.bainbridge.3...@gmail.com
+61 (0)447 667 468

UTC + 10:00

Re: f3tools vs Silicon Power 4T drive

[Andy Smith]

Hello,

On Fri, Feb 16, 2024 at 03:46:54PM -0500, Stefan Monnier wrote:
> FWIW, my crystal ball says "30s => software timeout rather than hardware
> problem"

Back in a previous thread Gene was saying that it's only evident
when some GUI app brings up a file requester to load or save
something so that was my thought too. In particular that it might be
doing some kind of failed network activity looking for network
shares or something.

The thing is, we've also seen Gene's computers with strange things
like syntax errors in /etc/nsswitch.conf and /etc/hosts, avahi bits
manually rm'd, resolv.conf whacked with chattr +i and so on, so
it's also no surprise to me that this is difficult to debug.

David's suggestion of starting with a minimal install might be the
only way to do it.

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: f3tools vs Silicon Power 4T drive

[Andy Smith]

Hello,

On Fri, Feb 16, 2024 at 02:02:59PM -0600, David Wright wrote:
> On Fri 16 Feb 2024 at 14:48:12 (+), Andy Smith wrote:
> > No, because it's a filesystem label for the ext4 fs created on
> > /dev/sdz1. If sdz1 is turned into an LVM Physical Volume, there
> > won't be an ext4 filesystem on it any more. If sdz1 is turned into a
> > member of an MD array, there won't be an ext4 filesystem on it any
> > more. The labels go with the filesystem.
> 
> It isn't a filesystem LABEL.

Oh dear, I am lost. I don't use gparted but at least one person in
this thread has said that Gene created a filesystem label not a
partition name, and Gene doesn't know which he created, so I've gone
from guessing partition name to fs label and now back to partition
name again.

I'm totally willing to believe that you know what you've created
there though, so fair enough.

> > You've not yet been clear about what you want, but from what little
> > information you have provided you've been told multiple times by
> > multiple people that filesystem labels won't help.
>↑
> 
> … which would be moot if only Gene could create partition PARTLABELs
> successfully.

Sure, but we still don't know what Gene is trying to do or why
partition names would be useful to him so I am kind of sceptical
that this leads anywhere.

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: "I: update-initramfs is disabled (live system is running on read-only media)" ...

[Albretch Mueller]

On 2/16/24, to...@tuxteam.de  wrote:
> On Fri, Feb 16, 2024 at 01:44:22PM -0600, Albretch Mueller wrote:
>> I've got a relatively old laptop with an ATI Radeon HD card, which
>> firmware I can't update. Wild pixelations happen even on relatively
>> simple pages not just videos. It seems to be a common problem. What I
>
> What is a "simple page" and what does "pixelation" mean in this
> context? Or is that irrelevant?

 A relatively simple, js-based web page  I meant to say.

>> have searched and found out is that I will have to un/repack initramfs
>> ..., but I haven't found a relatively safe, complete procedure.
>>
>> How can you update the initramfs on read-only media?
>
> You can't. Initramfs resides in the boot medium. To update it,
> you have to write to said medium.

 Right on the Debian Kernel Handbook they tell you you may use
"initramfs hooks" for such things:

 
https://kernel-team.pages.debian.net/kernel-handbook/ch-update-hooks.html#s-initramfs-hooks

 even though I couldn't find exactly the
"/etc/initramfs/post-update.d/" directory used by  update-initramfs
for post update hook options, I notice what seems to be a bunch of
those in:

 /usr/share/initramfs-tools/hooks/

 lbrtchx

Re: GRUB lost graphical terminal mode

[Borden]

Thank you for the tip!

So `GRUB_TERMINAL=gfxterm` works, `GRUB_TERMINAL=console` works, but whatever 
the default is supposed to be does not. Does this imply that "the platform's 
native terminal output" is broken?

Re: What sets LC_TIME?

[David Wright]

On Fri 16 Feb 2024 at 16:25:05 (-0500), Greg Wooledge wrote:
> On Fri, Feb 16, 2024 at 11:11:09AM -0600, David Wright wrote:
> > On Fri 16 Feb 2024 at 09:12:24 (-0500), Greg Wooledge wrote:
> > > On Fri, Feb 16, 2024 at 03:34:12PM +0200, Anssi Saari wrote:
> > > > Yah. It was ssh passing through all that. On serial console, locale
> > > > settings are as expected:
> > > > 
> > > > $ locale
> > > > LANG=en_US.UTF-8
> > > > LANGUAGE=en_US:en
> > > > LC_CTYPE="en_US.UTF-8"
> > > > LC_NUMERIC="en_US.UTF-8"
> > > > LC_TIME="en_US.UTF-8"
> > > [...]
> > > 
> > > Well then, that just changes the mystery from "happens on the Debian
> > > system I ssh into" to "happens on my ssh client".  For some reason,
> > > your ssh client has all of those LC_* variables set in its environment,
> > > which is still quite unusual.
> > 
> > Could something weird here do that?
> > 
> >   $ grep LC /etc/ssh/*g
> >   /etc/ssh/ssh_config:SendEnv LANG LC_*
> >   /etc/ssh/sshd_config:AcceptEnv LANG LC_*
> >   $ 
> 
> That's all normal and expected.

Yes, they're off my system :) though I should have added -r to
catch any ssh_config.d/* files, as in the illustration below.

> What's odd is that client *actually has* LC_NUMERIC and so on set in
> its environment.  Which... is not a problem if they're all set to the
> correct values.  It's weird, but not wrong.  The problem for the OP was
> that one of the values was not set correctly, or at least not as
> expected.

That's why I posted the last line about SetEnv, illustrated by:

  $ cat /etc/ssh/ssh_config.d/test.conf 
  Host ahost
SetEnv LC_PAPER=en_GB.utf8
  #
  $ ssh ahost
  Linux ahost 5.10.0-27-amd64 #1 SMP Debian 5.10.205-2 (2023-12-31) x86_64

  The programs included with the Debian GNU/Linux system are free software;
  [ … ]
  You have new mail.
  Last login: Fri Feb 16 22:41:18 2024 from 192.168.1.14
  $ locale
  LANG=C.UTF-8
  LANGUAGE=
  LC_CTYPE=en_GB.UTF-8
  LC_NUMERIC="C.UTF-8"
  LC_TIME="C.UTF-8"
  LC_COLLATE="C.UTF-8"
  LC_MONETARY="C.UTF-8"
  LC_MESSAGES="C.UTF-8"
  LC_PAPER=en_GB.utf8←
  LC_NAME="C.UTF-8"
  LC_ADDRESS="C.UTF-8"
  LC_TELEPHONE="C.UTF-8"
  LC_MEASUREMENT="C.UTF-8"
  LC_IDENTIFICATION="C.UTF-8"
  LC_ALL=
  $ 

It's not a place I'd have immediately thought of looking.

> At this point we have no idea whether the ssh client is even a Unix/Linux
> system.  It could be anything.  It could be a literal toaster.

More likely an æbleskiver pan?

Cheers,
David.

Re: SMART Uncorrectable_Error_Cnt rising - should I be worried?

[Gremlin]

On 2/16/24 13:56, Roy J. Tellason, Sr. wrote:

On Friday 16 February 2024 04:52:22 am David Christensen wrote:

I think the Raspberry Pi, etc., users on this list live with USB storage
and have found it to be reliable enough for personal and SOHO network use.
  
I have one,  haven't done much with it.  Are there any alternative ways to interface storage?  Maybe add SATA ports or something?





On raspberry Pi 1 to 4 No, you have a choice of USB 2 or USB 3

Raspberry Pi 5 Yes with and NVME hat interfaced to the pcie "port"

I am using a Pi 5 (desktop) with USB 3 port hooked to an NVME external 
drive and it works just fine.


It is much faster than the Pi 4 I was using because of the new "south 
bridge"

Re: cruft report: The new kid on the block

[Gremlin]

On 2/16/24 10:50, Sven Joachim wrote:

On 2024-02-16 09:06 -0500, Gremlin wrote:


cruft report: Fri Feb 16 08:54:01 2024
 missing: dpkg 
 /etc/network/if-post-down.d/wireless-tools
 /etc/network/if-pre-up.d/ethtool
 /etc/network/if-pre-up.d/wireless-tools
 /etc/network/if-up.d/ethtool

wireless-tools and ethtool owns these files but are missing from the
system, ie MIA


That is not supposed to happen, but it is hard to tell who removed these
files, when and why.  The etckeeper tool can help to track down such
changes.


Doing a reinstall does not recreate them, why?


Because these files are conffiles, and the admin is free to edit or
delete them; dpkg will respect these changes and not reinstate missing
conffiles, unless given the "--force-confmiss" option.

Cheers,
Sven




This did the trick:

Installation/pakman -r ethtool
pakman: 2024-02-13
Remove: ethtool
Package: ethtool
Packages that will be removed:
  ethtool*
Remove  y
Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be REMOVED:
  ethtool*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 737 kB disk space will be freed.
(Reading database ... 140228 files and directories currently installed.)
Removing ethtool (1:6.1-1) ...
Processing triggers for man-db (2.11.2-2) ...
(Reading database ... 140218 files and directories currently installed.)
Purging configuration files for ethtool (1:6.1-1) ...
Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be REMOVED:
ethtool*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 737 kB disk space will be freed.
(Reading database ... 140228 files and directories currently installed.)
Removing ethtool (1:6.1-1) ...
Processing triggers for man-db (2.11.2-2) ...
(Reading database ... 140218 files and directories currently installed.)
Purging configuration files for ethtool (1:6.1-1) ...
Removing: ethtool: Completed

Removal: Complete

pakman: 2024-02-13: Run Complete
Installation/pakman -i ethtool
pakman: 2024-02-13
Installing: ethtool
Package: ethtool
New packages: ethtool
Continue Install  y
Installing: ethtool
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  ethtool
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/184 kB of archives.
After this operation, 737 kB of additional disk space will be used.
Selecting previously unselected package ethtool.
(Reading database ... 140216 files and directories currently installed.)
Preparing to unpack .../ethtool_1%3a6.1-1_arm64.deb ...
Unpacking ethtool (1:6.1-1) ...
Setting up ethtool (1:6.1-1) ...
Processing triggers for man-db (2.11.2-2) ...
Installing: ethtool: Completed

Installation: Complete


Thanks

Re: What sets LC_TIME?

[Greg Wooledge]

On Fri, Feb 16, 2024 at 11:11:09AM -0600, David Wright wrote:
> On Fri 16 Feb 2024 at 09:12:24 (-0500), Greg Wooledge wrote:
> > On Fri, Feb 16, 2024 at 03:34:12PM +0200, Anssi Saari wrote:
> > > Yah. It was ssh passing through all that. On serial console, locale
> > > settings are as expected:
> > > 
> > > $ locale
> > > LANG=en_US.UTF-8
> > > LANGUAGE=en_US:en
> > > LC_CTYPE="en_US.UTF-8"
> > > LC_NUMERIC="en_US.UTF-8"
> > > LC_TIME="en_US.UTF-8"
> > [...]
> > 
> > Well then, that just changes the mystery from "happens on the Debian
> > system I ssh into" to "happens on my ssh client".  For some reason,
> > your ssh client has all of those LC_* variables set in its environment,
> > which is still quite unusual.
> 
> Could something weird here do that?
> 
>   $ grep LC /etc/ssh/*g
>   /etc/ssh/ssh_config:SendEnv LANG LC_*
>   /etc/ssh/sshd_config:AcceptEnv LANG LC_*
>   $ 

That's all normal and expected.

What's odd is that client *actually has* LC_NUMERIC and so on set in
its environment.  Which... is not a problem if they're all set to the
correct values.  It's weird, but not wrong.  The problem for the OP was
that one of the values was not set correctly, or at least not as
expected.

At this point we have no idea whether the ssh client is even a Unix/Linux
system.  It could be anything.  It could be a literal toaster.

Re: Does "LC_ALL=C" work on all shells?

[Franco Martelli]

On 16/02/24 at 17:44, Greg Wooledge wrote:


If my guess is correct, then I don't support the plan to modify the
Debian documentation to suggest that everyone log their dist-upgrades
in English "because if something goes wrong you will probably ask for
help from an English speaker".  There are way too many layers of
assumptions there.


No it wasn't for this argument that I wrote:


"I think that a recorded session with the output of the commands in
English is better then a localized session for debugging purposes."


In the paragraph in question ¹  I read:

"It is strongly recommended that you use the /usr/bin/script program to 
record a transcript of the upgrade session. Then if a problem occurs, 
you will have a log of what happened, and if needed, can provide exact 
information in a bug report. To start the recording, type:"


Therefore I ran "script" session to upgrade to stable 12.5, then I saw 
that the output of "apt" was localized to my native language. So I 
thought: How can I provide exact information in a bug report if I've 
only localized messages?


For this reason I've asked for feedback here before to propose a change 
to the syntax to the "script" command that IMHO it'd be:


# env LC_ALL=C.UTF-8 script -T ~/upgrade-bookwormstep.time -a 
~/upgrade-bookwormstep.script


or at the place of LC_ALL to use instead LC_MESSAGES as Teemu wrote:

On 16/02/24 at 08:13, Teemu Likonen wrote:

To change programs' output messages to English LC_MESSAGES=C is often
enough. Sometimes LC_TIME and LC_NUMERIC are required too.


but it seems may have drawbacks if other variables are involved.
From the manual page of "script" command the -t option is deprecated in 
favor of -T and the above command has the advantage to be executable in 
all shells (thank to your feedback). A change is required however and 
the command proposed seems to me an improvement.




On Fri, Feb 16, 2024 at 05:35:11PM +0100, Franco Martelli wrote:

however users that have set LC_ALL variable into .bashrc I suppose already
know what are they doing.


No.  No, they do not.  They may *think* they do.  They do not.


Ahah OK they do not.


¹ 
https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#record-session

--
Franco Martelli

Re: f3tools vs Silicon Power 4T drive

[gene heskett]

On 2/16/24 15:47, Stefan Monnier wrote:

One of the 1T samsungs in the md raid10 isn't entirely happy but mdadm has
not fussed about it, and smartctl seems to say its ok after testing.
  Other than that the gui access delay (30+ seconds) problems I have did
NOT go away when I moved /home off the raid to another SSD, so I may move
it back. One of the reasons I ma rsync'ing this /home back to it every
other day or so, takes < 5 minutes.

Please get a small SSD, do a fresh install, and test for the access delay.
If the delay is not present, incrementally add and test applications.
If you encounter the delay, please stop and post the details; console
sessions are best.  If not, then connect the disks with /home and test.
If you encounter the delay, then please stop and post the details.  If you
do not encounter the delay, then your system is fixed.
Take a Clonezilla image.


FWIW, my crystal ball says "30s => software timeout rather than hardware
problem"


 Stefan


We are on the same page, but what is causing the timeout?

.


Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis

Re: Using a Python script as a login shell

[Alex King]

Hey this looks like a fun thing to play with, I like what you've done.  
I logged in and accessed it.  Now that it's been some time since you 
announced it and it's still running, I guess it has had some testing 
already.


I don't see anything wrong with what you have done after a quick look, 
it seems like you took some steps to secure it.


If you care about security you want to think about defense in depth.  
Even if there don't appear to be ways for arbitrary filesystem or 
network access to happen, you have to consider the effect of bugs in 
your program and bugs in python itself.


To protect against unwanted filesystem access, I suggest:

 * use a vm without anything else important on it
 * consider filesystem quotas
 * lock down the user as much as possible.  Consider e.g. apparmor or
   selinux.  Maybe consider containerization/capabilities inside the VM

To protect against unwanted network access:

 * prevent all outgoing network connections from the VM using
   iptables/nftables (or whitelist any that are necessary)
 * again consider networking restrictions using apparmor or selinux.

What level of protection is necessary will depend on the severity of 
impact in the case it gets hacked, and also your own level of 
conscientiousness.


Also consider putting in some monitoring; monitor network bandwith and 
CPU usage at least (perhaps # of logins as well) and set up an alert if 
those go outside limits, so you get timely notification if something 
should happen.


Have fun,
Alex

P.S. this brings to mind 
https://en.wikipedia.org/wiki/Russell_Coker#SELinux_Play_Machine, which 
is no longer operating.


When you say "expose it to the internet via SSH", do you mean expose it 
to everyone (e.g. by publishing the pssword), or will there still be 
some restrictions on who can access it?  If the former, you should be 
able to set up ssh without any password required.


On 16/02/24 21:36, Ralph Aichinger wrote:

Hello fellow Debianites!

I want do do a custom CLI for a project, and I am quite happy with the
Python cmd module. Aside from having a practically un-googleable name
it is very nice, and does a lot with very little code. So far, so good.
But:

If I write a Python script with this module, and expose it to the
internet via SSH, will hell break loose? So far I've done the
following:

1. Put my script in /usr/local/bin/turtle (the canonical example in the
docs is something with turtle), you can see the sourcecode of my script
here:

https://pi.h5.or.at/mockturtle.txt

This script does absolutely nothing sensible, you can try it out
by doing a

ssh -l admin probe.aisg.at

from a IPv6 capable host (sorry, no IPv4). The password is "admin".

Any and all suggestions on stuff that is stupid and crazy from a
security standpoint in this script are very much appreciated!

2. Then I put /usr/local/bin/turtle in /etc/shells

3. I added a user "admin" that has /usr/local/bin/turtle as shell

4. I added following stanza to /etc/ssh/sshd_config

Match User admin
 X11Forwarding no
 AllowTcpForwarding no
 ForceCommand /usr/local/bin/turtle

5. In the script I tried to catch the Ctrl-C signal, so the interpreter
does not give out too obvious error messages (that show what is going
on behind the scenes).

Is this enough to harden this setup against escaping into a shell
or the full python interpreter, to do something nasty? Or is it
completely crazy, because theere is some way to abuse a setup like
this, that I have not found yet?

TIA
Ralph

Re: f3tools vs Silicon Power 4T drive

[David Christensen]

On 2/16/24 12:46, Stefan Monnier wrote:

One of the 1T samsungs in the md raid10 isn't entirely happy but mdadm has
not fussed about it, and smartctl seems to say its ok after testing.
  Other than that the gui access delay (30+ seconds) problems I have did
NOT go away when I moved /home off the raid to another SSD, so I may move
it back. One of the reasons I ma rsync'ing this /home back to it every
other day or so, takes < 5 minutes.

Please get a small SSD, do a fresh install, and test for the access delay.
If the delay is not present, incrementally add and test applications.
If you encounter the delay, please stop and post the details; console
sessions are best.  If not, then connect the disks with /home and test.
If you encounter the delay, then please stop and post the details.  If you
do not encounter the delay, then your system is fixed.
Take a Clonezilla image.


FWIW, my crystal ball says "30s => software timeout rather than hardware
problem"



+1


David

Re: "I: update-initramfs is disabled (live system is running on read-only media)" ...

[Thomas Schmitt]

Hi,

Albretch Mueller wrote:
> > How can you update the initramfs on read-only media?

to...@tuxteam.de wrote:
> You can't. Initramfs resides in the boot medium. To update it,
> you have to write to said medium.

One will have to create a new read-only medium.


In case the original is a Debian Live ISO:

One would have to extract the initramfs file out of the ISO. If its name
is not known, then the boot loader configuration file should tell. Like
in /boot/grub/grub.cfg of debian-live-12.0.0-amd64-standard.iso:
   initrd  /live/initrd.img-6.1.0-9-amd64
or in its /isolinux/live.cfg:
   initrd /live/initrd.img

Next one would modify the extracted initramfs.
(This is an adventure on its own. Other will know more about it than me.)

Finally one would pack up a new ISO, taking all files from the old ISO but
replacing the initramfs file by the modified one from hard disk.
Roughly like in
  
https://wiki.debian.org/RepackBootableISO#In_xorriso_load_ISO_tree_and_write_modified_new_ISO

Details could be determined when the name of ISO and initramfs file is
known. If it's about DVD media, it would be interesting to learn about
the DVD drives at the computer which shall do the modification.


Have a nice day :)

Thomas

Re: f3tools vs Silicon Power 4T drive

[Stefan Monnier]

>> One of the 1T samsungs in the md raid10 isn't entirely happy but mdadm has
>> not fussed about it, and smartctl seems to say its ok after testing.
>>  Other than that the gui access delay (30+ seconds) problems I have did
>> NOT go away when I moved /home off the raid to another SSD, so I may move
>> it back. One of the reasons I ma rsync'ing this /home back to it every
>> other day or so, takes < 5 minutes.
> Please get a small SSD, do a fresh install, and test for the access delay.
> If the delay is not present, incrementally add and test applications.
> If you encounter the delay, please stop and post the details; console
> sessions are best.  If not, then connect the disks with /home and test.
> If you encounter the delay, then please stop and post the details.  If you
> do not encounter the delay, then your system is fixed.
> Take a Clonezilla image.

FWIW, my crystal ball says "30s => software timeout rather than hardware
problem"


Stefan

Re: f3tools vs Silicon Power 4T drive

[David Christensen]

On 2/15/24 22:16, gene heskett wrote:
I want to know with absolute certainty, with of the 4 drives in that 
raid10, actually has a belly ache. When it has a belly ache. I can't see 
any reason on this ball of rock and water, why I should be expected to 
replace a drive at a time until the belly ache goes away.



I seem to recall the Samsung 1 TB SSD's in your /home RAID10 were worn 
out.  I suggest installing the 2 TB M.2 WD Black, partitioning it with 
GPT, creating one large partition, mounting it at /data, and copying all 
of the data from /home to /data before the SSD's and RAID fail completely.



I recently had an Intel SSD 520 Series 180 GB go from operational to 
toast, with nothing in between.  If that happens to one of those Samsung 
1 TB SSD's, there will be no way for the RAID10 to correct the bad 
blocks on the other other SSD.  You will corrupt and lose data.



I leave /home on my root partition.  My working directories are in CVS. 
The only ephemeral data is in $HOME/.thunderbird.  I have a mail filter 
that copies incoming mail to a second folder on the IMAP server.  I Bcc 
outgoing mail to another mail account.  If my OS disk dies, I restore 
the image from last month, update Debian, check out my work, reconnect 
Thunderbird to the various e-mail servers, and clean up the Thunderbird 
folders as required.  No data is lost.



David

Re: "I: update-initramfs is disabled (live system is running on read-only media)" ...

[The Wanderer]

On 2024-02-16 at 14:44, Albretch Mueller wrote:

> I've got a relatively old laptop with an ATI Radeon HD card, which
> firmware I can't update. Wild pixelations happen even on relatively
> simple pages not just videos. It seems to be a common problem. What I
> have searched and found out is that I will have to un/repack initramfs
> ..., but I haven't found a relatively safe, complete procedure.
> 
> How can you update the initramfs on read-only media?

At a guess:

* Copy the read-only media to a writable location. This is "the image
  tree".

* Extract the initramfs from the file which contains it, into an empty
  directory. This is "the extracted initramfs".

* Modify the files in the extracted initramfs. The result is "the
  updated extracted initramfs".

* Create a new initramfs whose contents are the updated extracted
  initramfs. Copy it into the image tree. The result is "the updated
  image tree".

* Write the updated image tree to new read-only media. Depending on what
  form the media is, this may require other steps first; for example, if
  it's a CD or DVD, you will probably need to create an ISO using a tool
  like genisoimage or (I think) xorriso.

Read-only media is by definition not update-able. You can only create
new media, using a modified copy of the files from the read-only media.

I have successfully built updated versions of live-boot CDs, with
updated kernels and initrd environments and so forth, using this basic
method. It has been a long time, but I can confirm that it works, if
done correctly.


Now, if what you want to know is how to extract the initramfs... that
depends on how it's compressed, which may depend on what live-system
boot media you're working with, but typically it will be a
gzip-compressed cpio archive.

In that case, working from memory based on the last time I was doing
such a thing, what you'd need to do is something like:

$ mkdir /tmp/extract
$ cp /path/to/image/tree/initrd.gz /tmp/extract
$ gunzip /tmp/extract/initrd.gz
$ mkdir /tmp/extract/extracted-initramfs
$ cd /tmp/extract/extracted-initramfs
$ cpio -i < ../initrd

And to create a new one (without overwriting anything created during the
above), you'd do something like:

$ mv /tmp/extract/initrd /tmp/extract/initrd.unmodified
$ cd /tmp/extract/extracted-initramfs
$ find . | cpio -o > ../initrd
$ gzip -9 /tmp/extract/initrd
$ mv /tmp/extract/initrd.gz /path/to/image/tree/initrd.gz

*DO* *NOT* just take this as a recipe to follow. Read the documentation
of the programs involved, look for examples online if that documentation
doesn't make things clear in your mind, and use this as a *starting
point* to figure out what the correct thing to do in your circumstance
actually is.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: f3tools vs Silicon Power 4T drive

[David Christensen]

On 2/15/24 17:44, gene heskett wrote:
One of the 1T samsungs in the md raid10 isn't entirely happy but mdadm 
has not fussed about it, and smartctl seems to say its ok after testing. 
  Other than that the gui access delay (30+ seconds) problems I have did 
NOT go away when I moved /home off the raid to another SSD, so I may 
move it back. One of the reasons I ma rsync'ing this /home back to it 
every other day or so, takes < 5 minutes.



Please get a small SSD, do a fresh install, and test for the access 
delay.  If the delay is not present, incrementally add and test 
applications.  If you encounter the delay, please stop and post the 
details; console sessions are best.  If not, then connect the disks with 
/home and test.  If you encounter the delay, then please stop and post 
the details.  If you do not encounter the delay, then your system is 
fixed.  Take a Clonezilla image.



David

Re: f3tools vs Silicon Power 4T drive

[David Wright]

On Fri 16 Feb 2024 at 11:59:40 (-0800), David Christensen wrote:
> On 2/15/24 12:59, gene heskett wrote:
> > ...  gigastones, I 5 of them but when all
> > are plugged in there are only 3 becauae there are 2 pairs of
> > matching serial numbers ...
> 
> I recall 2 pairs of SSD's with matching serial numbers.  Please remove
> one SSD of each pair so that the remaining SSD's all have unique
> serial numbers.  Return them for a refund while you still can.  If you
> cannot, put them in another computer or put them on the shelf as
> spares.

Surely split them between at least two computers, so that
neither contains a duplicate?

Cheers,
David.

Re: f3tools vs Silicon Power 4T drive

[David Wright]

On Fri 16 Feb 2024 at 14:48:12 (+), Andy Smith wrote:
> On Fri, Feb 16, 2024 at 01:32:26AM -0500, gene heskett wrote:
> > On 2/15/24 16:20, David Wright wrote:
> > ># gdisk -l /dev/sdz
> > >GPT fdisk (gdisk) version 1.0.3
> > > 
> > >Partition table scan:
> > >  MBR: protective
> > >  BSD: not present
> > >  APM: not present
> > >  GPT: present
> > > 
> > >Found valid GPT with protective MBR; using GPT.
> > >Disk /dev/sdb: 3907029168 sectors, 1.8 TiB
> > >Model: Desktop
> > >Sector size (logical/physical): 512/512 bytes
> > >Disk identifier (GUID): A1093790-9A1A-4A7E-A807-B9CC6F7CF77E
> > >Partition table holds up to 128 entries
> > >Main partition table begins at sector 2 and ends at sector 33
> > >First usable sector is 34, last usable sector is 3907029134
> > >Partitions will be aligned on 2048-sector boundaries
> > >Total free space is 2014 sectors (1007.0 KiB)
> > > 
> > >Number  Start (sector)End (sector)  Size   Code  Name
> > >   12048  3907029134   1.8 TiB 8300  Lulu01
> > >#
> > > .
> > And this "partition" name survives?
> 
> No, because it's a filesystem label for the ext4 fs created on
> /dev/sdz1. If sdz1 is turned into an LVM Physical Volume, there
> won't be an ext4 filesystem on it any more. If sdz1 is turned into a
> member of an MD array, there won't be an ext4 filesystem on it any
> more. The labels go with the filesystem.

It isn't a filesystem LABEL. See attached partition and filesystem
information, the output from:

  $ cp -ip /run/udev/data/b8\:33 /tmp/partition-data
  $ cp -ip /run/udev/data/b253\:2 /tmp/filesystem-data
  $ 

In particular, E:ID_PART_ENTRY_NAME=Lulu01 from the first attachment
and E:ID_FS_LABEL=lulu01 // E:ID_FS_LABEL_ENC=lulu01 from the second.

> > and can be unique?
> 
> I don't know what that means to you or why it is useful.
> 
> > and can be used in a mount cmd?
> 
> Once the RAID and/or LVM is set up and a filesystem put on it, that
> filesystem can be mounted by label just like any filesystem can, but
> that filesystem may have multiple devices underneath it owing to the
> fact that it's on RAID and/or LVM, so there is no information you
> can put in its label that will tell you anything about those
> underlying devices.
> 
> > if all 3 questions above can be answered with a yes is the answer
> > I've been trying to squeeze out all along.
> 
> You've not yet been clear about what you want, but from what little
> information you have provided you've been told multiple times by
> multiple people that filesystem labels won't help.
   ↑

… which would be moot if only Gene could create partition PARTLABELs
successfully.

Cheers,
David.
S:disk/by-partuuid/37cf9edf-c695-428e-9889-2f52c40dfca5
S:disk/by-partlabel/Lulu01
S:disk/by-id/ata-ST2000DL003-9VT166_5YD1QX3D-part1
S:disk/by-uuid/11bb81f5-14e5-404a-8548-80bcb1e5071c
S:disk/by-id/usb-Seagate_Desktop_2GHN1XW7-0:0-part1
S:disk/by-path/pci-:00:14.0-usb-0:2:1.0-scsi-0:0:0:0-part1
S:disk/by-id/wwn-0x5000c5002f893194-part1
W:32
I:3947430162
E:ID_ATA=1
E:ID_TYPE=disk
E:ID_BUS=ata
E:ID_MODEL=ST2000DL003-9VT166
E:ID_MODEL_ENC=ST2000DL003-9VT166\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
E:ID_REVISION=CC98
E:ID_SERIAL=ST2000DL003-9VT166_5YD1QX3D
E:ID_SERIAL_SHORT=5YD1QX3D
E:ID_ATA_WRITE_CACHE=1
E:ID_ATA_WRITE_CACHE_ENABLED=1
E:ID_ATA_FEATURE_SET_HPA=1
E:ID_ATA_FEATURE_SET_HPA_ENABLED=1
E:ID_ATA_FEATURE_SET_PM=1
E:ID_ATA_FEATURE_SET_PM_ENABLED=1
E:ID_ATA_FEATURE_SET_SECURITY=1
E:ID_ATA_FEATURE_SET_SECURITY_ENABLED=0
E:ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=332
E:ID_ATA_FEATURE_SET_SECURITY_ENHANCED_ERASE_UNIT_MIN=332
E:ID_ATA_FEATURE_SET_SMART=1
E:ID_ATA_FEATURE_SET_SMART_ENABLED=1
E:ID_ATA_FEATURE_SET_AAM=1
E:ID_ATA_FEATURE_SET_AAM_ENABLED=1
E:ID_ATA_FEATURE_SET_AAM_VENDOR_RECOMMENDED_VALUE=208
E:ID_ATA_FEATURE_SET_AAM_CURRENT_VALUE=208
E:ID_ATA_DOWNLOAD_MICROCODE=1
E:ID_ATA_SATA=1
E:ID_ATA_SATA_SIGNAL_RATE_GEN2=1
E:ID_ATA_SATA_SIGNAL_RATE_GEN1=1
E:ID_ATA_ROTATION_RATE_RPM=5900
E:ID_WWN=0x5000c5002f893194
E:ID_WWN_WITH_EXTENSION=0x5000c5002f893194
E:ID_USB_MODEL=Desktop
E:ID_USB_MODEL_ENC=Desktop\x20\x20\x20\x20\x20\x20\x20\x20\x20
E:ID_USB_MODEL_ID=3300
E:ID_USB_SERIAL=Seagate_Desktop_2GHN1XW7-0:0
E:ID_USB_SERIAL_SHORT=2GHN1XW7
E:ID_USB_VENDOR=Seagate
E:ID_USB_VENDOR_ENC=Seagate\x20
E:ID_USB_VENDOR_ID=0bc2
E:ID_USB_REVISION=0130
E:ID_USB_TYPE=disk
E:ID_USB_INSTANCE=0:0
E:ID_USB_INTERFACES=:080650:
E:ID_USB_INTERFACE_NUM=00
E:ID_USB_DRIVER=usb-storage
E:ID_PATH=pci-:00:14.0-usb-0:2:1.0-scsi-0:0:0:0
E:ID_PATH_TAG=pci-_00_14_0-usb-0_2_1_0-scsi-0_0_0_0
E:ID_PART_TABLE_UUID=a1093790-9a1a-4a7e-a807-b9cc6f7cf77e
E:ID_PART_TABLE_TYPE=gpt
E:ID_FS_VERSION=2
E:ID_FS_UUID=11bb81f5-14e5-404a-8548-80bcb1e5071c
E:ID_FS_UUID_ENC=11bb81f5-14e5-404a-8548-80bcb1e5071c
E:ID_FS_TYPE=crypto_LUKS
E:ID_FS_USAGE=crypto

Re: f3tools vs Silicon Power 4T drive

[David Wright]

On Fri 16 Feb 2024 at 01:32:26 (-0500), gene heskett wrote:
> On 2/15/24 16:20, David Wright wrote:
> > On Thu 15 Feb 2024 at 20:44:52 (+), Andy Smith wrote:
> > > On Thu, Feb 15, 2024 at 03:19:54PM -0500, gene heskett wrote:
> > > > On 2/15/24 11:21, Andy Smith wrote:
> > > > > You asked if "labels" would survive their associated partition being
> > > > > put into LVM.
> > > > > 
> > > > > I said, "yes if you mean partition names, no if you mean filesystem
> > > > > labels".
> > > > > 
> > > > I'm still confused and it is not all the well clarified by looking at
> > > > gparted, a shot of which I posted.
> > > 
> > > This could all be answered easily if you'd just post the copy-paste
> > > of your terminal scrollback for what you actually did. Hopefully you
> > > don't now object to me asking what you meant since apparently even
> > > you do not know if you mean partition names or filesystem labels.
> > > >From what you posted it now sounds like labels on the ext4
> > > filesystems that you created.
> > 
> > Gene effectively shoots himself in the foot by using gparted (GUI)
> > instead of, say, gdisk where it's easy to paste what was done, or
> > for someone, say me, to post an example:

[ … skipped over creating the partition table … ]

> ># gdisk -l /dev/sdz
> >GPT fdisk (gdisk) version 1.0.3
> > 
> >Partition table scan:
> >  MBR: protective
> >  BSD: not present
> >  APM: not present
> >  GPT: present
> > 
> >Found valid GPT with protective MBR; using GPT.
> >Disk /dev/sdb: 3907029168 sectors, 1.8 TiB
> >Model: Desktop
> >Sector size (logical/physical): 512/512 bytes
> >Disk identifier (GUID): A1093790-9A1A-4A7E-A807-B9CC6F7CF77E
> >Partition table holds up to 128 entries
> >Main partition table begins at sector 2 and ends at sector 33
> >First usable sector is 34, last usable sector is 3907029134
> >Partitions will be aligned on 2048-sector boundaries
> >Total free space is 2014 sectors (1007.0 KiB)
> > 
> >Number  Start (sector)End (sector)  Size   Code  Name
> >   12048  3907029134   1.8 TiB 8300  Lulu01
> >#
> > 
> And this "partition" name survives?, and can be unique?, and can be
> used in a mount cmd?  That's how I'll do it then.  This if all 3
> questions above can be answered with a yes is the answer I've been
> trying to squeeze out all along.  Thank you.

Yes, the partition name (PARTLABEL) is in the partition table, not
inside the partition itself. It's as unique as you make it, because
you choose it. I've scrawled the names of my disks on the casing with
a magic marker for 25 years, from adam (6.4GB fujitsu) to wick (2TB WD).
The PARTLABELs and LABELs use that name as the stem, capitalised and
lowercase respectively.

As for using it with the mount command, that depends on what the
partition contains. For a straightforward filesystem, you can, as
described by   man mount (under Indicating the device and filesystem).

But I wouldn't, and I don't think you want to, as I believe you want
to use the partition as /part/ of something larger.

Whether you /can/ use it to mount depends on what the partition
contains. I don't use LVM or RAID, so I can't advise you there, except
to say that you wouldn't want to mount one piece of a larger structure,
AFAIK. But in my case, I use LUKS encryption, and I can demonstrate
what happens:

  $ sudo udisksctl unlock --block-device /dev/disk/by-partlabel/Lulu01
  Passphrase: 
  Unlocked /dev/sdc1 as /dev/dm-2.
  $ 

  # mount /dev/disk/by-partlabel/Lulu01 /media/lulu01
  mount: /media/lulu01: unknown filesystem type 'crypto_LUKS'.
  # 

You don't want to mount the partition, but the filesystem /within/ the
partition:

  # mount LABEL=lulu01 /media/lulu01
  # 

Of course, I don't normally use mount as root because I have an entry
in /etc/fstab:

  LABEL=lulu01 /media/lulu01 ext4 rw,errors=remount-ro,user,noauto

and I use a bash function called, surprisingly, lulu, as there's only
one partition on the disk:

  $ type lulu
  lulu is a function
  lulu () 
  { 
sudo udisksctl unlock --block-device /dev/disk/by-partlabel/Lulu01 && mount 
/media/lulu01
  }
  $ 

thus:

  $ lulu
  Passphrase: 
  Unlocked /dev/sdc1 as /dev/dm-2.
  $ 

But I would emphasise that, having unlocked the partition, I mount
the filesystem because it stands alone. It's not part of a RAID,
LVM, or whatever, that might need assembling with other components
before mounting the whole ensemble.

Cheers,
David.

Re: f3tools vs Silicon Power 4T drive

[David Christensen]

On 2/15/24 12:59, gene heskett wrote:

...  gigastones, I 5 of them but when all
are plugged in there are only 3 becauae there are 2 pairs of matching 
serial numbers ...



I recall 2 pairs of SSD's with matching serial numbers.  Please remove 
one SSD of each pair so that the remaining SSD's all have unique serial 
numbers.  Return them for a refund while you still can.  If you cannot, 
put them in another computer or put them on the shelf as spares.



David

Re: SMART Uncorrectable_Error_Cnt rising - should I be worried?

[David Christensen]

On 2/16/24 10:56, Roy J. Tellason, Sr. wrote:

On Friday 16 February 2024 04:52:22 am David Christensen wrote:

I think the Raspberry Pi, etc., users on this list live with USB storage
and have found it to be reliable enough for personal and SOHO network use.
  
I have one,  haven't done much with it.  Are there any alternative ways to interface storage?  Maybe add SATA ports or something?



In general, there are many combinations of storage interfaces offered in 
the marketplace.  For your specific single-board computer (SBC), I 
suggest checking the manual and checking the manufacturer sales and/or 
support web pages.



David

Re: "I: update-initramfs is disabled (live system is running on read-only media)" ...

[tomas]

On Fri, Feb 16, 2024 at 01:44:22PM -0600, Albretch Mueller wrote:
> I've got a relatively old laptop with an ATI Radeon HD card, which
> firmware I can't update. Wild pixelations happen even on relatively
> simple pages not just videos. It seems to be a common problem. What I

What is a "simple page" and what does "pixelation" mean in this
context? Or is that irrelevant?

> have searched and found out is that I will have to un/repack initramfs
> ..., but I haven't found a relatively safe, complete procedure.
> 
> How can you update the initramfs on read-only media?

You can't. Initramfs resides in the boot medium. To update it,
you have to write to said medium.

[Rest deleted since it seems irrelevant to above question]

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: f3tools vs Silicon Power 4T drive

[David Christensen]

On 2/15/24 12:19, gene heskett wrote:

On 2/15/24 11:21, Andy Smith wrote:

... redundancy plans ...

Like which version of a raid is the best at tolerating a failed drive, 
which give he best balance between redundancy and capacity.



Given a small number of disks, N (say, 4 to 8), the obvious choices are 
RAID5, RAID6, and RAID10.



Regarding redundancy:

* RAID5 can tolerate the loss of any one disk.

* RAID6 can tolerate the loss of any two disks.

* RAID10 can tolerate the loss of any one disk.  If you get lucky, 
RAID10 can tolerate the loss of multiple disks if each lost disk is in a 
different mirror.



Regarding capacity, if each disk stores B bytes:

* RAID5 gives you (N-1) * B capacity.

* RAID6 gives you (N-2) * B capacity.

* RAID10 gives you (N/2) * B capacity.


If each disk has performance P:

* RAID5 has performance ranging from P to (N-1) * P.

* RAID6 has performance ranging from P to (N-2) * P.

* RAID10 with M mirrors of D disks each has write performance M * P and 
read performance M * D * P.



Other factors to consider:

* All of the above needs to be reconsidered when one or more disks fail 
-- e.g. the array is operating in degraded mode.


* All of the above needs to be reconsidered when a failed disk has been 
replaced -- e.g. the array is resilvering.


* All of the above needs to be reconsidered when disk(s) fail during 
resilvering (!).


* RAID5 and RAID6 typically do not allow changes to topology -- e.g. the 
number of disks in the array and the number of bytes used in each disk.


* RAID0, RAID1, and JBOD may allow some changes to topology.  What is 
allowed depends upon implementation.


* With more disks, you may be able to create hierarchies -- e.g. stripe 
of mirrors (RAID10).  Redundancy, capacity, and/or performance under 
operational, degraded, resilvering, etc., modes all need to be reconsidered.


* Hot spares can be added.  Again, reconsider everything.

* And more.


So, it's a multi-dimensional problem and there are many combinations and 
permutations.  The more disks you have, the more possibilities you have. 
 I suggest picking two or three, and exploring them using a dedicated 
computer, a snapshot of your data, and your workload.



I am currently using ZFS and a stripe of 2 mirrors with 2 @ 3 TB HDD's 
each and SSD read cache.  I expect the same could be implemented with 
mdadm(8), lvm(8), bcache, dm-cache, btrfs, and others.



David

"I: update-initramfs is disabled (live system is running on read-only media)" ...

[Albretch Mueller]

I've got a relatively old laptop with an ATI Radeon HD card, which
firmware I can't update. Wild pixelations happen even on relatively
simple pages not just videos. It seems to be a common problem. What I
have searched and found out is that I will have to un/repack initramfs
..., but I haven't found a relatively safe, complete procedure.

How can you update the initramfs on read-only media?

$ sudo lspci | grep "VGA\|Radeon"
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Wrestler [Radeon HD 6320]

$ sudo hwinfo --gfxcard
11: PCI 01.0: 0300 VGA compatible controller (VGA)
  [Created at pci.386]
  Unique ID: vSkL.bvK4VqmPxPA
  SysFS ID: /devices/pci:00/:00:01.0
  SysFS BusID: :00:01.0
  Hardware Class: graphics card
  Model: "ATI Wrestler [Radeon HD 6320]"
  Vendor: pci 0x1002 "ATI Technologies Inc"
  Device: pci 0x9806 "Wrestler [Radeon HD 6320]"
  SubVendor: pci 0x17aa "Lenovo"
  SubDevice: pci 0x21ec
  Driver: "radeon"
  Driver Modules: "radeon"
  Memory Range: 0xe000-0xefff (ro,non-prefetchable)
  I/O Ports: 0x3000-0x30ff (rw)
  Memory Range: 0xf030-0xf033 (rw,non-prefetchable)
  Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled)
  IRQ: 26 (4041584 events)
  I/O Ports: 0x3c0-0x3df (rw)
  Module Alias: "pci:v1002d9806sv17AAsd21ECbc03sc00i00"
  Driver Info #0:
Driver Status: radeon is active
Driver Activation Cmd: "modprobe radeon"
  Driver Info #1:
Driver Status: amdgpu is active
Driver Activation Cmd: "modprobe amdgpu"
  Config Status: cfg=new, avail=yes, need=no, active=unknown

Primary display adapter: #11

$ sudo dmesg | grep --ignore-case "VGA\|video\|display\|Radeon"
[0.226971] Console: colour VGA+ 80x25
[0.287622] smpboot: CPU0: AMD E-450 APU with Radeon(tm) HD
Graphics (family: 0x14, model: 0x2, stepping: 0x0)
[0.417444] acpi PNP0A08:00: ignoring host bridge window [mem
0x000ce000-0x000c window] (conflicts with Video ROM [mem
0x000c-0x000ce5ff])
[0.418510] pci :00:01.0: Video device with shadowed ROM at
[mem 0x000c-0x000d]
[0.457408] pci :00:01.0: vgaarb: setting as boot VGA device
[0.457408] pci :00:01.0: vgaarb: bridge control possible
[0.457408] pci :00:01.0: vgaarb: VGA device added:
decodes=io+mem,owns=io+mem,locks=none
[0.457408] vgaarb: loaded
[4.436446] ACPI: video: Video Device [VGA1] (multi-head: yes  rom:
no  post: no)
[4.436916] input: Video Bus as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input9
[5.659994] [drm] radeon kernel modesetting enabled.
[5.660219] radeon :00:01.0: vgaarb: deactivate vga console
[5.662092] radeon :00:01.0: VRAM: 384M 0x -
0x17FF (384M used)
[5.662100] radeon :00:01.0: GTT: 1024M 0x1800 -
0x57FF
[5.662185] [drm] radeon: 384M of VRAM memory ready
[5.662191] [drm] radeon: 1024M of GTT memory ready.
[5.662317] radeon :00:01.0: firmware: direct-loading firmware
radeon/PALM_pfp.bin
[5.662374] radeon :00:01.0: firmware: direct-loading firmware
radeon/PALM_me.bin
[5.662433] radeon :00:01.0: firmware: direct-loading firmware
radeon/SUMO_rlc.bin
[5.662693] [drm] radeon: dpm initialized
[5.663081] radeon :00:01.0: firmware: direct-loading firmware
radeon/SUMO_uvd.bin
[5.684961] radeon :00:01.0: WB enabled
[5.684968] radeon :00:01.0: fence driver on ring 0 use gpu
addr 0x18000c00
[5.684974] radeon :00:01.0: fence driver on ring 3 use gpu
addr 0x18000c0c
[5.685422] radeon :00:01.0: fence driver on ring 5 use gpu
addr 0x00072118
[5.685956] radeon :00:01.0: radeon: MSI limited to 32-bit
[5.686097] radeon :00:01.0: radeon: using MSI.
[5.686153] [drm] radeon: irq initialized.
[6.331634] radeon :00:01.0: [drm] Skipping radeon atom DIG
backlight registration
[6.338785] [drm] Radeon Display Connectors
[6.338819] [drm]   VGA-1
[6.785182] fbcon: radeondrmfb (fb0) is primary device
[7.350484] radeon :00:01.0: [drm] fb0: radeondrmfb frame buffer device
[7.363349] [drm] Initialized radeon 2.50.0 20080528 for
:00:01.0 on minor 0
[   25.811867] thinkpad_acpi: This ThinkPad has standard ACPI
backlight brightness control, supported by the ACPI video driver
$

 lbrtchx

Re: Erreur nvidia suite upgrade noyau 6.1.0-18

[ajh-valmer]

On Friday 16 February 2024 08:16:54 Michel Verdier wrote:
> Le 14 février 2024 zithro a écrit :
> > - Michel a compris qu'André disait "je laisse tomber, ça montre bien
> > qu'il y a que des noobs/gens inutiles ici".

> Effectivement ça me semblait une attaque de la liste, d'où la forme
> abrupte de mon mail pour laquelle je m'excuse :

Et oui, il faut bien lire les contenus des mails.

Repassons au positif :
Ma carte Nvidia supportait le mode 1280x1024,
Avec le pilote Nouveau, le mode maxi est de 1024x768.
J'ai tout essayé, xrandr et compagnie... que des messages d'erreur.
Un problème succède à un autre, je ne peux plus upgrader
mon système du noyau 6.1.0-17-amd64 à 6.1.0-18-amd64.
J'ai effacé dans le /boot/ par :
# rm *6.1.0-18-amd64*
purgé par :
# apt purge *6.1.0-18-amd64*
"tout est à jour",
comme s'il y avait un résidu 6.1.0-18-amd64 quelque part.
Bonne soirée.

Re: SMART Uncorrectable_Error_Cnt rising - should I be worried?

[Roy J. Tellason, Sr.]

On Friday 16 February 2024 04:52:22 am David Christensen wrote:
> I think the Raspberry Pi, etc., users on this list live with USB storage 
> and have found it to be reliable enough for personal and SOHO network use.
 
I have one,  haven't done much with it.  Are there any alternative ways to 
interface storage?  Maybe add SATA ports or something?


-- 
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space,  a critter that can
be killed but can't be tamed.  --Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James 
M Dakin

Re: GRUB lost graphical terminal mode

[Darac Marjal]

On 16/02/2024 17:27, Borden wrote:

For a couple weeks now, I can't use graphical terminal in my GRUB 
configuration. Setting `GRUB_TERMINAL=console` works fine. With that line 
commented out, (thus using default settings), I get a blank screen on boot, 5 
second timeout, then normal boot.

Curiously, keyboard commands work normally. Specifically, I'm on multi-boot 
system, so I can boot into Windows by pressing the down arrow the correct 
number of times and pressing Enter. So I suspect that GRUB is either sending to 
the wrong video output or GRUB no longer supports my video card.

Any way I can troubleshoot without setting set debug=all?



According to the info pages, "console" means "native platform console". 
So, for UEFI, that would mean the UEFI console. For BIOS, I'm not sure 
if there is an equivalent.


Strangely, the info page says that default is "to use the platform's 
native terminal output" (Minor nit, I wish documentation would be 
consistent. Is "native terminal" the same as "native console"?).


Things you can try:

* Keep "GRUB_TERMINAL=console" uncommented. If it works, don't break it.

* Try "GRUB_TERMINAL=gfxterm" (uses graphics mode output).

* Try "GRUB_TERMINAL=morse" (uses the system speaker. Only for really 
desperate debugging :) )




OpenPGP_signature.asc
Description: OpenPGP digital signature

Re: Does "LC_ALL=C" work on all shells?

[tomas]

On Fri, Feb 16, 2024 at 11:44:21AM -0500, Greg Wooledge wrote:
> On Fri, Feb 16, 2024 at 05:35:04PM +0100, Franco Martelli wrote:
> > It was stated here:
> > https://lists.debian.org/debian-user/2024/02/msg00592.html
> 
> "I think that a recorded session with the output of the commands in
> English is better then a localized session for debugging purposes."
> 
> I have trouble following your reasoning there.  Do you mean that you
> expect they'll hand over the logs to *someone else* to debug, instead
> of reading it themselves?  I mean, that may be true, but you certainly
> didn't state it.  That leaves me needing to guess.

There's also looking up errors on a search engine. English texts do
have a higher probability of a meaningful hit.

But yes, it's complicated, to say the least (a case in point: my main
(not my native) language is currently German, but I vastly prefer
error messages in English).

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: permissions on /dev/tty

[Joe Pfeiffer]

Joe Pfeiffer  writes:

> I have a laptop with a recent Debian install, which seems to have
> incorrect permissions on /dev/tty
>
> crw--w 1 root tty 5, 0 Feb 16 08:51 /dev/tty

Ah, found it. I somehow had a
/etc/systemd/system/getty.target.wants/getty@tty.service
file.

Found it looking through log files and seeing it had failed to
launch.

Re: Stretch vers Bullseye - Probleme lors du apt full-upgrade

[Gilles Mocellin]

Le vendredi 16 février 2024, 18:43:58 CET Hugues MORIN-TRENEULE a écrit :
> Salut
> 
> Merci pour tous ces conseils, je garde ça précieusement pour les prochains
> upgrade car  j'ai l'intention d'upgrader jusqu'à la dernière version stable.
> 
> Sinon, j'ai lancé le processus d'upgrade comme nous en avons parlé mais
> malheureusement avant d'avoir reçu les conseils de Gilles et Alain.
> Voila un petit compte rendu de ce que j'ai fait et des messages que j'ai eu:
> 
> - ps ne m'a pas afficher de processus apt en train de tourner donc pas
> besoin du killall.
> Je n'ai pas non plus exécuté de dpkg-reconfigure (ni meme dpkg --configure
> -a) qui m'a semblé n'être nécessaire que dans le cas ou il y aurait eu un
> processus apt dans le ps
> J'espère que je n'ai pas créé un probleme en ne le faisant pas.
> 
> - J'ai ensuite exécuté apt upgrade --without-new-pkgs
> qui m'a retourné un message d'erreur me signalant que des paquets liés au
> noyau linux-image-4.19.0-25-amd64 était absent
> et d'exécuter apt --fix-broken install pour résoudre le probleme.
> 
> - J'ai donc exécuté apt --fix-broken install, qui semble s'être déroulé
> sans incident.
> 
> - J'ai RE-exécuté apt upgrade --without-new-pkgs qui m'a listé les paquets
> qui ne sont plus nécessaires.
> Je les ai retirés avec apt autoremove comme le conseille la commande
> précédente.
> 
> Jusque là, tout semble OK :)

En effet !
 
> Normalement afin de finir mon upgrade il ne manque plus que le apt
> full-upgrade à exécuter.
> 
> Je me suis arrêté là pour l'instant, par manque de temps pour aller plus
> loin
> Je n'ai pas encore éteint (ou rebooter) la machine.
> 
> Est ce que mon oubli du dpkg -configure pourrait engendrer un probleme? et
> si oui comment le corriger avant de passer au full upgrade?
 
Non, les commandes apt que tu as passé auraient dit qu'il y avait un problème 
et qu'il fallait finir les opérations dpkg arrêtées en cours (par le dpkg --
configure -a).

Tu peux y aller.

> Bonne soirée
> Hugues

Bonne soirée, tu y es presque !

GRUB lost graphical terminal mode

[Borden]

For a couple weeks now, I can't use graphical terminal in my GRUB 
configuration. Setting `GRUB_TERMINAL=console` works fine. With that line 
commented out, (thus using default settings), I get a blank screen on boot, 5 
second timeout, then normal boot.

Curiously, keyboard commands work normally. Specifically, I'm on multi-boot 
system, so I can boot into Windows by pressing the down arrow the correct 
number of times and pressing Enter. So I suspect that GRUB is either sending to 
the wrong video output or GRUB no longer supports my video card.

Any way I can troubleshoot without setting set debug=all?

Re: Stretch vers Bullseye - Probleme lors du apt full-upgrade

[Hugues MORIN-TRENEULE]

Salut

Merci pour tous ces conseils, je garde ça précieusement pour les prochains
upgrade car  j'ai l'intention d'upgrader jusqu'à la dernière version stable.

Sinon, j'ai lancé le processus d'upgrade comme nous en avons parlé mais
malheureusement avant d'avoir reçu les conseils de Gilles et Alain.
Voila un petit compte rendu de ce que j'ai fait et des messages que j'ai eu:

- ps ne m'a pas afficher de processus apt en train de tourner donc pas
besoin du killall.
Je n'ai pas non plus exécuté de dpkg-reconfigure (ni meme dpkg --configure
-a) qui m'a semblé n'être nécessaire que dans le cas ou il y aurait eu un
processus apt dans le ps
J'espère que je n'ai pas créé un probleme en ne le faisant pas.

- J'ai ensuite exécuté apt upgrade --without-new-pkgs
qui m'a retourné un message d'erreur me signalant que des paquets liés au
noyau linux-image-4.19.0-25-amd64 était absent
et d'exécuter apt --fix-broken install pour résoudre le probleme.

- J'ai donc exécuté apt --fix-broken install, qui semble s'être déroulé
sans incident.

- J'ai RE-exécuté apt upgrade --without-new-pkgs qui m'a listé les paquets
qui ne sont plus nécessaires.
Je les ai retirés avec apt autoremove comme le conseille la commande
précédente.

Jusque là, tout semble OK :)

Normalement afin de finir mon upgrade il ne manque plus que le apt
full-upgrade à exécuter.

Je me suis arrêté là pour l'instant, par manque de temps pour aller plus
loin
Je n'ai pas encore éteint (ou rebooter) la machine.

Est ce que mon oubli du dpkg -configure pourrait engendrer un probleme? et
si oui comment le corriger avant de passer au full upgrade?


Bonne soirée
Hugues





Le mar. 13 févr. 2024 à 17:31, zithro  a écrit :

> On 13 Feb 2024 10:31, Hugues MORIN-TRENEULE wrote:
> > @zithro / Cyril: je me suis trompé en écrivant, j'upgrade de bien de
> >  Stretch à Buster ;-)
>
> Tant mieux ;)
> C'est toujours bon de préciser pour les futurs lecteurs !
>
>
> > Donc je récapitule pour voir si j'ai bien compris: - ps pour trouver
> > le PID d'apt - killall -9 "PID d'apt" - dpkg-reconfigure - apt
> > upgrade --without-new-pkgs (=> Cette commande met à niveau les
> > paquets qui peuvent l'être sans entraîner l'installation ou la
> > suppression d'autres paquets. ) - apt full-upgrade
> >
> > Ça vous semble correct ?
>
> Oui ça devrait aller, lis bien les docs officiels de MàJ, à chaque
> update majeur de version il y a des particularités (paquets obsolètes,
> etc).
> Quand tu changes les sources, pense à enlever les backports, si tu les
> utilises.
> Si c'est une install avec GUI, essaie de faire l'update depuis
> tty1/tty6, pas depuis X (vt7). Le serveur X -peut- redémarrer et te
> perdre la fenêtre d'upgrade (donc le stopper en plein milieu).
> Il est aussi recommandé d'utiliser "screen", pour parer à ce genre de
> problèmes (lancer avec "screen -R upgrade", et récup avec la même
> commande si ça coupe. Tu peux changer "upgrade" en hugues ou w/e).
> La commande "script" est aussi recommandée, pour tout enregistrer.
>
> J'ajoute quelques commandes qui peuvent être utiles avant de lancer
> l'upgrade. Elles sont aussi  recommandées dans les "Release Notes", afin
> de partir sur une base saine avant l'upgrade.
> Certaines commandes sont équivalentes et donneront le même résultat.
> Quant à quoi faire du résultat ... ça dépend ! Pas de recette miracle.
> Mais ce n'est ni parce que tu n'as rien, ni parce que tu as des
> résultats que c'est un gage de réussite (:
>
> # lister les paquets obsolètes et "not-from-Debian"
> apt list '~o'
> # les purger - ATTENTION, purge=remove conf files
>  apt purge '~o'
> apt list '?narrow(?installed, ?not(?origin(Debian)))'
> apt-forktracer | sort
>
> # vérif les paquets, surtout ceux en "hold"
> dpkg --audit
> dpkg --get-selections | grep 'hold$'
> apt-mark showhold
>
> # liens symboliques dans /etc qui pointent nulle part
> symlinks -r /etc | grep dangling
>
> # trouver les anciens fichiers config (ie. de paquets supprimés ou
> d'anciennes versions de paquets mis à jour)
> # (cette commande est affichée sur 2 lignes dans ce mail)
> find /etc -name '*.dpkg-*' -o -name '*.ucf-*' -o -name '*.merge-error'
> -o -name '*.old*'
> # equivalent
> dpkg -l | grep ^rc
> # les purger - ATTENTION, perte de données
>  apt purge $(dpkg -l | awk '/^rc/ { print $2 }')
>
> Sinon, quelques paquets à installer avant l'upgrade si t'aimes bien tout
> check :
> deborphan
> apt-forktracer
> apt-listbugs
> apt-listchanges
>
> Bref, tu as presque toutes les armes, "pick your poison" comme disent
> les ricains !
> Perso, je préfère mettre toutes les chances de mon côté donc je lance
> toutes les commandes sur toutes les machines.
> Certains risquent de dire que c'est too much. A toi de voir ;)
>
> --
> ++
> zithro / Cyril
>
>

Re: What sets LC_TIME?

[David Wright]

On Fri 16 Feb 2024 at 09:12:24 (-0500), Greg Wooledge wrote:
> On Fri, Feb 16, 2024 at 03:34:12PM +0200, Anssi Saari wrote:
> > Yah. It was ssh passing through all that. On serial console, locale
> > settings are as expected:
> > 
> > $ locale
> > LANG=en_US.UTF-8
> > LANGUAGE=en_US:en
> > LC_CTYPE="en_US.UTF-8"
> > LC_NUMERIC="en_US.UTF-8"
> > LC_TIME="en_US.UTF-8"
> [...]
> 
> Well then, that just changes the mystery from "happens on the Debian
> system I ssh into" to "happens on my ssh client".  For some reason,
> your ssh client has all of those LC_* variables set in its environment,
> which is still quite unusual.

Could something weird here do that?

  $ grep LC /etc/ssh/*g
  /etc/ssh/ssh_config:SendEnv LANG LC_*
  /etc/ssh/sshd_config:AcceptEnv LANG LC_*
  $ 

Perhaps the OP's also sets SetEnv … in the client's config?

Cheers,
David.

permissions on /dev/tty

[Joe Pfeiffer]

I have a laptop with a recent Debian install, which seems to have
incorrect permissions on /dev/tty

crw--w 1 root tty 5, 0 Feb 16 08:51 /dev/tty

/lib/udev/rules.d/50-udev-default.rules contains the usual

SUBSYSTEM=="tty", KERNEL=="tty", GROUP="tty", MODE="0666"

More strangely, udevadm info /dev/tty contains (among other things, of course)

E: DEVPATH=/devices/virtual/tty/tty
E: DEVNAME=/dev/tty
E: DEVMODE=0666

Does anyone have any idea what might be changing the permissions?  Or
have some ideas on how I might look for it?

Thanks,

Re: Does "LC_ALL=C" work on all shells?

[Greg Wooledge]

On Fri, Feb 16, 2024 at 05:35:04PM +0100, Franco Martelli wrote:
> It was stated here:
> https://lists.debian.org/debian-user/2024/02/msg00592.html

"I think that a recorded session with the output of the commands in
English is better then a localized session for debugging purposes."

I have trouble following your reasoning there.  Do you mean that you
expect they'll hand over the logs to *someone else* to debug, instead
of reading it themselves?  I mean, that may be true, but you certainly
didn't state it.  That leaves me needing to guess.

If my guess is correct, then I don't support the plan to modify the
Debian documentation to suggest that everyone log their dist-upgrades
in English "because if something goes wrong you will probably ask for
help from an English speaker".  There are way too many layers of
assumptions there.


On Fri, Feb 16, 2024 at 05:35:11PM +0100, Franco Martelli wrote:
> however users that have set LC_ALL variable into .bashrc I suppose already
> know what are they doing.

No.  No, they do not.  They may *think* they do.  They do not.

Re: Does "LC_ALL=C" work on all shells?

[Franco Martelli]

On 16/02/24 at 13:17, Greg Wooledge wrote:

On Fri, Feb 16, 2024 at 09:13:40AM +0200, Teemu Likonen wrote:

In my opinion it's often too much to set LC_ALL=C because it changes
charset to ASCII (LC_CTYPE).


It depends on what you're doing, of course.  If the purpose is to
normalize error messages so that you can report your issue to an
English-only mailing list, and if LC_ALL=C doesn't mangle the
output beyond recognition, then it might be good enough.

The OP of this thread seemed to have a goal of altering Debian
documentation to have *everyone* performing a dist-upgrade run
their dist-upgrade sessions under LC_ALL=C for reasons that I
can't remember (or which weren't stated).  I'm uncertain what the
larger goal is there -- many of these users would probably have
difficulty reading their own session logs afterward.



It was stated here:
https://lists.debian.org/debian-user/2024/02/msg00592.html

--
Franco Martelli

Re: cruft report: The new kid on the block

[Sven Joachim]

On 2024-02-16 09:06 -0500, Gremlin wrote:

> cruft report: Fri Feb 16 08:54:01 2024
>  missing: dpkg 
> /etc/network/if-post-down.d/wireless-tools
> /etc/network/if-pre-up.d/ethtool
> /etc/network/if-pre-up.d/wireless-tools
> /etc/network/if-up.d/ethtool
>
> wireless-tools and ethtool owns these files but are missing from the
> system, ie MIA

That is not supposed to happen, but it is hard to tell who removed these
files, when and why.  The etckeeper tool can help to track down such
changes.

> Doing a reinstall does not recreate them, why?

Because these files are conffiles, and the admin is free to edit or
delete them; dpkg will respect these changes and not reinstate missing
conffiles, unless given the "--force-confmiss" option.

Cheers,
   Sven

Re: f3tools vs Silicon Power 4T drive

[gene heskett]

On 2/16/24 07:46, debian-u...@howorth.org.uk wrote:

gene heskett  wrote:

On 2/15/24 15:45, Andy Smith wrote:


MD RAID isn't the only way to achieve redundancy. You also haven't
explained why you need LVM. Depending on your needs, maybe a
filesystem with redundancy and volume management features in it
would be better. Like btrfs or zfs.

May I miss-understood the wiki, xfs is stated as not being complete
for linux, a zfx is I think commercial?
Can you update that?


Sorry, which wiki page do you think says XFS is not complete?

.
I wasn't awake enough to bookmark it. I'm not done with wiki yet, if I 
run across it again I'll post the link.


Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis

Re: Package Identification Assistance

[Ralph Aichinger]

On Thu, 2024-02-15 at 20:33 -0500, Neal Heinecke wrote:
> I need to identify the package responsible for creating the software
> sources window. There is a minor bug/typo where the first tab reads
> "Ubuntu Software"

This could be synaptic?

https://help.ubuntu.com/community/SynapticHowto

Does the program have an "About" menu entry?

/ralph

Re: f3tools vs Silicon Power 4T drive

[Andy Smith]

Hi,

On Thu, Feb 15, 2024 at 08:44:26PM -0500, gene heskett wrote:
> On 2/15/24 15:45, Andy Smith wrote:
> > MD RAID isn't the only way to achieve redundancy. You also haven't
> > explained why you need LVM. Depending on your needs, maybe a
> > filesystem with redundancy and volume management features in it
> > would be better. Like btrfs or zfs.
> May I miss-understood the wiki, xfs is stated as not being complete for
> linux, a zfx is I think commercial?
> Can you update that?

I'd rather not try to explain XFS and ZFS to you when it's not even
clear what you're trying to achieve. In all likelihood you will not
need to use either XFS or ZFS.

Also we can't correct a wiki article without knowing what it is…

> the gui access delay (30+ seconds) problems I have did NOT go away
> when I moved /home off the raid to another SSD

More evidence that those problems had nothing to do with RAID or the
storage devices you used in your RAID, but is something broken in
your desktop software setup. Unfortunately I have no idea how to
debug that.

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: shred bug? [was: Unidentified subject!]

[Michael Stone]

On Sun, Feb 11, 2024 at 08:02:12AM +0100, to...@tuxteam.de wrote:

What Thomas was trying to do is to get a cheap, fast random number
generator. Shred seems to have such.


You're better off with /dev/urandom, it's much easier to understand what 
it's trying to do, vs the rather baroque logic in shred. In fact, 
there's nothing in shred's documenation AFAICT that suggests it should 
be used as a random number generator. For pure speed, playing games with 
openssl enc and /dev/zero will generally win. If speed doesn't matter, 
we're back to /dev/urandom as the simplest and most direct solution.


FWIW, the main use for shred in 2024 is: to be there so someone's old 
script doesn't break. There's basically no good use case for it, and it 
probably shouldn't have gotten into coreutils in the first place. The 
multipass pattern stuff is cargo-cult voodoo--a single overwrite with 
zeros will be as effective as anything else--and on modern 
storage/filesystems there's a good chance your overwrite won't overwrite 
anything anyway. Probably the right answer is a kernel facility 
(userspace can't guarantee anything). If you're really sure that 
overwrites work on your system, `shred -n0 -z` will be the fastest way 
to do that. The docs say don't do that because SSDs might optimize that 
away, but SSDs probably aren't overwriting anything anyway (also 
mentioned in the docs). ¯\_(ツ)_/¯

Re: f3tools vs Silicon Power 4T drive

[Andy Smith]

Hi,

On Fri, Feb 16, 2024 at 01:32:26AM -0500, gene heskett wrote:
> On 2/15/24 16:20, David Wright wrote:
> ># gdisk -l /dev/sdz
> >GPT fdisk (gdisk) version 1.0.3
> > 
> >Partition table scan:
> >  MBR: protective
> >  BSD: not present
> >  APM: not present
> >  GPT: present
> > 
> >Found valid GPT with protective MBR; using GPT.
> >Disk /dev/sdb: 3907029168 sectors, 1.8 TiB
> >Model: Desktop
> >Sector size (logical/physical): 512/512 bytes
> >Disk identifier (GUID): A1093790-9A1A-4A7E-A807-B9CC6F7CF77E
> >Partition table holds up to 128 entries
> >Main partition table begins at sector 2 and ends at sector 33
> >First usable sector is 34, last usable sector is 3907029134
> >Partitions will be aligned on 2048-sector boundaries
> >Total free space is 2014 sectors (1007.0 KiB)
> > 
> >Number  Start (sector)End (sector)  Size   Code  Name
> >   12048  3907029134   1.8 TiB 8300  Lulu01
> >#
> > .
> And this "partition" name survives?

No, because it's a filesystem label for the ext4 fs created on
/dev/sdz1. If sdz1 is turned into an LVM Physical Volume, there
won't be an ext4 filesystem on it any more. If sdz1 is turned into a
member of an MD array, there won't be an ext4 filesystem on it any
more. The labels go with the filesystem.

> and can be unique?

I don't know what that means to you or why it is useful.

> and can be used in a mount cmd?

Once the RAID and/or LVM is set up and a filesystem put on it, that
filesystem can be mounted by label just like any filesystem can, but
that filesystem may have multiple devices underneath it owing to the
fact that it's on RAID and/or LVM, so there is no information you
can put in its label that will tell you anything about those
underlying devices.

> if all 3 questions above can be answered with a yes is the answer
> I've been trying to squeeze out all along.

You've not yet been clear about what you want, but from what little
information you have provided you've been told multiple times by
multiple people that filesystem labels won't help.

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: Package Identification Assistance

[Max Nikulin]

On 16/02/2024 21:14, Greg Wooledge wrote:

On Fri, Feb 16, 2024 at 09:05:28PM +0700, Max Nikulin wrote:

I suspect that program name is the question. If "ps awf" gives no clue then
perhaps the following may help (untested):

https://unix.stackexchange.com/questions/362731/how-to-identify-window-by-clicking-in-wayland


I would also point out that this is a Debian mailing list, not an Ubuntu
mailing list, and therefore the people here don't know anything about
Ubuntu systems (generally).


https://codesearch.debian.net tells that "Ubuntu Software" occurs in 
translation files for gnome-software and software-properties packages.

Re: f3tools vs Silicon Power 4T drive

[Andy Smith]

Hello,

On Fri, Feb 16, 2024 at 01:16:59AM -0500, gene heskett wrote:
> On 2/15/24 16:20, Andy Smith wrote:
> > Suppose you have the MD array /dev/md42. What are you conceptually
> > wanting to do with that in relation to labels of some kind? What
> > information is it that you want?
> > 
> > Support you have LVM logical volume /dev/myvg/mylv. What are you
> > conceptually wanting to do with that in relation to labels of some
> > kind? What information is it that you want?
> > 
> I want to know with absolute certainty, with of the 4 drives in that raid10,
> actually has a belly ache. When it has a belly ache.

So this is an example of you moving the goal posts. You started off
by saying you needed to identify something just from the array
device name, but now you say you need to identify which drive in the
array has a problem (exact problem not specified).

The /proc/mdstats file shows all the devices that are in all the MD
arrays. Any time the kernel has problems with a device it logs the
name of the actual device (not the array etc.) in the system log. If
the problems are bad enough then the MD driver notices and removes
the device from the array.

This is normal-looking content of /proc/mdstat:

$ cat /proc/mdstat 
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] 
[raid10] 
md1 : active raid1 sda3[1] nvme0n1p3[0]
  243316736 blocks super 1.2 [2/2] [UU]
  bitmap: 1/2 pages [4KB], 65536KB chunk

Where it says [UU] it would say [_U] or [U_] if one of those devices
had been removed, and in the list of devices the one that's failed
would have an (F) after it.

But I'm fairly sure that in all your posts about your RAID-10 people
have been through this with you multiple times, so this must not
actually be the information that you are after.

Furthermore I do not understand how your idea of labelling drives
(or partitions or filesystems) would ever give you this information
even if it had worked.

If you mean that you have system logs that say for example that
sda1 has problems, and you want to find out what sda1 actually is,
well I already showed you one way: by looking in /dev/disk/by-id/.
There's also "smartctl -i /dev/sda", and others have posted other
ways.

If you don't mean that, then tell us what actual information you are
starting from, and what you hope to get from there. "My array has
problems, how do I find the problem drive within it" is too vague
because we don't know what "my array has problems" actually means.

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: Package Identification Assistance

[The Wanderer]

On 2024-02-16 at 09:14, Greg Wooledge wrote:

>>> On Thu, 15 Feb 2024 20:33:16 -0500 Neal Heinecke wrote:
>>> 
 I need to identify the package responsible for creating the
 software sources window. There is a minor bug/typo where the
 first tab reads "Ubuntu Software"

> I would also point out that this is a Debian mailing list, not an
> Ubuntu mailing list, and therefore the people here don't know
> anything about Ubuntu systems (generally).
> 
> Maybe this program is normal and common on Ubuntu.  If that's the
> case, then asking on an Ubuntu mailing list or web forum would
> probably have got a useful reply immediately, whereas all *we* can do
> is scratch our heads and toss out random guesses.

I could be on the wrong track, but I parsed the original post as
reporting that a program on Debian identifies itself as being connected
to Ubuntu, and that this would constitute a bug, and as wanting to
identify the package responsible for that program *so as to be able to
report that bug so that it can be fixed*.

If that's correct, then the original question was "how can I identify
the package on my Debian system which contains the program which is
misbehaving in this way?", which would seem to be perfectly fine as a
question for debian-user.

That said, I don't have any idea of suggestions to offer, without more
information which the original poster has not provided. To start with,
I'd want to know: what steps is it which cause the window which displays
this improperly-titled tab to open?

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: Package Identification Assistance

[Greg Wooledge]

On Fri, Feb 16, 2024 at 09:05:28PM +0700, Max Nikulin wrote:
> On 16/02/2024 12:16, Charles Curley wrote:
> > On Thu, 15 Feb 2024 20:33:16 -0500
> > Neal Heinecke wrote:
> > 
> > > I need to identify the package responsible for creating the software
> > > sources window. There is a minor bug/typo where the first tab reads
> > > "Ubuntu Software"
> > 
> > I have no idea what a "software sources window" is. Do you know the
> > name of the program?
> I suspect that program name is the question. If "ps awf" gives no clue then
> perhaps the following may help (untested):
> 
> https://unix.stackexchange.com/questions/362731/how-to-identify-window-by-clicking-in-wayland

I would also point out that this is a Debian mailing list, not an Ubuntu
mailing list, and therefore the people here don't know anything about
Ubuntu systems (generally).

Maybe this program is normal and common on Ubuntu.  If that's the case,
then asking on an Ubuntu mailing list or web forum would probably have
got a useful reply immediately, whereas all *we* can do is scratch our
heads and toss out random guesses.

Re: What sets LC_TIME?

[Greg Wooledge]

On Fri, Feb 16, 2024 at 03:34:12PM +0200, Anssi Saari wrote:
> Yah. It was ssh passing through all that. On serial console, locale
> settings are as expected:
> 
> $ locale
> LANG=en_US.UTF-8
> LANGUAGE=en_US:en
> LC_CTYPE="en_US.UTF-8"
> LC_NUMERIC="en_US.UTF-8"
> LC_TIME="en_US.UTF-8"
[...]

Well then, that just changes the mystery from "happens on the Debian
system I ssh into" to "happens on my ssh client".  For some reason,
your ssh client has all of those LC_* variables set in its environment,
which is still quite unusual.

cruft report: The new kid on the block

[Gremlin]

cruft report: Fri Feb 16 08:54:01 2024
 missing: dpkg 
/etc/network/if-post-down.d/wireless-tools
/etc/network/if-pre-up.d/ethtool
/etc/network/if-pre-up.d/wireless-tools
/etc/network/if-up.d/ethtool

wireless-tools and ethtool owns these files but are missing from the 
system, ie MIA


cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/;
SUPPORT_URL="https://www.debian.org/support;
BUG_REPORT_URL="https://bugs.debian.org/;

ls /etc/net*
/etc/netconfig  /etc/networks

/etc/network:
if-down.d  if-post-down.d  if-pre-up.d  if-up.d  interfaces
scott@scott:~/Installation $ ls -Rhal /etc/net*
-rw-r--r-- 1 root root  767 Aug 11  2022 /etc/netconfig
-rw-r--r-- 1 root root   60 Dec  4 23:36 /etc/networks

/etc/network:
total 36K
drwxr-xr-x   6 root root 4.0K Feb 16 08:53 .
drwxr-xr-x 119 root root  12K Feb 16 07:04 ..
drwxr-xr-x   2 root root 4.0K Feb 16 08:53 if-down.d
drwxr-xr-x   2 root root 4.0K Feb 16 08:50 if-post-down.d
drwxr-xr-x   2 root root 4.0K Feb 16 08:52 if-pre-up.d
drwxr-xr-x   2 root root 4.0K Feb 16 08:53 if-up.d
-rw-r--r--   1 root root  134 Feb 16 08:53 interfaces

/etc/network/if-down.d:
total 8.0K
drwxr-xr-x 2 root root 4.0K Feb 16 08:53 .
drwxr-xr-x 6 root root 4.0K Feb 16 08:53 ..
lrwxrwxrwx 1 root root   32 Feb 24  2023 wpasupplicant -> 
../../wpa_supplicant/ifupdown.sh


/etc/network/if-post-down.d:
total 8.0K
drwxr-xr-x 2 root root 4.0K Feb 16 08:50 .
drwxr-xr-x 6 root root 4.0K Feb 16 08:53 ..
lrwxrwxrwx 1 root root   32 Feb 24  2023 wpasupplicant -> 
../../wpa_supplicant/ifupdown.sh


/etc/network/if-pre-up.d:
total 8.0K
drwxr-xr-x 2 root root 4.0K Feb 16 08:52 .
drwxr-xr-x 6 root root 4.0K Feb 16 08:53 ..
lrwxrwxrwx 1 root root   32 Feb 24  2023 wpasupplicant -> 
../../wpa_supplicant/ifupdown.sh


/etc/network/if-up.d:
total 8.0K
drwxr-xr-x 2 root root 4.0K Feb 16 08:53 .
drwxr-xr-x 6 root root 4.0K Feb 16 08:53 ..
lrwxrwxrwx 1 root root   32 Feb 24  2023 wpasupplicant -> 
../../wpa_supplicant/ifupdown.sh


apt-file show ethtool
ethtool: /etc/network/if-pre-up.d/ethtool
ethtool: /etc/network/if-up.d/ethtool
ethtool: /sbin/ethtool
ethtool: /usr/share/bash-completion/completions/ethtool
ethtool: /usr/share/doc/ethtool/AUTHORS
ethtool: /usr/share/doc/ethtool/NEWS.gz
ethtool: /usr/share/doc/ethtool/README
ethtool: /usr/share/doc/ethtool/README.Debian
ethtool: /usr/share/doc/ethtool/changelog.Debian.gz
ethtool: /usr/share/doc/ethtool/copyright
ethtool: /usr/share/man/man8/ethtool.8.gz


Doing a reinstall does not recreate them, why?

Re: Package Identification Assistance

[Max Nikulin]

On 16/02/2024 12:16, Charles Curley wrote:

On Thu, 15 Feb 2024 20:33:16 -0500
Neal Heinecke wrote:


I need to identify the package responsible for creating the software
sources window. There is a minor bug/typo where the first tab reads
"Ubuntu Software"


I have no idea what a "software sources window" is. Do you know the
name of the program?
I suspect that program name is the question. If "ps awf" gives no clue 
then perhaps the following may help (untested):


https://unix.stackexchange.com/questions/362731/how-to-identify-window-by-clicking-in-wayland

Re: Package Identification Assistance

[Cindy Sue Causey]

On 2/16/24, Charles Curley  wrote:
> On Thu, 15 Feb 2024 20:33:16 -0500
> Neal Heinecke  wrote:
>
>> I need to identify the package responsible for creating the software
>> sources window. There is a minor bug/typo where the first tab reads
>> "Ubuntu Software"
>
> I have no idea what a "software sources window" is. Do you know the
> name of the program? Often the name of the program is also the name of
> the package.
>
> Apt-file is a useful tool here.


I a-sumed it was about something like maybe aptitude.. which just
generated approximately 1,320 "apt-file find" results. Kind of a nice
little "the more you know" treasure hunt for the curious, actually..

Cindy :)
-- 
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *

Re: What sets LC_TIME?

[Anssi Saari]

Greg Wooledge  writes:

> On Fri, Feb 16, 2024 at 10:24:07AM +0200, Anssi Saari wrote:
>> With the recent LC_ALL thread, I noticed I have LC_TIME set by
>> mysterious means on at least two headless systems, for example:
>> 
>> $ locale
>> LANG=en_US.UTF-8
>> LANGUAGE=
>> LC_CTYPE=en_US.utf8
>> LC_NUMERIC=en_US.utf8
>> LC_TIME=en_DK.utf8
>> LC_COLLATE=en_US.utf8
>> LC_MONETARY=en_US.utf8
>> LC_MESSAGES=en_US.utf8
>> LC_PAPER=en_US.utf8
>> LC_NAME=en_US.utf8
>> LC_ADDRESS=en_US.utf8
>> LC_TELEPHONE=en_US.utf8
>> LC_MEASUREMENT=en_US.utf8
>> LC_IDENTIFICATION=en_US.utf8
>> LC_ALL=
>
> This is *extremely* abnormal locale output.  Here's mine:

Yah. It was ssh passing through all that. On serial console, locale
settings are as expected:

$ locale
LANG=en_US.UTF-8
LANGUAGE=en_US:en
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

Re: Package Identification Assistance

[Stefan Monnier]

> I need to identify the package responsible for creating the software
> sources window. There is a minor bug/typo where the first tab reads
> "Ubuntu Software"

If all else fails, you can always try something like:

find / -mount -type f -print0 | xargs -0 grep -al "Ubuntu Software"

to find files that contain the string "Ubuntu Software".
Then pass those file names to `dpkg -S`.


Stefan

Re: f3tools vs Silicon Power 4T drive

[debian-user]

gene heskett  wrote:
> On 2/15/24 15:45, Andy Smith wrote:
> 
> > MD RAID isn't the only way to achieve redundancy. You also haven't
> > explained why you need LVM. Depending on your needs, maybe a
> > filesystem with redundancy and volume management features in it
> > would be better. Like btrfs or zfs.  
> May I miss-understood the wiki, xfs is stated as not being complete
> for linux, a zfx is I think commercial?
> Can you update that?

Sorry, which wiki page do you think says XFS is not complete?

Re: What sets LC_TIME?

[Greg Wooledge]

On Fri, Feb 16, 2024 at 10:24:07AM +0200, Anssi Saari wrote:
> With the recent LC_ALL thread, I noticed I have LC_TIME set by
> mysterious means on at least two headless systems, for example:
> 
> $ locale
> LANG=en_US.UTF-8
> LANGUAGE=
> LC_CTYPE=en_US.utf8
> LC_NUMERIC=en_US.utf8
> LC_TIME=en_DK.utf8
> LC_COLLATE=en_US.utf8
> LC_MONETARY=en_US.utf8
> LC_MESSAGES=en_US.utf8
> LC_PAPER=en_US.utf8
> LC_NAME=en_US.utf8
> LC_ADDRESS=en_US.utf8
> LC_TELEPHONE=en_US.utf8
> LC_MEASUREMENT=en_US.utf8
> LC_IDENTIFICATION=en_US.utf8
> LC_ALL=

This is *extremely* abnormal locale output.  Here's mine:

unicorn:~$ locale
LANG=en_US.utf8
LANGUAGE=
LC_CTYPE="en_US.utf8"
LC_NUMERIC="en_US.utf8"
LC_TIME=C
LC_COLLATE="en_US.utf8"
LC_MONETARY="en_US.utf8"
LC_MESSAGES="en_US.utf8"
LC_PAPER="en_US.utf8"
LC_NAME="en_US.utf8"
LC_ADDRESS="en_US.utf8"
LC_TELEPHONE="en_US.utf8"
LC_MEASUREMENT="en_US.utf8"
LC_IDENTIFICATION="en_US.utf8"
LC_ALL=

Do you see what's different?  The double quotes are meaningful here.
A value that's printed in double quotes is not actually set -- it's
deduced from LANG.  In my output, the only values that are actually
set are LANG and LC_TIME.

In yours, *every* variable is set (except LANGUAGE and LC_ALL).

> LC_TIME ends up with en_DK.utf8. It's what I usually want so I've
> probably set this up and possibly I did it in the Debian installer but
> where does it come from? /etc/default/locale has just LANG=en_US.UTF-8
> 
> find /etc /home/as -type f -print0 -follow|xargs -0 grep -e LC_TIME -e en_DK
> 
> does find some matches, in /etc/locale.gen as expected and in some
> binary files but not in any relevant config file. Come to think of it,
> is this actually hidden inside the initrd somehow?

I can't imagine how the initrd would be related.

My first suspicion would be your desktop environment, if you're running
one.  Who knows what those things do.

If you login on a text console (Ctrl-Alt-F2 for example), do you still
get these same locale values?  How about "ssh localhost" (if an ssh
server is installed)?  If those differ from what you see in your desktop
environment, then it's a strong indicator the DE is doing something.

Re: Does "LC_ALL=C" work on all shells?

[Greg Wooledge]

On Fri, Feb 16, 2024 at 09:13:40AM +0200, Teemu Likonen wrote:
> In my opinion it's often too much to set LC_ALL=C because it changes
> charset to ASCII (LC_CTYPE).

It depends on what you're doing, of course.  If the purpose is to
normalize error messages so that you can report your issue to an
English-only mailing list, and if LC_ALL=C doesn't mangle the
output beyond recognition, then it might be good enough.

The OP of this thread seemed to have a goal of altering Debian
documentation to have *everyone* performing a dist-upgrade run
their dist-upgrade sessions under LC_ALL=C for reasons that I
can't remember (or which weren't stated).  I'm uncertain what the
larger goal is there -- many of these users would probably have
difficulty reading their own session logs afterward.

Re: perte clavier suite à retour de veille depuis bookworm-12.5

[Jacques]

Bonjour Étienne,

Le 15/02/2024 à 20:25, Étienne Mollier a écrit :

Le comportement ne me paraît pas plus normal, quoiqu'il soit un
peu différent.  Je pense que ça vaudrait toujours le coup de le
signaler aux développeurs noyau.  Par ailleurs, la mitigation
appliquée pourrait les intéresser :


Je viens de faire un rapport de bug, il porte le numéro 1064041.

Encore un grand merci pour tes conseils,

Jacques

Re: SMART Uncorrectable_Error_Cnt rising - should I be worried?

[David Christensen]

On 2/15/24 07:41, The Wanderer wrote:

On 2024-02-15 at 03:09, David Christensen wrote:

On 2/14/24 18:54, The Wanderer wrote:

On 2024-01-09 at 14:22, The Wanderer wrote:

On 2024-01-09 at 14:01, Michael Kjörling wrote:

On 9 Jan 2024 13:25 -0500, from The Wanderer

I've ordered a 22TB external drive


Make?  Model?  How it is interfaced to your computer?


It's a WD Elements 20TB drive (I'm not sure where I got the 22 from);
the back of the case has the part number WDBWLG0200HBK-X8 (or possibly
-XB, the font is kind of ambiguous). The connection, per the packaging
label, is USB-3.



Okay.


STFW it seems that drive uses CMR, which is good:

https://nascompares.com/answer/list-of-wd-cmr-and-smr-hard-drives-hdd/



The big change of plans in the middle of my month-plus process was the
decision to replace the entire 8-drive array with a 6-drive array, and
the reason for that was because the 8-drive array left me with no open
SATA ports to be able to connect spare drives in order to do drive
replacements without needing to rebuild the whole shaboozle.



Having spare drive bays for RAID drive replacement is smart.



If you have a processor, memory, PCIe slot, and HBA to match those
SSD's, the performance of those SSD's should be very nice.


The CPU is a Ryxen 5 5600X. The RAM is G-Skill DDR4 2666MHz, in two 32GB
DIMMs. I don't know how to assess PCIe slots and HBA, but the
motherboard is an Asus ROG Crosshair VIII Dark Hero, which I think was
the top-of-the-line enthusiast motherboard (with the port set my
criteria called for) the year I built this machine.

I'm pretty sure my performance bottleneck for most things is the CPU (or
the GPU, where that comes into play, which here it doesn't);
storage-wise this seems so far to be at least as fast as what I had
before, but it's hard to tell if it's faster.



It would not surprise me if the Intel D3-S4510 server drives are 
somewhat slower than the Samsung EVO 870 desktop drives.  But the Intel 
disks are designed to pull a heavy load all day for years on end.



Do you have a tool to monitor disk throughput and utilization?  I use 
Xfce panel Disk Performance Monitor applets and nmon(1) in a Terminal. 
Those plus CPU and memory monitoring tools should allow you to determine 
if your workload is CPU bound, memory bound, or I/O bound.




The key concept is "data lifetime". (Or alternatively, "destruction
policy".)


I can see that for when you have a tiered backup structure, and are
looking at the lifetimes of each backup copy. For my live system, my
intended data lifetime (outside of caches and data kept in /tmp) is
basically "forever".



I try to group my data in anticipation of backup, etc., requirements. 
When I get it right, disaster preparedness and disaster recovery are easier.




I believe ZFS can do more hard links. (Much more?  Limited by
available storage space?)


I'm not sure, but I'll have to look into that, when I get to the point
of trying to set up that tiered backup.
...

... without [rsnapshot hard link]
deduplication there wouldn't have been enough space on the drive
for more than the single copy, ...


ZFS provides similarly useful results with built-in compression and
de-duplication.


I have the impression that there are risk and/or complexity aspects to
it ...



Of course.  ZFS is sophisticated storage technology.  It looks 
deceptively simple when you are window shopping, but becomes non-trivial 
once you put real data on it, have to live with it 24x7, have to prepare 
for disasters, and have to recover from disasters.  There is a lot to 
learn and "more than enough rope to shoot yourself in the foot".




That sounds like an N-way merge problem ...


It does sound like that, yes. I'm already aware of jdupes, and of a few
other tools (part of the work I already did in getting this far was
rdfind, which is what I used to set up much of the hardlink
deduplication that wound up biting me in the butt), but have not
investigated LVM snapshot - and the idea of trying to script something
like this, without an existing known-safe copy of the data to fall back
on, leaves me *very* nervous.

Figuring out how to be prepared to roll back is the other uncertain and
nervous-making part. In some cases it's straightforward enough, but
doing it at the scale of the size of those copies is at best daunting.



https://html.duckduckgo.com/html?q=lvm%20snapshot%20restore


Use another computer or a VM to learn and practice LVM snapshots and 
restores, then use those skills when doing the N-way merge.




out of the way, shutting down all parts of the system that might be
writing to the affected filesystems, and manually copying out the
final state of the *other* parts of those filesystems via rsync,
bypassing rsnapshot. That was on Saturday the 10th.

Then I grabbed copies of various metadata about the filesystems,
the LVM, and the mdraid config; modified /etc/fstab to not mount
them; deactivated the mdraid, and commented it out of

Using a Python script as a login shell

[Ralph Aichinger]

Hello fellow Debianites!

I want do do a custom CLI for a project, and I am quite happy with the
Python cmd module. Aside from having a practically un-googleable name
it is very nice, and does a lot with very little code. So far, so good.
But:

If I write a Python script with this module, and expose it to the
internet via SSH, will hell break loose? So far I've done the
following:

1. Put my script in /usr/local/bin/turtle (the canonical example in the
docs is something with turtle), you can see the sourcecode of my script
here:

https://pi.h5.or.at/mockturtle.txt

This script does absolutely nothing sensible, you can try it out 
by doing a

ssh -l admin probe.aisg.at 

from a IPv6 capable host (sorry, no IPv4). The password is "admin".

Any and all suggestions on stuff that is stupid and crazy from a
security standpoint in this script are very much appreciated!

2. Then I put /usr/local/bin/turtle in /etc/shells 

3. I added a user "admin" that has /usr/local/bin/turtle as shell

4. I added following stanza to /etc/ssh/sshd_config

Match User admin
X11Forwarding no
AllowTcpForwarding no
ForceCommand /usr/local/bin/turtle

5. In the script I tried to catch the Ctrl-C signal, so the interpreter
does not give out too obvious error messages (that show what is going
on behind the scenes).

Is this enough to harden this setup against escaping into a shell 
or the full python interpreter, to do something nasty? Or is it
completely crazy, because theere is some way to abuse a setup like
this, that I have not found yet?

TIA
Ralph

What sets LC_TIME?

[Anssi Saari]

With the recent LC_ALL thread, I noticed I have LC_TIME set by
mysterious means on at least two headless systems, for example:

$ locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE=en_US.utf8
LC_NUMERIC=en_US.utf8
LC_TIME=en_DK.utf8
LC_COLLATE=en_US.utf8
LC_MONETARY=en_US.utf8
LC_MESSAGES=en_US.utf8
LC_PAPER=en_US.utf8
LC_NAME=en_US.utf8
LC_ADDRESS=en_US.utf8
LC_TELEPHONE=en_US.utf8
LC_MEASUREMENT=en_US.utf8
LC_IDENTIFICATION=en_US.utf8
LC_ALL=

LC_TIME ends up with en_DK.utf8. It's what I usually want so I've
probably set this up and possibly I did it in the Debian installer but
where does it come from? /etc/default/locale has just LANG=en_US.UTF-8

find /etc /home/as -type f -print0 -follow|xargs -0 grep -e LC_TIME -e en_DK

does find some matches, in /etc/locale.gen as expected and in some
binary files but not in any relevant config file. Come to think of it,
is this actually hidden inside the initrd somehow?