Re: f3tools vs Silicon Power 4T drive
Stefan Monnier writes: > - Use an additional tiny dummy partition in which you can put any info > you like. This seems to be what Microsoft likes to do. At least I had the pleasure of tossing a "Microsoft reserved" partition out from my desktop recently, I think the Windows 10 installer created that but didn't use it. It was just 16 MB of zeros in a very inconvenient location.
Re: Erreur nvidia suite upgrade noyau 6.1.0-18
Le 14 février 2024 zithro a écrit : > - Michel a compris qu'André disait "je laisse tomber, ça montre bien > qu'il y a que des noobs/gens inutiles ici". Effectivement ça me semblait une attaque de la liste, d'où la forme abrupte de mon mail pour laquelle je m'excuse.
Re: Does "LC_ALL=C" work on all shells?
* 2024-02-15 21:17:44+0100, Franco Martelli wrote: > Doesn't LC_ALL=C setting override LANG or LANGUAGE settings? LC_ALL overrides LC_* variables. It's easy to test: $ locale LANG=fi_FI.UTF-8 LANGUAGE=fi LC_CTYPE="fi_FI.UTF-8" LC_NUMERIC="fi_FI.UTF-8" LC_TIME="fi_FI.UTF-8" LC_COLLATE="fi_FI.UTF-8" LC_MONETARY="fi_FI.UTF-8" LC_MESSAGES=C LC_PAPER="fi_FI.UTF-8" LC_NAME="fi_FI.UTF-8" LC_ADDRESS="fi_FI.UTF-8" LC_TELEPHONE="fi_FI.UTF-8" LC_MEASUREMENT="fi_FI.UTF-8" LC_IDENTIFICATION="fi_FI.UTF-8" $ LC_ALL=C locale LANG=fi_FI.UTF-8 LANGUAGE=fi LC_CTYPE="C" LC_NUMERIC="C" LC_TIME="C" LC_COLLATE="C" LC_MONETARY="C" LC_MESSAGES="C" LC_PAPER="C" LC_NAME="C" LC_ADDRESS="C" LC_TELEPHONE="C" LC_MEASUREMENT="C" LC_IDENTIFICATION="C" LC_ALL=C $ LC_ALL=C.UTF-8 locale LANG=fi_FI.UTF-8 LANGUAGE=fi LC_CTYPE="C.UTF-8" LC_NUMERIC="C.UTF-8" LC_TIME="C.UTF-8" LC_COLLATE="C.UTF-8" LC_MONETARY="C.UTF-8" LC_MESSAGES="C.UTF-8" LC_PAPER="C.UTF-8" LC_NAME="C.UTF-8" LC_ADDRESS="C.UTF-8" LC_TELEPHONE="C.UTF-8" LC_MEASUREMENT="C.UTF-8" LC_IDENTIFICATION="C.UTF-8" LC_ALL=C.UTF-8 In my opinion it's often too much to set LC_ALL=C because it changes charset to ASCII (LC_CTYPE). To change programs' output messages to English LC_MESSAGES=C is often enough. Sometimes LC_TIME and LC_NUMERIC are required too. -- /// Teemu Likonen - .-.. https://www.iki.fi/tlikonen/ // OpenPGP: 6965F03973F0D4CA22B9410F0F2CAE0E07608462 signature.asc Description: PGP signature
Re: f3tools vs Silicon Power 4T drive
On 2/15/24 16:20, David Wright wrote:
On Thu 15 Feb 2024 at 20:44:52 (+), Andy Smith wrote:
On Thu, Feb 15, 2024 at 03:19:54PM -0500, gene heskett wrote:
On 2/15/24 11:21, Andy Smith wrote:
You asked if "labels" would survive their associated partition being
put into LVM.
I said, "yes if you mean partition names, no if you mean filesystem
labels".
I'm still confused and it is not all the well clarified by looking at
gparted, a shot of which I posted.
This could all be answered easily if you'd just post the copy-paste
of your terminal scrollback for what you actually did. Hopefully you
don't now object to me asking what you meant since apparently even
you do not know if you mean partition names or filesystem labels.
>From what you posted it now sounds like labels on the ext4
filesystems that you created.
Gene effectively shoots himself in the foot by using gparted (GUI)
instead of, say, gdisk where it's easy to paste what was done, or
for someone, say me, to post an example:
# gdisk /dev/sdz
GPT fdisk (gdisk) version 1.0.3
Partition table scan:
MBR: not present
BSD: not present
APM: not present
GPT: not present
Creating new GPT entries.
Command (? for help): o
This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): y
Command (? for help): p
Disk /dev/sdb: 3907029168 sectors, 1.8 TiB
Model: Desktop
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): A1093790-9A1A-4A7E-A807-B9CC6F7CF77E
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 2048-sector boundaries
Total free space is 3907029101 sectors (1.8 TiB)
Number Start (sector)End (sector) Size Code Name
Command (? for help): n
Partition number (1-128, default 1):
First sector (34-3907029134, default = 2048) or {+-}size{KMGTP}:
Last sector (2048-3907029134, default = 3907029134) or {+-}size{KMGTP}:
Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300):
Changed type of partition to 'Linux filesystem'
Command (? for help): c
Using 1
Enter name: Lulu01
Command (? for help): i
Using 1
Partition GUID code: 0FC63DAF-8483-4772-8E79-3D69D8477DE4 (Linux filesystem)
Partition unique GUID: 37CF9EDF-C695-428E-9889-2F52C40DFCA5
First sector: 2048 (at 1024.0 KiB)
Last sector: 3907029134 (at 1.8 TiB)
Partition size: 3907027087 sectors (1.8 TiB)
Attribute flags:
Partition name: 'Lulu01'
Command (? for help): w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/sdb.
The operation has completed successfully.
#
# gdisk -l /dev/sdz
GPT fdisk (gdisk) version 1.0.3
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sdb: 3907029168 sectors, 1.8 TiB
Model: Desktop
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): A1093790-9A1A-4A7E-A807-B9CC6F7CF77E
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector)End (sector) Size Code Name
12048 3907029134 1.8 TiB 8300 Lulu01
#
Cheers,
David.
.
And this "partition" name survives?, and can be unique?, and can be used
in a mount cmd? That's how I'll do it then. This if all 3 questions
above can be answered with a yes is the answer I've been trying to
squeeze out all along. Thank you.
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/15/24 16:20, Andy Smith wrote: Hi, On Thu, Feb 15, 2024 at 03:59:30PM -0500, gene heskett wrote: Now the question remains howinhell do I put a label on a drive such that it does survive making a raid or lvm device with it? To not have a way to id its the drive in slot n of a multislot rack stops me in my tracks. Given that an MD RAID array or a LVM Logical Volume may be spread across many different underlying storage devices, the question doesn't make sense. Due to the fact that filesystems go on block devices, and RAID arrays and LVM LVs can be block devices, a filesystem label in that instance would represent possibly multiple underlying storage devices. So step back and tell us what are you actually trying to achieve, rather than insisting on your X solution to your Y problem. Suppose you have the MD array /dev/md42. What are you conceptually wanting to do with that in relation to labels of some kind? What information is it that you want? Support you have LVM logical volume /dev/myvg/mylv. What are you conceptually wanting to do with that in relation to labels of some kind? What information is it that you want? I want to know with absolute certainty, with of the 4 drives in that raid10, actually has a belly ache. When it has a belly ache. I can't see any reason on this ball of rock and water, why I should be expected to replace a drive at a time until the belly ache goes away. Particularly with these gigastones, I 5 of them but when all are plugged in there are only 3 becauae there are 2 pairs of matching serial numbers in the by-id output, by-id sees all 5 drives, but udev see's only the unique serial numbers. gparted can change the devices blkid, getting a new one from rng so while you all think that's the greatest thing since bottled beer, I know better. Once you explain what information you're trying to get when you start with an LVM or MD device, I can probably advise how to get it, but just to make clear: I don't think it's a good idea to continue to use such broken devices. We don't need to debate that since I know you've been posting about that a lot and clearly have decided to push ahead. I just think you haven't seen the end of the problems with that issue. Regards, Andy Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: Package Identification Assistance
On Fri, Feb 16, 2024 at 12:27 AM Neal Heinecke wrote: > > I need to identify the package responsible for creating the software sources > window. There is a minor bug/typo where the first tab reads "Ubuntu Software" If you can locate the program that owns the window, then you can identify the package with `dpkg -S`. To identify the program: $ ps -A > 1.txt $ ps -A > 2.txt Then run diff to see the list of candidate programs: $ diff 1.txt 2.txt Finally, run `dpkg -S` using the full path of the program, like /usr/bin/foo. Jeff
Re: Package Identification Assistance
On Thu, 15 Feb 2024 20:33:16 -0500 Neal Heinecke wrote: > I need to identify the package responsible for creating the software > sources window. There is a minor bug/typo where the first tab reads > "Ubuntu Software" I have no idea what a "software sources window" is. Do you know the name of the program? Often the name of the program is also the name of the package. Apt-file is a useful tool here. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: Issue with USB External Keyboard, External Mouse, and Screen Brightness on Dell Laptop
On 15/02/2024 12:39, David Wright wrote: 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? Battery health may be estimated from output of upower --dump by comparison energy-full-design, energy-full, and other values. I still believe it is excessively aggressive power settings in GNOME or in firmware (BIOS) setup. Maybe it is result of shooting own foot by tools like powertop or tlp. Anyway it is rather wrong settings than wrong behavior. There is a chance that the issue is with USB controller driver. Likely it is better to ask the same question in a user group more specific to power management.
Re: Does "LC_ALL=C" work on all shells?
On 16/02/2024 09:34, David Wright wrote: Yes, LC_ALL=C will override all the locale variables, but LC_ALL=C.UTF-8 will not: It is documented in 2.3.3 Specifying a Priority List of Languages (info "(gettext) The LANGUAGE variable") https://www.gnu.org/software/gettext/manual/html_node/The-LANGUAGE-variable.html however you may still prefer LC_ALL=C.UTF-8 LANGUAGE= due to touch /tmp/it/è LC_ALL=C.UTF-8 ls /tmp/it/ è LC_ALL=C ls /tmp/it/ ''$'\303\250'
Re: Does "LC_ALL=C" work on all shells?
On Thu 15 Feb 2024 at 21:17:44 (+0100), Franco Martelli wrote: > On 15/02/24 at 03:28, Max Nikulin wrote: > > > # 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. > > Doesn't LC_ALL=C setting override LANG or LANGUAGE settings? On my > system I have: > > ~$ env | grep LANG > LANGUAGE= > LANG=it_IT.UTF-8 BTW, you can also print locale information with: $ locale LANG=C.UTF-8 LANGUAGE= LC_CTYPE=en_GB.UTF-8 LC_NUMERIC="C.UTF-8" LC_TIME="C.UTF-8" LC_COLLATE="C.UTF-8" LC_MONETARY="C.UTF-8" LC_MESSAGES="C.UTF-8" LC_PAPER="C.UTF-8" LC_NAME="C.UTF-8" LC_ADDRESS="C.UTF-8" LC_TELEPHONE="C.UTF-8" LC_MEASUREMENT="C.UTF-8" LC_IDENTIFICATION="C.UTF-8" LC_ALL= $ > and LC_ALL=C override the LANG setting when used inline of the > command. This approach is to cover all cases, my goal is to do > apt/apt-get commands output in English when they are executed into a > "script" session. Yes, LC_ALL=C will override all the locale variables, but LC_ALL=C.UTF-8 will not: $ LC_ALL=C.UTF-8 LANGUAGE=it LANG=it_IT.UTF-8 aptitude why firefox-esr i firefox-esr-l10n-en-gb Dipende firefox-esr (< 115.7.0esr-1~deb11u1.1~) $ LC_ALL=C LANGUAGE=it LANG=it_IT.UTF-8 aptitude why firefox-esr i firefox-esr-l10n-en-gb Depends firefox-esr (< 115.7.0esr-1~deb11u1.1~) $ Cheers, David.
Re: Does "LC_ALL=C" work on all shells?
On 16/02/2024 03:17, Franco Martelli wrote: On 15/02/24 at 03:28, Max Nikulin wrote: LANG=C.UTF-8; LANGUAGE=; export LANG LANGUAGE Doesn't LC_ALL=C setting override LANG or LANGUAGE settings? Sorry, my bad. Of course LC_ALL=C.UTF-8; LANGUAGE=; export LC_ALL LANGUAGE and LC_ALL=C override the LANG setting when used inline of the command. LC_ALL does not override LANGUAGE. Try e.g. LC_ALL=C.UTF-8 LANGUAGE=it aptitude why firefox-esr # env LC_ALL=C script -T ~/upgrade-bookwormstep.time -a ~/upgrade-bookwormstep.script Try to add "export LC_ALL=it_IT.UTF-8" to .bashrc and e.g."date" in the script session.
Package Identification Assistance
I need to identify the package responsible for creating the software sources window. There is a minor bug/typo where the first tab reads "Ubuntu Software" Thanks!
Re: f3tools vs Silicon Power 4T drive
On 2/15/24 15:45, Andy Smith wrote: Hi, On Thu, Feb 15, 2024 at 03:19:54PM -0500, gene heskett wrote: On 2/15/24 11:21, Andy Smith wrote: You asked if "labels" would survive their associated partition being put into LVM. I said, "yes if you mean partition names, no if you mean filesystem labels". I'm still confused and it is not all the well clarified by looking at gparted, a shot of which I posted. This could all be answered easily if you'd just post the copy-paste of your terminal scrollback for what you actually did. Hopefully you don't now object to me asking what you meant since apparently even you do not know if you mean partition names or filesystem labels. From what you posted it now sounds like labels on the ext4 filesystems that you created. What you're trying to do (LVM on MD RAID?) is quite complicated and you clearly don't have much experience in this area. That's okay but it does mean that you're likely to make a lot of mistakes with a thing that holds your data, so you need to be prepared for that. For example, you mentioned only as an aside that you intended to get two more drives and put the four of them into an LVM, but you did not know that this would blow away the filesystems already on the drives, and that this would not by itself provide you with any redundancy. So if you hadn't said anything and I hadn't questioned this, you could well have spent a lot of time creating something that isn't correct and needs to be torn down again, possibly with data loss. Again that's okay — we learn by experimentation — but you're going to have to prepare yourself for doing this over again many times. And I also want to reiterate that you're going to have questions, and that is good, but if we here on this list are not to be driven insane by the ambiguities and misunderstandings, please, please, PLEASE post logs of the commands you type on this adventure when you ask them. Please. If you have questions, ask them. Like which version of a raid is the best at tolerating a failed drive, which give he best balance between redundancy and capacity. This is a complex subject. Before we get into it, what are you trying to achieve? Like, what is your end goal with these four drives? MD RAID isn't the only way to achieve redundancy. You also haven't explained why you need LVM. Depending on your needs, maybe a filesystem with redundancy and volume management features in it would be better. Like btrfs or zfs. May I miss-understood the wiki, xfs is stated as not being complete for linux, a zfx is I think commercial? Can you update that? Given the problems you had with MD RAID in the past I still maintain that you'd likely be better off just getting a storage appliance of some kind. One of the 1T samsungs in the md raid10 isn't entirely happy but mdadm has not fussed about it, and smartctl seems to say its ok after testing. Other than that the gui access delay (30+ seconds) problems I have did NOT go away when I moved /home off the raid to another SSD, so I may move it back. One of the reasons I ma rsync'ing this /home back to it every other day or so, takes < 5 minutes. Thanks, Andy Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: f3tools vs Silicon Power 4T drive
> Now the question remains howinhell do I put a label on a drive such > that it does survive making a raid or lvm device with it? LVM/MD take control of a block device (usually a partition), so any info in that block device can't be used for your purpose. IOW you have to put the info somewhere on the disk *outside* of the partition used by LVM/MD. I can see a few different options: - Use some disk-specific tool to change the disk's serial numbers. I'm not sure how common such tools are, they're probably manufacturer-specific and proprietary; my intuition tells me to try any other way first. - Use partition labels and/or partition UUIDs: contrary to filesystem labels, these are not stored inside the block device but inside the partition table. They don't exist in the old MBR-style partitions, but they do in GPT (GUID Partition Tables). - Use an additional tiny dummy partition in which you can put any info you like. Stefan
Re: f3tools vs Silicon Power 4T drive
On 2/15/24 15:45, Andy Smith wrote: Hi, On Thu, Feb 15, 2024 at 03:19:54PM -0500, gene heskett wrote: On 2/15/24 11:21, Andy Smith wrote: You asked if "labels" would survive their associated partition being put into LVM. I said, "yes if you mean partition names, no if you mean filesystem labels". I'm still confused and it is not all the well clarified by looking at gparted, a shot of which I posted. This could all be answered easily if you'd just post the copy-paste of your terminal scrollback for what you actually did. Hopefully you don't now object to me asking what you meant since apparently even you do not know if you mean partition names or filesystem labels. From what you posted it now sounds like labels on the ext4 filesystems that you created. What you're trying to do (LVM on MD RAID?) is quite complicated and you clearly don't have much experience in this area. That's okay but it does mean that you're likely to make a lot of mistakes with a thing that holds your data, so you need to be prepared for that. For example, you mentioned only as an aside that you intended to get two more drives and put the four of them into an LVM, but you did not know that this would blow away the filesystems already on the drives, and that this would not by itself provide you with any redundancy. So if you hadn't said anything and I hadn't questioned this, you could well have spent a lot of time creating something that isn't correct and needs to be torn down again, possibly with data loss. That is how we learn Andy Any data I put on this stuff while testing as normal files will be expected to be lost. So that possibility is expected. Experience is how I got where I am on an 8th grade education. Again that's okay — we learn by experimentation — but you're going to have to prepare yourself for doing this over again many times. Expected. And I also want to reiterate that you're going to have questions, and that is good, but if we here on this list are not to be driven insane by the ambiguities and misunderstandings, please, please, PLEASE post logs of the commands you type on this adventure when you ask them. I'll try. Please. If you have questions, ask them. When I get it assembled. Last 2 drives s/b here tom. Then I need to shut down and extract 4 of the gisastones which are plugged in atm but unmounted, the 5th one is now my /home partition. And I am rsync'ing /home back to that now idle raid10 about every other day. Like which version of a raid is the best at tolerating a failed drive, which give he best balance between redundancy and capacity. This is a complex subject. Before we get into it, what are you trying to achieve? Like, what is your end goal with these four drives? MD RAID isn't the only way to achieve redundancy. You also haven't explained why you need LVM. Depending on your needs, maybe a filesystem with redundancy and volume management features in it would be better. Like btrfs or zfs. Given the problems you had with MD RAID in the past I still maintain that you'd likely be better off just getting a storage appliance of some kind. Thanks, Andy Thank you Andy. Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: f3tools vs Silicon Power 4T drive
On Thu 15 Feb 2024 at 20:44:52 (+), Andy Smith wrote:
> On Thu, Feb 15, 2024 at 03:19:54PM -0500, gene heskett wrote:
> > On 2/15/24 11:21, Andy Smith wrote:
> > > You asked if "labels" would survive their associated partition being
> > > put into LVM.
> > >
> > > I said, "yes if you mean partition names, no if you mean filesystem
> > > labels".
> > >
> > I'm still confused and it is not all the well clarified by looking at
> > gparted, a shot of which I posted.
>
> This could all be answered easily if you'd just post the copy-paste
> of your terminal scrollback for what you actually did. Hopefully you
> don't now object to me asking what you meant since apparently even
> you do not know if you mean partition names or filesystem labels.
> >From what you posted it now sounds like labels on the ext4
> filesystems that you created.
Gene effectively shoots himself in the foot by using gparted (GUI)
instead of, say, gdisk where it's easy to paste what was done, or
for someone, say me, to post an example:
# gdisk /dev/sdz
GPT fdisk (gdisk) version 1.0.3
Partition table scan:
MBR: not present
BSD: not present
APM: not present
GPT: not present
Creating new GPT entries.
Command (? for help): o
This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): y
Command (? for help): p
Disk /dev/sdb: 3907029168 sectors, 1.8 TiB
Model: Desktop
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): A1093790-9A1A-4A7E-A807-B9CC6F7CF77E
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 2048-sector boundaries
Total free space is 3907029101 sectors (1.8 TiB)
Number Start (sector)End (sector) Size Code Name
Command (? for help): n
Partition number (1-128, default 1):
First sector (34-3907029134, default = 2048) or {+-}size{KMGTP}:
Last sector (2048-3907029134, default = 3907029134) or {+-}size{KMGTP}:
Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300):
Changed type of partition to 'Linux filesystem'
Command (? for help): c
Using 1
Enter name: Lulu01
Command (? for help): i
Using 1
Partition GUID code: 0FC63DAF-8483-4772-8E79-3D69D8477DE4 (Linux filesystem)
Partition unique GUID: 37CF9EDF-C695-428E-9889-2F52C40DFCA5
First sector: 2048 (at 1024.0 KiB)
Last sector: 3907029134 (at 1.8 TiB)
Partition size: 3907027087 sectors (1.8 TiB)
Attribute flags:
Partition name: 'Lulu01'
Command (? for help): w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/sdb.
The operation has completed successfully.
#
# gdisk -l /dev/sdz
GPT fdisk (gdisk) version 1.0.3
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sdb: 3907029168 sectors, 1.8 TiB
Model: Desktop
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): A1093790-9A1A-4A7E-A807-B9CC6F7CF77E
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector)End (sector) Size Code Name
12048 3907029134 1.8 TiB 8300 Lulu01
#
Cheers,
David.
Re: f3tools vs Silicon Power 4T drive
Hi, On Thu, Feb 15, 2024 at 03:59:30PM -0500, gene heskett wrote: > Now the question remains howinhell do I put a label on a drive > such that it does survive making a raid or lvm device with it? To > not have a way to id its the drive in slot n of a multislot rack > stops me in my tracks. Given that an MD RAID array or a LVM Logical Volume may be spread across many different underlying storage devices, the question doesn't make sense. Due to the fact that filesystems go on block devices, and RAID arrays and LVM LVs can be block devices, a filesystem label in that instance would represent possibly multiple underlying storage devices. So step back and tell us what are you actually trying to achieve, rather than insisting on your X solution to your Y problem. Suppose you have the MD array /dev/md42. What are you conceptually wanting to do with that in relation to labels of some kind? What information is it that you want? Support you have LVM logical volume /dev/myvg/mylv. What are you conceptually wanting to do with that in relation to labels of some kind? What information is it that you want? > Particularly with these gigastones, I 5 of them but when all are plugged in > there are only 3 becauae there are 2 pairs of matching serial numbers in the > by-id output, by-id sees all 5 drives, but udev see's only the unique > serial numbers. gparted can change the devices blkid, getting a new one from > rng so while you all think that's the greatest thing since bottled beer, I > know better. Once you explain what information you're trying to get when you start with an LVM or MD device, I can probably advise how to get it, but just to make clear: I don't think it's a good idea to continue to use such broken devices. We don't need to debate that since I know you've been posting about that a lot and clearly have decided to push ahead. I just think you haven't seen the end of the problems with that issue. Regards, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: f3tools vs Silicon Power 4T drive
On 2/15/24 14:41, Andy Smith wrote: Hello, On Thu, Feb 15, 2024 at 05:32:34PM +, debian-u...@howorth.org.uk wrote: Andy Smith wrote: Do remember that this mailing lists does not accept attachments (and very few mailing lists in general do), so any time you are tempted to send a photo to a mailing list it is probably an error. We did not see whatever it was, but it doesn't sound relevant. FWIW, the photo that Gene attached was certainly attached to the mail that the list sent to me, so I suppose that this list does permit attachments, at least in some circumstances. Oh yes you're right, I see it too now I've looked properly! So now I actually think Gene means a filesystem label? Sigh, this really does not need to be this difficult. Anyway I see that the image of gparted says there's an ext4 filesystem there. So, Gene: when you put those partitions into LVM (when you make them LVM Physical Volumes) the filesystems on them will be trashed, and so will the filesystem labels. Which is the answer I needed. Those names I wrote with gparted WILL be trashed. Now the question remains howinhell do I put a label on a drive such that it does survive making a raid or lvm device with it? To not have a way to id its the drive in slot n of a multislot rack stops me in my tracks. Particularly with these gigastones, I 5 of them but when all are plugged in there are only 3 becauae there are 2 pairs of matching serial numbers in the by-id output, by-id sees all 5 drives, but udev see's only the unique serial numbers. gparted can change the devices blkid, getting a new one from rng so while you all think that's the greatest thing since bottled beer, I know better. Take care, stay well all. Thanks, Andy Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: f3tools vs Silicon Power 4T drive
Hi, On Thu, Feb 15, 2024 at 03:19:54PM -0500, gene heskett wrote: > On 2/15/24 11:21, Andy Smith wrote: > > You asked if "labels" would survive their associated partition being > > put into LVM. > > > > I said, "yes if you mean partition names, no if you mean filesystem > > labels". > > > I'm still confused and it is not all the well clarified by looking at > gparted, a shot of which I posted. This could all be answered easily if you'd just post the copy-paste of your terminal scrollback for what you actually did. Hopefully you don't now object to me asking what you meant since apparently even you do not know if you mean partition names or filesystem labels. >From what you posted it now sounds like labels on the ext4 filesystems that you created. What you're trying to do (LVM on MD RAID?) is quite complicated and you clearly don't have much experience in this area. That's okay but it does mean that you're likely to make a lot of mistakes with a thing that holds your data, so you need to be prepared for that. For example, you mentioned only as an aside that you intended to get two more drives and put the four of them into an LVM, but you did not know that this would blow away the filesystems already on the drives, and that this would not by itself provide you with any redundancy. So if you hadn't said anything and I hadn't questioned this, you could well have spent a lot of time creating something that isn't correct and needs to be torn down again, possibly with data loss. Again that's okay — we learn by experimentation — but you're going to have to prepare yourself for doing this over again many times. And I also want to reiterate that you're going to have questions, and that is good, but if we here on this list are not to be driven insane by the ambiguities and misunderstandings, please, please, PLEASE post logs of the commands you type on this adventure when you ask them. Please. > > If you have questions, ask them. > > > Like which version of a raid is the best at tolerating a failed drive, which > give he best balance between redundancy and capacity. This is a complex subject. Before we get into it, what are you trying to achieve? Like, what is your end goal with these four drives? MD RAID isn't the only way to achieve redundancy. You also haven't explained why you need LVM. Depending on your needs, maybe a filesystem with redundancy and volume management features in it would be better. Like btrfs or zfs. Given the problems you had with MD RAID in the past I still maintain that you'd likely be better off just getting a storage appliance of some kind. Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: f3tools vs Silicon Power 4T drive
On 2/15/24 11:21, Andy Smith wrote: Hi, On Wed, Feb 14, 2024 at 09:56:07PM -0500, gene heskett wrote: On 2/14/24 19:48, Andy Smith wrote: 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.. You've split your reply to my mail across three different emails and now you're replying to a part about redundancy, but asking questions about something completely different, all while referring to bits that are not proximal to where your text is, so it's unclear to me exactly what you are asking about. You asked if "labels" would survive their associated partition being put into LVM. I said, "yes if you mean partition names, no if you mean filesystem labels". I'm still confused and it is not all the well clarified by looking at gparted, a shot of which I posted. Wikipedia seems to have the history but not the practice to the depth i'd like. I also looked at XFS on wikipedia, looks good, but I note it says then linux version linux is not complete. 2 more of the big Si Pwr 3.64T's will be here tomorrow. So I'll be inclined to put it together and see what I can make it do. There will no doubt be questions. To my implied question about your redundancy plans (if any), you then complain that I have not given you "a syllable about how to do it". Do *what*? I don't yet know what your plans are in that regard. If you have questions, ask them. Like which version of a raid is the best at tolerating a failed drive, which give he best balance between redundancy and capacity. Take care & stay well, Andy. Regards, Andy Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: Does "LC_ALL=C" work on all shells?
Thanks Max, On 15/02/24 at 03:28, Max Nikulin wrote: # 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. Doesn't LC_ALL=C setting override LANG or LANGUAGE settings? On my system I have: ~$ env | grep LANG LANGUAGE= LANG=it_IT.UTF-8 and LC_ALL=C override the LANG setting when used inline of the command. This approach is to cover all cases, my goal is to do apt/apt-get commands output in English when they are executed into a "script" session. Thank to Greg's contribute I think I've reached it: On 14/02/24 at 21:55, Greg Wooledge wrote: 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>. The following "script" command syntax should work on all shells (tested only in Bash): # env LC_ALL=C script -T ~/upgrade-bookwormstep.time -a ~/upgrade-bookwormstep.script -- Franco Martelli
Re: f3tools vs Silicon Power 4T drive
Hello, On Thu, Feb 15, 2024 at 05:32:34PM +, debian-u...@howorth.org.uk wrote: > Andy Smith wrote: > > Do remember that this mailing lists does not accept attachments (and > > very few mailing lists in general do), so any time you are tempted > > to send a photo to a mailing list it is probably an error. We did > > not see whatever it was, but it doesn't sound relevant. > > FWIW, the photo that Gene attached was certainly attached to the mail > that the list sent to me, so I suppose that this list does permit > attachments, at least in some circumstances. Oh yes you're right, I see it too now I've looked properly! So now I actually think Gene means a filesystem label? Sigh, this really does not need to be this difficult. Anyway I see that the image of gparted says there's an ext4 filesystem there. So, Gene: when you put those partitions into LVM (when you make them LVM Physical Volumes) the filesystems on them will be trashed, and so will the filesystem labels. Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: perte clavier suite à retour de veille depuis bookworm-12.5
Bonjour Jacques, > 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 ? Le comportement ne me paraît pas plus normal, quoiqu'il soit un peu différent. Je pense que ça vaudrait toujours le coup de le signaler aux développeurs noyau. Par ailleurs, la mitigation appliquée pourrait les intéresser : > 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 Bonne soirée, :) -- .''`. Étienne Mollier : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/2, please excuse my verbosity `- signature.asc Description: PGP signature
Re: Stretch vers Bullseye - Probleme lors du apt full-upgrade
Le lundi 12 février 2024, 19:23:39 CET Hugues MORIN-TRENEULE a écrit : > Salut > > Merci pour l'info > > Malheureusement même si j'entrevois de quoi tu parles, je ne sais pas trop > comment faire en pratique. > > Donc si je comprends bien, maintenant que j'ai fait de la place, il faut > que je relance la commande apt full-upgrade > Mais avant cela, je dois killer le pid de apt et faire un dpkg-reconfigure. > > Pour trouver le pid d'apt, c'est à l'aide de la commande ps? > Et apres kill "n° de pid" > > Est ce qu'il y a autre chose a faire pour killer le processus d'apt? Le plus simple c'est avec killall, et à mon avis il doit y avoir des enfants d'apt, en dpkg (avec sudo si tu n'es pas root) : killall dpkg killall apt Pour voir s'il en reste : ps -ef | grep apt ps -ef | grep dpkg Evidemment, ces commandes font aussi apparaitre le grep lui même. > Ensuite dpkg-reconfigure Je pense que c'est plutôt : dpkg --configure -a Quand l'install a été interrompue (notez les espaces, c'est bien la commande dpkg et non la commande dpkg-reconfigure. > et enfin apt full-upgrade > > Est ce que cela vous semble OK Ça devrait ! > Très cordialement > Hugues De même, Bonne soirée.
Re: AW: AW: su su- sudo dont work
Bump? On Wed, Feb 14, 2024 at 3:29 PM chris wrote: > 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 >> >> > >> >> > >> >> > >> >> > >> >>
Re: SMART Uncorrectable_Error_Cnt rising - should I be worried?
On 15 Feb 2024 10:41 -0500, from wande...@fastmail.fm (The Wanderer): >> 65,000 hard links seems to be an ext4 limit: >> >> https://www.linuxquestions.org/questions/linux-kernel-70/max-hard-link-per-file-on-ext4-4175454538/#post4914624 > > That sounds right. > >> I believe ZFS can do more hard links. (Much more? Limited by >> available storage space?) > > I'm not sure, but I'll have to look into that, when I get to the point > of trying to set up that tiered backup. ZFS can definitely do more; I ran a background loop hardlinking a single file on a new pool while typing up this email, and toward the end, it's at >75K and still going strong. That consumed about 5 MB of storage. >> Data integrity validation is tough without a mechanism. Adding an >> rsnapshot(1) postexec MD5SUMS, etc., file into the root of each >> backup tree could solve this need, but could waste a lot of time and >> energy checksumming files that have not changed. > > AFAIK, all such things require you to be starting from a point with a > known-good copy of the data, which is a luxury I don't currently have > (as far as validating my current data goes). It's something to keep in > mind when planning a more proper backup system, however. What you do have is a _current_ state. Being able to detect unintended changes from that state may be beneficial even if the current state isn't known-perfect. >> One of the reasons I switched to ZFS was because ZFS has built-in >> data and metadata integrity checking (and repair; depending upon >> redundancy). > > I'm not sure I understand how this would be useful in the case I have at > hand; that probably means that I'm not understanding the picture properly. Unless you go out of your way to turn off checksumming beforehand, ZFS will refuse to let you read a block where the checksum doesn't match the block's payload data. Meaning that if you're able to _read_ a block of data by normal means, you can be certain that the probability of it not matching what was originally written to disk to be _very_ low. ZFS will also automatically repair any repairable error it detects. In a redundant setup, this is almost everything; in a non-redundant setup, it's rather less, but still more than nothing. >> rsync(1) should be able to copy backups onto an external HDD. > > Yeah, but that only provides one tier of backup; the advantage of > rsnapshot (or similar) is the multiple deduplicated tiers, which gives > you options if it turns out the latest backup already included the > damage you're trying to recover from. rsnapshot is largely a front-end for rsync --link-dest=. It does make a few things easier but there isn't much you can do with rsnapshot that you can't do with rsync and a little shell scripting if you're willing to live with a specialized tool for your purposes. rsnapshot is generic. > (USB-3 will almost certainly not be a viable option for an automatic > scheduled backup of the sort rsnapshot's documentation suggests, because > the *fastest* backup cycle I saw from my working with the data I had was > over three hours, and the initial pass to copy the data out to the drive > in the first place took nearly *20* hours. A cron job to run even an > incremental backup even once a day, much less the several times a day > suggested for the deeper rsnapshot tiers, would not be *remotely* > workable in that sort of environment. Though on the flip side, that's > not just a USB-3 bottleneck, but also the bottleneck of the spinning > mechanical hard drive inside the external case...) I think rsnapshot's suggested backup schedule is excessively frequent for pretty much anything more than a relatively small home directory. In my case rsnapshot runs for several hours, much of which is likely for checking file metadata for updates; I run backups once a day and there is no realistic way that enough data is modified each day to take that long to copy. I recently wrote a script to take advantage of ZFS snapshots to get a basically point-in-time atomic snapshot of the data onto the backup drive, even in the presence of live changes while the backup is running. (It's not necessarily _quite_ point-in-time atomic because I have two ZFS pools plus an ext4 file system; but it's close enough to be a workable approximation.) -- Michael Kjörling https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
Re: f3tools vs Silicon Power 4T drive
Andy Smith wrote: > On Wed, Feb 14, 2024 at 08:48:31PM -0500, gene heskett wrote: > > On 2/14/24 19:48, Andy Smith wrote: > > > 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" > > Okay, thanks for clarifying. This, or preferably a copy-paste of the > actual parted command session would suffice. > > I don't know what the relevance is of the rest of the following > paragraph - your life story is not required and you were not accused > of lying, just asked to clarify. > > Do remember that this mailing lists does not accept attachments (and > very few mailing lists in general do), so any time you are tempted > to send a photo to a mailing list it is probably an error. We did > not see whatever it was, but it doesn't sound relevant. FWIW, the photo that Gene attached was certainly attached to the mail that the list sent to me, so I suppose that this list does permit attachments, at least in some circumstances. I do agree with your sentiment that the text output of a CLI command is both simpler and better though.
Re: f3tools vs Silicon Power 4T drive
On Thu 15 Feb 2024 at 16:12:06 (+), Andy Smith wrote: > On Wed, Feb 14, 2024 at 09:56:07PM -0500, gene heskett wrote: > > > On 2/14/24 19:48, Andy Smith wrote: > > > > 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.. > > You've split your reply to my mail across three different emails and > now you're replying to a part about redundancy, but asking questions > about something completely different, all while referring to bits > that are not proximal to where your text is, so it's unclear to me > exactly what you are asking about. > > You asked if "labels" would survive their associated partition being > put into LVM. > > I said, "yes if you mean partition names, no if you mean filesystem > labels". > > To my implied question about your redundancy plans (if any), you > then complain that I have not given you "a syllable about how to do > it". Do *what*? I don't yet know what your plans are in that regard. > If you have questions, ask them. I think the paste in https://lists.debian.org/debian-user/2024/02/msg00611.html shows that SiPwr_1 is a filesystem LABEL, not a PARTLABEL, lying as it does between an FSVER and a UUID. Cheers, David.
Re: f3tools vs Silicon Power 4T drive
Hi, On Wed, Feb 14, 2024 at 09:56:07PM -0500, gene heskett wrote: > > On 2/14/24 19:48, Andy Smith wrote: > > > 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.. You've split your reply to my mail across three different emails and now you're replying to a part about redundancy, but asking questions about something completely different, all while referring to bits that are not proximal to where your text is, so it's unclear to me exactly what you are asking about. You asked if "labels" would survive their associated partition being put into LVM. I said, "yes if you mean partition names, no if you mean filesystem labels". To my implied question about your redundancy plans (if any), you then complain that I have not given you "a syllable about how to do it". Do *what*? I don't yet know what your plans are in that regard. If you have questions, ask them. Regards, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: f3tools vs Silicon Power 4T drive
Hi, On Wed, Feb 14, 2024 at 08:48:31PM -0500, 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" Okay, thanks for clarifying. This, or preferably a copy-paste of the actual parted command session would suffice. I don't know what the relevance is of the rest of the following paragraph - your life story is not required and you were not accused of lying, just asked to clarify. Do remember that this mailing lists does not accept attachments (and very few mailing lists in general do), so any time you are tempted to send a photo to a mailing list it is probably an error. We did not see whatever it was, but it doesn't sound relevant. > 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. Regards, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: f3tools vs Silicon Power 4T drive
Hi, On Wed, Feb 14, 2024 at 09:06:43PM -0500, gene heskett wrote: > On 2/14/24 19:48, Andy Smith wrote: > > 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? I doubt it, but what would be the point of doing that? The device ID conveys all the same information that you're putting in the partition name. > I dare you to find the disk that udev calls sdc in the above wall of text. $ ls -l /dev/disk/by-id | grep sdb1 lrwxrwxrwx 1 root root 10 Jan 17 02:49 ata-SAMSUNG_MZ7KM1T9HAJM-5_S2HNNAAGA00863-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 Jan 17 02:49 wwn-0x5002538c00066800-part1 -> ../../sdb1 Thus, partition 1 of sdb1 is on partition 1 of /dev/disk/by-id/ata-SAMSUNG_MZ7KM1T9HAJM-5_S2HNNAAGA00863. Information already held by the kernel; no need to duplicate it in a GPT partition name or anywhere else. There are many other ways to retrieve the same information; that was the first that sprang to mind but I would not use that in a script because it's basically parsing ls (a big no-no). If you'd simply state what you're trying to achieve then 99.9% of all your posts wouldn't be massive X/Y problems. > 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. See above. You're welcome. I note that you still haven't responded with the exact command you used to set these "labels", so at this point we still do not know exactly what you mean and I have to proceed assuming you meant GPT partition name. A simple request that would enable us to help you better, ignored. Regards, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: SMART Uncorrectable_Error_Cnt rising - should I be worried?
On 2024-02-15 at 01:18, songbird wrote: > 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. :) Thank you. It's quite a relief on my end as well. > which SSDs did you use? The model name/number isn't terribly meaningful-looking. I gave it in my reply to David, fairly deep in the wall of text. They're Intel 3.84Ti?B SSDs, reportedly intended for server or data-center use. -- 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: SMART Uncorrectable_Error_Cnt rising - should I be worried?
On 2024-01-11 at 15:25, Stefan Monnier wrote: >> manufacturers in different memory banks, but since it's always >> possible to power down, replace or just remove memory, and power up >> again, > > Hmm... "always"? What about long running computations like that > simulation (or LLM training) launched a month ago and that's expected > to finish in another month or so? > > Some mainframes have supported hot (un)plugging RAM modules as well > and I wouldn't be surprised if some x86 servers also support it > nowadays. I remember, in my previous job (back in the oughts, now), one occasion on which I was going around adding RAM to various desktop computers in the area under my purview, by adding more DIMMs to the open slots - and discovering, when I put the case back together on one of those computers and went to power it back on, that *it was already powered on and the system was still booted*. Surprisingly, none of the hardware showed any sign of damage, and the system recognized the RAM just fine after a reboot. But it was a bit of a jolt at the time to realize that I'd just done parts surgery, however mild, on a powered and running system. -- 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: SMART Uncorrectable_Error_Cnt rising - should I be worried?
On 2024-02-15 at 03:09, David Christensen wrote: > On 2/14/24 18:54, 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! > > That is good to hear. :-) > >> 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 > > Make? Model? How it is interfaced to your computer? It's a WD Elements 20TB drive (I'm not sure where I got the 22 from); the back of the case has the part number WDBWLG0200HBK-X8 (or possibly -XB, the font is kind of ambiguous). The connection, per the packaging label, is USB-3. >> 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. > > Migrating large amounts of data from one storage configuration to > another storage configuration is non-trivial. Anticipating problems > and preparing for them ahead of time (e.g. backups) makes it even > less trivial. The last time I lost data was during a migration when > I had barely enough hardware. I made a conscious decision to always > have a surplus of hardware. The big change of plans in the middle of my month-plus process was the decision to replace the entire 8-drive array with a 6-drive array, and the reason for that was because the 8-drive array left me with no open SATA ports to be able to connect spare drives in order to do drive replacements without needing to rebuild the whole shaboozle. I don't currently have a surplus of hardware (see the $2200 it already cost me for the replacement drives I have), but I also haven't yet initiated a warranty claim on the 870 EVO drives, and it seems possible that that process might leave me with either replacement drives on that front or just plain money (even if from selling the replacement drives on e.g. eBay) with which to purchase spare-able hardware. >>> (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 remember reading your comment and then noticing you went silent. I > apologize if I pushed your button. As far as I know you didn't. I don't think I even read any of the replies after sending that message, and if I did, I don't remember any of them having this type of impact; it was just the holistic stress of the entire situation. >> 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, > > Ouch. Yeah. The cost factor is why I was originally planning to spread this out over time, buying two drives a month until I had enough to replace drives one at a time in the 8-drive array. I eventually decided that - especially with the rsnapshot tiered backups turning out not to be viable, because of the hardlinks thing - the risk factor of stretching things out further wasn't going to be worth the benefit. IIRC, the drives were actually $339 apiece, which would put the total price for six in the $2030-$2040 range; sales tax and shipping costs were what put it up to nearly $2200. > If you have a processor, memory, PCIe slot, and HBA to match those > SSD's, the performance of those SSD's should be very nice. The CPU is a Ryxen 5 5600X. The RAM is G-Skill DDR4 2666MHz, in two 32GB DIMMs. I don't know how to assess PCIe slots and HBA, but the motherboard is an Asus ROG Crosshair VIII Dark Hero, which I think was the top-of-the-line enthusiast motherboard (with the port set my criteria called for) the year I built this machine. I'm pretty sure my performance bottleneck for most things is the CPU (or the GPU, where that comes into play, which here it doesn't); storage-wise this seems so far to be at least as fast as what I had before, but it's hard to tell if it's faster. >> 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
Re: simple virt-manager setup
On Thu, 15 Feb 2024 10:31:30 +0100 Felix Natter wrote: > Looks like I write my own script, since I don't need snapshots or > incremental backups or even multiple disks :) Take a look at rsnapshot. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: SMART Uncorrectable_Error_Cnt rising - should I be worried?
On 2024-02-15 at 07:14, debian-u...@howorth.org.uk wrote: > The Wanderer wrote: > >> It turns out that there is a hard limit of 65000 hardlinks per >> on-disk file; > > That's a filesystem dependent value. That's the value for ext4. I think I recall reading that while I was flailing over this, yes. ext4 is what I use for daily-driver purposes these days; from the little I've looked into the matter, everything else seems to be either too complicated, or too non-robust, to be worth risking my live data on. > XFS has a much larger limit I believe. As well as some other helpful > properties for large filesystems. > > btrfs has different limits, depending on where the hardlinks are, > apparently. Some larger, some ridiculously smaller. So it might make sense to use one of those as the underpinning for whatever external system I wind up setting up for tiered backup, then. Though experimentation to determine the limits would be warranted. That's not immediately actionable, but it's good to have in the background as planning etc. takes place. -- 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: Thunderbird inbox malfunction
Paul D Schmitt wrote on 2/14/24 10:49: 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. I haven't seen any response to this, so I just thought I'd confirm to you for your peace of mind that there is indeed a problem (or several problems) of some sort, and it's not just you who is experiencing it/them. Following the last update of TB here, it's been awful to try to work with the view of messages. I don't know how they could have released it in such a horrible state, but am assuming that the next update will fix the problem(s). Doc -- Web: http://enginehousebooks.com/drevans
Re: SMART Uncorrectable_Error_Cnt rising - should I be worried?
The Wanderer wrote: > It turns out that there is a hard limit of 65000 > hardlinks per on-disk file; That's a filesystem dependent value. That's the value for ext4. XFS has a much larger limit I believe. As well as some other helpful properties for large filesystems. btrfs has different limits, depending on where the hardlinks are, apparently. Some larger, some ridiculously smaller.
Re: foss-north 2024
och har skaffat konferansbiljetter nu också någon som känner för att göra något Debian relaterat tillsammans i år? Orkar nog inte dra i något helt själv just nu annars drar jag dit som en vanlig besökare och tittar på föreläsningar Den mån 29 jan. 2024 kl 14:23 skrev Luna Jernberg : > > Tjena! > > Har bokat tågbiljetter nu med MTRExpress eller MTRX > https://mtrx.travel/sv som dom heter nu mera, för att kunna åka ner > till konferensen som allafall deltagare på plats i år och försöka dra > på min första Öppen Källkods/Linux/BSD konferans i götet sen 2015, såg > dock att biljettförsäljningen inte har öppnat än dock, något speciellt > datum den väntas öppna? > > och snackat med lillebror i Borås så jag kan sova där och hänga med honom lite > > Den tors 25 jan. 2024 kl 21:19 skrev Luna Jernberg : > > > > Hejsan! > > > > https://foss-north.se/2024/index.html > > > > Datum och biljettförsäljning för foss-north 2024 i Göteborg i mitten > > av April 2024 har nu startat > > > > Någon som har tänkt att göra något på foss-north i år? > > Funderar på att åka dit IRL för första gången i år (då jag inte har > > kunnat tidigare år pga COVID och personlig anledning) men i år ska det > > nog bli av
Re: foss-north 2024
och har skaffat konferansbiljetter nu också någon som känner för att göra något Debian relaterat tillsammans i år? Orkar nog inte dra i något helt själv just nu annars drar jag dit som en vanlig besökare och tittar på föreläsningar Den mån 29 jan. 2024 kl 14:23 skrev Luna Jernberg : > > Tjena! > > Har bokat tågbiljetter nu med MTRExpress eller MTRX > https://mtrx.travel/sv som dom heter nu mera, för att kunna åka ner > till konferensen som allafall deltagare på plats i år och försöka dra > på min första Öppen Källkods/Linux/BSD konferans i götet sen 2015, såg > dock att biljettförsäljningen inte har öppnat än dock, något speciellt > datum den väntas öppna? > > och snackat med lillebror i Borås så jag kan sova där och hänga med honom lite > > Den tors 25 jan. 2024 kl 21:19 skrev Luna Jernberg : > > > > Hejsan! > > > > https://foss-north.se/2024/index.html > > > > Datum och biljettförsäljning för foss-north 2024 i Göteborg i mitten > > av April 2024 har nu startat > > > > Någon som har tänkt att göra något på foss-north i år? > > Funderar på att åka dit IRL för första gången i år (då jag inte har > > kunnat tidigare år pga COVID och personlig anledning) men i år ska det > > nog bli av
Re: simple virt-manager setup
Me writes: > 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?) hello HdV, > Might this fit your needs? > > https://github.com/abbbi/virtnbdbackup Thank you very much for the suggestion. However, I will write my own script since I only need full backups, no thin-provisining, not even multiple disks. Also, I will need to learn about snapshots, checkpoints etc. before making use of this. Cheers and Best Regards, Felix -- Felix Natter debian/rules!
Re: simple virt-manager setup
hello Michael,
Michael Kjörling <2695bd53d...@ewoof.net> writes:
> 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.
That is why my sentence ended with ";-)".
> 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.
It seems there is none. And zfs is way too complicated for me right now.
>> 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.
Looks like I write my own script, since I don't need snapshots or
incremental backups or even multiple disks :)
Thank you again.
Cheers and Best Regards,
Felix
--
Felix Natter
debian/rules!
Re: SMART Uncorrectable_Error_Cnt rising - should I be worried?
On 2/14/24 18:54, 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! That is good to hear. :-) 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 Make? Model? How it is interfaced to your computer? 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. Migrating large amounts of data from one storage configuration to another storage configuration is non-trivial. Anticipating problems and preparing for them ahead of time (e.g. backups) makes it even less trivial. The last time I lost data was during a migration when I had barely enough hardware. I made a conscious decision to always have a surplus of hardware. (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 remember reading your comment and then noticing you went silent. I apologize if I pushed your button. 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, Ouch. If you have a processor, memory, PCIe slot, and HBA to match those SSD's, the performance of those SSD's should be very nice. 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. When I was
