You are not logged in.
I recently got an SSD. I was already using a LVM-On-LUKS setup on my HDD, so I created a LVM-On-LUKS on the new SSD to hold my swap and root partition.
Here is the output of lsblk:
sda 8:0 0 55.9G 0 disk
├─sda1 8:1 0 512M 0 part /boot
└─sda2 8:2 0 55.4G 0 part
└─serenityssd 254:0 0 55.4G 0 crypt
├─serenityssd-swap 254:1 0 8G 0 lvm [SWAP]
└─serenityssd-root 254:2 0 47.4G 0 lvm /
sdb 8:16 0 1.8T 0 disk
├─sdb1 8:17 0 500M 0 part
├─sdb2 8:18 0 1.6T 0 part
│ └─serenityhdd 254:3 0 1.6T 0 crypt
│ ├─serenityhdd-var 254:4 0 30G 0 lvm /var
│ ├─serenityhdd-home 254:5 0 1.5T 0 lvm /home
│ └─serenityhdd-swap 254:6 0 8G 0 lvmThe problem is that var now seems to be mounted too late.
systemctl status systemd-journald:
● systemd-journald.service - Journal Service
Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static; vendor preset: disabled)
Active: active (running) since Fri 2015-08-14 11:40:50 CEST; 33min ago
Docs: man:systemd-journald.service(8)
man:journald.conf(5)
Main PID: 327 (systemd-journal)
Status: "Processing requests..."
CGroup: /system.slice/systemd-journald.service
└─327 /usr/lib/systemd/systemd-journald
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.I have already thought about moving var on the SSD (not having it as a seperate partition anymore)
How bad would that be for an SSD. The wiki recommends moving the partition, but what happens if I don't do it?
Edit: I just went ahead and did it and everything is working much better now (even faster). So what ever that does to my SSD's life expectancy, I can live with that.
Last edited by th3voic3 (2015-08-15 06:57:13)
Offline