I’ve got two Sandisks (both 64GB but different models) that have both been through the washing machine multiple times (accidentally) and haven’t failed yet. They are probably about 3 years old at this point but I can’t remember.

Never thought I’d learn how to use tar on a meme post.

Been using Lemmynade (!lemmynade@lemm.ee) and am super happy with it. My instance also has a really nice looking frontend that works as a PWA as well.

How big would the learning curve be for someone who’s never used a system like this? I’ve been slightly intimidated in using Nix. If this makes it easier to get in I’d love to try it out.

It was causing me too much of a headache to try troubleshoot and fix that I decided to wipe the drive. I’ve got Fedora Silverblue running on the machine now. Thanks for the help!

This. Thank you for explaining it correctly, I’ve seen sooo many people saying it’s just filters. Of course, there will almost always be some colour correction but the way a camera a camera can capture the light is different to the naked eye.

It all started with a bad update that led to a kernel mismatch. I then attempted to fix the issue and made it worse…it was a little too much for my skill level (I was reading forum posts with similar issues when trying to fix it.)

I’ve just finished installing Silverblue on the laptop but will give Bluefin a shot. Thanks for the tip!

Just about saw them here in Dublin but I mistook it for a cloud the first time round lol. There was way too much light pollution.

I’m looking at putting Fedora Silverblue on my laptop (it’s shared between myself and my wife) after an update went bad on EndeavourOS — context

From what I’ve seen it looks rock solid.

Yes and no. Initially it was unlocked because I mounted and unlocked it via Dolphin. The second time round I was able to unlock and mount it with udsiksctl

I was able to get the output via Emergency Mode as the root user.

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=0BC7-CF22                            /efi           vfat    fmask=0137,dmask=0027 0 2
/dev/mapper/luks-5c6d5430-3706-48e8-bffb-f680d8c19dda /              btrfs   subvol=/@,noatime,compress=zstd 0 0
/dev/mapper/luks-5c6d5430-3706-48e8-bffb-f680d8c19dda /home          btrfs   subvol=/@home,noatime,compress=zstd 0 0
/dev/mapper/luks-5c6d5430-3706-48e8-bffb-f680d8c19dda /var/cache     btrfs   subvol=/@cache,noatime,compress=zstd 0 0
/dev/mapper/luks-5c6d5430-3706-48e8-bffb-f680d8c19dda /var/log       btrfs   subvol=/@log,noatime,compress=zstd 0 0
/dev/mapper/luks-81a912d5-fb81-40ed-a60f-0af27314b661 swap           swap    defaults   0 0
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

[liveuser@eos-2024.04.20 ~]$ lsblk -a
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0    7:0    0   2.3G  1 loop /run/archiso/airootfs
sda      8:0    0 238.5G  0 disk 
├─sda1   8:1    0  1000M  0 part 
├─sda2   8:2    0 228.7G  0 part 
└─sda3   8:3    0   8.8G  0 part 
sdb      8:16   1  57.3G  0 disk 
├─sdb1   8:17   1   2.5G  0 part /run/archiso/bootmnt
└─sdb2   8:18   1   159M  0 part 

EDIT:

I was able to chroot into the drive. The drive was unlocked as /dev/dm-0.

NAME   FSTYPE      FSVER            LABEL       UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0  squashfs    4.0                                                                     0   100% /run/archiso/airootfs
sda                                                                                                 
├─sda1 vfat        FAT32                        0BC7-CF22                                           
├─sda2 crypto_LUKS 2                            5c6d5430-3706-48e8-bffb-f680d8c19dda                
└─sda3 crypto_LUKS 2                            81a912d5-fb81-40ed-a60f-0af27314b661                
sdb    iso9660     Joliet Extension EOS_202404  2024-04-20-15-57-10-00                              
├─sdb1 iso9660     Joliet Extension EOS_202404  2024-04-20-15-57-10-00                     0   100% /run/archiso/bootmnt
└─sdb2 vfat        FAT16            ARCHISO_EFI 7156-9697  

I’ve added it to the original post as well.

[liveuser@eos-2024.04.20 ~]$ lsblk -f
NAME   FSTYPE      FSVER            LABEL       UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0  squashfs    4.0                                                                     0   100% /run/archiso/airootfs
sda                                                                                                 
├─sda1 vfat        FAT32                        0BC7-CF22                                           
├─sda2 crypto_LUKS 2                            5c6d5430-3706-48e8-bffb-f680d8c19dda                
└─sda3 crypto_LUKS 2                            81a912d5-fb81-40ed-a60f-0af27314b661                
sdb    iso9660     Joliet Extension EOS_202404  2024-04-20-15-57-10-00                              
├─sdb1 iso9660     Joliet Extension EOS_202404  2024-04-20-15-57-10-00                     0   100% /run/archiso/bootmnt
└─sdb2 vfat        FAT16            ARCHISO_EFI 7156-9697  

Would I be able to append the UUID?

I switched to Linux in October of last year and found “The Linux Experiment” to be really helpful in keeping up-to-date with things happening in the community without feeling overwhelmed

So…I’ve just updated my laptop with EOS and now my /efi partition won’t mount. Things definitely can break…unfortunately

Curiosity got the better of me, so I searched what it means. I did come across another interesting phrase…

Futa-te cangurii

Any problems I’ve had have been my own doing or a weird Nvidia driver issue. Having said that though, I’ve had very very few issues, it has been rock solid!

I’ve got a couple of packages from the AUR but I don’t recall ever having any issues with any of them.

The only real “issue” I’ve had has been related to the Linux Kernel on my main machine (Ryzen 5 3600 & Nvidia GTX1660 TI). For some reason, only the LTS and mainline kernel work, if I try any other kernel I get an error (something to do with Nvidia and my GPU).

I used Pop!_OS when transitioning from Windows 11 to Linux and ran it for about 3/4 months before deciding to try EndeavourOS. I had absolutely no issues with Pop and it really made the transition super easy.

I’m super excited to try out their new (cosmic) DE! I will probably install Pop on my 2nd SSD to test and play around with it.