Re: Recommendations for data layout in case of multiple machines (Was: Re: trying to install bullseye for about 25th time)
Hello, On Fri, Jun 10, 2022 at 06:30:18PM +0200, Linux-Fan wrote: > Andy Smith writes: > > It's a way of working that's served me well for about 25 years. It's > > hard to imagine going back to having data spread all over the place. > > What do you use as your file server? Is it running 24/7 or started as needed? Just another Debian machine, which does run all the time. I realise that is not an option for everyone and is probably a big / excessive step for someone who only has one machine. At first I only did it because I'm a nerd. Over time, lots more machines and lots more uses for the things on the fileserver. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Recommendations for data layout in case of multiple machines (Was: Re: trying to install bullseye for about 25th time)
Andy Smith writes: Hello, On Thu, Jun 09, 2022 at 11:30:26AM -0400, rhkra...@gmail.com wrote: > For Gene, he could conceivably just rename the RAID setup that he has > mounted > under /home to some new top level mountpoint. (Although he probably has > some > scripts or similar stuff that looks for stuff in /home/ that > would > need to be modifed. For anyone with a number of machines, like Gene, there is a lot to be said for having one be in the role of file server. - One place to have a ton of storage, which isn't a usual role for a simple desktop daily driver machine. I have always wondered about this. Back when I bought a new PC I got that suggestion, too (cf. thread at https://lists.debian.org/debian-user/2020/10/msg00037.html). All things considered, I ended up with _one_ workstation to address desktop and storage uses together for the main reason that whenever I work on my "daily driver". I also need the files hence either power on and maintain two machines all of the time vs. having just one machine for the purpose? - One place to back up. - Access from anywhere you want. - Easier to keep your other machines up to date without worrying about all the precious data on your fileserver. Blow them away completely if you like. Be more free to experiment. These points make a lot of sense and that is basically how I am operating, too. One central keeper of data and multiple satellite machines :) I factor out backups to some extent in order to explicitly store copies across multiple machines and some of them "offline" as to resist modern threats of "data encryption trojans". Also, I have been following rhkramer's suggestion of storing important data outside of /home and I can tell it has served me well. My main consideration for doing this is to separate automatically generated program data (such as .cache, .wine and other typical $HOME inhabitants) from _my_ actual data. I still backup selected parts of $HOME e.g. the ~/.mozilla directory for Firefox settings etc. It's a way of working that's served me well for about 25 years. It's hard to imagine going back to having data spread all over the place. What do you use as your file server? Is it running 24/7 or started as needed? Thanks in advance Linux-Fan öö [...] pgptZmlQKdJhL.pgp Description: PGP signature
Re: trying to install bullseye for about 25th time.
On 2022-06-10 at 02:54, gene heskett wrote: > On Friday, 10 June 2022 00:22:53 EDT David Wright wrote: >> >> On Thu 09 Jun 2022 at 15:44:48 (-0400), gene heskett wrote: >>> Here is that partitioner menu snapshot, obtained by a network >>> ssh login, smunched to 81kb base-64'd. Showing that d-i did not >>> even recognize the disk I want to use for this new install. >>> >>> So how & what do I do to this virgin disk to make the d-i >>> recognize it so I can install to it? >> >> Well, you already know what I would do as it's been posted on this >> list before: partition it with my personal favourite, gdisk. >> >> But before I started, I would list /dev/disk/ to checkout all the >> installed disks, and their correspondence with the /dev/sd* or >> /dev/nvme0n* names. This avoid's mick's problem. >> >> I'd then write a GPT-style partition table, and the partitions I >> wanted, create the EFI partition, and change the names of the other >> partitions to my requirements. (All my disks are named, and the >> partition LABELs and PARTLABELs are based on that name.) >> >> But I haven't used LVMs, and their users might have a different >> strategy. > > I had some nightmares with LVM back in its younger days, and have > shied away from it since. But I'd assume its more stable now than it > was in ext3 days long ago. I've built my systems with all partitions (except those which, for boot reasons, inherently cannot be) on LVM on top of mdraid, doing the partitioning in d-i, for at least a decade now - and I cannot recall having had a single problem that could trace back to LVM. (Though that boot-reasons exception can be a bit of a doozy.) FWIMBW. -- 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: trying to install bullseye for about 25th time.
On Friday, 10 June 2022 00:22:53 EDT David Wright wrote: > On Thu 09 Jun 2022 at 15:44:48 (-0400), gene heskett wrote: > > On Thursday, 9 June 2022 11:04:15 EDT David Wright wrote: > > > On Thu 09 Jun 2022 at 03:46:12 (-0400), gene heskett wrote: > > > > On Thursday, 9 June 2022 00:33:33 EDT David Wright wrote: > > > > > On Tue 07 Jun 2022 at 16:24:02 (-0400), gene heskett wrote: > > > > > > On Tuesday, 7 June 2022 15:16:16 EDT Andrew M.A. Cater wrote: > > > > > > > On Tue, Jun 07, 2022 at 02:17:08PM -0400, gene heskett wrote: > > > > > I always install my systems in this manner from my normal > > > > > workstation. > > > > > > > > This IS my normal workstation. But I imagine that I could reverse > > > > the > > > > path from one of my Dells dedicated to a task. Only one has a > > > > comfy > > > > chair though, the one normally running my biggest milling > > > > machine, > > > > out in the garage. I'll take my coffee cup out and try this from > > > > there. > > > > > > Unsurprisingly, I use the second most convenient machine to install > > > onto that one. In addition, I lose the benefit of apt-cacher-ng for > > > that particular installation process. If I'm installing a new > > > release, > > > then I save the normal cache's contents, and later import all its > > > .deb > > > files into apt-cacher-ng on my workstation's new installation. > > > > > > One more convenience of installing like this is that you can have > > > the > > > release notes, your own aide-memoires, and other reference > > > documents, > > > open on the same machine while you're running the installer. > > > > Here is that partitioner menu snapshot, obtained by a network ssh > > login, smunched to 81kb base-64'd. Showing that d-i did not even > > recognize the disk I want to use for this new install. > > > > So how & what do I do to this virgin disk to make the d-i recognize > > it so I can install to it? > > Well, you already know what I would do as it's been posted on this > list before: partition it with my personal favourite, gdisk. > > But before I started, I would list /dev/disk/ to checkout all the > installed disks, and their correspondence with the /dev/sd* or > /dev/nvme0n* names. This avoid's mick's problem. > > I'd then write a GPT-style partition table, and the partitions > I wanted, create the EFI partition, and change the names of > the other partitions to my requirements. (All my disks are named, > and the partition LABELs and PARTLABELs are based on that name.) > > But I haven't used LVMs, and their users might have a different > strategy. > I had some nightmares with LVM back in its younger days, and have shied away from it since. But I'd assume its more stable now than it was in ext3 days long ago. > 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
Re: trying to install bullseye for about 25th time.
On Thu 09 Jun 2022 at 03:22:56 (-0400), Felix Miata wrote: > gene heskett composed on 2022-06-09 02:59 (UTC-0400): > > > Are you saying that I can partition this new drive with gparted and make > > the d-i use that? That would be the holy grail if so. > > This possibility became reality in antiquity. I never would have completed my > first Debian installation attempt if this were not the case. I can't remember > the > last Gnu/Linux installer I ran across that didn't have this capability. Unlike > David, who /usually/ partitions prior to starting up the Debian installer, I > *always* do. Only one partitioner is ever used on any of my partitionable > media. I > usually format first too, including any swap partition. Actually, I haven't partitioned in the installer since the mid-1990s, and back then, I would have written the first partition with DOS6.22, so that it could set a disk geometry satisfactory to itself. These were dual-boot machines, sort of, in that they booted linux from DOS's config.sys using loadlin IIRC. "I always prefer to …" means that I do something as a considered choice, a preference, rather than habit, instruction, or whatever. Others might advise some other course (eg Andrew, with LVM). Perhaps it's rather British. Cheers, David.
Re: trying to install bullseye for about 25th time.
On Thu 09 Jun 2022 at 15:44:48 (-0400), gene heskett wrote: > On Thursday, 9 June 2022 11:04:15 EDT David Wright wrote: > > On Thu 09 Jun 2022 at 03:46:12 (-0400), gene heskett wrote: > > > On Thursday, 9 June 2022 00:33:33 EDT David Wright wrote: > > > > On Tue 07 Jun 2022 at 16:24:02 (-0400), gene heskett wrote: > > > > > On Tuesday, 7 June 2022 15:16:16 EDT Andrew M.A. Cater wrote: > > > > > > On Tue, Jun 07, 2022 at 02:17:08PM -0400, gene heskett wrote: > > > > I always install my systems in this manner from my normal > > > > workstation. > > > > > > This IS my normal workstation. But I imagine that I could reverse the > > > path from one of my Dells dedicated to a task. Only one has a comfy > > > chair though, the one normally running my biggest milling machine, > > > out in the garage. I'll take my coffee cup out and try this from > > > there. > > > > Unsurprisingly, I use the second most convenient machine to install > > onto that one. In addition, I lose the benefit of apt-cacher-ng for > > that particular installation process. If I'm installing a new release, > > then I save the normal cache's contents, and later import all its .deb > > files into apt-cacher-ng on my workstation's new installation. > > > > One more convenience of installing like this is that you can have the > > release notes, your own aide-memoires, and other reference documents, > > open on the same machine while you're running the installer. > > > Here is that partitioner menu snapshot, obtained by a network ssh login, > smunched to 81kb base-64'd. Showing that d-i did not even recognize the > disk I want to use for this new install. > > So how & what do I do to this virgin disk to make the d-i recognize it so > I can install to it? Well, you already know what I would do as it's been posted on this list before: partition it with my personal favourite, gdisk. But before I started, I would list /dev/disk/ to checkout all the installed disks, and their correspondence with the /dev/sd* or /dev/nvme0n* names. This avoid's mick's problem. I'd then write a GPT-style partition table, and the partitions I wanted, create the EFI partition, and change the names of the other partitions to my requirements. (All my disks are named, and the partition LABELs and PARTLABELs are based on that name.) But I haven't used LVMs, and their users might have a different strategy. Cheers, David.
Re: trying to install bullseye for about 25th time.
On Thursday, 9 June 2022 11:04:15 EDT David Wright wrote: > On Thu 09 Jun 2022 at 03:46:12 (-0400), gene heskett wrote: > > On Thursday, 9 June 2022 00:33:33 EDT David Wright wrote: > > > On Tue 07 Jun 2022 at 16:24:02 (-0400), gene heskett wrote: > > > > On Tuesday, 7 June 2022 15:16:16 EDT Andrew M.A. Cater wrote: > > > > > On Tue, Jun 07, 2022 at 02:17:08PM -0400, gene heskett wrote: > > > I always install my systems in this manner from my normal > > > workstation. > > > > This IS my normal workstation. But I imagine that I could reverse the > > path from one of my Dells dedicated to a task. Only one has a comfy > > chair though, the one normally running my biggest milling machine, > > out in the garage. I'll take my coffee cup out and try this from > > there. > > Unsurprisingly, I use the second most convenient machine to install > onto that one. In addition, I lose the benefit of apt-cacher-ng for > that particular installation process. If I'm installing a new release, > then I save the normal cache's contents, and later import all its .deb > files into apt-cacher-ng on my workstation's new installation. > > One more convenience of installing like this is that you can have the > release notes, your own aide-memoires, and other reference documents, > open on the same machine while you're running the installer. > > Cheers, > David. > > . Here is that partitioner menu snapshot, obtained by a network ssh login, smunched to 81kb base-64'd. Showing that d-i did not even recognize the disk I want to use for this new install. So how & what do I do to this virgin disk to make the d-i recognize it so I can install to 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
Re: trying to install bullseye for about 25th time.
On Thursday, 9 June 2022 11:03:52 EDT David Wright wrote: > On Thu 09 Jun 2022 at 03:31:30 (-0400), gene heskett wrote: > > On Thursday, 9 June 2022 00:34:28 EDT David Wright wrote: > > > On Wed 08 Jun 2022 at 14:04:44 (-0400), gene heskett wrote: > > > > On Wednesday, 8 June 2022 08:33:56 EDT rhkra...@gmail.com wrote: > > > > > Or exchange the memory card (if you have an appropriate card > > > > > reader > > > > > for (one of) your computer(s))? > > > > > > > > I do. but dragging the card out of the camera's, all of them, is > > > > betting Murphy is on vacation, the power surges seem to like to > > > > trash the cards. > > > > > > Turn the camera off first? > > > > I don't think thats enough, Cannon, Nikon and Olympus (I have one of > > each) seem to power the card even when the mechanicals are turned > > off, so removing the battery first might be safe. All 3 have to be > > turned on before digikam can access them, but the card contacts are > > so buried I can't verify socket power. The Cannon is the only one > > that hasn't destroyed its original card and its usb socket is both > > fast and dependable, the usb socket is worn out on the other two. > > Its also the only one with a removable to recharge lithium battery. > > The other 2 have a quad of AA's in them. That remove to recharge is > > a pita, as the recharge takes 8 hours. And no one stocks that > > battery so you can have a ready spare. The cannon takes the best > > pix, but that rules it out for use by a wedding photog unless he's > > carrying a second, fully charged backup. Thats all immaterial to > > this though. > > That's remarkable. Do the cameras have real on/off switches, or are > they just soft? That said, my mobiles have never given me problems > with removing their cards, even though their on/off switches are soft. > IDK for sure, David, I'm going by the clue which is that I can remove the card, import to digikam from a reader, put the card back in the camera, turn the camera back on and the camera will not recognize it again, but I can put tha card back in the reader, and its all there, back in the camera, its not recognized again. In 2 earlier cameras, a new card it had no problems recognizing. Thats my clue. The cannons usb port is still functioning so the card has only been out of it once, before digikam grew a cannon driver with the buster release. How I interpret that clue is driven by my electronics troubleshooting history which starts in about 1950 when I quit school and went to work as a tech. That fed me well for the next 52 years, and still does. Thank you David. > 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
Re: trying to install bullseye for about 25th time.
On Thursday, 9 June 2022 11:05:27 EDT David Wright wrote: > On Thu 09 Jun 2022 at 06:04:08 (-0400), gene heskett wrote: > > On Thursday, 9 June 2022 04:18:04 EDT Andrew M.A. Cater wrote: > > > On Thu, Jun 09, 2022 at 02:59:43AM -0400, gene heskett wrote: > > > > On Thursday, 9 June 2022 00:31:55 EDT David Wright wrote: > > > > > On Tue 07 Jun 2022 at 16:07:13 (-0400), gene heskett wrote: > > > > > > On Tuesday, 7 June 2022 15:03:41 EDT gene heskett wrote: > > > > > > > On Tuesday, 7 June 2022 14:35:50 EDT David Wright wrote: > > > > > > > > On Tue 07 Jun 2022 at 14:17:08 (-0400), gene heskett wrote: > > > > > > The only way I know how to do that is take a screen shot with > > > > > > my > > > > > > camera. But thats not possible when running the D-I cuz w/o > > > > > > gimp, > > > > > > its at least 5 megs bigger than the server will accept. BTDT. > > > > > > > > > > I don't see why you need a screenshot to post the name(s) of > > > > > the > > > > > > > > > > disk(s) in the partitioner menu. It's just one line per disk, like: > > > > >SCSI1 (0,0,0) (sda) - 500.1 GB ATA ST350AA > > > > > > > > > > taken from the listing posted in: > > > > > https://lists.debian.org/debian-user/2022/06/msg00055.html > > > > > > > > > > > > > > I could label it, but the partitioner doesn't do > > > > > > > > > labels. > > > > > > > > > This drive is new, and has not anything written to it. > > > > > > > > > > > > > > > > Really? Which partitioner is that? > > > > > > > > > > > > The one in the D-I. > > > > > > > > > > The d-i partitioner lists PARTLABELs, as the cited listing showed: > > > > > BIOS boot pa/BullBoot/Linux swap/Viva-A/Viva-B/Viva-Home > > > > Andy, What good is a "partlabel" when it does not tell me which drive > > by the drives own readily found name as displayed by dmesg after a > > normal boot? With this drive showing up as ata-5 in dmesg, but > > somehow udev calls it /dev/sdb is confusing as can be. How the h--- > > does a drive plugged into ata-5 on the mobo, get to be named sdb > > when there are 8 other drives in front of it, 4 of them on a > > different controller in the discovery process? > > Come on, we've known for years that the /dev/sdX names for disks are > as good as random. On some machines, you can change the lettering of > their internal drives just by inserting USB sticks at boot. > > > I've zero guarantees that the d-i boot will detect THIS drive I want > > to use, the same as it did for an 11-1 install which generates the > > dmesg I am reading. The d-i shoots itself in the foot with excellent > > aim in this regard. > > For some reason, you won't show what the d-i partitioner /does/ call > it (assuming you're going to partition it with that, which I wouldn't). > > And the d-i will wind up doing a format on the raid10, destroying 6 > > month work, I'll have to reinvent. It did it unfailingly for many > > previous installs, because if I removed brltty, it would not boot > > past not find it in the reboot, which meant the only way I could > > reboot was to re-install yet again. > > I've already posted how to ensure that can't happen, by telling the > d-i not to use the raid10 stuff when installing Debian, and setting up > your real /home later. > > > To the d-i, my history is of no concern, do NOT forget that I've > > already done 25 damned installs trying to save my work. > > Could we! > > > I finally did figure out > > how to silence orca, without destroying the ability to reboot, but > > the > > uptime is 5 to 7 days. All because of seagates f-ing experiment with > > helium filled shingled drives which failed well within a year because > > they thought they could seal them well enough to keep the helium in > > them. > > > > If in 1960, a bank of monel metal bottles with 2" thick walls, went > > from 7200 psi to 4800 psi because it leaks thru 2" of monel from > > midnight to 7:30 when the day shift clocked in. That leakage cost > > the laboratory I was working for around $10,000 a day, we were > > validating the ullage tank presuure regulators for the Atlas missles > > that probably gave John Glen his first ride. > > > > Now seagate thinks they can keep it in a teeny hard drive so they can > > lower the flying height of the heads? The insanity in Oklahoma City > > knows no bounds. And I am out of the spinning rust camp forever, > > SSD's are faster AND far more dependable. > > > > I now have around 6 months work stored on that all SSD raid, and I'll > > be damned if I'll take a chance of losing it. But I'm convinced that > > I have to do one more install, clean of brltty and orca, to get > > uptimes past 8 days. I have repeatedly asked how to get rid of it > > totally, several times on this list and have yet to be advised of a > > way to remove it that doesn't destroy the system, the dependency's > > removed cascade all the way back to libc6. Tying a specialty > > function that deep into the OS that it cannot be removed, only > > half-a--ed disabled and
Re: trying to install bullseye for about 25th time.
Hello, On Thu, Jun 09, 2022 at 11:30:26AM -0400, rhkra...@gmail.com wrote: > For Gene, he could conceivably just rename the RAID setup that he has mounted > under /home to some new top level mountpoint. (Although he probably has some > scripts or similar stuff that looks for stuff in /home/ that would > need to be modifed. For anyone with a number of machines, like Gene, there is a lot to be said for having one be in the role of file server. - One place to have a ton of storage, which isn't a usual role for a simple desktop daily driver machine. - One place to back up. - Access from anywhere you want. - Easier to keep your other machines up to date without worrying about all the precious data on your fileserver. Blow them away completely if you like. Be more free to experiment. It's a way of working that's served me well for about 25 years. It's hard to imagine going back to having data spread all over the place. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: trying to install bullseye for about 25th time.
I want to make a comment on this thread that is at least a little bit (maybe a lot) off point, it is more a suggestion on what might be a better way next time (although it could be done this time with a little work, I believe). Because I don't see a good place to put this comment in context, I'm deleting almost all of the quoted material and then top posting. I avoid /home as much as I possibly (or at least reasonably) can. I did it for different reasons than the reason I'm going to suggest it now, so I won't go into those, at least for now (well, ok, basically, I got frustrated once when I did something that I thought was innocent and wiped out all my "real user data" (that is things like my documents, code, photos, etc.) when I did something dumb and wiped out home. I would suggest moving (or renaming) all of your "real user data" (for Gene that would presumably include CNC instructions for various things he makes on his machinery) -- put all of that in a new top level directory (mine, on different computers are variations of /nn). Let the system use /home/ for whatever it wants, and don't worry about it if it gets lost. Doing what I describe might require some gymnastics with respect to keeping things like mail out of /home, but I did that. And various databases and backups seem to get created in /home/, but it seems to be stuff that can be recreated and maybe is recreated automatically under some circumstances if it disappears. For Gene, he could conceivably just rename the RAID setup that he has mounted under /home to some new top level mountpoint. (Although he probably has some scripts or similar stuff that looks for stuff in /home/ that would need to be modifed. FWIW On Thursday, June 09, 2022 06:04:08 AM gene heskett wrote: ---< deleted >---
Re: trying to install bullseye for about 25th time.
On Thu 09 Jun 2022 at 06:04:08 (-0400), gene heskett wrote: > On Thursday, 9 June 2022 04:18:04 EDT Andrew M.A. Cater wrote: > > On Thu, Jun 09, 2022 at 02:59:43AM -0400, gene heskett wrote: > > > On Thursday, 9 June 2022 00:31:55 EDT David Wright wrote: > > > > On Tue 07 Jun 2022 at 16:07:13 (-0400), gene heskett wrote: > > > > > On Tuesday, 7 June 2022 15:03:41 EDT gene heskett wrote: > > > > > > On Tuesday, 7 June 2022 14:35:50 EDT David Wright wrote: > > > > > > > On Tue 07 Jun 2022 at 14:17:08 (-0400), gene heskett wrote: > > > > > The only way I know how to do that is take a screen shot with my > > > > > camera. But thats not possible when running the D-I cuz w/o gimp, > > > > > its at least 5 megs bigger than the server will accept. BTDT. > > > > > > > > I don't see why you need a screenshot to post the name(s) of the > > > > > > > > disk(s) in the partitioner menu. It's just one line per disk, like: > > > >SCSI1 (0,0,0) (sda) - 500.1 GB ATA ST350AA > > > > > > > > taken from the listing posted in: > > > > https://lists.debian.org/debian-user/2022/06/msg00055.html > > > > > > > > > > > > I could label it, but the partitioner doesn't do labels. > > > > > > > > This drive is new, and has not anything written to it. > > > > > > > > > > > > > > Really? Which partitioner is that? > > > > > > > > > > The one in the D-I. > > > > > > > > The d-i partitioner lists PARTLABELs, as the cited listing showed: > > > > BIOS boot pa/BullBoot/Linux swap/Viva-A/Viva-B/Viva-Home > > Andy, What good is a "partlabel" when it does not tell me which drive by > the drives own readily found name as displayed by dmesg after a normal > boot? With this drive showing up as ata-5 in dmesg, but somehow udev > calls it /dev/sdb is confusing as can be. How the h--- does a drive > plugged into ata-5 on the mobo, get to be named sdb when there are 8 > other drives in front of it, 4 of them on a different controller in the > discovery process? Come on, we've known for years that the /dev/sdX names for disks are as good as random. On some machines, you can change the lettering of their internal drives just by inserting USB sticks at boot. > I've zero guarantees that the d-i boot will detect THIS drive I want to > use, the same as it did for an 11-1 install which generates the dmesg I > am reading. The d-i shoots itself in the foot with excellent aim in this > regard. For some reason, you won't show what the d-i partitioner /does/ call it (assuming you're going to partition it with that, which I wouldn't). > And the d-i will wind up doing a format on the raid10, destroying 6 month > work, I'll have to reinvent. It did it unfailingly for many previous > installs, because if I removed brltty, it would not boot past not find it > in the reboot, which meant the only way I could reboot was to re-install > yet again. I've already posted how to ensure that can't happen, by telling the d-i not to use the raid10 stuff when installing Debian, and setting up your real /home later. > To the d-i, my history is of no concern, do NOT forget that I've already > done 25 damned installs trying to save my work. Could we! > I finally did figure out > how to silence orca, without destroying the ability to reboot, but the > uptime is 5 to 7 days. All because of seagates f-ing experiment with > helium filled shingled drives which failed well within a year because > they thought they could seal them well enough to keep the helium in them. > > If in 1960, a bank of monel metal bottles with 2" thick walls, went from > 7200 psi to 4800 psi because it leaks thru 2" of monel from midnight to > 7:30 when the day shift clocked in. That leakage cost the laboratory I > was working for around $10,000 a day, we were validating the ullage tank > presuure regulators for the Atlas missles that probably gave John Glen > his first ride. > > Now seagate thinks they can keep it in a teeny hard drive so they can > lower the flying height of the heads? The insanity in Oklahoma City knows > no bounds. And I am out of the spinning rust camp forever, SSD's are > faster AND far more dependable. > > I now have around 6 months work stored on that all SSD raid, and I'll be > damned if I'll take a chance of losing it. But I'm convinced that I have > to do one more install, clean of brltty and orca, to get uptimes past 8 > days. I have repeatedly asked how to get rid of it totally, several times > on this list and have yet to be advised of a way to remove it that > doesn't destroy the system, the dependency's removed cascade all the way > back to libc6. Tying a specialty function that deep into the OS that it > cannot be removed, only half-a--ed disabled and killing the uptime > because it leaves a wild write someplace slowly destroying the system is > inexcusable. > > Thats bs, and I'm fresh out of patience. > > There should be a procedure to fix this, but the procedure so far is to > ignore my requests for help in this
Re: trying to install bullseye for about 25th time.
On Thu 09 Jun 2022 at 03:46:12 (-0400), gene heskett wrote: > On Thursday, 9 June 2022 00:33:33 EDT David Wright wrote: > > On Tue 07 Jun 2022 at 16:24:02 (-0400), gene heskett wrote: > > > On Tuesday, 7 June 2022 15:16:16 EDT Andrew M.A. Cater wrote: > > > > On Tue, Jun 07, 2022 at 02:17:08PM -0400, gene heskett wrote: > > I always install my systems in this manner from my normal workstation. > > This IS my normal workstation. But I imagine that I could reverse the > path from one of my Dells dedicated to a task. Only one has a comfy chair > though, the one normally running my biggest milling machine, out in the > garage. I'll take my coffee cup out and try this from there. Unsurprisingly, I use the second most convenient machine to install onto that one. In addition, I lose the benefit of apt-cacher-ng for that particular installation process. If I'm installing a new release, then I save the normal cache's contents, and later import all its .deb files into apt-cacher-ng on my workstation's new installation. One more convenience of installing like this is that you can have the release notes, your own aide-memoires, and other reference documents, open on the same machine while you're running the installer. Cheers, David.
Re: trying to install bullseye for about 25th time.
On Thu 09 Jun 2022 at 03:31:30 (-0400), gene heskett wrote: > On Thursday, 9 June 2022 00:34:28 EDT David Wright wrote: > > On Wed 08 Jun 2022 at 14:04:44 (-0400), gene heskett wrote: > > > On Wednesday, 8 June 2022 08:33:56 EDT rhkra...@gmail.com wrote: > > > > Or exchange the memory card (if you have an appropriate card reader > > > > for (one of) your computer(s))? > > > > > > I do. but dragging the card out of the camera's, all of them, is > > > betting Murphy is on vacation, the power surges seem to like to > > > trash the cards. > > Turn the camera off first? > > > I don't think thats enough, Cannon, Nikon and Olympus (I have one of > each) seem to power the card even when the mechanicals are turned off, so > removing the battery first might be safe. All 3 have to be turned on > before digikam can access them, but the card contacts are so buried I > can't verify socket power. The Cannon is the only one that hasn't > destroyed its original card and its usb socket is both fast and > dependable, the usb socket is worn out on the other two. Its also the > only one with a removable to recharge lithium battery. The other 2 have > a quad of AA's in them. That remove to recharge is a pita, as the > recharge takes 8 hours. And no one stocks that battery so you can have a > ready spare. The cannon takes the best pix, but that rules it out for use > by a wedding photog unless he's carrying a second, fully charged backup. > Thats all immaterial to this though. That's remarkable. Do the cameras have real on/off switches, or are they just soft? That said, my mobiles have never given me problems with removing their cards, even though their on/off switches are soft. Cheers, David.
Re: trying to install bullseye for about 25th time.
On Thursday, 9 June 2022 04:18:04 EDT Andrew M.A. Cater wrote: > On Thu, Jun 09, 2022 at 02:59:43AM -0400, gene heskett wrote: > > On Thursday, 9 June 2022 00:31:55 EDT David Wright wrote: > > > On Tue 07 Jun 2022 at 16:07:13 (-0400), gene heskett wrote: > > > > On Tuesday, 7 June 2022 15:03:41 EDT gene heskett wrote: > > > > > On Tuesday, 7 June 2022 14:35:50 EDT David Wright wrote: > > > > > > On Tue 07 Jun 2022 at 14:17:08 (-0400), gene heskett wrote: > > > > > > > But I've put another drive in, that I want to install a non > > > > > > > efi > > > > > > > system on too. > > > > > > > > > > > > > > The installer does not identify it by the same names, so > > > > > > > how do > > > > > > > I > > > > > > > install to this drive w/o touching any of the other 6 > > > > > > > samsung > > > > > > > EVO > > > > > > > series drives. > > > > > > > > > > > > > > I've never learn to love gnome, and the kde5 you offer is > > > > > > > buggier > > > > > > > than a 10 day old road kill in August, so this time is a > > > > > > > text > > > > > > > install to see if I can put TDE in for a desktop. > > > > > > > > > > > > > > How do I proceed? The partitioner does not identify the > > > > > > > drives > > > > > > > found > > > > > > > adequatly. The drive is plugged into the mainboard > > > > > > > controller, > > > > > > > I > > > > > > > think to port 5 of 6. > > > > > > > > > > > > Well, you post what it /does/ display. Then the experts here > > > > > > can > > > > > > make > > > > > > educated guesses, rather than just guessing. > > > > > > > > The only way I know how to do that is take a screen shot with my > > > > camera. But thats not possible when running the D-I cuz w/o gimp, > > > > its at least 5 megs bigger than the server will accept. BTDT. > > > > > > I don't see why you need a screenshot to post the name(s) of the > > > > > > disk(s) in the partitioner menu. It's just one line per disk, like: > > >SCSI1 (0,0,0) (sda) - 500.1 GB ATA ST350AA > > > > > > taken from the listing posted in: > > > https://lists.debian.org/debian-user/2022/06/msg00055.html > > > > > > > > > > I could label it, but the partitioner doesn't do labels. > > > > > > > This drive is new, and has not anything written to it. > > > > > > > > > > > > Really? Which partitioner is that? > > > > > > > > The one in the D-I. > > > > > > The d-i partitioner lists PARTLABELs, as the cited listing showed: > > > BIOS boot pa/BullBoot/Linux swap/Viva-A/Viva-B/Viva-Home Andy, What good is a "partlabel" when it does not tell me which drive by the drives own readily found name as displayed by dmesg after a normal boot? With this drive showing up as ata-5 in dmesg, but somehow udev calls it /dev/sdb is confusing as can be. How the h--- does a drive plugged into ata-5 on the mobo, get to be named sdb when there are 8 other drives in front of it, 4 of them on a different controller in the discovery process? I've zero guarantees that the d-i boot will detect THIS drive I want to use, the same as it did for an 11-1 install which generates the dmesg I am reading. The d-i shoots itself in the foot with excellent aim in this regard. > > > > > > But as your disk is new, I don't know what those PARTLABELs would > > > be > > > set to. If you booted a bullseye installation to capture the dmesg > > > you quoted, then it might be simplest to partition the new disk at > > > that time. You get the most flexibility that way. (I always prefer > > > to partition my disks before I let the d-i loose on them.) > > > > > > > > > I was rereading Andrew's reply in the other thread, and his > > > > > > appeal > > > > > > "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." > > > > > > > > > > > > And I was thinking, that's not enough. We only hear a summary > > > > > > of > > > > > > what > > > > > > you think you're doing. I had a hypothesis for why you > > > > > > couldn't > > > > > > avoid > > > > > > the speech synthesiser, but it would require knowing every > > > > > > keystroke > > > > > > you use from powering on the machine. No chance of that. > > > > > > > > Not to mention it would be TL,DR to most. > > > > > > It can hardly be /too/ long, as you claim that the speech > > > synthesiser > > > starts yakking almost straightaway. > > > > That, with only the keyboard and mouse plus a small b/w laser printer > > plugged in, did not occur this time giving me hope it won't install > > that crap. There is now, perhaps driven by my troubles, a manu > > selection for that I purposely have not gone near. > > > > Are you saying that I can partition this new drive with gparted and > > make the d-i use that? That would be the holy grail if so. Question > > then: Since /home
Re: trying to install bullseye for about 25th time.
On Thu, Jun 09, 2022 at 02:59:43AM -0400, gene heskett wrote: > On Thursday, 9 June 2022 00:31:55 EDT David Wright wrote: > > On Tue 07 Jun 2022 at 16:07:13 (-0400), gene heskett wrote: > > > On Tuesday, 7 June 2022 15:03:41 EDT gene heskett wrote: > > > > On Tuesday, 7 June 2022 14:35:50 EDT David Wright wrote: > > > > > On Tue 07 Jun 2022 at 14:17:08 (-0400), gene heskett wrote: > > > > > > But I've put another drive in, that I want to install a non efi > > > > > > system on too. > > > > > > > > > > > > The installer does not identify it by the same names, so how do > > > > > > I > > > > > > install to this drive w/o touching any of the other 6 samsung > > > > > > EVO > > > > > > series drives. > > > > > > > > > > > > I've never learn to love gnome, and the kde5 you offer is > > > > > > buggier > > > > > > than a 10 day old road kill in August, so this time is a text > > > > > > install to see if I can put TDE in for a desktop. > > > > > > > > > > > > How do I proceed? The partitioner does not identify the drives > > > > > > found > > > > > > adequatly. The drive is plugged into the mainboard controller, > > > > > > I > > > > > > think to port 5 of 6. > > > > > > > > > > Well, you post what it /does/ display. Then the experts here can > > > > > make > > > > > educated guesses, rather than just guessing. > > > > > > The only way I know how to do that is take a screen shot with my > > > camera. But thats not possible when running the D-I cuz w/o gimp, > > > its at least 5 megs bigger than the server will accept. BTDT. > > > > I don't see why you need a screenshot to post the name(s) of the > > disk(s) in the partitioner menu. It's just one line per disk, like: > > > >SCSI1 (0,0,0) (sda) - 500.1 GB ATA ST350AA > > > > taken from the listing posted in: > > https://lists.debian.org/debian-user/2022/06/msg00055.html > > > > > > > > I could label it, but the partitioner doesn't do labels. > > > > > > This drive is new, and has not anything written to it. > > > > > > > > > > Really? Which partitioner is that? > > > > > > The one in the D-I. > > > > The d-i partitioner lists PARTLABELs, as the cited listing showed: > > > > BIOS boot pa/BullBoot/Linux swap/Viva-A/Viva-B/Viva-Home > > > > But as your disk is new, I don't know what those PARTLABELs would be > > set to. If you booted a bullseye installation to capture the dmesg > > you quoted, then it might be simplest to partition the new disk at > > that time. You get the most flexibility that way. (I always prefer > > to partition my disks before I let the d-i loose on them.) > > > > > > > I was rereading Andrew's reply in the other thread, and his > > > > > appeal > > > > > "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." > > > > > > > > > > And I was thinking, that's not enough. We only hear a summary of > > > > > what > > > > > you think you're doing. I had a hypothesis for why you couldn't > > > > > avoid > > > > > the speech synthesiser, but it would require knowing every > > > > > keystroke > > > > > you use from powering on the machine. No chance of that. > > > > > > Not to mention it would be TL,DR to most. > > > > It can hardly be /too/ long, as you claim that the speech synthesiser > > starts yakking almost straightaway. > > That, with only the keyboard and mouse plus a small b/w laser printer > plugged in, did not occur this time giving me hope it won't install that > crap. There is now, perhaps driven by my troubles, a manu selection for > that I purposely have not gone near. > > Are you saying that I can partition this new drive with gparted and make > the d-i use that? That would be the holy grail if so. Question then: > Since /home would be just a mount point for the raid10, how big does that > partition actually have to be? Is a single 4096k inode big enough? I > assume it will have to be big enough for it to contain /etc/skel. > > > Cheers, > > David. > > Thanks David. > > . > Partition the disk as all in one: that will set up points on LVM for all directories. Separately, tag the RAID as mounting at /home - job done. There won't _be_ anything in /home until a user is set up and you've already told it to use a preexisting /home. Partitioning it with gparted will complicate matters: UEFI will set up the ESP partition for itself anyway. 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 > > >
Re: trying to install bullseye for about 25th time.
On Thursday, 9 June 2022 03:22:56 EDT Felix Miata wrote: > gene heskett composed on 2022-06-09 02:59 (UTC-0400): > > Are you saying that I can partition this new drive with gparted and > > make the d-i use that? That would be the holy grail if so. > > This possibility became reality in antiquity. I never would have > completed my first Debian installation attempt if this were not the > case. I can't remember the last Gnu/Linux installer I ran across that > didn't have this capability. Unlike David, who /usually/ partitions > prior to starting up the Debian installer, I *always* do. Only one > partitioner is ever used on any of my partitionable media. I usually > format first too, including any swap partition. > > > Question then: > > Since /home would be just a mount point for the raid10, how big does > > that partition actually have to be? Is a single 4096k inode big > > enough? > A mount point isn't a partition. It's a directory purposed for mounting > a separate filesystem. The directory, and its inode consumption, goes > on the root filesystem. Thanks Felix. That clarifies 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
Re: trying to install bullseye for about 25th time.
On Thursday, 9 June 2022 00:33:33 EDT David Wright wrote: > On Tue 07 Jun 2022 at 16:24:02 (-0400), gene heskett wrote: > > On Tuesday, 7 June 2022 15:16:16 EDT Andrew M.A. Cater wrote: > > > On Tue, Jun 07, 2022 at 02:17:08PM -0400, gene heskett wrote: > > > > > > Fourth: Use the text mode expert install. > > > > I have so far, but powered off to bail out when I couldn't figure out > > what to do next. Before it wrote anything. > > > > > Document this step by step: write yourself a tasklist and tick off > > > each small step as it completes. > > > > > > As someone who has done, conservatively, 500 installs - many with > > > the > > > text mode installer - it is not as hard as you seem to make it > > > every > > > single time. But, without knowing at what step you fail and > > > precisely > > > what you see when you do fail - what error messages, what it's > > > telling > > > you and what steps you are thinking of taking BEFORE you take them, > > > I'm at a loss to know. > > > > The D-I needs to grow the capability to mount an otherwise unused > > drive, and store as png's, snapshots of the screen. That way no one > > can accuse me of copy/paste fibbing. I can also take screen shots > > but the list server, even if I could figure out how to get it out of > > the camera and submit them, would justifiably balk at the 5+ megs a > > pix that would be. > As you're using the advanced text d-i, it's very simple to take > screenshots that you can include in your posts. They will look very > much like the ones I post, because this is how I generate them. > > When you get to this screen: > > ┌┤ [?] Load installer components from CD > ├┐ │ > │ │ All components of the installer > needed to complete the install will be loaded │ │ automatically and > are not listed here. Some other (optional) installer │ │ > components are shown below. They are probably not necessary, but may > be │ │ interesting to some users. > │ │ > │ │ Note that if you select a > component that requires others, those components │ │ will also be > loaded.│ │ > > │ │ Installer components to load: > │ │ >│ … … …… … …… … …… … … > … … …… … …… … …… … …… … … │[ ] > nbd-modules-4.9.0-7-686-di: Network Block Device modules > ▒ │ │[*] network-console: Continue installation remotely using > SSH ▒ │ │[ ] ntfs-modules-4.9.0-7-686-di: NTFS > filesystem support ▒ │ … … …… … …… … …… > … …… … …… … …… … …… … …… … … > > │ > │ │ >│ │ > │ > └─ > ┘ > > select "network-console" as shown above. > > When the network has been configured, select this option from > the main menu: > > Continue installation remotely using SSH > > It will ask you to type (twice) a password, and then tell you how to > connect to the d-i from another machine: > > ┌┤ [!!] Continue installation remotely using SSH > ├┐ │ > │ │ > Start SSH│ │ To continue the > installation, please use an SSH client to connect to the IP │ │ > address 192.168.1.xxx fe80::xxx::: and log in as the > "installer"│ │ user. For example: > │ │ > │ │ssh > instal...@192.168.1.xxx > │ │ >│ │ The fingerprint of this SSH server's host key is: > │ │ > │ │ > SHA256:xxx > │ │ > │ │ Please check this carefully against the > fingerprint reported by your SSH client.│ │ >
Re: trying to install bullseye for about 25th time.
On Thursday, 9 June 2022 00:34:28 EDT David Wright wrote: > On Wed 08 Jun 2022 at 14:04:44 (-0400), gene heskett wrote: > > On Wednesday, 8 June 2022 08:33:56 EDT rhkra...@gmail.com wrote: > > > Or exchange the memory card (if you have an appropriate card reader > > > for (one of) your computer(s))? > > > > I do. but dragging the card out of the camera's, all of them, is > > betting Murphy is on vacation, the power surges seem to like to > > trash the cards. > Turn the camera off first? > I don't think thats enough, Cannon, Nikon and Olympus (I have one of each) seem to power the card even when the mechanicals are turned off, so removing the battery first might be safe. All 3 have to be turned on before digikam can access them, but the card contacts are so buried I can't verify socket power. The Cannon is the only one that hasn't destroyed its original card and its usb socket is both fast and dependable, the usb socket is worn out on the other two. Its also the only one with a removable to recharge lithium battery. The other 2 have a quad of AA's in them. That remove to recharge is a pita, as the recharge takes 8 hours. And no one stocks that battery so you can have a ready spare. The cannon takes the best pix, but that rules it out for use by a wedding photog unless he's carrying a second, fully charged backup. Thats all immaterial to this though. > Cheers, > David. Thanks 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
Re: trying to install bullseye for about 25th time.
gene heskett composed on 2022-06-09 02:59 (UTC-0400): > Are you saying that I can partition this new drive with gparted and make > the d-i use that? That would be the holy grail if so. This possibility became reality in antiquity. I never would have completed my first Debian installation attempt if this were not the case. I can't remember the last Gnu/Linux installer I ran across that didn't have this capability. Unlike David, who /usually/ partitions prior to starting up the Debian installer, I *always* do. Only one partitioner is ever used on any of my partitionable media. I usually format first too, including any swap partition. > Question then: > Since /home would be just a mount point for the raid10, how big does that > partition actually have to be? Is a single 4096k inode big enough? A mount point isn't a partition. It's a directory purposed for mounting a separate filesystem. The directory, and its inode consumption, goes on the root filesystem. -- 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: trying to install bullseye for about 25th time.
On Thursday, 9 June 2022 00:31:55 EDT David Wright wrote: > On Tue 07 Jun 2022 at 16:07:13 (-0400), gene heskett wrote: > > On Tuesday, 7 June 2022 15:03:41 EDT gene heskett wrote: > > > On Tuesday, 7 June 2022 14:35:50 EDT David Wright wrote: > > > > On Tue 07 Jun 2022 at 14:17:08 (-0400), gene heskett wrote: > > > > > But I've put another drive in, that I want to install a non efi > > > > > system on too. > > > > > > > > > > The installer does not identify it by the same names, so how do > > > > > I > > > > > install to this drive w/o touching any of the other 6 samsung > > > > > EVO > > > > > series drives. > > > > > > > > > > I've never learn to love gnome, and the kde5 you offer is > > > > > buggier > > > > > than a 10 day old road kill in August, so this time is a text > > > > > install to see if I can put TDE in for a desktop. > > > > > > > > > > How do I proceed? The partitioner does not identify the drives > > > > > found > > > > > adequatly. The drive is plugged into the mainboard controller, > > > > > I > > > > > think to port 5 of 6. > > > > > > > > Well, you post what it /does/ display. Then the experts here can > > > > make > > > > educated guesses, rather than just guessing. > > > > The only way I know how to do that is take a screen shot with my > > camera. But thats not possible when running the D-I cuz w/o gimp, > > its at least 5 megs bigger than the server will accept. BTDT. > > I don't see why you need a screenshot to post the name(s) of the > disk(s) in the partitioner menu. It's just one line per disk, like: > >SCSI1 (0,0,0) (sda) - 500.1 GB ATA ST350AA > > taken from the listing posted in: > https://lists.debian.org/debian-user/2022/06/msg00055.html > > > > > > I could label it, but the partitioner doesn't do labels. > > > > > This drive is new, and has not anything written to it. > > > > > > > > Really? Which partitioner is that? > > > > The one in the D-I. > > The d-i partitioner lists PARTLABELs, as the cited listing showed: > > BIOS boot pa/BullBoot/Linux swap/Viva-A/Viva-B/Viva-Home > > But as your disk is new, I don't know what those PARTLABELs would be > set to. If you booted a bullseye installation to capture the dmesg > you quoted, then it might be simplest to partition the new disk at > that time. You get the most flexibility that way. (I always prefer > to partition my disks before I let the d-i loose on them.) > > > > > I was rereading Andrew's reply in the other thread, and his > > > > appeal > > > > "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." > > > > > > > > And I was thinking, that's not enough. We only hear a summary of > > > > what > > > > you think you're doing. I had a hypothesis for why you couldn't > > > > avoid > > > > the speech synthesiser, but it would require knowing every > > > > keystroke > > > > you use from powering on the machine. No chance of that. > > > > Not to mention it would be TL,DR to most. > > It can hardly be /too/ long, as you claim that the speech synthesiser > starts yakking almost straightaway. That, with only the keyboard and mouse plus a small b/w laser printer plugged in, did not occur this time giving me hope it won't install that crap. There is now, perhaps driven by my troubles, a manu selection for that I purposely have not gone near. Are you saying that I can partition this new drive with gparted and make the d-i use that? That would be the holy grail if so. Question then: Since /home would be just a mount point for the raid10, how big does that partition actually have to be? Is a single 4096k inode big enough? I assume it will have to be big enough for it to contain /etc/skel. > Cheers, > David. Thanks 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
Re: trying to install bullseye for about 25th time.
On Wed 08 Jun 2022 at 14:04:44 (-0400), gene heskett wrote: > On Wednesday, 8 June 2022 08:33:56 EDT rhkra...@gmail.com wrote: > > Or exchange the memory card (if you have an appropriate card reader for > > (one of) your computer(s))? > > I do. but dragging the card out of the camera's, all of them, is betting > Murphy is on vacation, the power surges seem to like to trash the cards. Turn the camera off first? Cheers, David.
Re: trying to install bullseye for about 25th time.
On Tue 07 Jun 2022 at 16:24:02 (-0400), gene heskett wrote: > On Tuesday, 7 June 2022 15:16:16 EDT Andrew M.A. Cater wrote: > > On Tue, Jun 07, 2022 at 02:17:08PM -0400, gene heskett wrote: > > Fourth: Use the text mode expert install. > > I have so far, but powered off to bail out when I couldn't figure out > what to do next. Before it wrote anything. > > Document this step by step: write yourself a tasklist and tick off each > > small step as it completes. > > > > As someone who has done, conservatively, 500 installs - many with the > > text mode installer - it is not as hard as you seem to make it every > > single time. But, without knowing at what step you fail and precisely > > what you see when you do fail - what error messages, what it's telling > > you and what steps you are thinking of taking BEFORE you take them, > > I'm at a loss to know. > The D-I needs to grow the capability to mount an otherwise unused drive, > and store as png's, snapshots of the screen. That way no one can accuse > me of copy/paste fibbing. I can also take screen shots but the list > server, even if I could figure out how to get it out of the camera and > submit them, would justifiably balk at the 5+ megs a pix that would be. As you're using the advanced text d-i, it's very simple to take screenshots that you can include in your posts. They will look very much like the ones I post, because this is how I generate them. When you get to this screen: ┌┤ [?] Load installer components from CD ├┐ │ │ │ All components of the installer needed to complete the install will be loaded │ │ automatically and are not listed here. Some other (optional) installer │ │ components are shown below. They are probably not necessary, but may be │ │ interesting to some users. │ │ │ │ Note that if you select a component that requires others, those components │ │ will also be loaded. │ │ │ │ Installer components to load: │ │ │ … … …… … …… … …… … …… … …… … …… … …… … …… … … │[ ] nbd-modules-4.9.0-7-686-di: Network Block Device modules ▒ │ │[*] network-console: Continue installation remotely using SSH ▒ │ │[ ] ntfs-modules-4.9.0-7-686-di: NTFS filesystem support ▒ │ … … …… … …… … …… … …… … …… … …… … …… … …… … … │ │ │ │ │ │ └─┘ select "network-console" as shown above. When the network has been configured, select this option from the main menu: Continue installation remotely using SSH It will ask you to type (twice) a password, and then tell you how to connect to the d-i from another machine: ┌┤ [!!] Continue installation remotely using SSH ├┐ │ │ │Start SSH │ │ To continue the installation, please use an SSH client to connect to the IP │ │ address 192.168.1.xxx fe80::xxx::: and log in as the "installer"│ │ user. For example: │ │ │ │ssh instal...@192.168.1.xxx │ │ │ │ The fingerprint of this SSH server's host key is: │ │ │ │ SHA256:xxx │ │ │ │ Please check this carefully against the fingerprint reported by your SSH client.│ │ │ │
Re: trying to install bullseye for about 25th time.
On Tue 07 Jun 2022 at 16:07:13 (-0400), gene heskett wrote: > On Tuesday, 7 June 2022 15:03:41 EDT gene heskett wrote: > > On Tuesday, 7 June 2022 14:35:50 EDT David Wright wrote: > > > On Tue 07 Jun 2022 at 14:17:08 (-0400), gene heskett wrote: > > > > But I've put another drive in, that I want to install a non efi > > > > system on too. > > > > The installer does not identify it by the same names, so how do I > > > > install to this drive w/o touching any of the other 6 samsung EVO > > > > series drives. > > > > > > > > I've never learn to love gnome, and the kde5 you offer is buggier > > > > than a 10 day old road kill in August, so this time is a text > > > > install to see if I can put TDE in for a desktop. > > > > > > > > How do I proceed? The partitioner does not identify the drives > > > > found > > > > adequatly. The drive is plugged into the mainboard controller, I > > > > think to port 5 of 6. > > > > > > Well, you post what it /does/ display. Then the experts here can make > > > educated guesses, rather than just guessing. > > The only way I know how to do that is take a screen shot with my camera. > But thats not possible when running the D-I cuz w/o gimp, its at least 5 > megs bigger than the server will accept. BTDT. I don't see why you need a screenshot to post the name(s) of the disk(s) in the partitioner menu. It's just one line per disk, like: SCSI1 (0,0,0) (sda) - 500.1 GB ATA ST350AA taken from the listing posted in: https://lists.debian.org/debian-user/2022/06/msg00055.html > > > > I could label it, but the partitioner doesn't do labels. > > > > This drive is new, and has not anything written to it. > > > > > > Really? Which partitioner is that? > > The one in the D-I. The d-i partitioner lists PARTLABELs, as the cited listing showed: BIOS boot pa/BullBoot/Linux swap/Viva-A/Viva-B/Viva-Home But as your disk is new, I don't know what those PARTLABELs would be set to. If you booted a bullseye installation to capture the dmesg you quoted, then it might be simplest to partition the new disk at that time. You get the most flexibility that way. (I always prefer to partition my disks before I let the d-i loose on them.) > > > I was rereading Andrew's reply in the other thread, and his appeal > > > "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." > > > > > > And I was thinking, that's not enough. We only hear a summary of what > > > you think you're doing. I had a hypothesis for why you couldn't avoid > > > the speech synthesiser, but it would require knowing every keystroke > > > you use from powering on the machine. No chance of that. > > Not to mention it would be TL,DR to most. It can hardly be /too/ long, as you claim that the speech synthesiser starts yakking almost straightaway. Cheers, David.
Re: trying to install bullseye for about 25th time.
On Wednesday, 8 June 2022 08:33:56 EDT rhkra...@gmail.com wrote: > On Tuesday, June 07, 2022 04:24:02 PM gene heskett wrote: > > The D-I needs to grow the capability to mount an otherwise unused > > drive, and store as png's, snapshots of the screen. That way no one > > can accuse me of copy/paste fibbing. I can also take screen shots > > but the list server, even if I could figure out how to get it out of > > the camera and submit them, would justifiably balk at the 5+ megs a > > pix that would be. > Isn't there a setting on your camera to lower the resolution (thus > fewer megs)? > It a middle of the line cannon, I've not been able to find it in the menu's. > Oh, getting the pictures out of the camera -- no USB or similar port on > the camera? One of the mini-usbs, works well with digicam. > > Or exchange the memory card (if you have an appropriate card reader for > (one of) your computer(s))? I do. but dragging the card out of the camera's, all of them, is betting Murphy is on vacation, the power surges seem to like to trash the cards. The point is that none of the stuff I've mentioned is available to D-I. Thank you, rhkramer 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
Re: trying to install bullseye for about 25th time.
On Tuesday, June 07, 2022 04:24:02 PM gene heskett wrote: > The D-I needs to grow the capability to mount an otherwise unused drive, > and store as png's, snapshots of the screen. That way no one can accuse > me of copy/paste fibbing. I can also take screen shots but the list > server, even if I could figure out how to get it out of the camera and > submit them, would justifiably balk at the 5+ megs a pix that would be. Isn't there a setting on your camera to lower the resolution (thus fewer megs)? Oh, getting the pictures out of the camera -- no USB or similar port on the camera? Or exchange the memory card (if you have an appropriate card reader for (one of) your computer(s))?
Re: trying to install bullseye for about 25th time.
gene heskett composed on 2022-06-07 16:07 (UTC-0400): > The only way I know how to do that is take a screen shot with my camera. > But thats not possible when running the D-I cuz w/o gimp, its at least 5 > megs bigger than the server will accept. BTDT. You have lots of computers. Surely at least one must have Gimp on it. Neither Gimp nor X is needed to shrink camera images. Several command line utilities I know of are available specifically for the purpose. ImageMagick provides the one I usually use, convert, which can shrink in multiple fashions, without a mouse. -- 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: trying to install bullseye for about 25th time.
On Tue, Jun 07, 2022 at 04:24:02PM -0400, gene heskett wrote: > On Tuesday, 7 June 2022 15:16:16 EDT Andrew M.A. Cater wrote: > > On Tue, Jun 07, 2022 at 02:17:08PM -0400, gene heskett wrote: > > > But I've put another drive in, that I want to install a non efi > > > system on too. > > > > > > > > > Ideas as to how to proceed? > > > > Hi Gene, > > > > First: get yourself an iso with all the firmware on to start with. > > > > got that. > > > Second: Disconnect all your FTDI and serial leads. > > keyboard/mouse, one printer left plugged in. > > > Third: Use UEFI - it makes sense at this point. > The reason I say this is that UEFI is gradually becoming more tied in to things like power management and MBR/legacy BIOS is very definitely deprecated. > Can I still mount and use my /home raid10, and 1 or 2 other drives if I > switch it? > > Yes, the UEFI boot will write it's grub-efi record to the disk you specify: your /home RAID10 will have a filesystem you can mount. If you want to use the other drives, it would be straightforward to add mount points for them in the partitioner. You can add labels for partitions: if I'm feeling lazy, I'll tell the installer to use the entire disk and autopartitioning to get a basic layout. If you then add /home on your RAID, that should work. > > Fourth: Use the text mode expert install. > > I have so far, but powered off to bail out when I couldn't figure out > what to do next. Before it wrote anything. > > > When it comes to using your > > RAID, single step through the partitioning. Use the partitioner's > > expert mode to label the partition on your RAID as home and untick the > > format - that should work. > > > > Fifth: Uncheck any desktop environment in tasksel. > > > > Sixth: After that point, and only at that point, install TDE > > > > Seventh: Reinstate your serial leads one by one - and at that point, > > sort out your issues with nut, printers and so on. > > And printed this for the checklist. > > > > Document this step by step: write yourself a tasklist and tick off each > > small step as it completes. > > > > As someone who has done, conservatively, 500 installs - many with the > > text mode installer - it is not as hard as you seem to make it every > > single time. But, without knowing at what step you fail and precisely > > what you see when you do fail - what error messages, what it's telling > > you and what steps you are thinking of taking BEFORE you take them, > > I'm at a loss to know. > The D-I needs to grow the capability to mount an otherwise unused drive, > and store as png's, snapshots of the screen. That way no one can accuse > me of copy/paste fibbing. I can also take screen shots but the list > server, even if I could figure out how to get it out of the camera and > submit them, would justifiably balk at the 5+ megs a pix that would be. > If you use the GUI installer, there's an option to take screenshots. They end up in /var/log/installer along with the install log. I'm fairly sure there's a log of the install in /var/log/installer too. https://wiki.debian.org/ScreenShots#debian-installer-gui gave me that information. > > All the very best, as ever, > > > > Andy Cater > > Back atcha Andy, take care & stay well. > Take care yourself - I'm feeling a bit flu-ish otherwise I'd single step through this myself to debug it. All best, as ever, 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 > > >
Re: trying to install bullseye for about 25th time.
On Tuesday, 7 June 2022 15:16:16 EDT Andrew M.A. Cater wrote: > On Tue, Jun 07, 2022 at 02:17:08PM -0400, gene heskett wrote: > > But I've put another drive in, that I want to install a non efi > > system on too. > > > > > > Ideas as to how to proceed? > > Hi Gene, > > First: get yourself an iso with all the firmware on to start with. > got that. > Second: Disconnect all your FTDI and serial leads. keyboard/mouse, one printer left plugged in. > Third: Use UEFI - it makes sense at this point. Can I still mount and use my /home raid10, and 1 or 2 other drives if I switch it? > > Fourth: Use the text mode expert install. I have so far, but powered off to bail out when I couldn't figure out what to do next. Before it wrote anything. > When it comes to using your > RAID, single step through the partitioning. Use the partitioner's > expert mode to label the partition on your RAID as home and untick the > format - that should work. > > Fifth: Uncheck any desktop environment in tasksel. > > Sixth: After that point, and only at that point, install TDE > > Seventh: Reinstate your serial leads one by one - and at that point, > sort out your issues with nut, printers and so on. And printed this for the checklist. > > Document this step by step: write yourself a tasklist and tick off each > small step as it completes. > > As someone who has done, conservatively, 500 installs - many with the > text mode installer - it is not as hard as you seem to make it every > single time. But, without knowing at what step you fail and precisely > what you see when you do fail - what error messages, what it's telling > you and what steps you are thinking of taking BEFORE you take them, > I'm at a loss to know. The D-I needs to grow the capability to mount an otherwise unused drive, and store as png's, snapshots of the screen. That way no one can accuse me of copy/paste fibbing. I can also take screen shots but the list server, even if I could figure out how to get it out of the camera and submit them, would justifiably balk at the 5+ megs a pix that would be. > All the very best, as ever, > > Andy Cater Back atcha Andy, 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
Re: trying to install bullseye for about 25th time.
On Tuesday, 7 June 2022 15:03:41 EDT gene heskett wrote: > On Tuesday, 7 June 2022 14:35:50 EDT David Wright wrote: > > I was sitting here rereading the thread "had another crash, reboot > > usb > > failed, powerdown reboot usb failed" when this came in: > > > > On Tue 07 Jun 2022 at 14:17:08 (-0400), gene heskett wrote: > > > But I've put another drive in, that I want to install a non efi > > > system on too. > > > > > > booted back to bullseye to id the drive, its this one: (from dmesg) > > > [7.366909] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl > > > 300) > > > [7.374281] ata5.00: both IDENTIFYs aborted, assuming NODEV > > > [7.686897] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl > > > 300) > > > [7.690699] ata5.00: failed to IDENTIFY (I/O error, > > > err_mask=0x100) > > > [ 13.126916] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl > > > 300) > > > [ 13.130587] ata5.00: failed to IDENTIFY (I/O error, > > > err_mask=0x100) > > > [ 13.130593] ata5: limiting SATA link speed to 3.0 Gbps > > > [ 18.502913] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl > > > 320) > > > [ 18.507502] ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET > > > FEATURES) > > > succeeded > > > [ 18.507509] ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY > > > FREEZE > > > LOCK) filtered out > > > [ 18.507513] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE > > > CONFIGURATION OVERLAY) filtered out > > > [ 18.507890] ata5.00: supports DRM functions and may not be fully > > > accessible > > > [ 18.508532] ata5.00: disabling queued TRIM support > > > === > > > [ 18.508537] ata5.00: ATA-11: Samsung SSD 870 QVO 1TB, SVQ02B6Q, > > > max > > > UDMA/133 > > > === > > > [ 18.508541] ata5.00: 1953525168 sectors, multi 1: LBA48 NCQ > > > (depth > > > 32), AA > > > [ 18.512287] ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET > > > FEATURES) > > > succeeded > > > [ 18.512294] ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY > > > FREEZE > > > LOCK) filtered out > > > [ 18.512298] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE > > > CONFIGURATION OVERLAY) filtered out > > > [ 18.512707] ata5.00: supports DRM functions and may not be fully > > > accessible > > > [ 18.513368] ata5.00: disabling queued TRIM support > > > [ 18.515302] ata5.00: configured for UDMA/133 > > > > > > The installer does not identify it by the same names, so how do I > > > install to this drive w/o touching any of the other 6 samsung EVO > > > series drives. > > > > > > I've never learn to love gnome, and the kde5 you offer is buggier > > > than a 10 day old road kill in August, so this time is a text > > > install to see if I can put TDE in for a desktop. > > > > > > How do I proceed? The partitioner does not identify the drives > > > found > > > adequatly. The drive is plugged into the mainboard controller, I > > > think to port 5 of 6. > > > > Well, you post what it /does/ display. Then the experts here can make > > educated guesses, rather than just guessing. The only way I know how to do that is take a screen shot with my camera. But thats not possible when running the D-I cuz w/o gimp, its at least 5 megs bigger than the server will accept. BTDT. > > > I could label it, but the partitioner doesn't do labels. > > > This drive is new, and has not anything written to it. > > > > Really? Which partitioner is that? The one in the D-I. > > > blkid is no help because udev, in naming drives puts the stuff on a > > > separate controller for a raid 10 with 3 partitions on 4 drives > > > completely out of order. This too is less than helpful. And the > > > raid10 is my existing /home partition & swap. > > > > > > Ideas as to how to proceed? > > > > I was rereading Andrew's reply in the other thread, and his appeal > > "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." > > > > And I was thinking, that's not enough. We only hear a summary of what > > you think you're doing. I had a hypothesis for why you couldn't avoid > > the speech synthesiser, but it would require knowing every keystroke > > you use from powering on the machine. No chance of that. Not to mention it would be TL,DR to most. > > So, post some information. I've done that once or twice, meriting the tl;dr response. > > Cheers, > > David. > > I think Dan (SR) may have helped, while booted to th d-i, I recall > seeing an odd sdb that was likely it, better than than a WAG for sure. > Now if I can get the tde list to disgorge a trinity.list for > /etc/apt/sources.d, I might have that famous snowballs chance of > making this next install actually work for more than 4 or 5 days at a > reboot. > > Thanks David. > > > Cheers, Gene Heskett. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury,
Re: trying to install bullseye for about 25th time.
On Tue, Jun 07, 2022 at 02:17:08PM -0400, gene heskett wrote: > But I've put another drive in, that I want to install a non efi system on > too. > > > Ideas as to how to proceed? > Hi Gene, First: get yourself an iso with all the firmware on to start with. Second: Disconnect all your FTDI and serial leads. Third: Use UEFI - it makes sense at this point. Fourth: Use the text mode expert install. When it comes to using your RAID, single step through the partitioning. Use the partitioner's expert mode to label the partition on your RAID as home and untick the format - that should work. Fifth: Uncheck any desktop environment in tasksel. Sixth: After that point, and only at that point, install TDE Seventh: Reinstate your serial leads one by one - and at that point, sort out your issues with nut, printers and so on. Document this step by step: write yourself a tasklist and tick off each small step as it completes. As someone who has done, conservatively, 500 installs - many with the text mode installer - it is not as hard as you seem to make it every single time. But, without knowing at what step you fail and precisely what you see when you do fail - what error messages, what it's telling you and what steps you are thinking of taking BEFORE you take them, I'm at a loss to know. All the very best, as ever, 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 > > >
Re: trying to install bullseye for about 25th time.
On Tuesday, 7 June 2022 14:35:50 EDT David Wright wrote: > I was sitting here rereading the thread "had another crash, reboot usb > failed, powerdown reboot usb failed" when this came in: > > On Tue 07 Jun 2022 at 14:17:08 (-0400), gene heskett wrote: > > But I've put another drive in, that I want to install a non efi > > system on too. > > > > booted back to bullseye to id the drive, its this one: (from dmesg) > > [7.366909] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) > > [7.374281] ata5.00: both IDENTIFYs aborted, assuming NODEV > > [7.686897] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) > > [7.690699] ata5.00: failed to IDENTIFY (I/O error, > > err_mask=0x100) > > [ 13.126916] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) > > [ 13.130587] ata5.00: failed to IDENTIFY (I/O error, > > err_mask=0x100) > > [ 13.130593] ata5: limiting SATA link speed to 3.0 Gbps > > [ 18.502913] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 320) > > [ 18.507502] ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) > > succeeded > > [ 18.507509] ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY > > FREEZE > > LOCK) filtered out > > [ 18.507513] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE > > CONFIGURATION OVERLAY) filtered out > > [ 18.507890] ata5.00: supports DRM functions and may not be fully > > accessible > > [ 18.508532] ata5.00: disabling queued TRIM support > > === > > [ 18.508537] ata5.00: ATA-11: Samsung SSD 870 QVO 1TB, SVQ02B6Q, > > max > > UDMA/133 > > === > > [ 18.508541] ata5.00: 1953525168 sectors, multi 1: LBA48 NCQ (depth > > 32), AA > > [ 18.512287] ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) > > succeeded > > [ 18.512294] ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY > > FREEZE > > LOCK) filtered out > > [ 18.512298] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE > > CONFIGURATION OVERLAY) filtered out > > [ 18.512707] ata5.00: supports DRM functions and may not be fully > > accessible > > [ 18.513368] ata5.00: disabling queued TRIM support > > [ 18.515302] ata5.00: configured for UDMA/133 > > > > The installer does not identify it by the same names, so how do I > > install to this drive w/o touching any of the other 6 samsung EVO > > series drives. > > > > I've never learn to love gnome, and the kde5 you offer is buggier > > than a 10 day old road kill in August, so this time is a text > > install to see if I can put TDE in for a desktop. > > > > How do I proceed? The partitioner does not identify the drives found > > adequatly. The drive is plugged into the mainboard controller, I > > think to port 5 of 6. > > Well, you post what it /does/ display. Then the experts here can make > educated guesses, rather than just guessing. > > > I could label it, but the partitioner doesn't do labels. > > This drive is new, and has not anything written to it. > > Really? Which partitioner is that? > > > blkid is no help because udev, in naming drives puts the stuff on a > > separate controller for a raid 10 with 3 partitions on 4 drives > > completely out of order. This too is less than helpful. And the > > raid10 is my existing /home partition & swap. > > > > Ideas as to how to proceed? > > I was rereading Andrew's reply in the other thread, and his appeal > "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." > > And I was thinking, that's not enough. We only hear a summary of what > you think you're doing. I had a hypothesis for why you couldn't avoid > the speech synthesiser, but it would require knowing every keystroke > you use from powering on the machine. No chance of that. > > So, post some information. > > Cheers, > David. > I think Dan (SR) may have helped, while booted to th d-i, I recall seeing an odd sdb that was likely it, better than than a WAG for sure. Now if I can get the tde list to disgorge a trinity.list for /etc/apt/sources.d, I might have that famous snowballs chance of making this next install actually work for more than 4 or 5 days at a reboot. Thanks 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
Re: trying to install bullseye for about 25th time.
gene heskett wrote: > But I've put another drive in, that I want to install a non efi system on > too. > > booted back to bullseye to id the drive, its this one: (from dmesg) > [ 18.508537] ata5.00: ATA-11: Samsung SSD 870 QVO 1TB, SVQ02B6Q, max > UDMA/133 > === > [ 18.508541] ata5.00: 1953525168 sectors, multi 1: LBA48 NCQ (depth > 32), AA > How do I proceed? The partitioner does not identify the drives found > adequatly. The drive is plugged into the mainboard controller, I think to > port 5 of 6. > > I could label it, but the partitioner doesn't do labels. > This drive is new, and has not anything written to it. ls -al /dev/disk/by-id/ | grep SVQ02B6Q should get you something like lrwxrwxrwx 1 root root 9 Jan 29 15:26 ata-Samsung_SSD_870_QVO_GB_SVQ02B6Q -> ../../sdb and that will let you know that it's /dev/sdb helpful? -dsr-
Re: trying to install bullseye for about 25th time.
I was sitting here rereading the thread "had another crash, reboot usb failed, powerdown reboot usb failed" when this came in: On Tue 07 Jun 2022 at 14:17:08 (-0400), gene heskett wrote: > But I've put another drive in, that I want to install a non efi system on > too. > > booted back to bullseye to id the drive, its this one: (from dmesg) > [7.366909] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) > [7.374281] ata5.00: both IDENTIFYs aborted, assuming NODEV > [7.686897] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) > [7.690699] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x100) > [ 13.126916] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) > [ 13.130587] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x100) > [ 13.130593] ata5: limiting SATA link speed to 3.0 Gbps > [ 18.502913] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 320) > [ 18.507502] ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) > succeeded > [ 18.507509] ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE > LOCK) filtered out > [ 18.507513] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE > CONFIGURATION OVERLAY) filtered out > [ 18.507890] ata5.00: supports DRM functions and may not be fully > accessible > [ 18.508532] ata5.00: disabling queued TRIM support > === > [ 18.508537] ata5.00: ATA-11: Samsung SSD 870 QVO 1TB, SVQ02B6Q, max > UDMA/133 > === > [ 18.508541] ata5.00: 1953525168 sectors, multi 1: LBA48 NCQ (depth > 32), AA > [ 18.512287] ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) > succeeded > [ 18.512294] ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE > LOCK) filtered out > [ 18.512298] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE > CONFIGURATION OVERLAY) filtered out > [ 18.512707] ata5.00: supports DRM functions and may not be fully > accessible > [ 18.513368] ata5.00: disabling queued TRIM support > [ 18.515302] ata5.00: configured for UDMA/133 > > The installer does not identify it by the same names, so how do I install > to this drive w/o touching any of the other 6 samsung EVO series drives. > > I've never learn to love gnome, and the kde5 you offer is buggier than a > 10 day old road kill in August, so this time is a text install to see if > I can put TDE in for a desktop. > > How do I proceed? The partitioner does not identify the drives found > adequatly. The drive is plugged into the mainboard controller, I think to > port 5 of 6. Well, you post what it /does/ display. Then the experts here can make educated guesses, rather than just guessing. > I could label it, but the partitioner doesn't do labels. > This drive is new, and has not anything written to it. Really? Which partitioner is that? > blkid is no help because udev, in naming drives puts the stuff on a > separate controller for a raid 10 with 3 partitions on 4 drives > completely out of order. This too is less than helpful. And the raid10 > is my existing /home partition & swap. > > Ideas as to how to proceed? I was rereading Andrew's reply in the other thread, and his appeal "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." And I was thinking, that's not enough. We only hear a summary of what you think you're doing. I had a hypothesis for why you couldn't avoid the speech synthesiser, but it would require knowing every keystroke you use from powering on the machine. No chance of that. So, post some information. Cheers, David.
trying to install bullseye for about 25th time.
But I've put another drive in, that I want to install a non efi system on too. booted back to bullseye to id the drive, its this one: (from dmesg) [7.366909] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [7.374281] ata5.00: both IDENTIFYs aborted, assuming NODEV [7.686897] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [7.690699] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x100) [ 13.126916] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 13.130587] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x100) [ 13.130593] ata5: limiting SATA link speed to 3.0 Gbps [ 18.502913] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 18.507502] ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded [ 18.507509] ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out [ 18.507513] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out [ 18.507890] ata5.00: supports DRM functions and may not be fully accessible [ 18.508532] ata5.00: disabling queued TRIM support === [ 18.508537] ata5.00: ATA-11: Samsung SSD 870 QVO 1TB, SVQ02B6Q, max UDMA/133 === [ 18.508541] ata5.00: 1953525168 sectors, multi 1: LBA48 NCQ (depth 32), AA [ 18.512287] ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded [ 18.512294] ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out [ 18.512298] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out [ 18.512707] ata5.00: supports DRM functions and may not be fully accessible [ 18.513368] ata5.00: disabling queued TRIM support [ 18.515302] ata5.00: configured for UDMA/133 The installer does not identify it by the same names, so how do I install to this drive w/o touching any of the other 6 samsung EVO series drives. I've never learn to love gnome, and the kde5 you offer is buggier than a 10 day old road kill in August, so this time is a text install to see if I can put TDE in for a desktop. How do I proceed? The partitioner does not identify the drives found adequatly. The drive is plugged into the mainboard controller, I think to port 5 of 6. I could label it, but the partitioner doesn't do labels. This drive is new, and has not anything written to it. blkid is no help because udev, in naming drives puts the stuff on a separate controller for a raid 10 with 3 partitions on 4 drives completely out of order. This too is less than helpful. And the raid10 is my existing /home partition & swap. Ideas as to how to proceed? 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
