Recent comments on posts in the blog:

Doesn't seem to work with nginx, had to use the webroot option, but maybe it's me...

certbot certificates

Found the following certs: Certificate Name: . Domains:

certbot delete

usage: certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ...

certbot delete --cert-name

Are you sure you want to delete the above certificate(s)? (Y)es/(N)o: y Deleted all files relating to certificate

certbot certonly -d -d --duplicate

Saving debug log to /var/log/letsencrypt/letsencrypt.log Error while running nginx -c /etc/nginx/nginx.conf -t.

nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:

Comment by Anonymous
Thank you so much for your detailed instructions
I am so excited that I now have a "Safe" way to run Windows for devices that do not support Linux. I walked away from all MS products in favor of Linux over a decade ago. I love that VM gives you full control over what resources Windows can see. I can download under linux and drag and drop onto the Windows VM and Windows will never have access to the internet. Thank you for your very detailed instructions. This has opened up many devices for me that are not supported under Linux.
Comment by Daniel - N2FY
debian wiki suggestion

this is a little over my head, so trying to learn a bit, I searched the Wiki.

It needs some help, nothing about this issue is mentioned.

can you add something to help others?

Comment by peter

Do you use special filename prefixes to ensure that this script is the last daily cron script to run? Because I'm not sure I'd trust cron to resume running the rest of the scripts automatically after the reboot.

I tend to enable automatic reboots in unattended-upgrades at a fixed hour when I know no cron scripts are supposed to be running (Unattended-Upgrade::Automatic-Reboot "true"; Unattended-Upgrade::Automatic-Reboot-Time "04:30"; in /etc/apt/apt.conf.d/50unattended-upgrades-local). So far it has worked out well.

Comment by Marius Gedminas
Get "partition table exists" and other warning when trying to create mdadm

I've followed the instructions, but when it comes to the "mdadm --create /dev/md0 --level=1 --raid-disks=2 missing /dev/sdh1" command, I get:

mdadm: partition table exists on /dev/sdh1

mdadm: partition table exists on /dev/sdh1 but will be lost or meaningless after creating array

mdadm: Note: this array has metadata at the start and may not be suitable as a boot device. If you plan to store '/boot' on this device please ensure that your boot-loader understands md/v1.x metadata, or use --metadata=0.90

Continue creating array?

...I answer no at that point, but what should I do?

My OS is AlmaLinux, but I would think the instructions would apply. It uses an LVM partition system, but other instructions I've found that include LVM have the same steps.

Thanks for any help.

Comment by James
Re: comment 1

Sorry to interupt but what's about nftables?

I have not yet switched to nftables, though it's on my list. In other words, I don't know yet.

Comment by francois
setting default branch
So is this done in the bare repo or where?
Comment by Anonymous
Slight issue with 2nd part of the fix

Hello - thanks for this info I've had the exact same issue and am now able to boot. Just struggling with the 2nd part of the fix;

system boots normally

fixing issue

edit /etc/crypttab

rename the first space delimited

occurrence with sameluksdrivenamethenappend_crypt

quit n save

finally run

root@ubuntu# update-initramfs -u -v

finally reboot


I can't seem to edit the crypttab file to start with, do you know which viewer i should be using? And then is it simply a case of adding the _crypt to the first space delimited occurence?

Comment by Adam Preston