On Thu, 03 Nov 2016, John Andersen wrote:
Thinking of replacing my Drive with a SSD. Probably happen about the time Leap 42.2 comes out.
Any words of wisdom here? I'm thinking I'll do the same drill I normally do, Fresh install, then copy /home a and /data over into similar partition sizes that I have before.
What to look out for? Any problem with a couple xfs/Luks partitions on the SSD? Brands?
-- After all is said and done, more is said than done.
I'm running Leap 42.2 (RC1) with a SATA Samsung SSD 850 EVO 250GB (AMD Phenom II X6 1090T, 8GB, Nvidia GTX 650 Ti, Seagate ST2000DM001). I'm using ext4 for root (I briefly toyed with btrfs, but backing up it's sub-partition structure proved difficult to retrofit to my simple rsync based backup regime). Btrfs is supposed to better support SSD's (but I gather its not a big deal). I did a fresh install of 42.2 (RC1) and re-applied all my usual settings and packages. It all went smoothly. There seems to be some confusion on the web about Samsung and trim support. My dmesg output contains: [ 3.267504] ata1.00: disabling queued TRIM support [ 3.267511] ata1.00: ATA-9: Samsung SSD 850 EVO 250GB, EMT02B6Q, max UDMA/133 I think this is mainly for older drives, which mine is not. I've decided not to worry about it. I may look into using fstrim (man 8 fstrim) but I'm not sure whether this too might be an issue. The 42.2 kernel build seems to have correctly picked to use the deadline scheduler for the SSD (only): cat /sys/block/sda/queue/scheduler noop [deadline] cfq I decided to put noatime in mount entry in /etc/fstab to reduce writes (some say this is no longer really necessary). My previous OCZ SSD died after 5 years. I've read that SSD's can fail without warning. In my case, the OS just started errorring like crazy and crashed. There was no possibility of recovering anything as the failed drive was no longer recognised. So it would be a good idea to keep backups on other media. I backup the OS to both online and offline hard drives, so I lose a day to a week depending. My SSD failed just after installing Tumbleweed in a spare partition, so perhaps all the new activity pushed the writes over some limit. I still keep /home on a hard drive - being into photography makes SSD to expensive for user space. Cheers. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org