Resizing LVM Volumes

Just a quick note to remind myself outhow to resize logical and physical LVM volumes

  • Activate the Volume group:

lvm vgchange -ay

  • Resize the logical volume (sizing down by 100G in this example)

lvm lvresize --size -100G /dev/vg/root -r --verbose

  • Resize the physical volume:

pvresize --setphysicalvolumesize {size of pv minus {size toreduce}}G /dev/path/to/pv

  • If you get an error about “later extents”, it’s due to the swap being added to the partition (which does not get moved automatically), so you will need to move the data

lvm pvs -v --segments /dev/sda5 to get position ids:

/dev/sda5 ubuntu lvm2 a-- 698.04g 150g 0 xxx root 0 linear /dev/sda:0-xxx
/dev/sda5 ubuntu lvm2 a-- 698.04g 150g xxx nnn 0 free                          
/dev/sda5 ubuntu lvm2 a-- 698.04g 150g yyy zzz swap 0 linear /dev/sda5:yyy-zzz
  • Move the data:

lvm pvmove --alloc anywhere /dev/sda5:yyy-zzz

  • Check the positioning again

pvs -v --segments /dev/sda5

/dev/sda5 ubuntu lvm2 a-- 698.04g 150g 0 xxx root 0 linear /dev/sda:0-xxx
/dev/sda5 ubuntu lvm2 a-- 698.04g 150g xxx nnn swap 0 linear /dev/sda5:xxx-yyy(-1)
/dev/sda5 ubuntu lvm2 a-- 698.04g 150g yyy zzz 0 free
  • Then retry the resize

pvresize --setphysicalvolumesize {size of pv minus {size toreduce}}G /dev/path/to/pv

Downgrading LineageOS to Android 10

LineageOS has now gone to Android 11, and like most users, I went ahead and upgraded to it. But then I started hitting lots of problems. Predominantly on location.

Android 11 changed the way location is requested and this breaks functionality in multiple apps. Ones I have noticed this issue with:

  • Just Eat
  • CityMapper
  • Google Maps (yes, surprisingly Google’s own app had trouble with locking on)

Other location apps may have also had the same issue, but I didn’t check those.

Waze did not have any issues locking on to location or tracking movement

Some non-location apps also broke. Fenix 2 (a Twitter client) and WeChat both stopped working and would not install off the Play Store, presumeably because of API differences.

I installed Plume instead (which I had previously purchased) and that installed and functioned happily.

WeChat I sideloaded by getting the apk from a mirror. That functioned okay, but could not log into Web WeChat

I decided to clean wipe and downgrade back to Android 10 (Lineage OS 17) to at least get things working again.

I formatted my SD card for Portable Storage, then took it to my laptop and saved the LOS flash zip, Open Gapps zip, and the latest Magisk.

I booted into TWRP Recovery and wiped, data, cache, system, ART and internal storage.

Switching to external storage, I then flashed LOS, OpenGapps, then Magisk.

I rebooted and let the OS do its thing until I got the welcome screen — that’s a good sign. I went through the setup but opted not to setup my Google Account yet.

Once through to the home page, I went and unlocked Developer options and enabled ADB, Local Terminal, Force Allow External Storage, and Force Close on Hold Back.

Then I plugged my phone into my pixelbook, allowed the debug connection and started up scrcpy which allows me to copy-paste text to and from the device.

I installed TitaniumBackup and the pro key so I can batch move apps to/from the storage.

The SD Card is still setup as Portable. So I formatted it as Internal. This took a few attempts as it kept erroring.

I went into Play Store and installed a few apps. A couple installed file, but the other errorred with a message:

"App requires external storage"

This was weird, I never saw that before, but checking around, I found this: https://forum.xda-developers.com/t/app-requires-external-storage.4098673/ which describes fixing the storage permissions. I ran this:

adb shell
su
restorecon -FR /data/media/0

I reinstalled the apps again, and there were no errors. Fenix 2 installed happily this time, enhancing my suspicion of some API change breaking it on Android 11.

Also found out that Strava required Google Maps so I also had to install Google Maps.

WeChat finally did install, but was then told by the app that my account cannot use Web WeChat, and I should use WeChat for Windows or Mac….. and I’m running Linux, so both of those options are not feasible.

However, I did find this: https://github.com/qo6xup6/ubuntu-deepin-wechat which is a Wine wrapper around the Windows WeChat app. This seems to work well, although I did have to update the client using the instructions on the README.md

FitBit refused to pair with my Ionic (again — it always seems to have this trouble whenever I have to reinstall the app). I eventually resorted to factory resetting my Ionic, and re-setting it up again. It worked this time, although the pairing took a few attempts.

Surprisingly, I was then able to add my Curve card to FitBit Pay, and the SMS verification worked.

All in all, it took me from around 7am to 12:30 pm to reflash, reinstall, and setup all the apps again, and reboot to make sure the apps still worked. So around 5 hours.

Pixelbook

Spent a big chunk of today preparing for, and attempting to upgrade my Pixelbook to Gallium OS.

I imaged it, then made a file backup of my home directory, before installing the OS, overwriting my Ubuntu, then restoring the home directory backup into the newly installed OS and then chowning the directory to me.

As a habit, I then imaged the laptop at this state.

I prepared a semi-automated script to install apps that I had installed on my Ubuntu, which included things like virt-manager, virtualbox, google-chrome and the like.

However, I soon found out that VirtualBox 6.1 seems to crash the mouse driver on reboot and the mouse pointer no longer moves and Gallium doesn’t even seem to see a pointer device when you check the mouse and touchpad option. I had to revert back to the image just after the file copy.

There is always the option of installing VirtualBox 6.0 from the Ubuntu repositories rather than the Oracle repositories, which uses a different installation setup. Maybe that will result in a different outcome.

Eventually, I restored back to my original Ubuntu installation so I can retry again tomorrow.

EDIT: Retried again the next day, and found out the sound wasn’t working, even on the live disk. Better find out what’s the deal with that…

EDIT2: Found out that my Pixelbook model doesn’t have working sound drivers on GalliumOS. I guess I will have to wait until that is fixed before using that. I guess I’m staying on Ubuntu. In the meantime, I’m going to see if I can compile a later version of the kernel to see if I can somehow get VirtualBox working better.

Pixelbooks and Ubuntu 20.04

After using my Pixelbook Eve on Ubuntu Eoan (19.10), my Ubuntu has started notifying me for an upgrade to 20.04 LTS. So, based on my past experiences of Ubuntu upgrades and how they always break things, I went through the process of backing up my files and making a Clonezilla image of my Pixelbook before even starting to do anything.

Then I went through the upgrade. It went through without any problems, but when it went to reboot afterwards, I was black screened after the Ubuntu splash screen.

I suspect it’s because my Pixelbook contains some tweaks via this GitHub repo, and that is still using a 4.x kernel. Last update was in 2019, so maybe it’s out of date.

Before restoring my old image back on, I installed GalliumOS which is an Ubuntu-based distro specifically aimed at ChromeOS devices. Then made a backup image of that before restoring the old image back on.

I might try installing Ubuntu 20.04 from clean and see if that has any better Pixelbook support than the older versions of Ubuntu, and make it so I don’t need to use the hacks. Bear in mind the hacks used the ChromeOS kernel, and I couldn’t do some things like use ufw or gufw. Using GalliumOS should fix that since I wouldn’t be using tweaks.

However, there’s still an annoying quirk GalliumOS has on my Pixelbook and that’s the jumpiness of the mouse pointer — touch the touchpad and the pointer jumps to that part of the screen, as if the touchpad was a representation of the screen, not a touchpad. It’s a quirk that can be gotten used to, but it is still annoying.

Slow Download Speeds on Steam For Linux

I’ve been getting horrendously slow speeds on Linux Steam (~500k/s) and 5-6Mb/s on Windows, and only now found out why. There’s a ticket on GitHub for this:

https://github.com/ValveSoftware/steam-for-linux/issues/3401

In short, the client is very aggressive on its DNS requests, which normally causes it to be throttled by servers, leading to really slow downloads. However, using dnsmasq allows the requests to be cached locally and offload the requests.

Even though the instructions are for Arch, they worked for me:

  1. Install dnsmasq
  2. Modify /etc/dnsmasq.config and add the line listen-address=127.0.0.1
  3. Restart the dnsmasq service (systemctl restart dnsmasq.service) or reboot your machine

Enjoy the speed

General Updates

So I haven’t been posting here much recently so here are some updates.

Been slowing trying to get back into running, have been slacking off WAAAAY too much lately. Tried using Aaptiv (@aaptiv) which is a training fitness app that has trainers talking you through the stuff, there are a few problems with it.

  1. When you use a stretch/strength training routine or yoga routine, you’re reliant on them telling you what to do, there’s no video guide to show you the correct form, and that’s bad. Other apps like FitBit Coach has videos where you can copy the coach to make sure you have the right form.
  2. On Treadmill/Running routines, they talk in mph, but treadmills here in the UK go in km/h, which requires conversion (1.0 mph = 1.6 kph)

On a separate note, I have bought another attempt at the CKA exam, but this time bought the bundle with the Kubernetes Fundamentals Training from Linux Foundation. Let’s see how different that is to Linux Academy’s training….

 

New Ubuntu Quirks

So, I install Ubuntu 17 clean on my laptop after the issues I had with drivers and immediately found out that gksu was not installed.

Installed that and tried to

gksudo nautilus

That failed and found out that Wayland had replaced the default of Xorg. Found an old Xauthority file from my backups and copied that back, which allowed me to get the popup window back for my gksu, but I couldn’t click it to enter the password :(

Then I found this article:

https://www.linuxuprising.com/2018/04/gksu-removed-from-ubuntu-heres.html

Which tells me I need to use the admin:/// file prefix instead to open something up as admin. Guess I’ll give it a go later.

%d bloggers like this: