Re: perte clavier suite à retour de veille depuis bookworm-12.5
Bonjour à tous , Le 14/02/2024 à 21:51, Étienne Mollier a écrit : Bonjour Jacques, Depuis la mise à jour bookworm du week-end dernier (12.5) , le clavier de mon PC portable (dell latitude 3340) ne fonctionne plus après un retour de veille. […] Est-ce que quelqu'un parmi vous est également confronté à ce problème et si oui a-t-il su contourner la difficulté (paramétrage du noyau au boot ou ...)? ou s'agit-il selon vous d'un bug du noyau 6.1.0-18-amd64 ? Le symptôme ressemble furieusement à celui décrit dans une rustine apparue dans Linux 6.1.74 pour éviter ce problème sur Acer P459-G2-M [1]. Linux a vu des mises à jour du pilote input en versions 6.1.70, 6.1.74 et 6.1.75. On n'est pas à l'abri que l'un de ces changements ait introduit ce bug. J'aurais donc tendance à penser que c'est un bug du noyau 6.1.0-18-amd64. [1] : https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.1.y=626b0c0ab3a06d02e32700de026c0c3f828f8492 Merci Étienne pour ta réponse: je ne suis pas sur d'être tout à fait dans le même cas que ce que tu évoques: au retour de veille l'écran s'affiche correctement, le "touchpad" fonctionne , les "magic SysRq keys" fonctionnent (Fn+Impécran+b reboote la machine). Penses-tu qu'il soit utile de remonter un rapport de bug debian pour le paquet linux-image-6.1.0-18-amd64 ? En parcourant internet j'ai finalement trouvé une rustine qui permet à mon ordinateur de fonctionner correctement après un retour de veille: - rajouter "atkbd.reset" à la ligne GRUB_CMDLINE_LINUX_DEFAULT du fichier /etc/default/grub - lancer la commande: update-grub Bonne journée
Re: SMART Uncorrectable_Error_Cnt rising - should I be worried?
The Wanderer wrote: > TL;DR: It worked! I'm back up and running, with what appears to be all > my data safely recovered from the failing storage stack! ... i'm glad you got it back up and running and i hope all your data is intact. :) which SSDs did you use? songbird
Re: Issue with USB External Keyboard, External Mouse, and Screen Brightness on Dell Laptop
On Wed 14 Feb 2024 at 20:09:09 (-0300), Marcelo Laia wrote: > Unfortunately, the issue has worsened. Today, I observed that upon unplugging > the power cable, within one or two seconds, the screen dims (brightness is > set to zero), and both the external mouse and keyboard (USB) stop working. > Even if I try to use the keyboard or mouse, they do not reactivate. Only the > laptop's internal touchpad and keyboard continue to function. When I > reconnect the power cable, both the external mouse and keyboard resume > working automatically. However, I need to manually adjust the screen > brightness. I have not installed the usbguard package. Could there be another > underlying cause? I would go further than tomas, and suggest that the battery might be suspect, or the charging circuit of course. (None of my three laptops works without AC power.) How old is it? Cheers, David.
Re: shred bug? [was: Unidentified subject!]
On Tue 13 Feb 2024 at 11:21:08 (-0500), Greg Wooledge wrote: > On Tue, Feb 13, 2024 at 09:35:11AM -0600, David Wright wrote: > > On Tue 13 Feb 2024 at 07:15:48 (-0500), Greg Wooledge wrote: > > > On Mon, Feb 12, 2024 at 11:01:47PM -0600, David Wright wrote: > > > > … but not much. For me, "standard output" is /dev/fd/1, yet it seems > > > > unlikely that anyone is going to use >&1 in the manner of the example. > > > > > > Standard output means "whatever file descriptor 1 points to". That > > > could be a file, a pipe, a terminal (character device), etc. > > > > Why pick on 1? > > It's the definition. Standard input is FD 0, standard output is FD 1, > and standard error is FD 2. > > > . It demonstrates the shell syntax element required (&) in order to > > avoid truncating the file, rather than shred overwriting it. > > You are confused. You're making assumptions about shell syntax that > are simply not true. You're right. I was looking too hard at the right side of the > and neglecting the implied left side. It's always worth running these things past your eyes. Thanks for the clear exposition that followed. Cheers, David.
Re: f3tools vs Silicon Power 4T drive
On 2/14/24 21:14, Max Nikulin wrote: On 15/02/2024 08:48, gene heskett wrote: This is what gparted calls a "partition label" and certainly does not need a 4.5 megabyte camera image to see. or even a 50k screen snap. lsblk --fs -o +PARTLABEL /dev/sdc NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS PARTLABEL sdc └─sdc1 ext4 1.0 SiPwr_1 70bfe832-38b1-46ed-85f4-33cf473185bb . Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: f3tools vs Silicon Power 4T drive
On 2/14/24 20:49, gene heskett wrote: On 2/14/24 19:48, Andy Smith wrote: Hi, On Wed, Feb 14, 2024 at 05:09:02PM -0500, gene heskett wrote: I have made 1 full partiton om each one, a labeled those partitions as SiPwr_0 and SiPwr_1 Please show us the command you used¹ to do that, so we know what exactly you are talking about, because as previously discussed there's a lot of different things that you like to call "partition labels". This is what gparted calls a "partition label" and certainly does not need a 4.5 megabyte camera image to see. or even a 50k screen snap. Taking this screenshot was a pita, because the gparted window disappears behind the terminal screen when you click on take another shot, so you have to quit, then find the gparted on the tool bar to bring it back to the front, then move it and the terminal so its not totally hidden. Then rerun spectacle again waste a click bringing it fwd, then 30 seconds later the spectacal instructions finally show up and after 5 minutes of screwing around, finally get the screen shot attached to prove I'm not lieing. If we take that literally that would be a GPT partition name, but you've used this same terminology before and meant a filesystem label. My only question it will those partition names survive lvcreating an 11T lvm out of these and 2 more 2T gigastones. Assuming you meant partition name the first time as well, nothing you do other than a disk wipe or re-name should alter those partition names. But your chosen partition names don't make a lot of sense to me. You've picked names based on the type/manufacturer of device so you may as well have just used the names from /dev/disk/by-id/… which already have that information and are already never going to change. I don't know why you want to complicate matters. If instead you put filesystems on these partitions and labelled *those*, well, no, LVM goes under filesystems so those filesystems and their labels (and contents) are not long for this world. I have not dealt with an lvm in about 15+ years trying it once when it first came out with a high disaster rating then. I hope you are putting a level of redundancy under that LVM or are using the redundancy features of LVM (which you need to go out of your way to do). Otherwise by default what you'll have is not redundant and a device failure will lose at least the contents of that device, possibly more. You pique my curiosity because this is going to be my backup system, but not a syllable about how to do it. You tell me its fine 3 paragraphs up. then tell me lvcreate will wipe it out. I'm asking for answers, not more connumdrums.. Regards, Andy ¹ and while you are there, maybe a post-it note with "I will show the exact command I used any time I write to debian-user" stuck to the top of the display of the screen you use to compose emails would help, because basically every thread you post here lacks that information. Cheers, Gene Heskett, CET. Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: SMART Uncorrectable_Error_Cnt rising - should I be worried?
TL;DR: It worked! I'm back up and running, with what appears to be all my data safely recovered from the failing storage stack! On 2024-01-09 at 14:22, The Wanderer wrote: > On 2024-01-09 at 14:01, Michael Kjörling wrote: > >> On 9 Jan 2024 13:25 -0500, from wande...@fastmail.fm (The >> Wanderer): >>> I've ordered a 22TB external drive for the purpose of creating >>> such a backup. Fingers crossed that things last long enough for >>> it to get here and get the backup created. >> >> I suggest selecting, installing and configuring (as much as >> possible) whatever software you will use to actually perform the >> backup while you wait for the drive to arrive. It might save you a >> little time later. Opinions differ but I like rsnapshot myself; >> it's really just a front-end for rsync, so the copy is simply >> files, making partial or full restoration easy without any special >> tools. > > My intention was to shut down everything that normally runs, log out > as the user who normally runs it, log in as root (whose home > directory, like the main installed system, is on a different RAID > array with different backing drives), and use rsync from that point. > My understanding is that in that arrangement, the only thing > accessing the RAID-6 array should be the rsync process itself. > > For additional clarity: the RAID-6 array is backing a pair of > logical volumes, which are backing the /home and /opt partitions. The > entire rest of the system is on a series of other logical volumes > which are backed by a RAID-1 array, which is based on entirely > different drives (different model, different form factor, different > capacity, I think even different connection technology) and which has > not seen any warnings arise. > >>> dmesg does have what appears to be an error entry for each of >>> the events reported in the alert mails, correlated with the >>> devices in question. I can provide a sample of one of those, if >>> desired. >> >> As long as the drive is being honest about failures and is >> reporting failures rapidly, the RAID array can do its work. What >> you absolutely don't want to see is I/O errors relating to the RAID >> array device (for example, with mdraid, /dev/md*), because that >> would presumably mean that the redundancy was insufficient to >> correct for the failure. If that happens, you are falling off a >> proverbial cliff. > > Yeah, *that* would be indicative of current catastrophic failure. I > have not seen any messages related to the RAID array itself. In the time since this, I continued mostly-normal but somewhat-curtailed use of the system, and saw few messages about these matters that did not arise from attempts to back up the data for later recovery purposes. > (For awareness: this is all a source of considerable psychological > stress to me, to an extent that is leaving me on the edge of > physically ill, and I am managing to remain on the good side of that > line only by minimizing my mental engagement with the issue as much > as possible. I am currently able to read and respond to these mails > without pressing that line, but that may change at any moment, and if > so I will stop replying without notice until things change again.) This need to stop reading wound up happening almost immediately after I sent the message to which I am replying. I now, however, have good news to report back: after more than a month, at least one change of plans, nearly $2200 in replacement hard drives, much nervous stress, several days of running data copies to and from a 20+-terabyte mechanical hard drive over USB, and a complete manual removal of my old 8-drive RAID-6 array and build of a new 6-drive RAID-6 array (and of the LVM structure on top of it), I now appear to have complete success. I am now running on a restored copy of the data on the affected partitions, taken from a nearly-fully-shut-down system state, which is sitting on a new RAID-6 array built on what I understand to be data-center-class SSDs (which should, therefore, be more suitable to the 24/7-uptime read-mostly workload I expect of my storage). The current filesystems involved are roughly the same size as the ones previously in use, but the underlying drives are nearly 2x the size; I decided to leave the extra capacity for later allocation via LVM, if and when I may need it. I did my initial data backup to the external drive, from a still-up-and-running system, via rsnapshot. Attempting to do a second rsnapshot, however, failed at the 'cp -al' stage with "too many hardlinks" errors. It turns out that there is a hard limit of 65000 hardlinks per on-disk file; I had so many files already hardlinked together on the source filesystem that trying to hardlink each one to just as many new names as there were already hardlinks for that file ran into that limit. (The default rsnapshot configuration doesn't preserve hardlinks, possibly in order to avoid this exact problem - but that isn't viable for the case I had
Re: f3tools vs Silicon Power 4T drive
On 2/14/24 18:06, gene heskett wrote: Will the by-id string fit in the space reserved for a label?That IF there was a connection between the /dev/sdc that udev assigns and anything in this list: root@coyote:~# ls /dev/disk/by-id ata-ATAPI_iHAS424_B_3524253_327133504865 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W-part1 wwn-0x5002538f413394a5 ata-Gigastone_SSD_GST02TBG221146 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W-part2 wwn-0x5002538f413394a5-part1 ata-Gigastone_SSD_GST02TBG221146-part1 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W-part3 wwn-0x5002538f413394a5-part2 ata-Gigastone_SSD_GSTD02TB230102 ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V wwn-0x5002538f413394a5-part3 ata-Gigastone_SSD_GSTD02TB230102-part1 ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V-part1 wwn-0x5002538f413394a9 ata-Gigastone_SSD_GSTG02TB230206 ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V-part2 wwn-0x5002538f413394a9-part1 ata-Gigastone_SSD_GSTG02TB230206-part1 ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V-part3 wwn-0x5002538f413394a9-part2 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T ata-SPCC_Solid_State_Disk_AA231107S304KG00080 wwn-0x5002538f413394a9-part3 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T-part1 ata-SPCC_Solid_State_Disk_AA231107S304KG00080-part1 wwn-0x5002538f413394ae ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T-part2 md-name-coyote:0 wwn-0x5002538f413394ae-part1 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T-part3 md-name-coyote:0-part1 wwn-0x5002538f413394ae-part2 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E md-name-coyote:2 wwn-0x5002538f413394ae-part3 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E-part1 md-name-_none_:1 wwn-0x5002538f413394b0 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E-part2 md-uuid-3d5a3621:c0e32c8a:e3f7ebb3:318edbfb wwn-0x5002538f413394b0-part1 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E-part3 md-uuid-3d5a3621:c0e32c8a:e3f7ebb3:318edbfb-part1 wwn-0x5002538f413394b0-part2 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V md-uuid-57a88605:27f5a773:5be347c1:7c5e7342 wwn-0x5002538f413394b0-part3 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V-part1 md-uuid-bb6e03ce:19d290c8:5171004f:0127a392 wwn-0x5002538f42205e8e ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V-part2 usb-SPCC_Sol_id_State_Disk_1234567897E6-0:0 wwn-0x5002538f42205e8e-part1 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V-part3 usb-SPCC_Sol_id_State_Disk_1234567897E6-0:0-part1 wwn-0x5002538f42205e8e-part2 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W usb-USB_Mass_Storage_Device_816820130806-0:0 wwn-0x5002538f42205e8e-part3 root@coyote:~# I dare you to find the disk that udev calls sdc in the above wall of text. Why can't you understand that I want a unique label for all of this stuff that is NOT a wall of HEX numbers no one can remember. Its not mounted, so blkid does NOT see it. For labeled disk partitions, use /dev/disk/by-label/* paths: 2024-02-14 18:22:34 root@taz ~ # ls -1 /dev/disk/by-label/ sda3_crypt taz_boot taz_root David
Re: Does "LC_ALL=C" work on all shells?
On 14/02/2024 23:11, Franco Martelli wrote: Well, I'll go with env command syntax for shells portability. I was asking this because I want to suggest a change to the DDP (Debian Documentation Project) members for the releases notes documentation ¹ # env LC_ALL=C script -t 2>~/upgrade-bookwormstep.time -a ~/upgrade-bookwormstep.script Perhaps LC_ALL=C.UTF-8 is safer. At least several years ago some python scripts (unrelated to Debian upgrade however) failed trying to log e.g. non-ascii file paths, etc. I would reset LANGUAGE as well otherwise some programs may use localized messages. Finally, some users might have LC_ALL (despite it is not recommended) or LANGUAGE set in a file like ~/.bashrc. That is why the following approach may be more reliable. Run commands within the "script" session LANG=C.UTF-8; LANGUAGE=; export LANG LANGUAGE with a note concerning csh. To affect messages generated by shell itself, "export" is separated from setting of the variables.
Re: f3tools vs Silicon Power 4T drive
On 15/02/2024 08:48, gene heskett wrote: This is what gparted calls a "partition label" and certainly does not need a 4.5 megabyte camera image to see. or even a 50k screen snap. lsblk --fs -o +PARTLABEL /dev/sdc
Re: f3tools vs Silicon Power 4T drive
On 2/14/24 17:48, gene heskett wrote: On 2/14/24 19:48, Andy Smith wrote: On Wed, Feb 14, 2024 at 05:09:02PM -0500, gene heskett wrote: I have made 1 full partiton om each one, a labeled those partitions as SiPwr_0 and SiPwr_1 Please show us the command you used¹ to do that, so we know what exactly you are talking about, because as previously discussed there's a lot of different things that you like to call "partition labels". This is what gparted calls a "partition label" and certainly does not need a 4.5 megabyte camera image to see. or even a 50k screen snap. Taking this screenshot was a pita, because the gparted window disappears behind the terminal screen when you click on take another shot, so you have to quit, then find the gparted on the tool bar to bring it back to the front, then move it and the terminal so its not totally hidden. Then rerun spectacle again waste a click bringing it fwd, then 30 seconds later the spectacal instructions finally show up and after 5 minutes of screwing around, finally get the screen shot attached to prove I'm not lieing. The easy and accurate answer is to use a root console, fdisk(8) with --list-details, select the console session, and paste into a mail reply: 2024-02-14 18:09:26 root@taz ~ # fdisk --list-details /dev/sda Disk /dev/sda: 55.9 GiB, 60022480896 bytes, 117231408 sectors Disk model: INTEL SSDSC2CW06 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 816CF78F-AFAD-4F70-AAA0-B08C6CE95AE7 First LBA: 34 Last LBA: 117231374 Alternative LBA: 117231407 Partition entries LBA: 2 Allocated partition entries: 128 DeviceStart End Sectors Type-UUID UUID Name Attrs /dev/sda1 2048 1953791 1951744 C12A7328-F81F-11D2-BA4B-00A0C93EC93B 5A1358F4-23A2-4CF6-A4E2-0A30A0FFC904 ESP /dev/sda2 1953792 3907583 1953792 0FC63DAF-8483-4772-8E79-3D69D8477DE4 B429D984-E32D-4BAE-A7AE-137168B0F0F3 taz_boot /dev/sda3 3907584 5861375 1953792 0FC63DAF-8483-4772-8E79-3D69D8477DE4 83862E6A-7B89-4AB9-A21D-BAEF3AD0F7A3 taz_swap_crypt /dev/sda4 5861376 29298687 23437312 0FC63DAF-8483-4772-8E79-3D69D8477DE4 2A708FD7-F6EE-49D7-8E23-65905BCD6512 taz_root_crypt /dev/sda5 29298688 117229567 87930880 0FC63DAF-8483-4772-8E79-3D69D8477DE4 B8468EA2-B66D-4D13-9FD1-E46AEDA58067 taz_scratch_crypt David
Re: f3tools vs Silicon Power 4T drive
On 2/14/24 19:48, Andy Smith wrote: Hi, On Wed, Feb 14, 2024 at 05:09:02PM -0500, gene heskett wrote: I have made 1 full partiton om each one, a labeled those partitions as SiPwr_0 and SiPwr_1 Please show us the command you used¹ to do that, so we know what exactly you are talking about, because as previously discussed there's a lot of different things that you like to call "partition labels". If we take that literally that would be a GPT partition name, but you've used this same terminology before and meant a filesystem label. My only question it will those partition names survive lvcreating an 11T lvm out of these and 2 more 2T gigastones. Assuming you meant partition name the first time as well, nothing you do other than a disk wipe or re-name should alter those partition names. But your chosen partition names don't make a lot of sense to me. You've picked names based on the type/manufacturer of device so you may as well have just used the names from /dev/disk/by-id/… which already have that information and are already never going to change. I don't know why you want to complicate matters. Will the by-id string fit in the space reserved for a label?That IF there was a connection between the /dev/sdc that udev assigns and anything in this list: root@coyote:~# ls /dev/disk/by-id ata-ATAPI_iHAS424_B_3524253_327133504865 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W-part1wwn-0x5002538f413394a5 ata-Gigastone_SSD_GST02TBG221146 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W-part2 wwn-0x5002538f413394a5-part1 ata-Gigastone_SSD_GST02TBG221146-part1 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W-part3 wwn-0x5002538f413394a5-part2 ata-Gigastone_SSD_GSTD02TB230102 ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V wwn-0x5002538f413394a5-part3 ata-Gigastone_SSD_GSTD02TB230102-part1 ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V-part1wwn-0x5002538f413394a9 ata-Gigastone_SSD_GSTG02TB230206 ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V-part2 wwn-0x5002538f413394a9-part1 ata-Gigastone_SSD_GSTG02TB230206-part1 ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V-part3 wwn-0x5002538f413394a9-part2 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T ata-SPCC_Solid_State_Disk_AA231107S304KG00080 wwn-0x5002538f413394a9-part3 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T-part1 ata-SPCC_Solid_State_Disk_AA231107S304KG00080-part1 wwn-0x5002538f413394ae ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T-part2 md-name-coyote:0 wwn-0x5002538f413394ae-part1 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T-part3 md-name-coyote:0-part1 wwn-0x5002538f413394ae-part2 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502Emd-name-coyote:2 wwn-0x5002538f413394ae-part3 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E-part1 md-name-_none_:1 wwn-0x5002538f413394b0 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E-part2 md-uuid-3d5a3621:c0e32c8a:e3f7ebb3:318edbfb wwn-0x5002538f413394b0-part1 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E-part3 md-uuid-3d5a3621:c0e32c8a:e3f7ebb3:318edbfb-part1 wwn-0x5002538f413394b0-part2 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V md-uuid-57a88605:27f5a773:5be347c1:7c5e7342 wwn-0x5002538f413394b0-part3 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V-part1 md-uuid-bb6e03ce:19d290c8:5171004f:0127a392 wwn-0x5002538f42205e8e ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V-part2 usb-SPCC_Sol_id_State_Disk_1234567897E6-0:0 wwn-0x5002538f42205e8e-part1 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V-part3 usb-SPCC_Sol_id_State_Disk_1234567897E6-0:0-part1 wwn-0x5002538f42205e8e-part2 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W usb-USB_Mass_Storage_Device_816820130806-0:0 wwn-0x5002538f42205e8e-part3 root@coyote:~# I dare you to find the disk that udev calls sdc in the above wall of text. Why can't you understand that I want a unique label for all of this stuff that is NOT a wall of HEX numbers no one can remember. Its not mounted, so blkid does NOT see it. If instead you put filesystems on these partitions and labelled *those*, well, no, LVM goes under filesystems so those filesystems and their labels (and contents) are not long for this world. I have not dealt with an lvm in about 15+ years trying it once when it first came out with a high disaster rating then. I hope you are putting a level of redundancy under that LVM or are using the redundancy features of LVM (which you need to go out of your way to do). Otherwise by default what you'll have is not redundant and a device failure will lose at least the contents of that device, possibly more. Regards, Andy ¹ and while you are there, maybe a post-it note with "I will show the exact command I used any time I write to debian-user" stuck to the top of the display of the screen you use to compose emails would help, because basically every thread you post here lacks that information. Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense
Re: f3tools vs Silicon Power 4T drive
On 2/14/24 19:48, Andy Smith wrote: Hi, On Wed, Feb 14, 2024 at 05:09:02PM -0500, gene heskett wrote: I have made 1 full partiton om each one, a labeled those partitions as SiPwr_0 and SiPwr_1 Please show us the command you used¹ to do that, so we know what exactly you are talking about, because as previously discussed there's a lot of different things that you like to call "partition labels". This is what gparted calls a "partition label" and certainly does not need a 4.5 megabyte camera image to see. or even a 50k screen snap. Taking this screenshot was a pita, because the gparted window disappears behind the terminal screen when you click on take another shot, so you have to quit, then find the gparted on the tool bar to bring it back to the front, then move it and the terminal so its not totally hidden. Then rerun spectacle again waste a click bringing it fwd, then 30 seconds later the spectacal instructions finally show up and after 5 minutes of screwing around, finally get the screen shot attached to prove I'm not lieing. If we take that literally that would be a GPT partition name, but you've used this same terminology before and meant a filesystem label. My only question it will those partition names survive lvcreating an 11T lvm out of these and 2 more 2T gigastones. Assuming you meant partition name the first time as well, nothing you do other than a disk wipe or re-name should alter those partition names. But your chosen partition names don't make a lot of sense to me. You've picked names based on the type/manufacturer of device so you may as well have just used the names from /dev/disk/by-id/… which already have that information and are already never going to change. I don't know why you want to complicate matters. If instead you put filesystems on these partitions and labelled *those*, well, no, LVM goes under filesystems so those filesystems and their labels (and contents) are not long for this world. I have not dealt with an lvm in about 15+ years trying it once when it first came out with a high disaster rating then. I hope you are putting a level of redundancy under that LVM or are using the redundancy features of LVM (which you need to go out of your way to do). Otherwise by default what you'll have is not redundant and a device failure will lose at least the contents of that device, possibly more. Regards, Andy ¹ and while you are there, maybe a post-it note with "I will show the exact command I used any time I write to debian-user" stuck to the top of the display of the screen you use to compose emails would help, because basically every thread you post here lacks that information. Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: f3tools vs Silicon Power 4T drive
Hi, On Wed, Feb 14, 2024 at 05:09:02PM -0500, gene heskett wrote: > I have made 1 full partiton om each one, a labeled those partitions as > SiPwr_0 and SiPwr_1 Please show us the command you used¹ to do that, so we know what exactly you are talking about, because as previously discussed there's a lot of different things that you like to call "partition labels". If we take that literally that would be a GPT partition name, but you've used this same terminology before and meant a filesystem label. > My only question it will those partition names survive lvcreating an 11T lvm > out of these and 2 more 2T gigastones. Assuming you meant partition name the first time as well, nothing you do other than a disk wipe or re-name should alter those partition names. But your chosen partition names don't make a lot of sense to me. You've picked names based on the type/manufacturer of device so you may as well have just used the names from /dev/disk/by-id/… which already have that information and are already never going to change. I don't know why you want to complicate matters. If instead you put filesystems on these partitions and labelled *those*, well, no, LVM goes under filesystems so those filesystems and their labels (and contents) are not long for this world. > I have not dealt with an lvm in about 15+ years trying it once > when it first came out with a high disaster rating then. I hope you are putting a level of redundancy under that LVM or are using the redundancy features of LVM (which you need to go out of your way to do). Otherwise by default what you'll have is not redundant and a device failure will lose at least the contents of that device, possibly more. Regards, Andy ¹ and while you are there, maybe a post-it note with "I will show the exact command I used any time I write to debian-user" stuck to the top of the display of the screen you use to compose emails would help, because basically every thread you post here lacks that information. -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: Re: Issue with USB External Keyboard, External Mouse, and Screen Brightness on Dell Laptop
Dear Debian community, Thank you for your insights. Unfortunately, the issue has worsened. Today, I observed that upon unplugging the power cable, within one or two seconds, the screen dims (brightness is set to zero), and both the external mouse and keyboard (USB) stop working. Even if I try to use the keyboard or mouse, they do not reactivate. Only the laptop's internal touchpad and keyboard continue to function. When I reconnect the power cable, both the external mouse and keyboard resume working automatically. However, I need to manually adjust the screen brightness. I have not installed the usbguard package. Could there be another underlying cause? Best regards, -- Marcelo
Re: Erreur nvidia suite upgrade noyau 6.1.0-18
On Wednesday 14 February 2024 18:07:35 zithro wrote: > Rilax les gens (: > A mon avis c'est juste une incompréhension. > En caricaturant : > - Michel a compris qu'André disait "je laisse tomber, ça montre bien > qu'il y a que des noobs/gens inutiles ici". > - Alors qu'André voulait dire "je laisse tomber car ça me saoûle, > dommage car ça aurait pu profiter à d'autres". > PS: je t'ai envoyé quelques pistes, mais bon si t'es saoûlé je > comprends. On est tous tombé sur des problèmes "qui piquent" où tout le > monde s'arrache les cheveux, au bout d'un moment tu te dis, "et merde", > et tu fais avec/sans ! > J'ai bon ? : Merci : Oui, bien sûr, c'est cela, les conseils fournis ne fonctionnaient pas. D'un coup, je reçois un mail agressif carrément injuste d'un auteur qui n'avait pas lu mes réponses d'erreur et en m'accusant de ne pas avoir testé les commandes, alors que l'avais dûment fait. Mon "je laisse tomber" exprimait que j'avais lancé toutes les commandes fournies dont "xrandr", résultats dûment relatés sur la liste, (la preuve sur mes récents mails). Aussi la suppression des fichiers du /boot/ "6.1.0-18-amd64", m'empêche toujours d'upgrader mon système Bookworm. Tant pis, je décide de ne pas insister pour ne pas perturber la ML, sans accusation d'aucune sorte à qui que ce soit. On ne peut qu'exploser quand on reçoit une réaction aussi inique. Un incident bien inutile, par un membre ne lit pas les contenus des mails. Allez bonne nuit, je m'en remettrai :-)
f3tools vs Silicon Power 4T drive
Drive is plugged into amobo usb-3 port via a startech USB3S2SAT3CB ADAPTER CABLE. f3probe took over 16 seconds, but says it the real thing: root@coyote:~# f3probe /dev/sdc F3 probe 8.0 Copyright (C) 2010 Digirati Internet LTDA. This is free software; see the source for copying conditions. WARNING: Probing normally takes from a few seconds to 15 minutes, but it can take longer. Please be patient. Probe finished, recovering blocks... Done Good news: The device `/dev/sdc' is the real thing Device geometry: *Usable* size: 3.64 TB (7814037168 blocks) Announced size: 3.64 TB (7814037168 blocks) Module: 4.00 TB (2^42 Bytes) Approximate cache size: 0.00 Byte (0 blocks), need-reset=no Physical block size: 512.00 Byte (2^9 Bytes) Probe time: 16.04s 2nd drive is a CC of first. So in hex, those two should yield 7.28T of storage.. I have made 1 full partiton om each one, a labeled those partitions as SiPwr_0 and SiPwr_1 I have not attempted to do anything else until the hdwe is fully assembled. My only question it will those partition names survive lvcreating an 11T lvm out of these and 2 more 2T gigastones. Thanks for any advice since I have not dealt with an lvm in about 15+ years trying it once when it first came out with a high disaster rating then. This time the experiment will be on something expendable in its early days. Thank you all. Take care, stay warm and well. Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: Does "LC_ALL=C" work on all shells?
On Wed, Feb 14, 2024 at 09:45:52PM +0100, Franco Martelli wrote: > A new question arise spontaneously: how can csh users run a "script" saved > session using "scriptreplay" command? In the §4.4.1 "Recording the session" > paragraph ¹ I see this syntax: > > # scriptreplay ~/upgrade-bookwormstep.time ~/upgrade-bookwormstep.script > > That it uses both stderr and stdout saved separately. Maybe they have to use > another syntax or forcibly run a Bourne shell as you wrote below: The man page says: -t[file], --timing[=file] Output timing data to standard error, or to file when given. This option is deprecated in favour of --log-timing where the file argument is not optional. And: -T, --log-timing file Log timing information to the file. Two timing file formats are supported now. The classic format is used when only one stream (input or output) logging is enabled. The multi-stream format is used on --log-io or when --log-in and --log-out are used together. See also --logging-format. One of these paragraphs should give a solution that avoids needing 2>.
Re: perte clavier suite à retour de veille depuis bookworm-12.5
Bonjour Jacques, > Depuis la mise à jour bookworm du week-end dernier (12.5) , le > clavier de mon PC portable (dell latitude 3340) ne fonctionne > plus après un retour de veille. […] > Est-ce que quelqu'un parmi vous est également confronté à ce > problème et si oui a-t-il su contourner la difficulté > (paramétrage du noyau au boot ou ...)? ou s'agit-il selon vous > d'un bug du noyau 6.1.0-18-amd64 ? Le symptôme ressemble furieusement à celui décrit dans une rustine apparue dans Linux 6.1.74 pour éviter ce problème sur Acer P459-G2-M [1]. Linux a vu des mises à jour du pilote input en versions 6.1.70, 6.1.74 et 6.1.75. On n'est pas à l'abri que l'un de ces changements ait introduit ce bug. J'aurais donc tendance à penser que c'est un bug du noyau 6.1.0-18-amd64. [1] : https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.1.y=626b0c0ab3a06d02e32700de026c0c3f828f8492 Si ça peut aider, -- .''`. Étienne Mollier : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/5, please excuse my verbosity `-on air: Spock's Beard - 4th Of July signature.asc Description: PGP signature
Re: Does "LC_ALL=C" work on all shells?
On 14/02/24 at 17:48, Greg Wooledge wrote: On Wed, Feb 14, 2024 at 05:35:59PM +0100, Franco Martelli wrote: On 14/02/24 at 17:15, Greg Wooledge wrote: # env LC_ALL=C script -t 2>~/upgrade-bookwormstep.time -a ~/upgrade-bookwormstep.script That command is already using Bourne family shell syntax (the 2> part) so you can drop the env. It'll fail in csh regardless. On the other hand, the env doesn't hurt anything. It's just extra typing. Ah! However it's needed for csh users so they are warned, if it's extra typing it doesn't hurt, thought. csh cannot redirect stdout and stderr separately. You can either redirect stdout only, or redirect them both into the same file. It has *nothing* equivalent to >file1 2>file2. A new question arise spontaneously: how can csh users run a "script" saved session using "scriptreplay" command? In the §4.4.1 "Recording the session" paragraph ¹ I see this syntax: # scriptreplay ~/upgrade-bookwormstep.time ~/upgrade-bookwormstep.script That it uses both stderr and stdout saved separately. Maybe they have to use another syntax or forcibly run a Bourne shell as you wrote below: The usual recommendations for csh users who need to do this are either: 1) Run sh, and then run the command. 2) sh -c 'long command with >file1 2>file2' Then run env command at the beginning it is useless. Thanks again ¹ https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#record-session -- Franco Martelli
Re: AW: AW: su su- sudo dont work
Yes there are many updated kernels to choose from. Please go ahead and do so On Sat, Feb 10, 2024 at 8:21 AM Schwibinger Michael wrote: > Yes. > > > I found out > I do use an old kernel. > > Can LINUX update a kernel? > > Regards > Sophie > > > -- > *Von:* chris > *Gesendet:* Mittwoch, 7. Februar 2024 19:35 > *An:* Schwibinger Michael > *Betreff:* Re: AW: AW: su su- sudo dont work > > Very helpful ty > > On Wed, Feb 7, 2024, 1:57 PM Schwibinger Michael wrote: > > Good afternoon. > > The bug report > > sudo ... > You are not in the sudoers file. > Regards > Sophie > > > -- > *Von:* Hans > *Gesendet:* Freitag, 26. Januar 2024 18:44 > *An:* debian-user@lists.debian.org > *Betreff:* Re: AW: AW: su su- sudo dont work > > > Am Freitag, 26. Januar 2024, 17:23:07 CET schrieben Sie: > > Yes, if you want to install soemthing for example by using the apt > command, best way is becoming root with the command "su -" and then install > the rquired package. > > > Example: > > su - then enter the password of the user root > > > If installing for example firefox, first read the repository: > > > apt update > > > then install the package > > > apt install firefox-esr > > > - > > > Hint: If you want a graphical method and you have no X and Wndow-Manager > running (like KDE, Gnome, XFCE whatever), I suggest using aptitude. > > > You have to install aptitude first: > > > apt install aptitude > > > Then you can start the gui with the command "aptitude" as root. > > > Hint 2: aptitude is controlled by keypresses without any enter-key. > > For example, when started aptitude, just press the "u" key and it reads > the update, "U" (Shift + u) marks all newer packages automatically to be > updated, then press "g" and you will shwo, what it will do. Press "g" > again, and it will do the update. > > > Please note: If you want to upgrade the whole sytem, then using apt or > apt-get will be the better choice! > > > But aptitude is very well for installing single packages or weekly > upgrades, where not much packages will be renewed. > > > If you are not much experienced, and you have a window-manager running > like KDE, Gnome, XFCE, LXDE or another one, then look at synaptic. Synaptic > is a graphical tool for installing packages, it is a GUI for apt. > > > Synaptic MUST run as root. > > > Hope this helps. > > > By the way: I believe, you are not very experienced in English language, > so I suggest to suscribe in the fine German forum, > > which is debian-user-ger...@lists.debioan.org. > > > Here is the link: > > https://lists.debian.org/debian-user-german/ > > > Good luck! > > > Hans > > > > > Sorry > > > it was my mistake > > > > > > It is > > > > > > su - > > > su > > > or sudo. > > > > > > Sorry. > > > > > > Is su - > > > the best for install? > > > > > > Regards > > > > > > Sophie > > > > > > > > > > > > > >
Thunderbird inbox malfunction
After an upgrade of Debian 11 yesterday, Thunderbird 115.7.0 now has an inbox issue where the listings move making it difficult to save or delete them! I had this exact issue with Debian based Antix 22 after a recent upgrade. That problem was resolved by a subsequent upgrade from Thunderbird.
Re: Erreur nvidia suite upgrade noyau 6.1.0-18
Rilax les gens (: A mon avis c'est juste une incompréhension. En caricaturant : - Michel a compris qu'André disait "je laisse tomber, ça montre bien qu'il y a que des noobs/gens inutiles ici". - Alors qu'André voulait dire "je laisse tomber car ça me saoûle, dommage car ça aurait pu profiter à d'autres". J'ai bon ? PS: je t'ai envoyé quelques pistes, mais bon si t'es saoûlé je comprends. On est tous tombé sur des problèmes "qui piquent" où tout le monde s'arrache les cheveux, au bout d'un moment tu te dis, "et merde", et tu fais avec/sans ! -- ++ zithro / Cyril
Re: Does "LC_ALL=C" work on all shells?
On Wed, Feb 14, 2024 at 05:35:59PM +0100, Franco Martelli wrote: > On 14/02/24 at 17:15, Greg Wooledge wrote: > > > # env LC_ALL=C script -t 2>~/upgrade-bookwormstep.time -a > > > ~/upgrade-bookwormstep.script > > That command is already using Bourne family shell syntax (the 2> part) > > so you can drop the env. It'll fail in csh regardless. On the other > > hand, the env doesn't hurt anything. It's just extra typing. > > > > Ah! However it's needed for csh users so they are warned, if it's extra > typing it doesn't hurt, thought. csh cannot redirect stdout and stderr separately. You can either redirect stdout only, or redirect them both into the same file. It has *nothing* equivalent to >file1 2>file2. The usual recommendations for csh users who need to do this are either: 1) Run sh, and then run the command. 2) sh -c 'long command with >file1 2>file2'
Re: Does "LC_ALL=C" work on all shells?
On Wed, Feb 14, 2024 at 05:11:55PM +0100, Franco Martelli wrote: > Well, I'll go with env command syntax for shells portability. I was asking > this because I want to suggest a change to the DDP (Debian Documentation > Project) members for the releases notes documentation ¹ > > The change I want to suggest is to add "env LC_ALL=C" to the "script" > command: > > # env LC_ALL=C script -t 2>~/upgrade-bookwormstep.time -a > ~/upgrade-bookwormstep.script That command is already using Bourne family shell syntax (the 2> part) so you can drop the env. It'll fail in csh regardless. On the other hand, the env doesn't hurt anything. It's just extra typing.
Re: Does "LC_ALL=C" work on all shells?
On 13/02/24 at 23:23, Nicolas George wrote: Will Mengarini (12024-02-13): * Greg Wooledge [24-02/13=Tu 15:59 -0500]: In csh, you need to use env. Like this: What Greg posted also works, because it's an invocation of the 'env' command, not csh syntax. Yes. What made Greg's statement false was not the fact that it does not work but the verb “need”. What you posted also works, but it runs the command in a subshell of csh, so I doubt it gains efficiency over running the command under env. env is also executed in a subshell, but unlike what I posted, env will also require an exec() and probably some dynamic linking. Well, I'll go with env command syntax for shells portability. I was asking this because I want to suggest a change to the DDP (Debian Documentation Project) members for the releases notes documentation ¹ The change I want to suggest is to add "env LC_ALL=C" to the "script" command: # env LC_ALL=C script -t 2>~/upgrade-bookwormstep.time -a ~/upgrade-bookwormstep.script I think that a recorded session with the output of the commands in English is better then a localized session for debugging purposes. Thanks to all for the feedback! ¹ https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#record-session -- Franco Martelli
Re: Erreur nvidia suite upgrade noyau 6.1.0-18
On Wednesday 14 February 2024 10:53:52 Michel Verdier wrote: > Le 13 février 2024 ajh-valmer a écrit : > > Je vais arrêter de vous embêter avec mes déboires, > > sauf qu'il peut servir l'expérience des membres de cette ML. > Je ne peux pas laisser passer ça !! > La seule expérience que tu peux donner aux autres, pour ce thread, et > sans doute d'autres de tes threads, c'est : > - il faut lire *la totalité* des commandes suggérées, les comprendre, et > les passer *en totalité* > - de même pour les docs indiquées > - si on te demande des infos, les fournir avant d'affirmer que personne > ne donne de solution > - séparer les problèmes et les résoudre un à un au lieu de les enchaîner > et de noyer tout le monde sans avoir respecté les points précédents : À mon tour : JE NE PEUX PAS LAISSER PASSER ÇA !! VOILÀ QUI EST UN PEU FORT, HONTEUX DE TA PART !!! J'ai brossé TOUTES les commandes indiquées. Je ne pouvais pas tester des commandes qui m'affichaient des erreurs, que j'ai dûment publiées sur ma ML. Je n'ai jamais "affirmé que personne ne me donnait de solution". Peux tu me fournir cet écrit ? Alors, j'ai simplement décidé de ne pas poursuivre sur ce sujet, c'est tout. Mail complètement à côté de la plaque, "va te faire foutre". André Valmer
perte clavier suite à retour de veille depuis bookworm-12.5
Bonjour à tous, Depuis la mise à jour bookworm du week-end dernier (12.5) , le clavier de mon PC portable (dell latitude 3340) ne fonctionne plus après un retour de veille. Je suis actuellement contraint de rebooter pour en retrouver l'usage :-( Cette erreur est systématique avec le noyau linux-image-6.1.0-18-amd64. Par contre si je boote sur un noyau linux-image-6.1.0-17-amd64 , je ne constate pas ce problème. Est-ce que quelqu'un parmi vous est également confronté à ce problème et si oui a-t-il su contourner la difficulté (paramétrage du noyau au boot ou ... )? ou s'agit-il selon vous d'un bug du noyau 6.1.0-18-amd64 ? Merci pour vos réponses et bonne journée
Re: Does "LC_ALL=C" work on all shells?
On 2/13/24 22:11, Greg Wooledge wrote: On Tue, Feb 13, 2024 at 09:47:52PM -0500, Gremlin wrote: This is from a script installed by a package that does a dpkg-reconfigure locales to set the locale on the machine. What package? What script? I am working on it with a high rate a speed, should be completed next year. BTW where is LANGUAGE defined in the "standards/conventions"? It's a GNUism. https://www.gnu.org/software/gettext/manual/html_node/The-LANGUAGE-variable.html -- Hindi madali ang maging ako
Re: simple virt-manager setup
On 2024-02-14 09:40, Felix Natter wrote: Dear Michael, many thanks for the detailed answer, I will keep all of this for reference as I learn about libvirt! Am I right that it is not possible to backup/restore VMs using virt-manager GUI (on Debian12)? ChatGPT suggested this is possible, but confused this with Hyper-V I think ;-) So my best bet for backup/restore of data+config of a VM is to script libvirt or use an existing bash script [1]? (Can you recommend one?) Might this fit your needs? https://github.com/abbbi/virtnbdbackup Grx HdV
Re: Erreur nvidia suite upgrade noyau 6.1.0-18
Le 13 février 2024 ajh-valmer a écrit : > Je vais arrêter de vous embêter avec mes déboires, > sauf qu'il peut servir l'expérience des membres de cette ML. Je ne peux pas laisser passer ça !! La seule expérience que tu peux donner aux autres, pour ce thread, et sans doute d'autres de tes threads, c'est : - il faut lire *la totalité* des commandes suggérées, les comprendre, et les passer *en totalité* - de même pour les docs indiquées - si on te demande des infos, les fournir avant d'affirmer que personne ne donne de solution - séparer les problèmes et les résoudre un à un au lieu de les enchaîner et de noyer tout le monde sans avoir respecté les points précédents
Re: simple virt-manager setup
On 14 Feb 2024 09:40 +0100, from fnat...@gmx.net (Felix Natter):
> Am I right that it is not possible to backup/restore VMs
> using virt-manager GUI (on Debian12)? ChatGPT suggested this
> is possible, but confused this with Hyper-V I think ;-)
ChatGPT is _not_ a reliable source of information. Do not treat it as
a source of truthful statements.
If there is a way to back up VMs through virt-manager, I haven't found
it in my usage. Admittedly, I use ZFS snapshots for when I need to
roll back a VM disk image, which has happened rarely.
> So my best bet for backup/restore of data+config of a VM is to script
> libvirt or use an existing bash script [1]? (Can you recommend one?)
> Or is there a ProxMox vzdump equivalent for Debian?
I haven't looked at the page you link to, but yes, a disk image backup
of some kind plus a XML dump of the virtual machine ("domain" in
libvirt/KVM parlace) will allow you to recreate the VM to that point
in time. You can also clone VMs.
--
Michael Kjörling https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”
Re: simple virt-manager setup
Dear Michael, many thanks for the detailed answer, I will keep all of this for reference as I learn about libvirt! Am I right that it is not possible to backup/restore VMs using virt-manager GUI (on Debian12)? ChatGPT suggested this is possible, but confused this with Hyper-V I think ;-) So my best bet for backup/restore of data+config of a VM is to script libvirt or use an existing bash script [1]? (Can you recommend one?) Or is there a ProxMox vzdump equivalent for Debian? [1] https://ostechnix.com/export-import-kvm-virtual-machines-linux/ Further answers inline. Michael Kjörling <2695bd53d...@ewoof.net> writes: > On 13 Feb 2024 18:10 +0100, from fnat...@gmx.net (Felix Natter): >> regarding virt-manager (qemu/kvm): >> >> Can I safely choose the "NAT" network type for a new VM >> in virt-manager (Debian12): > > Yes. Doing so should create a new network interface named virbr[0-9] > and assign an IPv4 address range to it which will be used for VM > purposes. > >> Can I safely say yes to >> "Do you want to bring it up?"? (is it undoable?) > > Yes, it is undoable. You can either use virt-manager -> connection > details -> virtual networks (select the network and then click the > stop button below the list) or you can use > > $ sudo virsh net-list --all > > $ sudo virsh net-destroy network-name > > Despite the scary action name, virsh net-destroy only stops the > network; it doesn't actually deconfigure it. (For that, you use virsh > net-undefine. There is also virsh net-autostart.) See the virsh(1) man > page. > > If you want to be extra certain, you can dump your firewall rules just > before you bring up the KVM network so that you can restore them > without a reboot. > > >> If I choose NAT, can multiple VMs connect to each other >> and with the host? > > I know that VMs can talk to the host through a KVM NAT interface. I > haven't tested whether they can talk to each other, but I would expect > so. In my previous installation I used WLAN as well, so my understanding is that I could not have used type=bridge, and I did communicate between vms (mounting nfs shares), so I think this _should_ work. > If you are using nftables on the host, you might find my blog post at > https://michael.kjorling.se/blog/2022/linux-kvm-host-nftables-guest-networking/ > helpful if VMs can't talk to the network. I have received some > feedback that there are easier solutions, but try as I did at the time > I couldn't find them, and what I wrote up there Works For Me (tm). I did not change anything in the firewall. >> (I would like to avoid making many changes that I don't understand >> to a productive server) > > Very understandable, and prudent. *thumbup* > You may want to consider subscribing to > https://lists.libvirt.org/archives/list/us...@lists.libvirt.org/; > subscription is mailto:users-j...@lists.libvirt.org. Good suggestion! I will do this. Many Thanks and Best Regards, Felix -- Felix Natter
