alphapuggle 5d ago • 98%
Anal (Ubuntu)
Because at this point, if you're still on it you're taking it up the ass from Canonical
alphapuggle 1w ago • 86%
If I had stopped reading after 2 seconds I wouldn't know it was the lemonade, something that should be put front and center because if I was a drinker of minute maid zero sugar lemonade and I saw "Coke recalls popular zero sugar drink", I wouldn't've bothered reading further.
alphapuggle 1w ago • 93%
Headline could be written better, I warned my friend who's sister is a diabetic before realizing its just the lemonade
alphapuggle 1w ago • 93%
Kentucky fried human
alphapuggle 2w ago • 21%
...yknow other languages than English exist right?
alphapuggle 2w ago • 97%
Aaron Schwartz killed himself over punishments for less
alphapuggle 3w ago • 100%
Interesting, both of my F40 installs with btrfs only have a root folder, but it looks like yours has created separate ones for /, /home, and /boot. run ll /mnt/boot; ll /mnt/home; ll /mnt/root
so I can take a quick look at where things are located. My best guess is that sda1 gets mounted to /mnt/boot, while everything else (/dev, /sys, etc) gets mounted to /mnt/root
alphapuggle 3w ago • 100%
Since you're using btrfs, there is likely another subfolder under /mnt. ll /mnt will tell you this, but the drive isn't still mounted from the other day. When you're mounting the EFI partition, you're going to want to mount it to that folder, and not /mnt itself (/mnt/root/boot/efi, instead of /mnt/boot/efi) same for the binds (/dev, /proc, /run, etc)
alphapuggle 3w ago • 100%
Yup, should be the same release, just using a different token and therefore needs approved separately
alphapuggle 3w ago • 93%
Ugh they didn't keep the same oauth flow so I have to get IT to approve it again for Outlook
alphapuggle 3w ago • 100%
Oh absolutely, my account has been overwritten (as if that does anything ) and deleted for over a year now.
alphapuggle 3w ago • 100%
Took me wayy too long to realize this is just "Randolph"
alphapuggle 3w ago • 100%
“While we are making this change to ensure users’ expectations regarding a community’s access do not suddenly change, protest is allowed on Reddit,” writes Nestler. “We want to hear from you when you think Reddit is making decisions that are not in your communities’ best interests. But if a protest crosses the line into harming redditors and Reddit, we’ll step in.”
Yall have very clearly demonstrated that you do not care about the communities best interest, and you have no interest in hearing what we think. Fuck Spez and good riddance to reddit
alphapuggle 3w ago • 100%
Could you send me the output of lsblk -no FSTYPE /dev/sda3
and ll /mnt
?
alphapuggle 3w ago • 100%
Apologies, I think I got a bit ahead of myself in the description.
Once you've determined which partition is which (in your case, /dev/sda1 does appear to be the EFI partition, and /dev/sda3 appears to be your root partition), you need to mount them in this order
mount /dev/sda3 /mnt
mount /dev/sda1 /mnt/boot/efi
alphapuggle 3w ago • 100%
That's alright, I'll do my best to walk you through it.
Your drive contains multiple partitions (/dev/sda1 through /dev/sda3).
One of these drives is going to be your EFI partition. This is what your system can read before linux boots, your BIOS can't understand ext4 / btrfs / etc, but it can understand fat32.
If you run lsblk -no FSTYPE /dev/sda1
it should return vfat if that's your EFI partition. That's what we're going to mount to /mnt/boot/efi
I'm assuming that /dev/sda3 is your data partition, e.g. where your linux install is. You can find the filesystem format the same way as your EFI partition.
Edit: After determining which partition is which, you're going to want to mount the root partition, and then the EFI partition
mount /dev/sda3 /mnt
mount /dev/sda1 /mnt/boot/efi
Unix systems have theology of "everything is a file", all devices and system interfaces are mounted as files. As such, to be able to properly chroot into an offline install, we need to make binds from our running system to the offline system. That's what's achieved by running for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; done
This is just a simple loop that mounts /dev, /dev/pts, /proc, /sys, and /run to your offline install. You're going to want to either add /sys/firmware/efi/efivars to that list, or mount it (with -B, which is shorthand for --bind, not a normal mount).
Once you've done this, you should be able to successfully chroot into /mnt (or /mnt/root if running btrfs)
At this point, you should be able to run your grub repair commands.
alphapuggle 3w ago • 100%
I'm doing my morning scroll before I start my day, so I can't delve too deep, but this is the article I always reference when I have to do repairs
https://askubuntu.com/a/831241
#1 thing I noticed in your image is that lsblk only shows you partitions, and doesn't mount them. You probably want /dev/sda3 mounted at /mnt
The only thing from the article you want to modify is using
mount -B /sys/firmware/efi/efivars /mnt/sys/efi/efivars
, I believe the functionality changed since that article was written and that's what worked for me
Additionally, if you drive is formatted as btrfs instead of ext4, once you mount your drive your root will most likely be at /mnt/admin or similar. Mount subdirectories to that folder instead of /mnt
If you have questions lmk and I'll get back to you at some point today
alphapuggle 3w ago • 100%
It was designed as a test to be up the for 6 months, with no self propulsion.
It stated up and operational for 2 years.
alphapuggle 4w ago • 93%
C (see)
U (you)
N(ext)
T(Tuesday)
Edit: Conclusion at the bottom I just sent my ThinkPad X13 Yoga Gen 2 in for service the other day, it hasn't yet reached the depot but I'm worried after seeing reviews online about Lenovo's customer service. I know people are definitely more likely to write a review if they have a bad experience than a good one. The repair is just for the TrackPoint, which hasn't been really up to the old ThinkPads I've had (T23, T43, T61, T410, T460) and had recently stopped going to the right entirely. TrackPoints are the only reason I still buy ThinkPads and not something like a framework (and I don't think I can go back to non 2-in-1 laptop after this last one) I also took the NVMe drive out and swapped it with one that had a fresh install of windows 11 on it so that I could use my data while it was sent in. Will they refuse to work on it if they have a non oem drive inside? AFTER REPAIR EDIT: Just got it back from the warranty center! Instead of replacing just the TrackPoint module, they replaced the whole top cover & TrackPad (I did mention that it was having similar issues to them). Came with the factory plastic on it. They didn't try to short-change me in any way, didn't try to argue that it was normal or that it was wear and tear or anything like that. It works better they day it was new, and all of the scuffs that I had on the corners are now gone (so is my intel sticker but I can live with that). In regards to the SSD being out, they didn't say anything or refuse service because of it. I was up front that I had been inside the device before I had sent it in, so YMMV, but all in all 10/10 experience
Started an update for a minor version and it's been like 20 minutes and I have no display out from the nas and I can't access it over the network. This is the first update I've done on the system how long does this usually take and when should I try rebooting it?