Page 13 of 13 FirstFirst ... 3111213
Results 121 to 124 of 124

Thread: Make new ssd the boot drive

  1. #121
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    2,422
    Blog Entries
    1

    Default Re: Make new ssd the boot drive

    Quote Originally Posted by Prexy View Post
    karlmistelberger, here is fdisk -l
    Code:
    fdisk -l
    Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
    Disk model: ST3500418AS      
    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: dos
    Disk identifier: 0xf010f010
    
    DeviceBoot    Start      End  Sectors  SizeIdType
    /dev/sda1  *         2048    206847    204800   100M  7 HPFS/NTFS/exFAT
    /dev/sda2          206848 564633026 564426179 269.1G  7 HPFS/NTFS/exFAT
    /dev/sda3       564633600 565776383   1142784   558M 27 Hidden NTFS WinRE
    /dev/sda4       565778432 976773119 410994688   196G  f W95 Ext'd (LBA)
    /dev/sda5       565780480 570001407   4220928     2G 82 Linux swap / Solaris
    /dev/sda6       570003456 653893631  83890176    40G 83 Linux
    /dev/sda7       653895680 976752639 322856960   154G 83 Linux
    
    
    Disk /dev/sdb: 111.79 GiB, 120034123776 bytes, 234441648 sectors
    Disk model: Samsung SSD 850  
    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: dos
    Disk identifier: 0x821faa25
    
    DeviceBoot    Start      End  Sectors SizeIdType
    /dev/sdb1  *         2048    206847    204800  100M  7 HPFS/NTFS/exFAT
    /dev/sdb2          206848 127377387 127170540 60.6G  7 HPFS/NTFS/exFAT
    /dev/sdb3       152518656 234441647  81922992 39.1G 83 Linux
    /dev/sdb4       127377408 152518655  25141248   12G 83 Linux
    
    Partition table entries are not in disk order.
    
    
    Your HDD is an old drive with SATA II interface. It's a bad bottleneck. Moving home from /dev/sdb4 to /dev/sda7 will slow down your machine again. To avoid this buy a larger SSD, which now come with a very reasonable price tag.

    Another option is to go with /home on /dev/sdb4 and mount /dev/sda7 somewhere /home/username/HDD. Thus heavily used files stay on the faster /dev/sdb4 and less often used files may still be accessed easily.

    If you indeed prefer to do the move, boot into Tumbleweed on /dev/sdb3 and login into a virtual console, e.g vt1. Change the mount point /home from /dev/sdb4 to /dev/sda7 in /etc/fstab and reboot.
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  2. #122
    Join Date
    Jun 2008
    Location
    USA
    Posts
    1,335

    Default Re: Make new ssd the boot drive

    I'm both inept and intimidated by the console. I had to reboot just to get out of VT2. Then I researched and found I could do the same by going to VT7. You've taught me something new! Next, I looked at fstab in kate, where it is editable. lsblk shows me that the UUID for /home on the hdd (sda7) is
    Code:
    c9554cbb-f155-4e5b-aef5-51987573e0b1
    
    The sdb3 /home has UUID
    Code:
    795d9510-a37b-422b-bfca-856cc4a68170
    
    Couldn't I just change this by editing in kate?

    Your suggestion to leave those as they are led me to add a "Places" to dolphin that I labeled "Old Home" that lets me easily access docs and downloads. Also, I looked at
    Code:
    System Settings > Applications > Locations
    that lets me modify where the system looks for docs, downloads etc. I can set that to the appropriate locations on the hdd (Old Home.) That seems like an acceptable solution. However, my motivation is conserving the limited space on the ssd. I use programs (k3b is an example) that did not come automatically in the install on the ssd. That was one reason I wanted to switch the /home mount: to run programs already on the hdd and add new programs there, too. Am I thinking clearly?
    Any sufficiently advanced technology is indistinguishable from magic. - Arthur C. Clarke

  3. #123
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    2,422
    Blog Entries
    1

    Default Re: Make new ssd the boot drive

    Quote Originally Posted by Prexy View Post
    I'm both inept and intimidated by the console. I had to reboot just to get out of VT2. Then I researched and found I could do the same by going to VT7. You've taught me something new! Next, I looked at fstab in kate, where it is editable. lsblk shows me that the UUID for /home on the hdd (sda7) is
    Code:
    c9554cbb-f155-4e5b-aef5-51987573e0b1
    
    The sdb3 /home has UUID
    Code:
    795d9510-a37b-422b-bfca-856cc4a68170
    
    Couldn't I just change this by editing in kate?
    Yes, you can edit that with kate. However with a graphical login to a normal user you can't test your changes. If you made a mistake it might happen you can no longer login on reboot. Thus it's safer to use the virtual console, make the changes with nano and test them before rebooting.

    Your suggestion to leave those as they are led me to add a "Places" to dolphin that I labeled "Old Home" that lets me easily access docs and downloads. Also, I looked at
    Code:
    System Settings > Applications > Locations
    that lets me modify where the system looks for docs, downloads etc. I can set that to the appropriate locations on the hdd (Old Home.) That seems like an acceptable solution. However, my motivation is conserving the limited space on the ssd. I use programs (k3b is an example) that did not come automatically in the install on the ssd. That was one reason I wanted to switch the /home mount: to run programs already on the hdd and add new programs there, too. Am I thinking clearly?
    With booting into Tumbleweed on /dev/sdb3 new programs will go to /dev/sdb3 and not to the smaller /dev/sdb4. For the time being there is ample space on /dev/sdb3.

    I suggest you watch usage of your disks carefully and take action if required only.
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  4. #124
    Join Date
    Jun 2008
    Location
    USA
    Posts
    1,335

    Default Re: Make new ssd the boot drive

    Quote Originally Posted by karlmistelberger View Post
    Yes, you can edit that with kate. However with a graphical login to a normal user you can't test your changes. If you made a mistake it might happen you can no longer login on reboot. Thus it's safer to use the virtual console, make the changes with nano and test them before rebooting.

    With booting into Tumbleweed on /dev/sdb3 new programs will go to /dev/sdb3 and not to the smaller /dev/sdb4. For the time being there is ample space on /dev/sdb3.

    I suggest you watch usage of your disks carefully and take action if required only.
    I'm going to do just that. I've made this over-complicated. The only changes I'll make is to put Documents on the hdd. I have plenty of room and that is the kind of stuff that will fill up a drive. If I download any data, I can manually move it over to the hdd as needed.

    Thanks again for your patience.
    Any sufficiently advanced technology is indistinguishable from magic. - Arthur C. Clarke

Page 13 of 13 FirstFirst ... 3111213

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •