Siduction Forum
Siduction Forum => Installation - Support => Topic started by: sotnik on 2018/10/14, 13:20:13
-
Hello
I plan to build a new PC with two disks. A WD HDD and the Samsung 970 Evo NVMe M.2 500GB https://www.samsung.com/us/computing/memory-storage/solid-state-drives/ssd-970-evo-nvme-m2-500gb-mz-v7e500bw/ (https://www.samsung.com/us/computing/memory-storage/solid-state-drives/ssd-970-evo-nvme-m2-500gb-mz-v7e500bw/). The mobo will be ASUS PRIME X470-PRO https://www.asus.com/gr/Motherboards/PRIME-X470-PRO/ (https://www.asus.com/gr/Motherboards/PRIME-X470-PRO/)
The pc will be dual booted with windows.
What is the best options to install without problems?
Also I am looking for a how-to of ramdisk setup.
Thank you
sotnik
-
I recently built a new desktop on a Samsumg EVO 860 and a pair of WD-1000 hdds. This will give you the idea:
Drives:
Local Storage: total: 2.27 TiB used: 908.92 GiB (39.0%)
ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB
ID-2: /dev/sdb vendor: Western Digital model: WD1003FZEX-00K3CA0 size: 931.51 GiB
ID-3: /dev/sdc vendor: Western Digital model: WD1003FZEX-00K3CA0 size: 931.51 GiB
Partition:
ID-1: / size: 58.81 GiB used: 8.98 GiB (15.3%) fs: ext4 dev: /dev/sda2
ID-2: /home size: 393.18 GiB used: 51.23 GiB (13.0%) fs: ext4 dev: /dev/sda4
ID-3: swap-1 size: 5.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3
root@dibl-patience:/# fdisk -lu
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 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
Disklabel type: gpt
Disk identifier: 7FAFE064-EE29-4865-8CA1-CF1F42852DCA
Device Start End Sectors Size Type
/dev/sda1 2048 616447 614400 300M EFI System
/dev/sda2 616448 126445567 125829120 60G Linux filesystem
/dev/sda3 126445568 136931327 10485760 5G Linux swap
/dev/sda4 136931328 976768031 839836704 400.5G Linux filesystem
Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
root@dibl-patience:/# blkid -c /dev/null -o list
device fs_type label mount point UUID
---------------------------------------------------------------------------------------
/dev/sda1 vfat /boot/efi 6530-F244
/dev/sda2 ext4 / 8195ff52-31c2-4e0b-9ab6-6acef8c52c18
/dev/sda3 swap [SWAP] 39ef397b-9d25-404a-8f7e-eec2ddc61645
/dev/sda4 ext4 /home ddc1f6e1-5e90-459b-917e-d925d19b267e
/dev/sdb btrfs (in use) dc117543-b8de-4d32-a300-8e7925beb5f5
/dev/sdc btrfs (in use) dc117543-b8de-4d32-a300-8e7925beb5f5
I don't dual boot. I run Windows 10 on a qemu/kvm VM, under siduction Linux.
-
Thank you dibl.
I plan to install cuda in windows, mainly because it is difficult to set up it in linux (siducation).
On the other hand, I am not sure whether cuda setup in a VM environment is appropriate. Therefore, I believe I will have better luck using a dual boot setting.
About the second question regarding the M.2. I heard it's better to avoid frequent read/writes in SSD. That's why I am looking for a ramdisk how-to.
sotnik
-
Modern SSDs are far less susceptible to "wear" than the early ones. I like to mount ext4 partitions with a "commit=120" or even 180 option, which gives a 20X-30X slowdown on journal writing. Also, once your system is stable and you feel confident you can safely lose logs after shutdown, you can mount some of the /var/log files as tmpfs, which puts them in memory.
UUID=4ff5a5d1-6421-4051-b620-80f61e848d79 / ext4 defaults,noatime,commit=180 0 1
UUID=610eb1c9-be26-4bf8-a11e-6886dd2c6200 swap swap defaults,noatime 0 0
UUID=fa814d78-08c3-49c8-a749-d1164c23debd /mnt/DATA ext4 defaults,noatime,commit=180 0 2
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
tmpfs /var/log tmpfs defaults,noatime 0 0
Also, firefox and chromium can both be set to use a particular directory for caching. For browser or other user caches, there is a temporary user folder created at boot time at /run/user/nnnn, where "nnnn" is the user ID number, for example 1000 for the first user. You can make a directory there and set your browser to use that for the cache directory, according to the browser's settings for cache location. This cache will also disappear at shutdown, For example, in firefox, about:config, you set "browser.cache.parent_directory modified string /run/user/1000/firefox-cache"