u/GuyWithoutAHat

... Ich würde sogar sagen, sie sind das Wurst-Käs'-Szenario.

I would even go so far as to say they're the wurst käse scenario.

Seriously asking. What is stopping innovative flashlight companies like Wurkkos or Loop from building a massive modern Maglite D6 style lamp? I'm thinking:

• airplane grade extruded 6061-t6 aluminum body. Relatively cheap yet very robust. Also doubles as a massive heat sink.
• Either: 5x 32700 LiFePO4, obvious upsides of LiFePO4 batteries. This would give us 16V at about 30,000 mAh.
• Or: 5x 21700 LiIon. The thinner batteries would allow a much thicker wall, improving stability and weight distribution for bonking. This would give us 18.5V at about 25,000 mAh.
• obviously a very powerful emitter, I'm thinking für tactical use probably something strong and throwy? Though a big head might make it a bit problematic to handle. 12V probably because we're thinking big here. Battery capacity and heat shouldn't be too problematic here since we have huge capacity and a massive heat sink in the body. I'm not deep enough into the flashlight game (yet) to have the proper knowledge here to suggest something specific. I'm sure you guys will have some great ideas.
• Buck driver would be necessary for voltage conversion I think.
• USB-C charging and powerbank functionality with the USB-C port hidden behind a screw cap on the back end of the light for dust and water safety
• a single sturdy, "tactical" button with single button control with hold to moonlight and double for turbo
• 5 xx700 batteries plus other components by my rough calculation would put us at about 45-48cm/18-19 inches, so just slightly shorter than the D6
• in both battery configurations we'd end at roughly 1400-1500g/3-3.3lbs, so also very similar to the D6. With the 21700s we'd just have 350g of batteries less and 350g of additional aluminum in the thicker walls.
• shorter versions with 3/4 batteries would also work of course, but let's be honest... We'd all want the biggest one possible to show off and swing around.

Thank you for listening to my TED talk! I'm very open to suggestions why this doesn't exist (yet) and what we could do to change it.

Post Ubuntu Grub problems

Hi everyone and thank you in advance for reading and trying to help, I rent a small VServer running Ubuntu and Plesk (hosted at ionos). Yesterday I tried upgrading from Ubuntu 22.04 to 24.04. I did so using the step by step howto by Plesk [1]. With some small hiccups everything went mostly smoothly, until the last step. While running dist-upgrade I was asked to configure several programmes, for which I selected not to change anything in order to not fuck with Plesk. The last one I was asked for was Grub. I confirmed the preselection (install to vda1 /boot/; at least I'm 90% sure I did that), there were no errors and I rebooted.

This is what the partition table looked like according to lsblk:

NAME          FSTYPE       SIZE MOUNTP
vda                         80G
├─vda1        ext4         487M /boot
└─vda2        LVM2_member 79.5G
  ├─vg00-lv00 swap         1.9G [SWAP]
  └─vg00-lv01 ext4        77.6G /

Now after rebooting, the server didn't come back online. I used my hosters remote recovery console and saw that the server had not booted and just showed the following:

BdsDxe: failed to load Boot0001 "UEFI Misc Device" from PciRoot (0x0)/Pci(0x5,0x0): Not Found
BdsDxe: No bootable option or device was found.
BdsDxe: Press any key to enter the Boot Manager Menu

I again used my hoster to remotely boot into a grml recovery system, hoping I might be able to access the partitions containing the grub config and fix the problem. Now from grml, running lsblk shows the following:

NAME	FSTYPE		SIZE	MOUNTPOINT		
loop0	squashfs	910.7M	/usr/lib/live/mount/rootfs/grml-full-amd64.squashfs
sr0		iso9660		996M	/usr/lib/live/mount/medium
vda					80G
├─vda1	ext4		487M
└─vda2	LVM2_member	79.5G

meaning it seems to no longer identify the main root partition and the swap partition as seperate subpartitions of vda2 but instead just identifies vda2 as LVM2_member. That's where I ran out of ideas on solving the problem, except reinstalling the whole image (and probably go with 26.04 this time in order to not have to do that again in a long time).

I'm looking for any kind of suggestion on how I might be able to fix this problem and get the system to boot again. Thank you!