1 Topic by zapper

  • zapper
  • zapper
  • Hyper Cyber
  • Offline
  • Registered: 2017-10-18
  • Posts: 1,075

Topic: Had some issues with lvm2, a while back,

so I kind of have to readd you throgh and rachad on tox.  I didn't back up enough of my tox configs... sad

That being said, I  went through a three day challenge lol trying to get my Hyperbola 0.4 install back to normal. 

I used disk cloning though to simplify it. 

The current lvm2 works fine, but still has errors when it boots. 

Heh, but it least I can boot it up completely.

That being said, anytime you reinstall it now, you can see the linux image isn't complete, but it does at least boot properly. tongue

smile

HyperbolaBSD: The Future of Secure Libre Lightweight Operating Systems!

2 Reply by the_hype (edited by the_hype 2021-07-19 03:03:52)

  • the_hype
  • Guest

Re: Had some issues with lvm2, a while back,

for all who had the same problem: you can fix it in the initramfs with:

lvm vgchange -a y my-volume-group (default matrix)

exit (reboot)

and pacman -Syu (lvm2 reinstall)

edit: lvm vgchange -a y my-volume-group (default matrix)

3 Reply by zapper

  • zapper
  • zapper
  • Hyper Cyber
  • Offline
  • Registered: 2017-10-18
  • Posts: 1,075

Re: Had some issues with lvm2, a while back,

the_hype wrote:

for all who had the same problem: you can fix it in the initramfs with:

vgchange -a y my-volume-group (default matrix)

exit (reboot)

and pacman -Syu (lvm2 reinstall)

When issues like this pop up, I wish someone would post the solution to it sooner... tongue

Oh well, its over and done with I suppose. But yeah, if you see any hazards like this, please report them here. smile

Although I do admit I shouldve tested with qemu first. ;0

HyperbolaBSD: The Future of Secure Libre Lightweight Operating Systems!

4 Reply by the_hype (edited by the_hype 2021-07-19 05:42:00)

  • the_hype
  • Guest

Re: Had some issues with lvm2, a while back,

zapper wrote:

...

When issues like this pop up, I wish someone would post the solution to it sooner... tongue

...

I wasn't really sure that the problem was a systemic fault or something i messed up myself (because i test a lot of stuff right now) until i saw your post.

Should have been obvious from the package update timeline, but i needet some time to figure it out.