Difference between revisions of "User:Whnr"

From ArchWiki
Jump to navigation Jump to search
(s3 sleep works now and fwupd)
(snapshot stuff)
Line 3: Line 3:
 
== Installation ==
 
== Installation ==
 
* Followed mainly https://gist.github.com/heppu/6e58b7a174803bc4c43da99642b6094b
 
* Followed mainly https://gist.github.com/heppu/6e58b7a174803bc4c43da99642b6094b
 +
** This uses [[Systemd-boot]]
 +
** There is a pacman hook to update {{ic|bootctl}} everytime the systemd package gets an update
 
* Took the cryptsetup from [[Dm-crypt/Device_encryption#Encryption_options_for_LUKS_mode]]
 
* Took the cryptsetup from [[Dm-crypt/Device_encryption#Encryption_options_for_LUKS_mode]]
 
* S3 sleep works with the firmware 1.30 and higher.  
 
* S3 sleep works with the firmware 1.30 and higher.  
Line 37: Line 39:
 
* Goal: Create an automatic or manual snapshot that can be restored if needed
 
* Goal: Create an automatic or manual snapshot that can be restored if needed
 
* Creation:
 
* Creation:
** Create a backup of the boot folder, as it is not covered by the lvm =>{{ic|cd /boot}} =>{{ic|sudo tar -cvf boot-snap.tar.gz *}}
+
** Create a backup of the boot folder, as it is not covered by the lvm =>{{ic|cd /boot}} =>{{ic|sudo tar -uvf boot-snap.tar.gz *}}
**{{ic|sudo lvcreate --snapshot --size 30G --name root-snap /dev/vg0/root}}
+
** The root file system snapshot should be created during boot to keep the consistency of the file system
 +
*** Basic command: {{ic|sudo lvcreate --snapshot --size 30G --name root-snap /dev/vg0/root}}
 +
*** This will be done with a systemd service similar to what is said in [[Create_root_filesystem_snapshots_with_LVM]]
 +
** Add a loader configuration with the kernel parameter with the systemd target
 
* Restore:
 
* Restore:
 
** Check if the boot partition has changed:{{ic|cd /boot}} =>{{ic|sudo tar --compare boot-snap.tar.gz}} => If yes recreate the old state by extracting files
 
** Check if the boot partition has changed:{{ic|cd /boot}} =>{{ic|sudo tar --compare boot-snap.tar.gz}} => If yes recreate the old state by extracting files
 
**{{ic|sudo lvconvert --merge /dev/vg0/root-snap}} => Will automatically merge the snapshot back at the next reboot => This does hang at some point (FIXME), a reboot works.
 
**{{ic|sudo lvconvert --merge /dev/vg0/root-snap}} => Will automatically merge the snapshot back at the next reboot => This does hang at some point (FIXME), a reboot works.
 
* Or remove:{{ic|sudo lvremove /dev/vg0/root-swap}}
 
* Or remove:{{ic|sudo lvremove /dev/vg0/root-swap}}
 +
 +
==== Service files ====
 +
Are in .dotfiles/systemd
  
 
== ToDo / Wishlist ==
 
== ToDo / Wishlist ==

Revision as of 11:08, 12 November 2018

I am using this page to keep track of "stuff". I'm new with Arch. My Lenovo ThinkPad X1 Carbon (Gen 6) just arrived. Time to move away from MacOS once and for all (initial idea mainly because of the new Apple keyboards).

Installation

Fiwrmware updates

Can be done through fwupd

System restore snapshots

Setting up system snapshots that can be restored if e.g. an update fails

  • Goal: Create an automatic or manual snapshot that can be restored if needed
  • Creation:
    • Create a backup of the boot folder, as it is not covered by the lvm =>cd /boot =>sudo tar -uvf boot-snap.tar.gz *
    • The root file system snapshot should be created during boot to keep the consistency of the file system
    • Add a loader configuration with the kernel parameter with the systemd target
  • Restore:
    • Check if the boot partition has changed:cd /boot =>sudo tar --compare boot-snap.tar.gz => If yes recreate the old state by extracting files
    • sudo lvconvert --merge /dev/vg0/root-snap => Will automatically merge the snapshot back at the next reboot => This does hang at some point (FIXME), a reboot works.
  • Or remove:sudo lvremove /dev/vg0/root-swap

Service files

Are in .dotfiles/systemd

ToDo / Wishlist

  • Stability testing
    • systester-cli -gausslg 16M -threads 8 -bench -turns 50 -log (first try with -120mv ran for 1 minute before crashing)
    • Settled to -100mv on CPU (as -110 had 3 errors after 60 Minutes), -110 on GPU => No graphic failiures with unigine-haven and systester at the same time
  • Changing the thermal paste?