Optimal 2 drive partitioning during installation

Currently in my laptop I have 2 drives, 1 SSD (250Gb) and 1 HDD (1 Tb). The SSD is used for the Windows OS and the HDD for my general files.
Would it be better to install the root,swap, and grub mount points on the SSD and the home one on the HDD or should I have them all on my HDD ?
Would it mess something up with the already existing Windows one on the SSD?

Please, provide some more info:

Most important info for the moment is output of:

inxi -Fxxxza --no-host
1 Like

New to the forum and manjaro in general so didnt know what info to provide.
Here is the output of the command :

System:    Kernel: 5.2.21-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.2.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.2-x86_64 root=UUID=5a9c8096-cca5-4e7b-a12d-0d51ebce7083 rw quiet apparmor=1 
           security=apparmor udev.log_priority=3 
           Desktop: i3 4.17.1 info: polybar dm: LightDM 1.30.0 Distro: Manjaro Linux 
Machine:   Type: Laptop System: Micro-Star product: GS63VR 7RF v: REV:1.0 serial: <filter> Chassis: type: 10 serial: <filter> 
           Mobo: Micro-Star model: MS-16K2 v: REV:1.0 serial: <filter> UEFI: American Megatrends v: E16K2IMS.312 
           date: 06/13/2017 
Battery:   ID-1: BAT1 charge: 55.7 Wh condition: 58.5/65.0 Wh (90%) volts: 11.7/11.4 model: MSI BIF0_9 type: Li-ion 
           serial: N/A status: Discharging 
CPU:       Topology: Quad Core model: Intel Core i7-7700HQ bits: 64 type: MT MCP arch: Kaby Lake family: 6 model-id: 9E (158) 
           stepping: 9 microcode: B4 L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 44944 
           Speed: 800 MHz min/max: 800/3800 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 801 
           Vulnerabilities: Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling 
Graphics:  Device-1: Intel HD Graphics 630 vendor: Micro-Star MSI driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:591b 
           Device-2: NVIDIA GP106M [GeForce GTX 1060 Mobile] vendor: Micro-Star MSI driver: nvidia v: 430.40 bus ID: 01:00.0 
           chip ID: 10de:1c20 
           Display: x11 server: X.Org 1.20.5 driver: modesetting,nvidia compositor: compton resolution: 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 1060/PCIe/SSE2 v: 4.6.0 NVIDIA 430.40 direct render: Yes 
Audio:     Device-1: Intel CM238 HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           chip ID: 8086:a171 
           Sound Server: ALSA v: k5.2.21-1-MANJARO 
Network:   Device-1: Qualcomm Atheros Killer E2500 Gigabit Ethernet vendor: Micro-Star MSI driver: alx v: kernel port: d000 
           bus ID: 3d:00.0 chip ID: 1969:e0b1 
           IF: enp61s0 state: down mac: <filter> 
           Device-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter vendor: Bigfoot Networks driver: ath10k_pci 
           v: kernel port: d000 bus ID: 3e:00.0 chip ID: 168c:003e 
           IF: wlp62s0 state: up mac: <filter> 
           Device-3: Qualcomm Atheros type: USB driver: btusb bus ID: 1-10:4 chip ID: 0cf3:e300 
Drives:    Local Storage: total: 1.14 TiB used: 9.29 GiB (0.8%) 
           ID-1: /dev/nvme0n1 vendor: Toshiba model: N/A size: 238.47 GiB block size: physical: 512 B logical: 512 B 
           speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: 57XA4104 scheme: GPT 
           ID-2: /dev/sda vendor: Seagate model: ST1000LM048-2E7172 size: 931.51 GiB block size: physical: 4096 B 
           logical: 512 B speed: 6.0 Gb/s rotation: 5400 rpm serial: <filter> rev: SDM1 scheme: GPT 
Partition: ID-1: / raw size: 245.90 GiB size: 241.04 GiB (98.02%) used: 9.25 GiB (3.8%) fs: ext4 dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 50.0 C mobo: 27.8 C gpu: nvidia temp: 43 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 199 Uptime: 1m Memory: 15.55 GiB used: 464.0 MiB (2.9%) Init: systemd v: 242 Compilers: gcc: 9.2.0 
           clang: 9.0.0 Shell: bash v: 5.0.11 running in: urxvt inxi: 3.0.36 

Thanks. It looks like you have installed Manjaro with an i3 desktop on the SSD so it is already a dual boot install with Win10? If so, everything installed in UEFI mode? Can you provide output of

lsblk -f

By the way, kernel 5.2.21-1 is EOL, check forum Announcements before next update.

In principle I would think this install has benefits as the faster SSD is used for both OS. On the other side dual boot on same disk is always a bit higher risk of getting in trouble when Windows is updating.

Currently manjaro is installed entirely on the HDD, both the grub partition and the root one, without a separate one for /home.
Here is the output you asked :

NAME        FSTYPE   LABEL       UUID                                 FSAVAIL FSUSE% MOUNTPOINT
loop0       squashfs                                                        0   100% /var/lib/snapd/snap/sublime-text/77
loop1       squashfs                                                        0   100% /var/lib/snapd/snap/spotify/36
loop2       squashfs                                                        0   100% /var/lib/snapd/snap/core/7917
├─sda1      ntfs     Data        01D57E01C09B2DC0                                    
├─sda2      ext4                 5a9c8096-cca5-4e7b-a12d-0d51ebce7083  219.5G     4% /
├─sda3      ntfs     BIOS_RVY    CABCD012BCCFF6CB                                    
└─sda4      vfat                 A287-80C3                                           
├─nvme0n1p1 vfat     SYSTEM      D4C7-1D90                             255.9M    14% /boot/efi
├─nvme0n1p3 ntfs     Windows     0C44C78D44C777CA                                    
└─nvme0n1p4 ntfs     WinRE tools 1EAEC963AEC933D5  

Can you provide output of cat /etc/fstab and sudo fdisk -l

How do you currently switch between the OS, can you use grub or do you need to enter the firmware?

Also, I would recommend to have / and home on same disk, swap does not matter as you have 16GB memory and I guess swap is not used frequently. If swap would be used often to a high degree it's better to use the HDD as it is more suitable for many write requests, even if newer SDD are not so sensitive any more.

I have set my boot order to Manjaro first and then through the grub I can choose either manjaro or windows to boot

cat output :

# /etc/fstab: static file system information.
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=D4C7-1D90                            /boot/efi      vfat    umask=0077 0 2
UUID=A287-80C3                            /boot/efi      vfat    umask=0077 0 2
UUID=5a9c8096-cca5-4e7b-a12d-0d51ebce7083 /              ext4    defaults,noatime 0 1

fdisk output:

Disk /dev/nvme0n1: 238.49 GiB, 256060514304 bytes, 500118192 sectors
Disk model: THNSN5256GPU7 TOSHIBA                   
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: DB0D0DFE-0554-4990-9F9B-10E6812689AB

Device             Start       End   Sectors   Size Type
/dev/nvme0n1p1      2048    616447    614400   300M EFI System
/dev/nvme0n1p2    616448    878591    262144   128M Microsoft reserved
/dev/nvme0n1p3    878592 498274303 497395712 237.2G Microsoft basic data
/dev/nvme0n1p4 498274304 500117503   1843200   900M Windows recovery environment

Disk /dev/sda: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: ST1000LM048-2E71
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 28FC2E9A-CDB0-4F60-89C9-CE55B26C4A72

Device          Start        End    Sectors   Size Type
/dev/sda1        2048 1393663999 1393661952 664.6G Microsoft basic data
/dev/sda2  1394278400 1909970943  515692544 245.9G Linux filesystem
/dev/sda3  1909970944 1953523711   43552768  20.8G Windows recovery environment
/dev/sda4  1393664000 1394278399     614400   300M EFI System

Partition table entries are not in disk order.

Disk /dev/loop0: 181.8 MiB, 189870080 bytes, 370840 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: 89.13 MiB, 93454336 bytes, 182528 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: 67.58 MiB, 70844416 bytes, 138368 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

Everything looks fine to me, I would keep it as it is. Linux Manjaro is usually fast, so I would assume the performance is OK if it stays on the HDD. Or do you have any issues not being discussed?

Yea, thats what I currently have. I was just thinking if it would be more efficient if root was on an SSD for the better read/write speeds and keep /home on the HDD.

No, generally it works just fine. Maybe some times a few windows take 1-2 sec to load but I dont mind. Mainly created the post out of curiosity, if it would boost performance to have root on an SSD separated from /home.

It would be faster but your current install is more robust.

To verify your performance, what is the output of

systemd-analyze blame
Startup finished in 8.915s (firmware) + 4.773s (loader) + 6.228s (kernel) + 31.345s (userspace) = 51.263s 
graphical.target reached after 30.509s in userspace

         12.819s systemd-journal-flush.service
         12.196s snapd.service
         10.142s ModemManager.service
          8.215s lvm2-monitor.service
          6.711s dev-sda2.device
          3.701s accounts-daemon.service
          3.545s NetworkManager.service
          3.057s polkit.service
          2.714s ldconfig.service
          2.641s avahi-daemon.service
          2.603s systemd-logind.service
          2.600s bluetooth.service
          2.591s maia-console@tty1.service
          2.054s apparmor.service
          1.932s systemd-udevd.service
          1.369s systemd-sysusers.service
          1.316s snapd.apparmor.service
          1.120s lightdm.service
          1.103s ufw.service
           832ms tlp.service
           747ms systemd-sysctl.service
           745ms upower.service
           742ms var-lib-snapd-snap-spotify-36.mount
           687ms wpa_supplicant.service
           644ms systemd-tmpfiles-setup-dev.service
           639ms var-lib-snapd-snap-core-7917.mount
           580ms var-lib-snapd-snap-sublime\x2dtext-77.mount
           458ms systemd-udev-trigger.service
           452ms systemd-random-seed.service
           375ms systemd-tmpfiles-setup.service
           348ms systemd-fsck@dev-disk-by\x2duuid-D4C7\x2d1D90.service
           330ms systemd-backlight@backlight:intel_backlight.service
           330ms systemd-modules-load.service
           316ms systemd-rfkill.service
           311ms systemd-journald.service
           289ms systemd-journal-catalog-update.service
           245ms systemd-tmpfiles-clean.service
           207ms boot-efi.mount
           179ms systemd-update-utmp.service
           139ms systemd-remount-fs.service
            86ms systemd-user-sessions.service
            85ms user@1000.service
            79ms tmp.mount
            78ms sys-kernel-debug.mount
            72ms kmod-static-nodes.service
            71ms dev-hugepages.mount
            70ms dev-mqueue.mount
            41ms systemd-update-done.service
            24ms user-runtime-dir@1000.service
             5ms sys-kernel-config.mount
             2ms sys-fs-fuse-connections.mount
             2ms snapd.socket

I use a SSD and have:

Startup finished in 2.369s (kernel) + 2.045s (userspace) = 4.414s 
graphical.target reached after 1.868s in userspace

So, no question an SSD install would boost boot and normal operation.

1 Like

Yea, I think I ll re-install and have root and grub partitions on the SSD and /home on the HDD, just for the better performance.

1 Like

Please study the tutorial

and other related posts of this forum to "dual boot" for valuable hints, and good luck!

1 Like

Forum kindly sponsored by