Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot
Hello, On Wed, May 22, 2024 at 05:03:34PM -0400, Stefan Monnier wrote: > Hmm... I've been using a "plain old partition" for /boot (with > everything else in LVM) for "ever", originally because the boot loader > was not able to read LVM, and later out of habit. I was thinking of > finally moving /boot into an LV to make things simpler, but I see that > it'd still be playing with fire grub supports, for a long time: - / on LVM, with /boot within that filesystem - /boot on LVM, separately (it also worked with LILO, because LILO would record the exact address where the kernel & initrd was, regardless of abstractions layers :->) Recently, I have been playing with RAID-on-LVM (I was mostly using LVM on md before, which worked with grub), and it works too. Where grub fails, is if you have /boot on the same LVM volume group where any of the LVs "before him in order" have: - dm-integrity - specific metadata So yes, any advanced setup might break grub, and so the easiest is to have /boot on its separate partition again for the time being. Which makes two partitions of you also have an UEFI. > (AFAICT booting off of LVM was still not > supported by U-Boot either last time I checked). No idea about that one, sorry.
Re: Bookworm: Weird Firefox issue
On 22 May 2024 15:17 -0600, from charlescur...@charlescurley.com (Charles Curley): >> about a week ago when I started >> to get a blank empty white page when trying to access the Tutanota >> login page: https://mail.tutanota.com/login > > I get what looks like a proper log-in page on both firefox and vivaldi Works fine for me too, on the same firefox-esr package version. If clearing the browser cache doesn't help, try with a brand new fresh profile. `firefox --no-remote --new-instance --ProfileManager` should be a good start. If it works in a brand new profile, it's _something_ about your Firefox settings. -- Michael Kjörling 🔗 https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
Re: OpenSMTPD can't parse smarthost
Kamil Jońca writes: [...] > [...] >> action "relay" relay host smtp+notls://pa...@yosemite.mars.lan:25 auth >> >> > > I have some opensmtpd config around and this line should work. > My suspects are: > 1. whitespaces / end lines - have you test your config with xxd to check > if there CRLF for rexample ? > 2. do you have a line > > --8<---cut here---start->8--- > paulf username:password > --8<---cut here---end--->8--- > > in your secrets file? > HTH After closer look I have another doubt: https://man.openbsd.org/smtpd.conf says: --8<---cut here---start->8--- The label corresponds to an entry in a credentials table, as documented in table(5). It is used with the “smtp+tls” and “smtps” protocols for authentication. Server certificates for those protocols are verified by default. --8<---cut here---end--->8--- So if you use smtp+notls or pure smtp - maybe 'paulf@' is wrong here? KJ -- http://stopstopnop.pl/stop_stopnop.pl_o_nas.html If the human brain were so simple that we could understand it, we would be so simple we couldn't.
Re: OpenSMTPD can't parse smarthost
Paul M Foster writes: > Folks: > > Here's a shot in the dark. I've looked up and down the internet, and can't > find a solution. > > I have a mini PC which just serves up videos. Daily it backs up to an > attached drive. This happens with a script in /etc/cron.daily, which > typically emails results to root. In my case it's aliased to me. I have > OpenSMTPD installed with this config: > > --- > [...] > action "relay" relay host smtp+notls://pa...@yosemite.mars.lan:25 auth > > I have some opensmtpd config around and this line should work. My suspects are: 1. whitespaces / end lines - have you test your config with xxd to check if there CRLF for rexample ? 2. do you have a line --8<---cut here---start->8--- paulf username:password --8<---cut here---end--->8--- in your secrets file? HTH -- http://stopstopnop.pl/stop_stopnop.pl_o_nas.html Support Bingo, keep Grandma off the streets.
Re: OpenSMTPD can't parse smarthost
On Thu, May 23, 2024 at 12:43 AM Paul M Foster wrote: > > Folks: > > Here's a shot in the dark. I've looked up and down the internet, and can't > find a solution. > > I have a mini PC which just serves up videos. Daily it backs up to an > attached drive. This happens with a script in /etc/cron.daily, which > typically emails results to root. In my case it's aliased to me. I have > OpenSMTPD installed with this config: > > --- > > # $OpenBSD: smtpd.conf,v 1.10 2018/05/24 11:40:17 gilles Exp $ > > # This is the smtpd server system-wide configuration file. > # See smtpd.conf(5) for more information. > > table aliases file:/etc/aliases > table secrets file:/etc/secrets > > listen on localhost > > action "relay" relay host smtp+notls://pa...@yosemite.mars.lan:25 auth > > > match from local for any action "relay" > > --- > > Note: yosemite is my desktop machine; that where I want the mail to be > sent. "paulf" is a tag in the secrets file. Note that this connection > between the mini PC (buckaroo) and yosemite should be a plain text > connection, very simple. My username and password are in the secrets file. > > When I attempt to send a test message to check this all works (via swaks or > mail), I get an error message in the /var/log/mail.log file which says: > > "warn: Failed to parse smarthost smtp+notls://pa...@yosemite.mars.lan:25" > > Note that the "protocol" doesn't matter. I can use "smtp" alone as the > protocol, and it still won't parse. And yes, yosemite.mars.lan is in my > local hosts file. On the video server, run nslookup and see if it can resolve yosemite.mars.lan. Looking at the string smtp+notls://pa...@yosemite.mars.lan:25, it looks more like a url than a hostname. Maybe that is confusing your mail agent. Also, I think you should be using *.home.arpa, and not *.lan. home.arpa is reserved for private use by ICANN and the IETF. I suspect *.lan is not reserved for private use. Jeff
Re: OpenSMTPD can't parse smarthost
On Wed, May 22, 2024 at 09:37:18PM -0400, Paul M Foster wrote: > Folks: > > Here's a shot in the dark. I've looked up and down the internet, and can't > find a solution. [...] > "warn: Failed to parse smarthost smtp+notls://pa...@yosemite.mars.lan:25" > > Note that the "protocol" doesn't matter. I can use "smtp" alone as the > protocol, and it still won't parse. And yes, yosemite.mars.lan is in my > local hosts file. But "p...@yosemite.mars.lan" doesn't look like a host (unless you are trying to sneak in the creds in the URL -- then I'd expect something like user:pass@host). No idea how opensmtp works and whether it tries to parse credentials off the URL. Have you tried leaving out the "paul@" part? Do you have access credentials elsewhere in your config (typically they are in a separate file to better control access to that). Cheers -- t signature.asc Description: PGP signature
OpenSMTPD can't parse smarthost
Folks: Here's a shot in the dark. I've looked up and down the internet, and can't find a solution. I have a mini PC which just serves up videos. Daily it backs up to an attached drive. This happens with a script in /etc/cron.daily, which typically emails results to root. In my case it's aliased to me. I have OpenSMTPD installed with this config: --- # $OpenBSD: smtpd.conf,v 1.10 2018/05/24 11:40:17 gilles Exp $ # This is the smtpd server system-wide configuration file. # See smtpd.conf(5) for more information. table aliases file:/etc/aliases table secrets file:/etc/secrets listen on localhost action "relay" relay host smtp+notls://pa...@yosemite.mars.lan:25 auth match from local for any action "relay" --- Note: yosemite is my desktop machine; that where I want the mail to be sent. "paulf" is a tag in the secrets file. Note that this connection between the mini PC (buckaroo) and yosemite should be a plain text connection, very simple. My username and password are in the secrets file. When I attempt to send a test message to check this all works (via swaks or mail), I get an error message in the /var/log/mail.log file which says: "warn: Failed to parse smarthost smtp+notls://pa...@yosemite.mars.lan:25" Note that the "protocol" doesn't matter. I can use "smtp" alone as the protocol, and it still won't parse. And yes, yosemite.mars.lan is in my local hosts file. Any help would be appreciated. Paul -- Paul M. Foster Personal Blog: http://noferblatz.com Company Site: http://quillandmouse.com Software Projects: https://gitlab.com/paulmfoster
Re: Bookworm: Weird Firefox issue
On Wed, 22 May 2024 23:02:17 +0200 (CEST) local10 wrote: > Have been using Debian + Firefox with Tutanota email for a number of > years and everything was fine until about a week ago when I started > to get a blank empty white page when trying to access the Tutanota > login page: https://mail.tutanota.com/login > > Tried https://mail.tutanota.com/login in Chromium and it works as it > should, that is, shows a proper log in page with the ID and password > fields, no issues. Tried https://mail.tutanota.com/login in Firefox > v126 but still got an empty white page. > > Any ideas? Thanks > > $ aptitude show firefox-esr > Package: firefox-esr > Version: 115.11.0esr-1~deb12u1 I get what looks like a proper log-in page on both firefox and vivaldi (a derivative of chromium). BTW, they are advising of a change in log-in URL. charles@hawk:~$ pre firefox vivaldi firefox-esr 115.11.0esr-1~deb12u1 amd64 vivaldi-stable 6.7.3329.31-1 amd64 charles@hawk:~$ Try a hard refresh to clear your cache: ctl-r. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot
> I found this [1], quoting: "I'd also like to share an issue I've > discovered: if /boot's partition is a LV, then there must not be a > raidintegrity LV anywhere before that LV inside the same VG. Otherwise, > update-grub will show an error (disk `lvmid/.../...' not found) and GRUB > cannot boot. So it's best if you put /boot into its own VG. (PS: Errors > like unknown node '..._rimage_0 can be ignored.)" Hmm... I've been using a "plain old partition" for /boot (with everything else in LVM) for "ever", originally because the boot loader was not able to read LVM, and later out of habit. I was thinking of finally moving /boot into an LV to make things simpler, but I see that it'd still be playing with fire (AFAICT booting off of LVM was still not supported by U-Boot either last time I checked). 🙁 Stefan
Bookworm: Weird Firefox issue
Hi, Have been using Debian + Firefox with Tutanota email for a number of years and everything was fine until about a week ago when I started to get a blank empty white page when trying to access the Tutanota login page: https://mail.tutanota.com/login Tried https://mail.tutanota.com/login in Chromium and it works as it should, that is, shows a proper log in page with the ID and password fields, no issues. Tried https://mail.tutanota.com/login in Firefox v126 but still got an empty white page. Any ideas? Thanks $ aptitude show firefox-esr Package: firefox-esr Version: 115.11.0esr-1~deb12u1 Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-21-amd64 (64-bit) Graphics Platform: X11
Re: Will te UUID or blkid of a device change?
Am 22.05.2024 um 21:19:35 Uhr schrieb Hans: > Whenever I dd to the target stick, does the UUID change? I know, the > UUID of the partitions are changing, but what is with the device > itself? No. The UUID is part of the file system and will just be copied. Mounting based on the UUID will be ambiguous in that case, so you should generate a new UUID for each file system that supports that. Be aware that in a GPT the disk itself has a GUID and each partition a PART-UUID that you maybe also want to change. -- Gruß Marco Send unsolicited bulk mail to 1716405575mu...@cartoonies.org
Will te UUID or blkid of a device change?
Hi folks, just aquestion. I am booting a lie system from USB-stick. In this live system I am creating an ISO-file, which I then want to dd onto another USB-stick. As I am doing this with a script, I want to make sure, that the correct USB- stick is used. Thus I can do by using the UUID of the target stick like dd if=/path/to/myfile.iso of=UUID="123456-abcd-" This is working. Now my question: Whenever I dd to the target stick, does the UUID change? I know, the UUID of the partitions are changing, but what is with the device itself? Or is there a better way? Maybe by using a label? I read also about blkid, but does this change, too when dd to the device? At all, is my idea possible at all or are ALL UUIDs changing, whenever I do a dd? If yes, then how can this be prohibited, if any. Thanks for any help. Best Hans
Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot
Hello, On Wed, May 22, 2024 at 10:13:06AM +, Andy Smith wrote: > metadata tags to some PVs prevented grub from assembling them, grub is indeed very fragile if you use dm-integrity anywhere on any of your LVs on the same VG where /boot is (or at least if in the list of LVs, the dm-integrity protected ones come first). I guess it's a general problem how grub2 parses LVM, yes, as soon as their are special things going on, it somehow breaks. However, if you don't have /boot on LVM, hand-fixing grub2 can be trivial, e.g. here on another system with /boot/efi on 1st disk's first partition and /boot on 2nd disk's first partition. linux (hd1,1)vmlinuz-5.10.0-29-amd64 root=/dev/mapper/vg1-root ro quiet initrd (hd1,1)initrd.img-5.10.0-29-amd64 boot (you even have completions in grub's interactive boot system) and it boots. Next step: I am going to make me a USB boot key for that system, in case (first using a simple mount of two partitions of the USB key on /boot, respectively /boot/efi (vfat), then update-grub, or if it breaks, completely by hand like above -- I have been using syslinux for the last 20 years or so for that purpose, but it gets apparently too complicated with Secure Boot and stuff). PS: I have from now on decided I will always use a /boot no longer on LVM but on a separate partition, like the /boot/efi, it seems, indeed, much less fragile. Aka, back to what I was doing a few years ago before my confidence in grub2 got apparently too high :)
Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot
Hello, On Wed, May 22, 2024 at 08:57:38AM +0200, Marc SCHAEFER wrote: > I will try this work-around and report back here. As I said, I can > live with /boot on RAID without dm-integrity, as long as the rest can be > dm-integrity+raid protected. I'm interested in how you get on. I don't (yet) use dm-integrity, but I have seen extreme fragility in grub with regard to LVM. For example, a colleague of mine recently lost 5 hours of their life (and their SLA budget) when simply adding metadata tags to some PVs prevented grub from assembling them, resulting in a hard to debug failed boot at next boot. Anything that involves grub having to interact with LVM just seems really fragile. Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot
Hello, On Wed, May 22, 2024 at 08:57:38AM +0200, Marc SCHAEFER wrote: > I will try this work-around and report back here. As I said, I can > live with /boot on RAID without dm-integrity, as long as the rest can be > dm-integrity+raid protected. So, enable dm-integrity on all LVs, including /, /var/lib/lxc, /scratch and swap, now boots without any issue with grub2 as long as /boot is NOT on the same VG where the dm-integrity over LVM RAID is enabled. This is OK for me, I don't need /boot on dm-integrity. update-grub gives out warning for every of the rimage subvolumes, but can still then reboot. I would guess the bug is thus in grub2, not yet supporting boot on a /boot not necessarily dm-integrityfied itself, but on a VG where any of the LV is. Are readers seconding conclusion? If yes, I could report a bug on grub2. Have a nice day. Details: root@ds-03:~# lvs -a LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert docker vg1 rwi-aor--- 500.00g 100.00 [docker_rimage_0]vg1 gwi-aor--- 500.00g [docker_rimage_0_iorig] 100.00 [docker_rimage_0_imeta] vg1 ewi-ao <4.07g [docker_rimage_0_iorig] vg1 -wi-ao 500.00g [docker_rimage_1]vg1 gwi-aor--- 500.00g [docker_rimage_1_iorig] 100.00 [docker_rimage_1_imeta] vg1 ewi-ao <4.07g [docker_rimage_1_iorig] vg1 -wi-ao 500.00g [docker_rmeta_0] vg1 ewi-aor--- 4.00m [docker_rmeta_1] vg1 ewi-aor--- 4.00m root vg1 rwi-aor--- 10.00g 100.00 [root_rimage_0] vg1 gwi-aor--- 10.00g [root_rimage_0_iorig] 100.00 [root_rimage_0_imeta]vg1 ewi-ao 148.00m [root_rimage_0_iorig]vg1 -wi-ao 10.00g [root_rimage_1] vg1 gwi-aor--- 10.00g [root_rimage_1_iorig] 100.00 [root_rimage_1_imeta]vg1 ewi-ao 148.00m [root_rimage_1_iorig]vg1 -wi-ao 10.00g [root_rmeta_0] vg1 ewi-aor--- 4.00m [root_rmeta_1] vg1 ewi-aor--- 4.00m scratch vg1 rwi-aor--- 10.00g 100.00 [scratch_rimage_0] vg1 gwi-aor--- 10.00g [scratch_rimage_0_iorig] 100.00 [scratch_rimage_0_imeta] vg1 ewi-ao 148.00m [scratch_rimage_0_iorig] vg1 -wi-ao 10.00g [scratch_rimage_1] vg1 gwi-aor--- 10.00g [scratch_rimage_1_iorig] 100.00 [scratch_rimage_1_imeta] vg1 ewi-ao 148.00m [scratch_rimage_1_iorig] vg1 -wi-ao 10.00g [scratch_rmeta_0]vg1 ewi-aor--- 4.00m [scratch_rmeta_1]vg1 ewi-aor--- 4.00m swap vg1 rwi-aor--- 8.00g 100.00 [swap_rimage_0] vg1 gwi-aor--- 8.00g [swap_rimage_0_iorig] 100.00 [swap_rimage_0_imeta]vg1 ewi-ao 132.00m [swap_rimage_0_iorig]vg1 -wi-ao 8.00g [swap_rimage_1] vg1 gwi-aor--- 8.00g [swap_rimage_1_iorig] 100.00 [swap_rimage_1_imeta]vg1 ewi-ao 132.00m
