Swap Partition 1st step

U174 · 21 September 2022 21:16

Dear all,

I am stuck on knowing what step to take to create a swap partition or file, get my hibernation button back on the start menu and hibernate.

I have a dual boot and installed manjaro without enough swap partition and i have 64gb ram.

My root partition is 64gb. Not enough space for swap.
I could not get the swap to work on /home.

What’s the best step:

To increase the root partition size and add the swap file there?
Or create a new partition for the swap?

That’s all i need to know. And any important reminder, not to break the system is welcome.

I know backups are a must. I am going to install Timeshift Backup app, and give it a go.
I have some space management to do before i can backup everything.
Is backing up root, enough to roll the system back?

I got an issue where i mixed a UUID in Grub or fstab, and KDE would not load.
But because i had the changes noted down in my editor, i reverted them back using the CLI (which is super cool).

Does manjaro always offer the CLI when the system panics etc?
With manjaro a user is probably 98% of the time responsible for breaking a system down.
But to your knowledge what will bring the system completely down. Including the CLI?

I recall reading this on a thread, but i cannot find it.

tracyanne · 21 September 2022 21:38

How is your system currently Partitioned? That might help.

Nachlese · 21 September 2022 21:44

I’d say:
depending on what you need
(or think to need)
the swap space for

… you might be in good shape as it is

What makes you think that?
What do you currently have?

I second @tracyanne :
How is your system currently set up?

If you have the space to do the latter - why not do it?
Increasing the size of the root partition is IMO not to be preferred
(not even when it’s doable - if you have the space to do it)

But then again: increasing the size is not a big risk. If you have free space available to the right of that partition to be grown into.

… you expand the partition, then you grow the filesystem to fill the newly available space

U174 · 21 September 2022 21:59

I am not being able to add embedded images or links.
Getting: Sorry, you can’t embed media items in a post.

Nachlese · 21 September 2022 22:02

no pictures needed
(they cannot be parsed for text content)

the text output of:

lsblk -f

would be a start

or:
some form of inxi - the recommendation is to share:
inxi -Fazy

please use proper formatting
the little symbols atop the edit window - use code (preformatted text)

it should look like this:

[jo@vajo ~]$ lsblk -f
NAME     FSTYPE      FSVER LABEL  UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                                   
├─sda1   vfat        FAT32 EFISYS ACDE-A3C7                             510,7M     0% /boot/efi
├─sda2   ext4        1.0   boot   ef07ba8b-8853-4d17-bce2-e86737b35aaa  293,4M    32% /boot
└─sda4   crypto_LUKS 2            7b4bb6e5-f2e3-435d-834e-8c3ee34f3865                
  └─encr ext4        1.0          305afbd2-b8a3-4e18-8828-34c6d1ead4d1  910,1G     2% /
sr0

the form - not the content -
this is the output of that command from my system

Olli · 21 September 2022 22:11

Swap file creation

Note: Btrfs supports swap file with limitations since Linux kernel version 5.0, for this filesystem follow the procedure described in Btrfs#Swap file to initialize the swap file.

Use dd to create a swap file the size of your choosing. For example, creating a 4 GiB swap file:

sudo dd if=/dev/zero of=/swapfile bs=1M count=4096 status=progress

Note: Using dd to allocate a swap file is the most portable solution, see swapon(8) § Files with holes for details.

Set the right permissions (a world-readable swap file is a huge local vulnerability):

sudo chmod 0600 /swapfile

After creating the correctly sized file, format it to swap:

sudo mkswap -U clear /swapfile

Activate the swap file:

sudo swapon /swapfile

Finally, edit the fstab configuration to add an entry for the swap file:

/etc/fstab

/swapfile none swap defaults 0 0

https://wiki.archlinux.org/title/Swap

Nachlese · 21 September 2022 22:18

it might not be the best idea to supress the generation of a UUID with

mkswap -U clear

as the UUID might be needed, to refer to it in /etc/default/grub for example

and he doesn’t have enough space to create a swap file, as he says - certainly not the size of his RAM

Olli · 21 September 2022 22:19

touche, that’s a mistake by copy and paste, i corrected my post

U174 · 21 September 2022 23:10

I appreciate everyone’s input.
But what i really need is 1 way. The best recommended way, and stick to it!
I have enough space to create a 66gb swap partition to hibernate. This is the best approach right?

Updating fstab and grub with the new UUID and i should be good to go?

lsblk -f
NAME        FSTYPE   FSVER LABEL      UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0       squashfs 4.0                                                         0   100% /var/lib/snapd/snap/core18/2566
loop1       squashfs 4.0                                                         0   100% /var/lib/snapd/snap/core/13425
loop2       squashfs 4.0                                                         0   100% /var/lib/snapd/snap/bare/5
loop3       squashfs 4.0                                                         0   100% /var/lib/snapd/snap/core20/1611
loop4       squashfs 4.0                                                         0   100% /var/lib/snapd/snap/acrordrdc/62
loop5       squashfs 4.0                                                         0   100% /var/lib/snapd/snap/core20/1623
loop6       squashfs 4.0                                                         0   100% /var/lib/snapd/snap/core/13741
loop7       squashfs 4.0                                                         0   100% /var/lib/snapd/snap/gnome-3-28-1804/161
loop8       squashfs 4.0                                                         0   100% /var/lib/snapd/snap/core18/2560
loop9       squashfs 4.0                                                         0   100% /var/lib/snapd/snap/gnome-3-38-2004/115
loop10      squashfs 4.0                                                         0   100% /var/lib/snapd/snap/gtk-common-themes/1535
loop11      squashfs 4.0                                                         0   100% /var/lib/snapd/snap/notepad-plus-plus/372
loop12      squashfs 4.0                                                         0   100% /var/lib/snapd/snap/notepad-plus-plus/374
loop13      squashfs 4.0                                                         0   100% /var/lib/snapd/snap/wine-platform-6-stable/19
loop14      squashfs 4.0                                                         0   100% /var/lib/snapd/snap/wine-platform-7-devel-core20/17
loop15      squashfs 4.0                                                         0   100% /var/lib/snapd/snap/wine-platform-7-devel-core20/18
loop16      squashfs 4.0                                                         0   100% /var/lib/snapd/snap/wine-platform-runtime/315
loop17      squashfs 4.0                                                         0   100% /var/lib/snapd/snap/wine-platform-runtime/316
loop18      squashfs 4.0                                                         0   100% /var/lib/snapd/snap/wine-platform-runtime-core20/36
loop19      squashfs 4.0                                                         0   100% /var/lib/snapd/snap/wine-platform-runtime-core20/37
sda                                                                                       
├─sda1      vfat     FAT32 ACRONIS HM 121D-A79D                                           
└─sda2      ntfs           T7         DEE024B9E0249A33                      982.9G    47% /run/media/user/T7
nvme0n1                                                                                   
├─nvme0n1p1 vfat     FAT32            1C88-56D1                                           
├─nvme0n1p2 ntfs                      28E289C4E28996AA                      204.6G    71% /run/media/user/28E289C4E28996AA
├─nvme0n1p3 ntfs                      5E1806201805F7B3                                    
├─nvme0n1p4 vfat     FAT32 NO_LABEL   AC41-CD02                             511.4M     0% /boot/efi
├─nvme0n1p5 swap     1                41b019f3-091c-4ab7-88df-be4b1cf9cee1                
├─nvme0n1p6 ext4     1.0              ece9fde4-aa4e-441d-8ef7-db685b9c348e   19.6G    63% /
└─nvme0n1p7 ext4     1.0              32a01f29-852c-43f0-8b05-9b57ed038190  129.5G    26% /home

inxi -Fazy
System:
  Kernel: 5.19.7-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-5.19-x86_64
    root=UUID=ece9fde4-aa4e-441d-8ef7-db685b9c348e rw
    resume=UUID=32a01f29-852c-43f0-8b05-9b57ed038190 resume_offset=xxx quiet
    udev.log_priority=3 nowatchdog
  Console: pty pts/1 wm: kwin_x11 DM: SDDM Distro: Manjaro Linux
    base: Arch Linux
Machine:
  Type: Laptop System: Dell product: Precision 5540 v: N/A serial: <filter>
    Chassis: type: 10 serial: <filter>
  Mobo: Dell model: 03DYVY v: A00 serial: <filter> UEFI: Dell v: 1.17.0
    date: 04/19/2022
Battery:
  ID-1: BAT0 charge: 76.4 Wh (100.0%) condition: 76.4/97.0 Wh (78.8%)
    volts: 12.6 min: 11.4 model: SMP DELL GPM0365 type: Li-ion serial: <filter>
    status: full
CPU:
  Info: model: Intel Xeon E-2276M socket: BGA1440 (U3E1) note: check bits: 64
    type: MT MCP arch: Coffee Lake level: v3 built: 2018 process: Intel 14nm
    family: 6 model-id: 0x9E (158) stepping: 0xD (13) microcode: 0xF0
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
    L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 1519 high: 2800 min/max: 800/4700 base/boost: 3465/4700
    scaling: driver: intel_pstate governor: powersave volts: 1.0 V
    ext-clock: 100 MHz cores: 1: 900 2: 866 3: 900 4: 900 5: 2800 6: 833
    7: 2800 8: 836 9: 900 10: 2800 11: 2800 12: 900 bogomips: 67226
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: Split huge pages
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: Enhanced IBRS
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB
    filling, PBRSB-eIBRS: SW sequence
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: Dell
    driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
    ports: active: DP-4,DP-5 off: eDP-1 empty: DP-1, DP-2, DP-3, DP-6
    bus-ID: 00:02.0 chip-ID: 8086:3e9b class-ID: 0300
  Device-2: NVIDIA TU117GLM [Quadro T2000 Mobile / Max-Q] vendor: Dell
    driver: nouveau v: kernel non-free: 515.xx+ status: current (as of 2022-08)
    arch: Turing code: TUxxx process: TSMC 12nm built: 2018-22 pcie: gen: 3
    speed: 8 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:1fb8 class-ID: 0302
  Device-3: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo
    bus-ID: 1-12:7 chip-ID: 0c45:6723 class-ID: 0e02
  Display: x11 server: X.Org v: 21.1.4 compositor: kwin_x11 driver: X:
    loaded: modesetting alternate: fbdev,vesa gpu: i915 display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 3840x1200 s-dpi: 96 s-size: 1014x317mm (39.92x12.48")
    s-diag: 1062mm (41.83")
  Monitor-1: not-matched mapped: DP-1-1 pos: primary,left res: 1920x1200
    hz: 60 dpi: 94 size: 518x324mm (20.39x12.76") diag: 611mm (24.05")
    modes: N/A
  Monitor-2: not-matched mapped: DP-1-2 pos: primary,right res: 1920x1080
    hz: 60 dpi: 102 size: 477x268mm (18.78x10.55") diag: 547mm (21.54")
    modes: N/A
  Monitor-3: eDP-1 note: disabled model: Sharp 0x14ba built: 2019
    res: 1920x1080 dpi: 142 gamma: 1.2 size: 344x194mm (13.54x7.64")
    diag: 395mm (15.5") ratio: 16:9 modes: 1920x1080
  OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 22.1.7
    direct render: Yes
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: Dell driver: snd_hda_intel
    bus-ID: 1-5.3.4:10 v: kernel chip-ID: 0bda:402e
    alternate: snd_soc_skl,snd_sof_pci_intel_cnl class-ID: 0102
    bus-ID: 00:1f.3 chip-ID: 8086:a348 serial: <filter> class-ID: 0403
  Device-2: Realtek USB Audio type: USB driver: snd-usb-audio
  Sound Server-1: ALSA v: k5.19.7-1-MANJARO running: yes
  Sound Server-2: JACK v: 1.9.21 running: no
  Sound Server-3: PulseAudio v: 16.1 running: yes
  Sound Server-4: PipeWire v: 0.3.57 running: yes
Network:
  Device-1: Intel Wireless-AC 9260 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 3b:00.0 chip-ID: 8086:2526 class-ID: 0280
  IF: wlp59s0 state: down mac: <filter>
  Device-2: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152
    bus-ID: 4-1.4:5 chip-ID: 0bda:8153 class-ID: 0000 serial: <filter>
  IF: enp58s0u1u4 state: up speed: 100 Mbps duplex: full mac: <filter>
  IF-ID-1: vboxnet0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel Wireless-AC 9260 Bluetooth Adapter type: USB driver: btusb
    v: 0.8 bus-ID: 1-4:3 chip-ID: 8087:0025 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 2 state: up address: see --recommends
Drives:
  Local Storage: total: 2.75 TiB used: 1.42 TiB (51.7%)
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: SK Hynix model: PC601A NVMe 1TB
    size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: 80001111 temp: 33.9 C scheme: GPT
  SMART: yes health: PASSED on: 357d 3h cycles: 878 read-units: 249,642,482
    [127 TB] written-units: 94,031,225 [48.1 TB]
  ID-2: /dev/sda maj-min: 8:0 type: USB vendor: Samsung model: PSSD T7 Touch
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B type: SSD
    serial: <filter> scheme: GPT
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: 62.5 GiB size: 61.22 GiB (97.95%) used: 38.46 GiB (62.8%)
    fs: ext4 block-size: 4096 B dev: /dev/nvme0n1p6 maj-min: 259:6
  ID-2: /boot/efi raw-size: 512.8 MiB size: 511.7 MiB (99.80%) used: 316 KiB
    (0.1%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p4 maj-min: 259:4
  ID-3: /home raw-size: 191 GiB size: 186.94 GiB (97.87%) used: 47.85 GiB
    (25.6%) fs: ext4 block-size: 4096 B dev: /dev/nvme0n1p7 maj-min: 259:7
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 49.0 C pch: 47.0 C mobo: 36.0 C gpu: nouveau
    temp: 29.0 C
  Fan Speeds (RPM): cpu: 2391 fan-2: 2399
Info:
  Processes: 321 Uptime: 5h 36m wakeups: 9 Memory: 62.44 GiB used: 9.05 GiB
  (14.5%) Init: systemd v: 251 default: graphical tool: systemctl Compilers:
  gcc: 12.2.0 clang: 14.0.6 Packages: 1711 pm: pacman pkgs: 1695 libs: 445
  tools: pamac,yay pm: flatpak pkgs: 16 Shell: Bash (sudo) v: 5.1.16
  running-in: konsole inxi: 3.3.21

U174 · 21 September 2022 23:28

I don’t have enough space in root partition for the swap file that needs to be at least 64gb.
See what i answered @Nachlese

Why am i unable to include links even when quoting your own arch swap link?
Is this because i am a new user?
How to overcome this?

tracyanne · 22 September 2022 02:11

What are all those squashfs entries?

I notice that lsblk doen’t give the size of your Swap partition.

try sudo fdisk -l

You don’t seem to have a lot of space there for your Linux install. I suspect that whatever you do it will require a lot of shuffling around of stuff.

One way I would consider is removing the current swap, and moving root back into that, resizing root, and probably home to accommodate the 64 Gig you are going to need for a swap partition.

Another way would be to remove the swap partition and move root into that thus resizing it, and also shuffling home to the ‘right’ to make extra room in the root partition for a swap file.

I can’t see many options myself, given the amount of disk space available to you.

FancierTech · 22 September 2022 05:37

In your case (64GB of RAM) I wouldn’t use swap file as it will be slower with massive information than a partition (if it on ssd) and also I would not play with root.

If the system was broken by something in root and not somewhere else and the filesystem is not damaged — yes, this would be enough.

Running every or at least most of commands by root or allowing home/user/ to act as root after expanding the rights by chmod. That was how I broke Manjaro around 9 months ago when I started to learn Linux by the most fun way I got know after college practice period

Nachlese · 22 September 2022 06:16

There are multiple ways and none of them is the best per se.
You have to decide what is best for you.

What DO you (think) you need the spap space for?

Your kernel command line does refer to some swap space - but none is to be seen in the rest of the inxi output,
your system does not see any.
(resume_offset=xxx refers to swap, to hibernate from and to).
Where is your current swap that this refers to?
cat /etc/fstab
and how big is it?

To hibernate the system, you need swap.
On the other hand, with an SSD, the boot time is fast, so you might not need to hibernate.
Suspend will work in any case.

If you have the disk space, create a swap partition.
Big enough to hold the contents of RAM - which might not need to be 64 GB.
Even 16 GB might be enough - look at your typical RAM usage.
I have just 8 GB and seldom even touch swap.

I’m probably greedy,
but to set aside 64 GB of an SSD that will rarely if ever be used - or just be used to hibernate the system -
does not look like something I’d be eager and willing to do.

By creating a partition, there is no chance to mess up anything.
All you need to do is create it, format it to swap and then add it to /etc/fstab.

It might be more complicated if your system is encrypted - it looks like it - and you also want to encrypt the swap space.
The Arch wiki is a good reference for info on all of this.

There is also zram, zswap and zramswap - basically methods to virtually increasing the available RAM by compressing it or setting aside a portion of it for swap.
But none of these will help or be of use for you to hibernate your system.

yes, that is the reason

format them differently - blockquote might help

There is info for new users here on the forum explaining all this.

U174 · 22 September 2022 09:25

ok

Humm, looks like the best is to backup the entire system.
I have to expand my linux partitions size. I am installing software under home to save root space.
Expanding root space should not break anything.
If something goes wrong i will re-install manjaro again but it will take me time to install needed apps and tweak them, which i want to avoid.

This i understood is the rule of thumb in the unix/linux world. Excessive root use will create problems, and security vulnerabilities.
I run everything in windows as admin with no user control alerts, but in linux it’s a mistake, as it will break a rolling release distro.
Guilty as charged; i tend to run most commands as root because so far 70% of them require it. So far no problems, but this is why backups and in depth knowledge of linux will come handy. To correct mistakes.

U174 · 22 September 2022 13:05

drag to the right to see

fdisk -l

Disk /dev/nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: PC601A NVMe SK hynix 1TB                
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: BDA4A58F-387A-4CBD-9795-FD63F95896C0

Device              Start        End    Sectors   Size Type
/dev/nvme0n1p1       2048     206847     204800   100M EFI System
/dev/nvme0n1p2     206848 1462479344 1462272497 697.3G Microsoft basic data
/dev/nvme0n1p3 1999354544 2000405167    1050624   513M Windows recovery environment
/dev/nvme0n1p4 1462479345 1463529471    1050127 512.8M EFI System
/dev/nvme0n1p5 1463529472 1467723775    4194304     2G Linux swap
/dev/nvme0n1p6 1467723776 1598795775  131072000  62.5G Linux filesystem
/dev/nvme0n1p7 1598795776 1999354543  400558768   191G Linux filesystem

Partition table entries are not in disk order.


Disk /dev/loop0: 55.56 MiB, 58261504 bytes, 113792 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 113.99 MiB, 119525376 bytes, 233448 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 4 KiB, 4096 bytes, 8 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop4: 68 KiB, 69632 bytes, 136 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 61.96 MiB, 64966656 bytes, 126888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop6: 114.93 MiB, 120508416 bytes, 235368 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop8: 55.56 MiB, 58261504 bytes, 113792 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop7: 164.76 MiB, 172761088 bytes, 337424 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop5: 63.22 MiB, 66293760 bytes, 129480 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop9: 346.3 MiB, 363118592 bytes, 709216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop10: 91.69 MiB, 96141312 bytes, 187776 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop11: 6.01 MiB, 6303744 bytes, 12312 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop13: 322.95 MiB, 338636800 bytes, 661400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop12: 6.02 MiB, 6311936 bytes, 12328 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop14: 434.95 MiB, 456073216 bytes, 890768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop15: 436.97 MiB, 458199040 bytes, 894920 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop16: 347.09 MiB, 363945984 bytes, 710832 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop17: 346.97 MiB, 363827200 bytes, 710600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop18: 465.73 MiB, 488349696 bytes, 953808 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop19: 463.16 MiB, 485662720 bytes, 948560 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: PSSD T7 Touch   
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 33553920 bytes
Disklabel type: gpt
Disk identifier: 3C50A09C-29B2-4056-8DE7-177E278F38DA

Device       Start        End    Sectors  Size Type
/dev/sda1     2048    4196351    4194304    2G Microsoft basic data
/dev/sda2  4196352 3907025071 3902828720  1.8T Microsoft basic data

It’s the opposite. I am getting many options from peers, and it’s confusing me further
Options help you analyze best course of action plus a better understanding of things.
But at this stage i just want to get it done, and that’s it!

Disk space is not an issue. As i will reduce windows size to increase linux’s.
Not being able to paste links, or paste/upload images is really annoying me.

Anyway i will delete the existing swap partition and create a 32gb one, to see if this much allows hibernation.

Let me know if there’s anything else you could chime as you use manjaro for much longer than i do

U174 · 22 September 2022 13:12

Nachlese:

U174:

But what i really need is 1 way. The best recommended way, and stick to it!

There are multiple ways and none of them is the best per se.
You have to decide what is best for you.

Nachlese:

depending on what you need
(or think to need)
the swap space for

… you might be in good shape as it is

What DO you (think) you need the spap space for?

Your kernel command line does refer to some swap space - but none is to be seen in the rest of the inxi output,
your system does not see any.
(resume_offset=xxx refers to swap, to hibernate from and to).
Where is your current swap that this refers to?
cat /etc/fstab
and how big is it?

To hibernate the system, you need swap.
On the other hand, with an SSD, the boot time is fast, so you might not need to hibernate.
Suspend will work in any case.

If you have the disk space, create a swap partition.
Big enough to hold the contents of RAM - which might not need to be 64 GB.
Even 16 GB might be enough - look at your typical RAM usage.
I have just 8 GB and seldom even touch swap.

I’m probably greedy,
but to set aside 64 GB of an SSD that will rarely if ever be used - or just be used to hibernate the system -
does not look like something I’d be eager and willing to do.

By creating a partition, there is no chance to mess up anything.
All you need to do is create it, format it to swap and then add it to /etc/fstab.

It might be more complicated if your system is encrypted - it looks like it - and you also want to encrypt the swap space.
The Arch wiki is a good reference for info on all of this.

There is also zram, zswap and zramswap - basically methods to virtually increasing the available RAM by compressing it or setting aside a portion of it for swap.
But none of these will help or be of use for you to hibernate your system.

U174:

Why am i unable to include links even when quoting your own arch swap link?
Is this because i am a new user?

yes, that is the reason

U174:

How to overcome this?

format them differently - blockquote might help

There is info for new users here on the forum explaining all this.

You’re very helpful and appreciated!
But you’re shooting in every direction and confusing me

Not everyone is at level

Nachlese · 22 September 2022 17:43

That was certainly not my intention.

Read one paragraph at a time so you don’t get lost.

The long and short of it is: I don’t think you need swap
… unless you know or think otherwise

U174 · 22 September 2022 20:56

But hibernating is a cool thing. It preserves our workspace and allows the computer to save energy and not heat up.

This is my main reason.

Olli · 22 September 2022 20:59

and shutting off the computer saves a way more …
but yes i agree we live in a world of decay and stupidity where a power-off button is too much work for people.

tracyanne · 22 September 2022 21:07

I prefer to think of it as a Power On button, for when I resume from Hibernation