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

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

about 10th new install of bullseye

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

Contents

  about 10th new install of bullseye Gene Heskett <gheskett@shentel.net> - 2022-02-18 18:20 +0100
    Re: about 10th new install of bullseye "Andrew M.A. Cater" <amacater@einval.com> - 2022-02-18 20:50 +0100
      Re: about 10th new install of bullseye Andy Smith <andy@strugglers.net> - 2022-02-18 21:20 +0100
        Re: about 10th new install of bullseye Curt <curty@free.fr> - 2022-02-19 16:40 +0100
      Re: about 10th new install of bullseye David Wright <deblis@lionunicorn.co.uk> - 2022-02-19 03:10 +0100
        Re: about 10th new install of bullseye Greg Wooledge <greg@wooledge.org> - 2022-02-19 03:20 +0100
          Re: about 10th new install of bullseye The Wanderer <wanderer@fastmail.fm> - 2022-02-19 03:20 +0100
            Re: about 10th new install of bullseye David Wright <deblis@lionunicorn.co.uk> - 2022-02-19 04:00 +0100
          Re: about 10th new install of bullseye rhkramer@gmail.com - 2022-02-19 05:40 +0100
    Re: about 10th new install of bullseye David Wright <deblis@lionunicorn.co.uk> - 2022-02-18 21:30 +0100
      Re: about 10th new install of bullseye Felix Miata <mrmazda@earthlink.net> - 2022-02-19 01:30 +0100
        Re: about 10th new install of bullseye Greg Wooledge <greg@wooledge.org> - 2022-02-19 01:50 +0100
        Re: about 10th new install of bullseye Cindy Sue Causey <butterflybytes@gmail.com> - 2022-02-19 01:50 +0100
          Re: about 10th new install of bullseye David Wright <deblis@lionunicorn.co.uk> - 2022-02-19 03:20 +0100
      Re: about 10th new install of bullseye gene heskett <gheskett@shentel.net> - 2022-02-20 03:50 +0100
    Re: about 10th new install of bullseye David Christensen <dpchrist@holgerdanske.com> - 2022-02-19 06:50 +0100
      Re: about 10th new install of bullseye Felix Miata <mrmazda@earthlink.net> - 2022-02-19 07:20 +0100
        Re: about 10th new install of bullseye David Christensen <dpchrist@holgerdanske.com> - 2022-02-20 01:10 +0100
          Re: about 10th new install of bullseye gene heskett <gheskett@shentel.net> - 2022-02-20 03:50 +0100
            Re: about 10th new install of bullseye Charles Kroeger <mbone@gmx.co.uk> - 2022-02-23 06:30 +0100

#245515 — about 10th new install of bullseye

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

Two problems:


terminals went funkity late tuesday, spent Wed-Thu trying to reboot, would not go beyond the 15 second mark rebooting. Finally ran the net installer in rescue mode, copied my 122gb /home dir, on a 1.9T raid10 to a different drive and reinstalled, then copied it back, but kmail refuses to use the copied back data so I'm using FF to post this.


I also need to get totally, absolutely rid of brltty, its driving me berzerk with its incessant muttering in a voice as bandwidth limited, or worse, than a cell phone. Understandable maybe 5% of the time. I purposely did NOT even visit those pieces of the installer for fear it would be enabled, because even though killed by removing brltty in the previous install, 90% of the syslog was errors because it couldn't use brltty. But I got it anyway.  So how do it get rid of it without it tearing down the system with its copius error screaming?


Thanks for any advice on these two fronts.


Cheers, Gene

[toc] | [next] | [standalone]

#245520

On Fri, Feb 18, 2022 at 09:15:50AM -0800, Gene Heskett wrote:
> Two problems:
> 
> 
> terminals went funkity late tuesday, spent Wed-Thu trying to reboot, would not go beyond the 15 second mark rebooting. Finally ran the net installer in rescue mode, copied my 122gb /home dir, on a 1.9T raid10 to a different drive and reinstalled, then copied it back, but kmail refuses to use the copied back data so I'm using FF to post this.
> 
> 

Hi Gene 


Check permissions on spools etc - how did you copy your data out?
A tar ball preserving permissions is also quite useful for this.
Goodness, what do you keep to make your /home directory 122G?

> I also need to get totally, absolutely rid of brltty, its driving me berzerk with its incessant muttering in a voice as bandwidth limited, or worse, than a cell phone. Understandable maybe 5% of the time. I purposely did NOT even visit those pieces of the installer for fear it would be enabled, because even though killed by removing brltty in the previous install, 90% of the syslog was errors because it couldn't use brltty. But I got it anyway.  So how do it get rid of it without it tearing down the system with its copius error screaming?
> 

Just a thought: apt rdepends brltty reveals a small number of things
that depend on it. Use apt-get / aptitude or whatever to remove these in
order.

I don't know _why_ you keep getting brltty installed - disconnect any
serial leads from this machine as a start. If you can't get brltty 
removed as above - copy your home directory off again and do a reinstall
with the minimum connected to your machine.

[The serial idea is because I seem to recall that if brltty finds a serial
connection active at install, it may assume there's a brltty installed.

In something of 150 or more installs of bullseye - we do a bunch with
each release of images with a point release - I don't think I've ever
seen brltty installed "by accident" so I'd love to know exactly what you
do do each time.

All the very best, as ever,

Andy Cater


> 
> Thanks for any advice on these two fronts.
> 
> 
> Cheers, Gene

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

#245522

Hello,

On Fri, Feb 18, 2022 at 07:41:01PM +0000, Andrew M.A. Cater wrote:
> In something of 150 or more installs of bullseye - we do a bunch with
> each release of images with a point release - I don't think I've ever
> seen brltty installed "by accident" so I'd love to know exactly what you
> do do each time.

It is really bizarre that this keeps happening to Gene and I can
only think it is, as you say, something to do with the serial
devices he has connected at install time.

Will the installer logs give any hint as to why brltty gets
installed? If so perhaps he could try saving those before letting
the installer reboot, and put them somewhere for us to see.

Cheers,
Andy

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

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

#245557

On 2022-02-18, Andy Smith <andy@strugglers.net> wrote:
> Hello,
>
> On Fri, Feb 18, 2022 at 07:41:01PM +0000, Andrew M.A. Cater wrote:
>> In something of 150 or more installs of bullseye - we do a bunch with
>> each release of images with a point release - I don't think I've ever
>> seen brltty installed "by accident" so I'd love to know exactly what you
>> do do each time.
>
> It is really bizarre that this keeps happening to Gene and I can
> only think it is, as you say, something to do with the serial
> devices he has connected at install time.

In a long-ago thread we speculated Gene had an ft232 connected to his
machine, which was mistaken for a refreshable braille display and so
brought in brltty as a consequence. 

> Will the installer logs give any hint as to why brltty gets
> installed? If so perhaps he could try saving those before letting
> the installer reboot, and put them somewhere for us to see.
>
> Cheers,
> Andy
>


-- 

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

#245534

On Fri 18 Feb 2022 at 19:41:01 (+0000), Andrew M.A. Cater wrote:
> On Fri, Feb 18, 2022 at 09:15:50AM -0800, Gene Heskett wrote:
> > Two problems:
> > 
> > terminals went funkity late tuesday, spent Wed-Thu trying to reboot, would not go beyond the 15 second mark rebooting. Finally ran the net installer in rescue mode, copied my 122gb /home dir, on a 1.9T raid10 to a different drive and reinstalled, then copied it back, but kmail refuses to use the copied back data so I'm using FF to post this.
> 
> Check permissions on spools etc - how did you copy your data out?
> A tar ball preserving permissions is also quite useful for this.
> Goodness, what do you keep to make your /home directory 122G?

I'm not sure what's eyebrow-raising about 122GB under /home.

$ dfree
Filesystem      IUse%  Type  1MB-blocks    Used  Avail  Use%  Mounted  on
/dev/sda4         19%  ext4       30830   26224¹   3016   90%  /
/dev/sda2           -  vfat         520       7    514    2%  /boot/efi
/dev/dm-1          2%  ext4      428208  382990  23396   95%  /home
$ 

A large /home seems sufficient reason to mount it from a separate
partition. Then all you have to worry about when you reinstall is
which of your dotfiles do you let the fresh system get to see, and
which do you hide (in case they're causing problems).

¹ /var/cache/apt-cacher-ng/<2½ versions> occupies ~13GB.

Cheers,
David.

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

#245536

On Fri, Feb 18, 2022 at 08:08:21PM -0600, David Wright wrote:
> I'm not sure what's eyebrow-raising about 122GB under /home.

unicorn:~$ df -h /home
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda8        23G   17G  5.0G  78% /home

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

#245538

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

On 2022-02-18 at 21:14, Greg Wooledge wrote:

> On Fri, Feb 18, 2022 at 08:08:21PM -0600, David Wright wrote:
>
>> I'm not sure what's eyebrow-raising about 122GB under /home.
> 
> unicorn:~$ df -h /home
> Filesystem      Size  Used Avail Use% Mounted on
> /dev/sda8        23G   17G  5.0G  78% /home

aorta:~$ df -h /home/
Filesystem                               Size  Used Avail Use% Mounted on
/dev/mapper/vg_data_aorta-lv_home_aorta   11T  5.6T  4.4T  57% /home

Though to be fair that's (part of) an... 8-drive?... RAID-6 array, and
this system's storage capacities are *utterly ridiculous* for most
consumer purposes.

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

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

#245543

On Fri 18 Feb 2022 at 21:18:32 (-0500), The Wanderer wrote:
> On 2022-02-18 at 21:14, Greg Wooledge wrote:
> > On Fri, Feb 18, 2022 at 08:08:21PM -0600, David Wright wrote:
> >
> >> I'm not sure what's eyebrow-raising about 122GB under /home.
> > 
> > unicorn:~$ df -h /home
> > Filesystem      Size  Used Avail Use% Mounted on
> > /dev/sda8        23G   17G  5.0G  78% /home
> 
> aorta:~$ df -h /home/
> Filesystem                               Size  Used Avail Use% Mounted on
> /dev/mapper/vg_data_aorta-lv_home_aorta   11T  5.6T  4.4T  57% /home
> 
> Though to be fair that's (part of) an... 8-drive?... RAID-6 array, and
> this system's storage capacities are *utterly ridiculous* for most
> consumer purposes.

# ssh -X wren
Linux wren 5.10.0-11-amd64 #1 SMP Debian 5.10.92-1 (2022-01-18) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Feb 18 14:20:22 2022 from 192.168.1.14
wren 20:54:02 ~# ls -GRagl /home/
/home/:
total 12
drwxr-xr-x  3 4096 Jan 31 19:30 .
drwxr-xr-x 20 4096 Feb 14 22:53 ..
-rw-r--r--  1    0 Jan 31 19:30 0
drwxr-xr-x  2 4096 Jan 31 19:30 admin

/home/admin:
total 16
drwxr-xr-x 2 4096 Jan 31 19:30 .
drwxr-xr-x 3 4096 Jan 31 19:30 ..
-rw-r--r-- 1  680 Jan 28 12:38 .bashrc
-rw-r--r-- 1  807 Jan  1 11:29 .profile
wren 20:54:11 ~# 

by way of contrast!

Cheers,
David.

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

#245545

On Friday, February 18, 2022 09:14:00 PM Greg Wooledge wrote:
> On Fri, Feb 18, 2022 at 08:08:21PM -0600, David Wright wrote:
> > I'm not sure what's eyebrow-raising about 122GB under /home.
> 
> unicorn:~$ df -h /home
> Filesystem      Size  Used Avail Use% Mounted on
> /dev/sda8        23G   17G  5.0G  78% /home

I want to play to:

rhk@s19:/usr/share/man$ df -h /home
Filesystem      Size  Used Avail Use% Mounted on
/dev/sdb12      1.9G  1.3G  489M  73% /home

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

#245523

On Fri 18 Feb 2022 at 09:15:50 (-0800), Gene Heskett wrote:
> Two problems:
> 
> terminals went funkity late tuesday, spent Wed-Thu trying to reboot, would not go beyond the 15 second mark rebooting. Finally ran the net installer in rescue mode, copied my 122gb /home dir, on a 1.9T raid10 to a different drive and reinstalled, then copied it back, but kmail refuses to use the copied back data so I'm using FF to post this.

No idea what funkity means, nor what is significant about 15 seconds
when booting. I have systems that boot in <3.5 seconds and other that
take nearly a minute. Nor am I sure what's special about /home with
respect to booting — it should have no role.

> I also need to get totally, absolutely rid of brltty, its driving me berzerk with its incessant muttering in a voice as bandwidth limited, or worse, than a cell phone. Understandable maybe 5% of the time. I purposely did NOT even visit those pieces of the installer for fear it would be enabled, because even though killed by removing brltty in the previous install, 90% of the syslog was errors because it couldn't use brltty. But I got it anyway.  So how do it get rid of it without it tearing down the system with its copius error screaming?

Um, perhaps https://lists.debian.org/debian-user/2019/05/msg01001.html

Cheers,
David.

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

#245529

David Wright composed on 2022-02-18 14:19 (UTC-0600):

> On Fri 18 Feb 2022 at 09:15:50 (-0800), Gene Heskett wrote:

>> Two problems:

>> terminals went funkity late tuesday, spent Wed-Thu trying to reboot, would not go beyond the 15 second mark rebooting. Finally ran the net installer in rescue mode, copied my 122gb /home dir, on a 1.9T raid10 to a different drive and reinstalled, then copied it back, but kmail refuses to use the copied back data so I'm using FF to post this.

> No idea what funkity means,

nuts, cuckoo, fubar, whacky, loopy aka abnormal

> nor what is significant about 15 seconds
> when booting.

Boot messages scroll on vtty 1 normally for about 15 seconds, then quit.

> I have systems that boot in <3.5 seconds and other that
> take nearly a minute. Nor am I sure what's special about /home with
> respect to booting — it should have no role.

It's about protecting user data against unexpected installation results.
-- 
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

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

#245530

On Fri, Feb 18, 2022 at 07:21:19PM -0500, Felix Miata wrote:
> David Wright composed on 2022-02-18 14:19 (UTC-0600):
> 
> > On Fri 18 Feb 2022 at 09:15:50 (-0800), Gene Heskett wrote:
> 
> >> Two problems:
> 
> >> terminals went funkity late tuesday, spent Wed-Thu trying to reboot, would not go beyond the 15 second mark rebooting. Finally ran the net installer in rescue mode, copied my 122gb /home dir, on a 1.9T raid10 to a different drive and reinstalled, then copied it back, but kmail refuses to use the copied back data so I'm using FF to post this.
> 
> > No idea what funkity means,
> 
> nuts, cuckoo, fubar, whacky, loopy aka abnormal

But what are the *actual* symptoms?  What did Gene see?  What did he
try, to troubleshoot, and what results did he get?

These are basic questions that someone with Gene's level of experience
shouldn't need to be asked.

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

#245531

On 2/18/22, Felix Miata <mrmazda@earthlink.net> wrote:
> David Wright composed on 2022-02-18 14:19 (UTC-0600):
>
>> On Fri 18 Feb 2022 at 09:15:50 (-0800), Gene Heskett wrote:
>
>>> Two problems:
>
>>> terminals went funkity late tuesday, spent Wed-Thu trying to reboot,
>>> would not go beyond the 15 second mark rebooting. Finally ran the net
>>> installer in rescue mode, copied my 122gb /home dir, on a 1.9T raid10 to
>>> a different drive and reinstalled, then copied it back, but kmail refuses
>>> to use the copied back data so I'm using FF to post this.
>
>> No idea what funkity means,
>
> nuts, cuckoo, fubar, whacky, loopy aka abnormal
>
>> nor what is significant about 15 seconds
>> when booting.
>
> Boot messages scroll on vtty 1 normally for about 15 seconds, then quit.


That's what I understood, too. Mine's occasionally doing something
like that. It seems to be tied to CPU temperatures (overheating).

It's really kind of weird. It's for that first few seconds of booting
where it's running through a checkup before those boot messages begin
appearing. When mine keeps flicking off like that, fanning it with a
piece of paper gets it past that hump then it doesn't do it again.
It's like something in the first stage is pushing the CPUs hard then
it backs off once those messages start scrolling.

That presents a detail that's not clear on Gene's case. Is the
computer just stopping and standing at that screen, or is it shutting
off? Mine shuts off. This might be an apples and oranges thing where I
typed a bunch of noise. :)

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

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

#245535

On Fri 18 Feb 2022 at 19:48:40 (-0500), Cindy Sue Causey wrote:
> On 2/18/22, Felix Miata <mrmazda@earthlink.net> wrote:
> > David Wright composed on 2022-02-18 14:19 (UTC-0600):
> >> On Fri 18 Feb 2022 at 09:15:50 (-0800), Gene Heskett wrote:
> >
> >>> Two problems:
> >
> >>> terminals went funkity late tuesday, spent Wed-Thu trying to reboot,
> >>> would not go beyond the 15 second mark rebooting. Finally ran the net
> >>> installer in rescue mode, copied my 122gb /home dir, on a 1.9T raid10 to
> >>> a different drive and reinstalled, then copied it back, but kmail refuses
> >>> to use the copied back data so I'm using FF to post this.
> >
> >> No idea what funkity means,
> >
> > nuts, cuckoo, fubar, whacky, loopy aka abnormal
> >
> >> nor what is significant about 15 seconds
> >> when booting.
> >
> > Boot messages scroll on vtty 1 normally for about 15 seconds, then quit.
> 
> That's what I understood, too. Mine's occasionally doing something
> like that. It seems to be tied to CPU temperatures (overheating).
> 
> It's really kind of weird. It's for that first few seconds of booting
> where it's running through a checkup before those boot messages begin
> appearing.

What I call the POST? Yes, well in the olden days, when we had real
CRTs, and "everything" ran at VGA resolution, you could sit back for
a minute and watch the whole light show: Graphics card, BIOS, POST,
Lilo, Kernel, and all the dmesg stuff, with the odd screen clearance
but no noticeable change in mode. (I used to scroll back and cut and
paste everything post-POST into an archived file.)

Nowadays, with these fancy flatscreens, each change in mode can lead
to a significant blank period (seconds) while it sorts itself out.

> When mine keeps flicking off like that, fanning it with a
> piece of paper gets it past that hump then it doesn't do it again.
> It's like something in the first stage is pushing the CPUs hard then
> it backs off once those messages start scrolling.

Do you mean that you hear the fan going at full speed? Yes, that's
quite normal AIUI, and seems very sensible: if nothing is monitoring
the temperature of the system, then running the fan is the failsafe state.

> That presents a detail that's not clear on Gene's case. Is the
> computer just stopping and standing at that screen,

Exactly — and if it does, what's printed, and are you aware of
anything that might be missing. Or does it reboot. Or is it still
running, but writing to one of the many serial connections?

> or is it shutting
> off? Mine shuts off.

Cheers,
David.

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

#245579

On Friday, February 18, 2022 3:19:43 PM EST David Wright wrote:
> On Fri 18 Feb 2022 at 09:15:50 (-0800), Gene Heskett wrote:
> > Two problems:
> > 
> > terminals went funkity late tuesday, spent Wed-Thu trying to reboot,
> > would not go beyond the 15 second mark rebooting. Finally ran the
> > net installer in rescue mode, copied my 122gb /home dir, on a 1.9T
> > raid10 to a different drive and reinstalled, then copied it back,
> > but kmail refuses to use the copied back data so I'm using FF to
> > post this.
> No idea what funkity means, nor what is significant about 15 seconds
> when booting. I have systems that boot in <3.5 seconds and other that
> take nearly a minute. Nor am I sure what's special about /home with
> respect to booting — it should have no role.
> 
> > I also need to get totally, absolutely rid of brltty, its driving me
> > berzerk with its incessant muttering in a voice as bandwidth
> > limited, or worse, than a cell phone. Understandable maybe 5% of the
> > time. I purposely did NOT even visit those pieces of the installer
> > for fear it would be enabled, because even though killed by removing
> > brltty in the previous install, 90% of the syslog was errors because
> > it couldn't use brltty. But I got it anyway.  So how do it get rid
> > of it without it tearing down the system with its copius error
> > screaming?
> Um, perhaps https://lists.debian.org/debian-user/2019/05/msg01001.html
> 

At 87 yo, you're expecting me to remember a post I made, what, 3 years 
ago? But its pretty close to exactly it. But I still don't recall if I 
unplugged the adapter that time, and by now there is probably at least 
one more, maybe two in my usb tree.

> Cheers,
> David.
> 
> .


Cheers, Gene Heskett.
-- 
"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
Genes Web page <http://geneslinuxbox.net:6309/gene>

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

#245547

On 2/18/22 09:15, Gene Heskett wrote:
> Two problems:
> 
> 
> terminals went funkity late tuesday, spent Wed-Thu trying to reboot, would not go beyond the 15 second mark rebooting. Finally ran the net installer in rescue mode, copied my 122gb /home dir, on a 1.9T raid10 to a different drive and reinstalled, then copied it back, but kmail refuses to use the copied back data so I'm using FF to post this.
> 
> 
> I also need to get totally, absolutely rid of brltty, its driving me berzerk with its incessant muttering in a voice as bandwidth limited, or worse, than a cell phone. Understandable maybe 5% of the time. I purposely did NOT even visit those pieces of the installer for fear it would be enabled, because even though killed by removing brltty in the previous install, 90% of the syslog was errors because it couldn't use brltty. But I got it anyway.  So how do it get rid of it without it tearing down the system with its copius error screaming?
> 
> 
> Thanks for any advice on these two fronts.
> 
> 
> Cheers, Gene


On 2/18/22 15:38, Gene Heskett wrote:
 > I'm on web mail using FF, which does not quote worth a damn. My "usb 
tree" looks like a weeping willow and contains several devices that 
answer to serial protocols. Both this keyboard and this mouse are 
wireless, and speak serial.  So how am I supposed to install with no 
keyboard?
 >
 >
 > Interesting question that.
 >
 >
 > Thanks, Cheers Gene


On 2/18/22 18:13, Gene Heskett wrote:
 > On Fri, 18 Feb, 2022 at 7:41 PM, Greg Wooledge <greg@wooledge.org> wrote:

 >> But what are the *actual* symptoms?  What did Gene see?  What did he
 >> try, to troubleshoot, and what results did he get?
 >
 >
 >
 > Exactly what I wrote Greg, the boot stops at the 15 second mark, 
forever. I let it set there once for several hours while I caught some 
shuteye.
 >
 >
 > Repeated at least 20 times.
 >
 >
 >
 > Putting the install dvd in that drive, and selecting rescue mode, 
works and I was able to make a backup of /home. Then I reinstalled. And 
on the reboot after the install this PITA of a blast of unintelligible 
noise per keystroke was back and I did not go anywhere near those menu 
item for this install.
 >
 >
 >
 >> These are basic questions that someone with Gene's level of experience
 >> shouldn't need to be asked.
 >
 >
 >
 > Maybe so but I also getting upset with the feigned ignorance of what 
I type you won't believe. I said it stopped at about 15 seconds and I 
don't understand your lack of comprehension of the word "stopped". At 
that point, the only thing that worked was the front panel of this 30" 
towers reset button, or after a delay, the power button.
 >
 >
 > Right now I've removed brltty and its api library which stops he 
racket of unintelligible sound, but my syslog is growing by abut 6 lines 
of errors per keystroke because brltty can't be found, or about every 4 
or 5 seconds even if the keyboard isn't in use.
 >
 > I need to find a way to remove this stuff w/o eviscerating half the 
system with its dependencies. Respin the installer for 11-4 if needed 
but this needs fixed.
 >
 >
 >
 > I'd also bet you a six pack of suds it won't reboot right now because 
I have removed brltty, and that IS the 15 second showstopper. But if my 
theory is correct, it will also add to the reinstall count which is 
already annoyingly high. Which with this system means at least a day to 
do it.
 >
 >
 > Give us back stretch, once the install was fixed so it had 
networking, it just worked, till hell froze over.
 >
 >
 > Oh, since we're on the subject, how do I put an option on the kernel 
load line,(in grub.cfg) to make very noisy debugging so the next time I 
have to reboot, I can see exactly what stopped it.  That would be a 
great help.
 >
 >
 >
 > Thanks Greg, take care and stay well.
 >
 >
 > Cheers Gene


I recall that you have several computers, that your hobby is using Linux 
for CNC woodworking, and that you modify the OS's significantly and/or 
install specialized, non-Debian software.


I have found that when I install too much software, when I put 
non-Debian software on a Debian computer, and/or when I make too many 
changes to the OS and/or software, that the computer becomes unstable.


I have found it useful to spread storage and functionality across 
several computers, to limit the scope of disasters and to facilitate 
recovery.  These are the three key computers at my site:

1.  Primary workstation.

2.  Live server (Samba and SSH/CVS).

3.  Backup/ archive/ image/ replication server.


For Debian and FreeBSD machines, including the above, I install the OS 
as follows:

1.  Disconnect all hard disk drives, solid-state drives, USB flash 
drives, SDHC cards, etc..

2.  Disconnect all external devices from the computer except a keyboard, 
a mouse, a monitor, and the network connection (servers and desktops), 
or the network connection (laptops).

3.  Install a blank SSD.  Ensure that it is the first device node when 
the installer runs (e.g. /dev/sda).

4.  Do the simplest install of the OS of choice onto the SSD, using 
BIOS, MBR, and partitioning the OS drive such that the system image fits 
onto "16 GB" devices with room to spare -- 1 GB ext4 boot, 1 GB 
encrypted swap, 12 GB encrypted ext4 root.


For the key computers, I then install "official" packages for only the 
software needed for the chosen function.  For a Debian primary 
workstation, I also install the Debianized VirtualBox from Oracle.


I use VM's and/or additional computers for everything else.


The small OS image size makes it easy to take and restore images; 
monthly and as needed.  I keep all of the system configuration files in 
a version control system (CVS).  And, I backup boot and root daily and 
as needed.  So, when an OS instance becomes damaged, recovery is 
straight-forward.


Your computer with the RAID10 (4 @ 1 TB HDD?) would seem to be the 
logical choice for use as a live server.  Put the OS on a small SSD and 
use the big disks for data.


Pick a machine to use as your workstation.  Put the OS on a small SSD 
and move as much of the 122 GB as you can to the live server.  My home 
directory is ~2.6 GB and fits on root.  Most of that is used by Xfce and 
apps.  The only volatile user data is e-mail.  If you cannot shrink your 
home directory, move it to another partition or to a second SSD.


Pick a machine to use as your backup (Amanda?), etc., server.  Again, a 
small SSD for the OS; one or more big disks for backups, etc..


David

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

#245548

David Christensen composed on 2022-02-18 21:38 (UTC-0800):

> 4.  Do the simplest install of the OS of choice onto the SSD, using 
> BIOS, MBR, and partitioning the OS drive such that the system image fits 
> onto "16 GB" devices with room to spare -- 1 GB ext4 boot, 1 GB 
> encrypted swap, 12 GB encrypted ext4 root.

1 + 1 + 12 = 14. Does the remaining 2 remain unallocated?
-- 
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

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

#245569

On 2/18/22 22:15, Felix Miata wrote:
> David Christensen composed on 2022-02-18 21:38 (UTC-0800):
> 
>> 4.  Do the simplest install of the OS of choice onto the SSD, using
>> BIOS, MBR, and partitioning the OS drive such that the system image fits
>> onto "16 GB" devices with room to spare -- 1 GB ext4 boot, 1 GB
>> encrypted swap, 12 GB encrypted ext4 root.
> 
> 1 + 1 + 12 = 14. Does the remaining 2 remain unallocated?


Yes -- to allow for "16 GB" devices with differing block counts.


David

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

#245578

On Saturday, February 19, 2022 6:59:52 PM EST David Christensen wrote:
> On 2/18/22 22:15, Felix Miata wrote:
> > David Christensen composed on 2022-02-18 21:38 (UTC-0800):
> >> 4.  Do the simplest install of the OS of choice onto the SSD, using
> >> BIOS, MBR, and partitioning the OS drive such that the system image
> >> fits onto "16 GB" devices with room to spare -- 1 GB ext4 boot, 1
> >> GB encrypted swap, 12 GB encrypted ext4 root.
> > 
> > 1 + 1 + 12 = 14. Does the remaining 2 remain unallocated?
> 
> Yes -- to allow for "16 GB" devices with differing block counts.
> 
> 
> David
> 
> .
Precisely.

Cheers, Gene Heskett.
-- 
"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
Genes Web page <http://geneslinuxbox.net:6309/gene>

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

#245642

replace the GPU card Gene it's kaput.

C

[toc] | [prev] | [standalone]

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

csiph-web