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

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

had another crash, reboot usb failed, powerdown reboot usb failed

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

Contents

  had another crash, reboot usb failed, powerdown reboot usb failed gene heskett <gheskett@shentel.net> - 2022-05-31 09:30 +0200
    Re: had another crash, reboot usb failed, powerdown reboot usb failed "Andrew M.A. Cater" <amacater@einval.com> - 2022-05-31 22:30 +0200
      Re: had another crash, reboot usb failed, powerdown reboot usb failed gene heskett <gheskett@shentel.net> - 2022-06-01 06:30 +0200
        Re: had another crash, reboot usb failed, powerdown reboot usb failed David Wright <deblis@lionunicorn.co.uk> - 2022-06-01 07:00 +0200
          Re: had another crash, reboot usb failed, powerdown reboot usb failed gene heskett <gheskett@shentel.net> - 2022-06-01 07:30 +0200
            Re: had another crash, reboot usb failed, powerdown reboot usb failed David Wright <deblis@lionunicorn.co.uk> - 2022-06-01 22:40 +0200
              Re: had another crash, reboot usb failed, powerdown reboot usb failed gene heskett <gheskett@shentel.net> - 2022-06-02 01:40 +0200
                Re: had another crash, reboot usb failed, powerdown reboot usb failed David Wright <deblis@lionunicorn.co.uk> - 2022-06-02 17:10 +0200
                  Re: had another crash, reboot usb failed, powerdown reboot usb failed gene heskett <gheskett@shentel.net> - 2022-06-02 18:00 +0200
              Re: had another crash, reboot usb failed, powerdown reboot usb failed gene heskett <gheskett@shentel.net> - 2022-06-02 04:50 +0200
                Re: had another crash, reboot usb failed, powerdown reboot usb failed Anssi Saari <as@sci.fi> - 2022-06-02 10:10 +0200
                  Re: had another crash, reboot usb failed, powerdown reboot usb failed gene heskett <gheskett@shentel.net> - 2022-06-02 16:40 +0200
                    Re: had another crash, reboot usb failed, powerdown reboot usb failed gene heskett <gheskett@shentel.net> - 2022-06-02 17:50 +0200
                    Re: had another crash, reboot usb failed, powerdown reboot usb failed gene heskett <gheskett@shentel.net> - 2022-06-02 17:50 +0200

#248601 — had another crash, reboot usb failed, powerdown reboot usb failed

See subject, mouse, keyboard, usb printers working, but /dev/ttyUSB* is 
not, 

"sudo lsusb -v|grep -C3 Couldn -" reports most devices can't be opened.
 Example:
gene@coyote:/etc/nut$ sudo lsusb -v|grep -c3 Couldn -
can't get debug descriptor: Resource temporarily unavailable
can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable

I am uptodate a/o yesterday with debian 11. And nothing was offered just 
now.

Whats changed in the last 10 days?

And where do I start, nut and heyu are both spamming the log. And 
something is beeping at me at 5 minute intervals.

Thanks all;

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

[toc] | [next] | [standalone]

#248614

On Tue, May 31, 2022 at 03:25:59AM -0400, gene heskett wrote:
> See subject, mouse, keyboard, usb printers working, but /dev/ttyUSB* is 
> not, 
> 
> "sudo lsusb -v|grep -C3 Couldn -" reports most devices can't be opened.
>  Example:
> gene@coyote:/etc/nut$ sudo lsusb -v|grep -c3 Couldn -
> can't get debug descriptor: Resource temporarily unavailable
> can't get device qualifier: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get device qualifier: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get device qualifier: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get device qualifier: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> can't get device qualifier: Resource temporarily unavailable
> can't get debug descriptor: Resource temporarily unavailable
> 
> I am uptodate a/o yesterday with debian 11. And nothing was offered just 
> now.
> 
> Whats changed in the last 10 days?
> 
> And where do I start, nut and heyu are both spamming the log. And 
> something is beeping at me at 5 minute intervals.
> 

Hi Gene,

We've had something similar to this previously when you were talking about
USB->TTY converters for driving your CNC machinery and you were complaining
about accessibility software for blind users being installed.

Pull the leads. Reboot. Insert the leads - check to see whether the leads
ar recognised. Reboot again. Divide and conquer until you find the problematic
lead or component. Treat it like troubleshooting a troublesome TV transmitter
or broadcast system niggle.

The simpler you can make your system while troubleshooting, the easier you
(and the rest of us) may find the whack-a-mole process of trying to 
nail down what the actual issue is.

The more you can tell us what _EXACTLY_ you are doing, what you see, what
errors come up and what you have done to try and fix them, the easier we'll
all find it to come up with suggestions or actual answers for you.

There are a bunch of the usual suspects who will attempt to help: we can't
jump on a plane or a bus to see what your screen says and help you debug.
The more you can give us to go on, the easier it will be all round.

All the very best to you, as ever,

Andy Cater 



> Thanks all;
> 
> 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
> 
> 
> 

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

#248620

On Tuesday, 31 May 2022 16:25:01 EDT Andrew M.A. Cater wrote:
> On Tue, May 31, 2022 at 03:25:59AM -0400, gene heskett wrote:
> > See subject, mouse, keyboard, usb printers working, but /dev/ttyUSB*
> > is not,
> > 
> > "sudo lsusb -v|grep -C3 Couldn -" reports most devices can't be
> > opened.> 
> >  Example:
> > gene@coyote:/etc/nut$ sudo lsusb -v|grep -c3 Couldn -
> > can't get debug descriptor: Resource temporarily unavailable
> > can't get device qualifier: Resource temporarily unavailable
> > can't get debug descriptor: Resource temporarily unavailable
> > can't get debug descriptor: Resource temporarily unavailable
> > can't get debug descriptor: Resource temporarily unavailable
> > can't get debug descriptor: Resource temporarily unavailable
> > can't get debug descriptor: Resource temporarily unavailable
> > can't get debug descriptor: Resource temporarily unavailable
> > can't get device qualifier: Resource temporarily unavailable
> > can't get debug descriptor: Resource temporarily unavailable
> > can't get device qualifier: Resource temporarily unavailable
> > can't get debug descriptor: Resource temporarily unavailable
> > can't get debug descriptor: Resource temporarily unavailable
> > can't get debug descriptor: Resource temporarily unavailable
> > can't get debug descriptor: Resource temporarily unavailable
> > can't get device qualifier: Resource temporarily unavailable
> > can't get debug descriptor: Resource temporarily unavailable
> > can't get debug descriptor: Resource temporarily unavailable
> > can't get debug descriptor: Resource temporarily unavailable
> > can't get device qualifier: Resource temporarily unavailable
> > can't get debug descriptor: Resource temporarily unavailable
> > 
> > I am uptodate a/o yesterday with debian 11. And nothing was offered
> > just now.
> > 
> > Whats changed in the last 10 days?
> > 
> > And where do I start, nut and heyu are both spamming the log. And
> > something is beeping at me at 5 minute intervals.
> 
> Hi Gene,
> 
> We've had something similar to this previously when you were talking
> about USB->TTY converters for driving your CNC machinery and you were
> complaining about accessibility software for blind users being
> installed.
> 
> Pull the leads. Reboot. Insert the leads - check to see whether the
> leads ar recognised. Reboot again. Divide and conquer until you find
> the problematic lead or component. Treat it like troubleshooting a
> troublesome TV transmitter or broadcast system niggle.
> 
> The simpler you can make your system while troubleshooting, the easier
> you (and the rest of us) may find the whack-a-mole process of trying
> to nail down what the actual issue is.
> 
> The more you can tell us what _EXACTLY_ you are doing, what you see,
> what errors come up and what you have done to try and fix them, the
> easier we'll all find it to come up with suggestions or actual answers
> for you.
> 
> There are a bunch of the usual suspects who will attempt to help: we
> can't jump on a plane or a bus to see what your screen says and help
> you debug. The more you can give us to go on, the easier it will be
> all round.
> 
> All the very best to you, as ever,
> 
There are no man pages for nut for starters. So you wind up browseing in 
/usr/share/doc/nut with a browser. But while those docs point at 
troubleshooting aids, the link to the aid is a 404 for konqueror. Thats 
really really helpful, NOT!

I went thru dmesg looking to see where it may have been detected, cvame 
up blank. unplugged the ups for ten secs and plugged it back in and it 
was then detected as /dem/hidraw4 or hiddev4. Put that in ups.conf, no 
permissions. perms are root:dialout. Add nut to dialout in /etc/group.

I can't get heyu to stay up long enough to see who its running as but 
again its no permissions at its normal /dev/ttyUSB0. The ups used to be 
/dev/ttyUSB1. The lsusb -v output is full of no permissions errors that 
do not go away if I sudo it.

The newest files in /lib/udev/rules.d is in february, and I've rebooted 
many times since then bcuz uptimes are in the 5 to maybe 11 days range.

Please give me back the stability even buster had, better yet wheezy, 
there it was not uncommon to get uptimes from power failure to power 
failure.  And I do better than that on an rpi4b running buster, thats 
uptime until I screw something up as it has a small, ultracheap 
cyberpower 650 usp on it and the only time it gets rebooted is when I 
switch to a bullseye card to see if I can build linuxcnc from a git clone 
that a cron script keeps up to date with linuxcnc master of the rpi4. But 
linuxcnc has not yet learned how to use the newer python 3.10 in 
bullseye. So that fails.  So I finally sent another rpi4 user building a 
bigger mill, converting a 1980 vintage cinci mill, a pair of cards with 
my 4.19.71-preempt-rt kernel in place of the raspi kernel. bullseye runs 
just peachy on that kernel and the tarball I made to install it on the pi 
is 28 megabytes, uncompressed.

debian can start by giving us back the troubleshooting tools mentioned in 
/usr/share/doc/nut-doc/user-manual/index.html that are missing from the 
packaging system. heyu similarly doesn't install any man pages. So I'm 
stuck wading thru /etc/heyu/x10.conf looking for clues, and tbt there are 
few.  The default device has been set to TTY = /dev/ttyUSB0 for decades.

I now know where the seriel convertors are so I can unplug them so I 
could reinstall for about the 25th time if someone could tell me how to 
skip formatting my raid10 /home partition, othewise I am stuck building a 
working system to do my daily stuff from nothing.

The installer blindly goes ahead and formats it every time, losing 6 
months of work in OpenSCAD and thats pure bs IMNSHO. I'm halfway thru 
building another raid10 I can hide from the installer, needing two more 
terabyte samsung ssd's and a slot for aother controller which I can free 
up by temporarily pulling my firewire card that runs my movie camera with 
kino.

My backups died with the loss of those 2 2T seacrates in 2 weeks time 
last fall. Both less than 6 months old, yet I caught hell for bad 
mouthing the shingled technology. Quietly introduced by seagate without 
warning the consumer it was at best alpha technology. Or maybe it was the 
helium that leaked out, and they fly the heads too high on air.  All I 
know is that there was no warning, they just disappeared from the end of 
the sata cable in the middle of the night.

Somebody's miss-guided idea of security is now putting me between a rock 
and a hard place.

I get denegrated because of my network setup, but haven't been hacked in 
25 years so I see me as doing it right.

So I'm that example of an unreasonable man that Goerge Bernard Shaw wrote 
about decades ago.

So lets fix THIS install. Quit treating me like a windowz user (something 
I've only done for a week after buying a new machine, but I gave up since 
its impossible to buy a windowless machine, so I've built my own from 
scratch since nearly 20 years back) and give us back the tools to 
troubleshoot this with.  Right now they seem to be on the missing list.

As a furinstance, I used to be able to cat a /dev/ttyUSB*, which made 
self indentifying which was which easy, cuz if you unplug a cm11a, it 
will send a message back to the port its connected to asking for a clock 
set from the server, in this case heyu which will then set the clock in 
the cm11a from local non-dst time. Its hex data but recognizable by 
someone who has written code to do that as I am one of the two authors 
who wrote ezhome for the amiga 30 years ago. We also wrote ezcron, the 
only cron ever written for tha amiga that didn't busy wait, it calculated 
how many ticks to the top of the next minute, and put itself to sleep for 
that long, freeing up the amiga to do its gfx with which ever program we 
were using at the time.

Ditto for the data that pours out of the port connected to a ups. Usually 
at 15 second intervals. Now suddenly, even a root session of cat has no 
permissions, killing a once valuable troubleshooting tool. Has a better 
tool been written? If it has been, please tell us about it!

Or quit resticting useful tools in the name of security as it sure 
doesn't pass the smell test in this camp. :(>

So where now do I find the tools to troubleshoot this with?
 
Thanks Andy, take care and stay well.

> Andy Cater

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

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

#248621

On Wed 01 Jun 2022 at 00:26:27 (-0400), gene heskett wrote:
> On Tuesday, 31 May 2022 16:25:01 EDT Andrew M.A. Cater wrote:
> > On Tue, May 31, 2022 at 03:25:59AM -0400, gene heskett wrote:

> I now know where the seriel convertors are so I can unplug them so I 
> could reinstall for about the 25th time if someone could tell me how to 
> skip formatting my raid10 /home partition, othewise I am stuck building a 
> working system to do my daily stuff from nothing.
> 
> The installer blindly goes ahead and formats it every time, losing 6 
> months of work in OpenSCAD and thats pure bs IMNSHO. I'm halfway thru 
> building another raid10 I can hide from the installer, needing two more 
> terabyte samsung ssd's and a slot for aother controller which I can free 
> up by temporarily pulling my firewire card that runs my movie camera with 
> kino.

I don't understand. You have /home on a separate partition(s), yes?
Then why do you tell the installer anything about it/them?
Just make sure that if you select it/them, they look like this:

                                                                                
                                                                                
  ┌────────────────────────┤ [!!] Partition disks ├─────────────────────────┐   
  │                                                                         │   
  │ You are editing partition #1 of SCSI1 (0,0,0) (sda). This partition     │   
  │ is formatted with the Ext4 journaling file system.                      │   
  │                                                                         │   
  │ Partition settings:                                                     │   
  │                                                                         │   
  │               Use as:         do not use   ←←←←←←←←←←←←←←← LEAVE THIS   │   
  │                                                                         │   
  │               Bootable flag:  off                                       │   
  │                                                                         │   
  │               Resize the partition (currently 200.0 GB)                 │   
  │               Erase data on this partition                              │   
  │               Delete the partition                                      │   
  │               Done setting up the partition   ←←←←←←←←←←←← PRESS THIS   │   
  │                                                                         │   
  │     <Go Back>                                                           │   
  │                                                                         │   
  └─────────────────────────────────────────────────────────────────────────┘   
                                                                                

You don't need a /home *partition* to install Debian. Just let it
create a /home/gene on the root filesystem, populated with the
contents of /etc/skel/, as per usual. When it's done, then as root,
set up your real home directory (or "assemble" it, or whatever you
do) and use the /home directory that the installer created as mount point.

Cheers,
David.

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

#248622

On Wednesday, 1 June 2022 00:58:32 EDT David Wright wrote:
> On Wed 01 Jun 2022 at 00:26:27 (-0400), gene heskett wrote:
> > On Tuesday, 31 May 2022 16:25:01 EDT Andrew M.A. Cater wrote:
> > > On Tue, May 31, 2022 at 03:25:59AM -0400, gene heskett wrote:
> > I now know where the seriel convertors are so I can unplug them so I
> > could reinstall for about the 25th time if someone could tell me how
> > to skip formatting my raid10 /home partition, othewise I am stuck
> > building a working system to do my daily stuff from nothing.
> > 
> > The installer blindly goes ahead and formats it every time, losing 6
> > months of work in OpenSCAD and thats pure bs IMNSHO. I'm halfway thru
> > building another raid10 I can hide from the installer, needing two
> > more terabyte samsung ssd's and a slot for aother controller which I
> > can free up by temporarily pulling my firewire card that runs my
> > movie camera with kino.
> 
> I don't understand. You have /home on a separate partition(s), yes?
> Then why do you tell the installer anything about it/them?
> Just make sure that if you select it/them, they look like this:
> 
> 
> 
>   ┌────────────────────────┤ [!!] Partition disks
> ├─────────────────────────┐ │                                         
>                                │ │ You are editing partition #1 of
> SCSI1 (0,0,0) (sda). This partition     │ │ is formatted with the Ext4
> journaling file system.                      │ │                      
>                                                   │ │ Partition
> settings:                                                     │ │     
>                                                                    │ │
>               Use as:         do not use   ←←←←←←←←←←←←←←← LEAVE THIS 
>  │ │                                                                  
>       │ │               Bootable flag:  off                           
>            │ │                                                        
>                 │ │               Resize the partition (currently
> 200.0 GB)                 │ │               Erase data on this
> partition                              │ │               Delete the
> partition                                      │ │               Done
> setting up the partition   ←←←←←←←←←←←← PRESS THIS   │ │              
>                                                           │ │     <Go
> Back>                                                           │ │   
>                                                                      │
> └─────────────────────────────────────────────────────────────────────
> ────┘
> 
> 
> You don't need a /home *partition* to install Debian. Just let it
> create a /home/gene on the root filesystem, populated with the
> contents of /etc/skel/, as per usual. When it's done, then as root,
> set up your real home directory (or "assemble" it, or whatever you
> do) and use the /home directory that the installer created as mount
> point.
> 
> Cheers,
> David.
> 
> .
I've tried to do that David, several times. But the net installer just 
keeps looping back to that until I use it, which formats it.

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

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

#248647

On Wed 01 Jun 2022 at 01:23:08 (-0400), gene heskett wrote:
> On Wednesday, 1 June 2022 00:58:32 EDT David Wright wrote:
> > On Wed 01 Jun 2022 at 00:26:27 (-0400), gene heskett wrote:
> > > On Tuesday, 31 May 2022 16:25:01 EDT Andrew M.A. Cater wrote:
> > > > On Tue, May 31, 2022 at 03:25:59AM -0400, gene heskett wrote:
> > > I now know where the seriel convertors are so I can unplug them so I
> > > could reinstall for about the 25th time if someone could tell me how
> > > to skip formatting my raid10 /home partition, othewise I am stuck
> > > building a working system to do my daily stuff from nothing.
> > > 
> > > The installer blindly goes ahead and formats it every time, losing 6
> > > months of work in OpenSCAD and thats pure bs IMNSHO. I'm halfway thru
> > > building another raid10 I can hide from the installer, needing two
> > > more terabyte samsung ssd's and a slot for aother controller which I
> > > can free up by temporarily pulling my firewire card that runs my
> > > movie camera with kino.
> > 
> > I don't understand. You have /home on a separate partition(s), yes?
> > Then why do you tell the installer anything about it/them?
> > Just make sure that if you select it/them, they look like this:
> > 
> > [ … ]
> > 
> > 
> > You don't need a /home *partition* to install Debian. Just let it
> > create a /home/gene on the root filesystem, populated with the
> > contents of /etc/skel/, as per usual. When it's done, then as root,
> > set up your real home directory (or "assemble" it, or whatever you
> > do) and use the /home directory that the installer created as mount
> > point.
> > 
> I've tried to do that David, several times. But the net installer just 
> keeps looping back to that until I use it, which formats it.

Because that statement is /so/ vague, I'll have to read /something/
into it. By "until I use it", do you mean that you have to use the
Partitioner Disks step, as seen here, before you can Install the
Base System?

│  Detect disks                       │
│  Partition disks                    │
│  Install the base system            │

Cheers,
David.

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

#248649

On Wednesday, 1 June 2022 16:34:01 EDT David Wright wrote:
> On Wed 01 Jun 2022 at 01:23:08 (-0400), gene heskett wrote:
> > On Wednesday, 1 June 2022 00:58:32 EDT David Wright wrote:
> > > On Wed 01 Jun 2022 at 00:26:27 (-0400), gene heskett wrote:
> > > > On Tuesday, 31 May 2022 16:25:01 EDT Andrew M.A. Cater wrote:
> > > > > On Tue, May 31, 2022 at 03:25:59AM -0400, gene heskett wrote:
> > > > I now know where the seriel convertors are so I can unplug them
> > > > so I
> > > > could reinstall for about the 25th time if someone could tell me
> > > > how
> > > > to skip formatting my raid10 /home partition, othewise I am stuck
> > > > building a working system to do my daily stuff from nothing.
> > > > 
> > > > The installer blindly goes ahead and formats it every time,
> > > > losing 6
> > > > months of work in OpenSCAD and thats pure bs IMNSHO. I'm halfway
> > > > thru
> > > > building another raid10 I can hide from the installer, needing
> > > > two
> > > > more terabyte samsung ssd's and a slot for aother controller
> > > > which I
> > > > can free up by temporarily pulling my firewire card that runs my
> > > > movie camera with kino.
> > > 
> > > I don't understand. You have /home on a separate partition(s), yes?
> > > Then why do you tell the installer anything about it/them?
> > > Just make sure that if you select it/them, they look like this:
> > > 
> > > [ … ]
> > > 
> > > 
> > > You don't need a /home *partition* to install Debian. Just let it
> > > create a /home/gene on the root filesystem, populated with the
> > > contents of /etc/skel/, as per usual. When it's done, then as root,
> > > set up your real home directory (or "assemble" it, or whatever you
> > > do) and use the /home directory that the installer created as mount
> > > point.
> > 
> > I've tried to do that David, several times. But the net installer
> > just
> > keeps looping back to that until I use it, which formats it.
> 
> Because that statement is /so/ vague, I'll have to read /something/
> into it. By "until I use it", do you mean that you have to use the
> Partitioner Disks step, as seen here, before you can Install the
> Base System?
> 
yes, it will not proceed w/o it.

> │  Detect disks                       │
> │  Partition disks                    │
> │  Install the base system            │
> 
> 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

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

#248669

On Wed 01 Jun 2022 at 19:30:37 (-0400), gene heskett wrote:
> On Wednesday, 1 June 2022 16:34:01 EDT David Wright wrote:
> > On Wed 01 Jun 2022 at 01:23:08 (-0400), gene heskett wrote:
> > > On Wednesday, 1 June 2022 00:58:32 EDT David Wright wrote:
> > > > On Wed 01 Jun 2022 at 00:26:27 (-0400), gene heskett wrote:
> > > > > On Tuesday, 31 May 2022 16:25:01 EDT Andrew M.A. Cater wrote:
> > > > > > On Tue, May 31, 2022 at 03:25:59AM -0400, gene heskett wrote:
> > > > > I now know where the seriel convertors are so I can unplug them
> > > > > so I
> > > > > could reinstall for about the 25th time if someone could tell me
> > > > > how
> > > > > to skip formatting my raid10 /home partition, othewise I am stuck
> > > > > building a working system to do my daily stuff from nothing.
> > > > > 
> > > > > The installer blindly goes ahead and formats it every time,
> > > > > losing 6
> > > > > months of work in OpenSCAD and thats pure bs IMNSHO. I'm halfway
> > > > > thru
> > > > > building another raid10 I can hide from the installer, needing
> > > > > two
> > > > > more terabyte samsung ssd's and a slot for aother controller
> > > > > which I
> > > > > can free up by temporarily pulling my firewire card that runs my
> > > > > movie camera with kino.
> > > > 
> > > > I don't understand. You have /home on a separate partition(s), yes?
> > > > Then why do you tell the installer anything about it/them?
> > > > Just make sure that if you select it/them, they look like this:
> > > > 
> > > > [ … ]
> > > > 
> > > > 
> > > > You don't need a /home *partition* to install Debian. Just let it
> > > > create a /home/gene on the root filesystem, populated with the
> > > > contents of /etc/skel/, as per usual. When it's done, then as root,
> > > > set up your real home directory (or "assemble" it, or whatever you
> > > > do) and use the /home directory that the installer created as mount
> > > > point.
> > > 
> > > I've tried to do that David, several times. But the net installer
> > > just
> > > keeps looping back to that until I use it, which formats it.
> > 
> > Because that statement is /so/ vague, I'll have to read /something/
> > into it. By "until I use it", do you mean that you have to use the
> > Partitioner Disks step, as seen here, before you can Install the
> > Base System?
> > 
> yes, it will not proceed w/o it.
> 
> > │  Detect disks                       │
> > │  Partition disks                    │
> > │  Install the base system            │

ISTR your having problems driving the partitioner back in 2015.
You need that partitioning step at the very least in order to indicate
on which partition to install the base system. But that doesn't mean
you have to format any of the partitions. That's why there's an option:
  "Format the partition:  no, keep existing data"

Obviously, it would complicate configuring a system if you actually
went ahead with installing the root filesystem onto a partition that
still contained a load of old files from some previous installation.

So I'd be interested to see the screen display at the point where you
tell it to "Finish partitioning and write changes to disk". That's
at the bottom of the screen that displays all the partitions, that
looks vaguely like this:

  ┌────────────────────────┤ [!!] Partition disks ├─────────────────────────┐   
  │                                                                         │   
  │ This is an overview of your currently configured partitions and mount   │   
  │ points. Select a partition to modify its settings (file system, mount   │   
  │ point, etc.), a free space to create partitions, or a device to         │   
  │ initialize its partition table.                                         │   
  │                                                                         │   
  │  Configure iSCSI volumes                                            ↑   │   
  │                                                                     ▒   │   
  │  Encrypted volume (sda5_crypt) - 31.4 GB Linux device-mapper (cryp  ▒   │   
  │  >     #1     31.4 GB    f  ext4                      /             ▒   │   
  │  SCSI1 (0,0,0) (sda) - 500.1 GB ATA ST3500000AA                     ▒   │   
  │  >             1.0 MB       FREE SPACE                              ▒   │   
  │  >     #1      3.1 MB    K  biosgrub    BIOS boot pa                ▒   │   
  │  >     #2    520.1 MB    F  ext2        BullBoot      /boot         ▒   │   
  │  >     #3    524.3 MB       ext2        Linux swap                  ▒   │   
  │  >     #4     31.5 GB       ext4        Viva-A                      ▒   │   
  │  >     #5     31.5 GB    K  crypto      Viva-B        (sda5_crypt)  ▒   │   
  │  >     #6    436.1 GB                   Viva-Home                   ▒   │   
  │  >             7.7 kB       FREE SPACE                              ▒   │   
  │  SCSI7 (0,0,0) (sdb) - 1.0 GB Multiple Card Reader                  ▒   │   
  │                                                                     ▒   │   
  │  Undo changes to partitions                                         ▮   │   
  │  Finish partitioning and write changes to disk                      ↓   │   
  │                                                                         │   
  │     <Go Back>                                                           │   
  │                                                                         │   
  └─────────────────────────────────────────────────────────────────────────┘   

In this particular instance, my real, encrypted /home on partition #6,
the unencrypted buster on #4, the random-encrypted swap almost filling
#3, and Grub's playground in #1 will all be left undisturbed by the
"write changes to disk" step. Only partition #2 (for unencrypted /boot)
and the encrypted filesystem inside partition #5 (for /) will be formatted.

At the end of the d-i, there will be a vestigial /home/me containing
three dotfiles in the root filesystem, and I will login as root to
set up the script that decrypts partition #6 and mounts it on /home,
"concealing" /home/me. Also there will be a swap configuration to add
to /etc/crypttab and /etc/fstab.

The d-i doesn't have to know about any of this. It would be sensible
for you to treat your raid10 /home partition similarly.

Cheers,
David.

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

#248673

On Thursday, 2 June 2022 11:02:10 EDT David Wright wrote:
> On Wed 01 Jun 2022 at 19:30:37 (-0400), gene heskett wrote:
> > On Wednesday, 1 June 2022 16:34:01 EDT David Wright wrote:
> > > On Wed 01 Jun 2022 at 01:23:08 (-0400), gene heskett wrote:
> > > > On Wednesday, 1 June 2022 00:58:32 EDT David Wright wrote:
> > > > > On Wed 01 Jun 2022 at 00:26:27 (-0400), gene heskett wrote:
> > > > > > On Tuesday, 31 May 2022 16:25:01 EDT Andrew M.A. Cater wrote:
> > > > > > > On Tue, May 31, 2022 at 03:25:59AM -0400, gene heskett 
wrote:
> > > > > > I now know where the seriel convertors are so I can unplug
> > > > > > them
> > > > > > so I
> > > > > > could reinstall for about the 25th time if someone could tell
> > > > > > me
> > > > > > how
> > > > > > to skip formatting my raid10 /home partition, othewise I am
> > > > > > stuck
> > > > > > building a working system to do my daily stuff from nothing.
> > > > > > 
> > > > > > The installer blindly goes ahead and formats it every time,
> > > > > > losing 6
> > > > > > months of work in OpenSCAD and thats pure bs IMNSHO. I'm
> > > > > > halfway
> > > > > > thru
> > > > > > building another raid10 I can hide from the installer,
> > > > > > needing
> > > > > > two
> > > > > > more terabyte samsung ssd's and a slot for aother controller
> > > > > > which I
> > > > > > can free up by temporarily pulling my firewire card that runs
> > > > > > my
> > > > > > movie camera with kino.
> > > > > 
> > > > > I don't understand. You have /home on a separate partition(s),
> > > > > yes?
> > > > > Then why do you tell the installer anything about it/them?
> > > > > Just make sure that if you select it/them, they look like this:
> > > > > 
> > > > > [ … ]
> > > > > 
> > > > > 
> > > > > You don't need a /home *partition* to install Debian. Just let
> > > > > it
> > > > > create a /home/gene on the root filesystem, populated with the
> > > > > contents of /etc/skel/, as per usual. When it's done, then as
> > > > > root,
> > > > > set up your real home directory (or "assemble" it, or whatever
> > > > > you
> > > > > do) and use the /home directory that the installer created as
> > > > > mount
> > > > > point.
> > > > 
> > > > I've tried to do that David, several times. But the net installer
> > > > just
> > > > keeps looping back to that until I use it, which formats it.
> > > 
> > > Because that statement is /so/ vague, I'll have to read /something/
> > > into it. By "until I use it", do you mean that you have to use the
> > > Partitioner Disks step, as seen here, before you can Install the
> > > Base System?
> > 
> > yes, it will not proceed w/o it.
> > 
> > > │  Detect disks                       │
> > > │  Partition disks                    │
> > > │  Install the base system            │
> 
> ISTR your having problems driving the partitioner back in 2015.
> You need that partitioning step at the very least in order to indicate
> on which partition to install the base system. But that doesn't mean
> you have to format any of the partitions. That's why there's an option:
> "Format the partition:  no, keep existing data"
> 
> Obviously, it would complicate configuring a system if you actually
> went ahead with installing the root filesystem onto a partition that
> still contained a load of old files from some previous installation.
> 
> So I'd be interested to see the screen display at the point where you
> tell it to "Finish partitioning and write changes to disk". That's
> at the bottom of the screen that displays all the partitions, that
> looks vaguely like this:
> 
>   ┌────────────────────────┤ [!!] Partition disks
> ├─────────────────────────┐ │                                         
>                                │ │ This is an overview of your
> currently configured partitions and mount   │ │ points. Select a
> partition to modify its settings (file system, mount   │ │ point,
> etc.), a free space to create partitions, or a device to         │ │
> initialize its partition table.                                       
>  │ │                                                                  
>       │ │  Configure iSCSI volumes                                    
>        ↑   │ │                                                        
>             ▒   │ │  Encrypted volume (sda5_crypt) - 31.4 GB Linux
> device-mapper (cryp  ▒   │ │  >     #1     31.4 GB    f  ext4         
>             /             ▒   │ │  SCSI1 (0,0,0) (sda) - 500.1 GB ATA
> ST3500000AA                     ▒   │ │  >             1.0 MB      
> FREE SPACE                              ▒   │ │  >     #1      3.1 MB 
>   K  biosgrub    BIOS boot pa                ▒   │ │  >     #2   
> 520.1 MB    F  ext2        BullBoot      /boot         ▒   │ │  >    
> #3    524.3 MB       ext2        Linux swap                  ▒   │ │ 
> >     #4     31.5 GB       ext4        Viva-A                      ▒  
> │ │  >     #5     31.5 GB    K  crypto      Viva-B        (sda5_crypt)
>  ▒   │ │  >     #6    436.1 GB                   Viva-Home            
>       ▒   │ │  >             7.7 kB       FREE SPACE                  
>            ▒   │ │  SCSI7 (0,0,0) (sdb) - 1.0 GB Multiple Card Reader 
>                 ▒   │ │                                               
>                      ▒   │ │  Undo changes to partitions              
>                           ▮   │ │  Finish partitioning and write
> changes to disk                      ↓   │ │                          
>                                               │ │     <Go Back>       
>                                                    │ │                
>                                                         │
> └─────────────────────────────────────────────────────────────────────
> ────┘
> 
> In this particular instance, my real, encrypted /home on partition #6,
> the unencrypted buster on #4, the random-encrypted swap almost filling
> #3, and Grub's playground in #1 will all be left undisturbed by the
> "write changes to disk" step. Only partition #2 (for unencrypted /boot)
> and the encrypted filesystem inside partition #5 (for /) will be
> formatted.
> 
> At the end of the d-i, there will be a vestigial /home/me containing
> three dotfiles in the root filesystem, and I will login as root to
> set up the script that decrypts partition #6 and mounts it on /home,
> "concealing" /home/me. Also there will be a swap configuration to add
> to /etc/crypttab and /etc/fstab.
> 
> The d-i doesn't have to know about any of this. It would be sensible
> for you to treat your raid10 /home partition similarly.

I might give this install one more re-install, after I swap a 240G 
kingston SSD for a 1t samsung and back up my present raid10's contents to 
it so I've a backup/recovery at least possible.

But I have other alligators snapping at me too so it won't be for a 
couple weeks yet.

Thanks David, take care and stay well.

> 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

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

#248656

On Wednesday, 1 June 2022 16:34:01 EDT David Wright wrote:
> On Wed 01 Jun 2022 at 01:23:08 (-0400), gene heskett wrote:
> > On Wednesday, 1 June 2022 00:58:32 EDT David Wright wrote:
> > > On Wed 01 Jun 2022 at 00:26:27 (-0400), gene heskett wrote:
> > > > On Tuesday, 31 May 2022 16:25:01 EDT Andrew M.A. Cater wrote:
> > > > > On Tue, May 31, 2022 at 03:25:59AM -0400, gene heskett wrote:
> > > > I now know where the seriel convertors are so I can unplug them
> > > > so I
> > > > could reinstall for about the 25th time if someone could tell me
> > > > how
> > > > to skip formatting my raid10 /home partition, othewise I am stuck
> > > > building a working system to do my daily stuff from nothing.
> > > > 
> > > > The installer blindly goes ahead and formats it every time,
> > > > losing 6
> > > > months of work in OpenSCAD and thats pure bs IMNSHO. I'm halfway
> > > > thru
> > > > building another raid10 I can hide from the installer, needing
> > > > two
> > > > more terabyte samsung ssd's and a slot for aother controller
> > > > which I
> > > > can free up by temporarily pulling my firewire card that runs my
> > > > movie camera with kino.
> > > 
> > > I don't understand. You have /home on a separate partition(s), yes?
> > > Then why do you tell the installer anything about it/them?
> > > Just make sure that if you select it/them, they look like this:
> > > 
> > > [ … ]
> > > 
> > > 
> > > You don't need a /home *partition* to install Debian. Just let it
> > > create a /home/gene on the root filesystem, populated with the
> > > contents of /etc/skel/, as per usual. When it's done, then as root,
> > > set up your real home directory (or "assemble" it, or whatever you
> > > do) and use the /home directory that the installer created as mount
> > > point.
> > 
> > I've tried to do that David, several times. But the net installer
> > just
> > keeps looping back to that until I use it, which formats it.
> 
> Because that statement is /so/ vague, I'll have to read /something/
> into it. By "until I use it", do you mean that you have to use the
> Partitioner Disks step, as seen here, before you can Install the
> Base System?
> 
> │  Detect disks                       │
> │  Partition disks                    │
> │  Install the base system            │
> 
> Cheers,
> David.
> 
> .
Tell me how long this will work:

I reset the perms on /dev/ttyUSB* to 777
retarted heyu, got some config errors that made sense, fixed those and 
its working.
Then I started nut-server and client, getting more errors that made 
sense, fixed those and its working.

Do I have to reset those perms everytime I'm forced to reboot, which is 
usually in 5 to 10 days. Or is there someplace in /lib/udev/rules.d where 
I can fix this until the next udev update?

Thanks David. Take care & stay well.

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

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

#248662

gene heskett <gheskett@shentel.net> writes:

> Do I have to reset those perms everytime I'm forced to reboot, which is 
> usually in 5 to 10 days. Or is there someplace in /lib/udev/rules.d where 
> I can fix this until the next udev update?

It seems almost certain the permissions for /dev/ttyUSB* won't stick,
unless you fix them with udev rules (or some other means but udev's the
tool for the job in my opinion).

Do you really want to set all ttyUSB* to 777? Not 666 or 660 for
example? The usual way is to apply a udev rule to a specific USB product
and vendor ID which you can get from lsusb. But to change permissions on
device files I think you can do

KERNEL=="ttyUSB*", MODE="0777"

in a udev rule file.

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

#248667

On Thursday, 2 June 2022 04:08:45 EDT Anssi Saari wrote:
> gene heskett <gheskett@shentel.net> writes:
> > Do I have to reset those perms everytime I'm forced to reboot, which
> > is usually in 5 to 10 days. Or is there someplace in
> > /lib/udev/rules.d where I can fix this until the next udev update?
> 
> It seems almost certain the permissions for /dev/ttyUSB* won't stick,
> unless you fix them with udev rules (or some other means but udev's the
> tool for the job in my opinion).
> 
> Do you really want to set all ttyUSB* to 777? Not 666 or 660 for
> example? The usual way is to apply a udev rule to a specific USB
> product and vendor ID which you can get from lsusb. But to change
> permissions on device files I think you can do
> 
> KERNEL=="ttyUSB*", MODE="0777"
> 
> in a udev rule file.

/dev/ttyUSB* seems to only apply to seriel adapters, which I have two of. 
One driving a cm11a interface to talk to C10 stuff, and one driving a 
ups.

Thank you Anssi. Take care and stay well.

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

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

#248671

On Thursday, 2 June 2022 10:39:33 EDT gene heskett wrote:
> On Thursday, 2 June 2022 04:08:45 EDT Anssi Saari wrote:
> > gene heskett <gheskett@shentel.net> writes:
> > > Do I have to reset those perms everytime I'm forced to reboot,
> > > which
> > > is usually in 5 to 10 days. Or is there someplace in
> > > /lib/udev/rules.d where I can fix this until the next udev update?
> > 
> > It seems almost certain the permissions for /dev/ttyUSB* won't stick,
> > unless you fix them with udev rules (or some other means but udev's
> > the tool for the job in my opinion).
> > 
> > Do you really want to set all ttyUSB* to 777? Not 666 or 660 for
> > example? The usual way is to apply a udev rule to a specific USB
> > product and vendor ID which you can get from lsusb. But to change
> > permissions on device files I think you can do
> > 
> > KERNEL=="ttyUSB*", MODE="0777"
> > 
> > in a udev rule file.
> 
> /dev/ttyUSB* seems to only apply to seriel adapters, which I have two
> of. One driving a cm11a interface to talk to C10 stuff, and one
> driving a ups.
> 
> Thank you Anssi. Take care and stay well.
> 
> Cheers, Gene Heskett.


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

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

#248672

On Thursday, 2 June 2022 10:39:33 EDT gene heskett wrote:
> On Thursday, 2 June 2022 04:08:45 EDT Anssi Saari wrote:
> > gene heskett <gheskett@shentel.net> writes:
> > > Do I have to reset those perms everytime I'm forced to reboot,
> > > which
> > > is usually in 5 to 10 days. Or is there someplace in
> > > /lib/udev/rules.d where I can fix this until the next udev update?
> > 
> > It seems almost certain the permissions for /dev/ttyUSB* won't stick,
> > unless you fix them with udev rules (or some other means but udev's
> > the tool for the job in my opinion).
> > 
> > Do you really want to set all ttyUSB* to 777? Not 666 or 660 for
> > example? The usual way is to apply a udev rule to a specific USB
> > product and vendor ID which you can get from lsusb. But to change
> > permissions on device files I think you can do
> > 
> > KERNEL=="ttyUSB*", MODE="0777"
> > 
> > in a udev rule file.
> 
> /dev/ttyUSB* seems to only apply to seriel adapters, which I have two
> of. One driving a cm11a interface to talk to C10 stuff, and one
> driving a ups.

Darn typus, that s/b X10 above, not C10. Short/fat ancient finger 
syndrome.

> Thank you Anssi. Take care and stay well.
> 
> Cheers, Gene Heskett.


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

[toc] | [prev] | [standalone]

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

csiph-web