Page 1 of 13 12311 ... LastLast
Results 1 to 10 of 124

Thread: Make new ssd the boot drive

  1. #1
    Join Date
    Jun 2008
    Location
    USA
    Posts
    1,333

    Default Make new ssd the boot drive

    I finally gathered the hardware I needed to add an ssd to my desktop. My granddaughter broke her laptop and I took it to a big box computer store to salvage the ssd for my own use. I didn't have the right screwdriver to open the case and they wanted $40 to unscrew the 8 screws to get the back off. This is more than the price of 256GB ssd. So, I took it home and drilled out the screws. While at the store, I bought a PCIe adapter card with a heat sink.

    My neighbor gave me a Dell Inspiron 3668 with Windows 10. I have installed the salvaged ssd and Windows sees it as drive E: but prevents me from accessing any documents. This is ok, I intend to format the ssd. I have several goals:

    1: Install Tumbleweed on the ssd (wiping all current data)
    2: Make this a dual boot machine with the current Windows 10 installation
    3: Repartition the existing 1TB hard drive, which has over 800GB available, to make storage space available to Tumbleweed

    I have tried to do this previously and did not get an optimal setup. I work under the assumption that only the OS should be on the ssd. Documents and downloads should go on the slower, more spacious, hdd. Do programs/apps go on the ssd or hd? What is optimal?

    Miscellaneous details:
    While investigating the ssd in Windows, I saw the word UEFI. This makes a difference in booting and install, correct?
    This "new" ssd is a Samsung MZVLV512 NVMe with 512GB capacity installed in a PCIe slot meant for a video card.
    I have a Tumbleweed install DVD that I downloaded about a week ago.
    I am posting this from the new machine. So, the Windows install booted and works as normal.
    If any further info is needed, I will be happy to supply it.

    I realize that some of the answers are exact and others are opinions. I welcome all input.
    Any sufficiently advanced technology is indistinguishable from magic. - Arthur C. Clarke

  2. #2
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    30,865
    Blog Entries
    15

    Default Re: Make new ssd the boot drive

    Quote Originally Posted by Prexy View Post
    I finally gathered the hardware I needed to add an ssd to my desktop. My granddaughter broke her laptop and I took it to a big box computer store to salvage the ssd for my own use. I didn't have the right screwdriver to open the case and they wanted $40 to unscrew the 8 screws to get the back off. This is more than the price of 256GB ssd. So, I took it home and drilled out the screws. While at the store, I bought a PCIe adapter card with a heat sink.

    My neighbor gave me a Dell Inspiron 3668 with Windows 10. I have installed the salvaged ssd and Windows sees it as drive E: but prevents me from accessing any documents. This is ok, I intend to format the ssd. I have several goals:

    1: Install Tumbleweed on the ssd (wiping all current data)
    2: Make this a dual boot machine with the current Windows 10 installation
    3: Repartition the existing 1TB hard drive, which has over 800GB available, to make storage space available to Tumbleweed

    I have tried to do this previously and did not get an optimal setup. I work under the assumption that only the OS should be on the ssd. Documents and downloads should go on the slower, more spacious, hdd. Do programs/apps go on the ssd or hd? What is optimal?

    Miscellaneous details:
    While investigating the ssd in Windows, I saw the word UEFI. This makes a difference in booting and install, correct?
    This "new" ssd is a Samsung MZVLV512 NVMe with 512GB capacity installed in a PCIe slot meant for a video card.
    I have a Tumbleweed install DVD that I downloaded about a week ago.
    I am posting this from the new machine. So, the Windows install booted and works as normal.
    If any further info is needed, I will be happy to supply it.

    I realize that some of the answers are exact and others are opinions. I welcome all input.
    Hi
    Boot from a Tumbleweed Rescue USB to pre-configure the drive if no data on it is needed. If you need data off it, then should be able to mount the windows partition to recover data. When in rescue mode, show the output of;

    Code:
    lsblk
    efibootmgr
    Word of caution with the nvme device, see this thread (although btrfs centric, is actually hardware related).: https://forums.opensuse.org/showthre...very-few-hours

    Use the whole device for everything... OS (~40GB) and a separate partition for $HOME.

    I would do a fresh 20H2 WinX install...
    Last edited by malcolmlewis; 11-Feb-2021 at 16:00.
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  3. #3
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    2,745
    Blog Entries
    1

    Default Re: Make new ssd the boot drive

    https://www.cnet.com/products/dell-i...hz-12-gb-1-tb/ says the 3668 features an M.2 slot. M.2s usually support NVME devices directly, so you could probably put that NVME in it to free that PCIe slot back up, if the 3668 is the same PC you are "building". If it isn't, it would be a good idea to show us output from inxi -b along with efibootmgr and lsblk.

    UEFI is a massive improvement over legacy booting. Once understood, it's much easier to manage and avoid any multiboot issues. Do understand that most Windows installations come with an ESP partition of 100M, while the openSUSE installer has traditionally complained when attempting to share an ESP that size. You can safely ignore that warning should you encounter it in choosing to use it for openSUSE. While the openSUSE installer may suggest much larger is necessary, it absolutely is not, unless you are using a HDD larger than 16T for the ESP, or plan to put a lot of files on it that a normal installation would never put there.

    What to put on NVME and what on HDD is somewhat like choosing between Toyota and Nissan, or Coke and Pepsi. There's not really a right answer to what to put where, beyond having the OS and software on the faster device. If your NVME is amply sized for your needs, I suggest to use the HDD only for extra copies of important personal data, or large files like videos or a photo or music collection, where loading speed is usually of little concern, while maximum safety is a priority.

    I've had 3 SSDs go bad out of around 17 total acquired in less than two years. I don't keep any videos on any SSD, other than a few extra copies, mostly for testing. On my 24/7 box, most of my user data is on a HDD RAID with EXT4, while my OSes are on a GPT partitioned 128GB SSD that's a home to 5 openSUSE releases, each on EXT4.

    On my 4 PCs using UEFI, all have a single 320M ESP partition on SSD. I always do all partitioning prior to beginning any OS installation, "pre-configuring", as malcolmlewis suggests. That means I rarely find need to re-partition in order to free up space for something new. I plan ahead for lots of something news. Except for two PCs with both HDD RAID and SSD, all booting here is done from an SSD, if the PC has an SSD.

    On the few PCs I have sharing space with Windows, all OSes are on a single HDD, with each Windows installation begun only after the HD was well tested and running using at least one openSUSE installation. There's no need to install Windows first. After all, Windows traditionally needs frequent re-installation, something that cannot be done after Linux has been added, unless re-installing it too.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 15.1, TW, 15.2 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2)&15.1 on i965P/Radeon
    Tertiary: TW,15.2,15.1,Fedora,Debian,more on Kaby Lake,iQ45,iQ43,iG41,iG3X,i965G,AMD,NVidia&&&

  4. #4
    Join Date
    Sep 2012
    Posts
    6,311

    Default Re: Make new ssd the boot drive

    Quote Originally Posted by mrmazda View Post
    M.2s usually support NVME devices directly
    M.2 defines mechanical characteristics and possible interfaces. It is entirely up to manufacturer what interfaces are actually provided and even if interface is provided it does not mean BIOS allows it to be used for your purposes.

  5. #5
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    2,745
    Blog Entries
    1

    Default Re: Make new ssd the boot drive

    Quote Originally Posted by arvidjaar View Post
    M.2 defines mechanical characteristics and possible interfaces. It is entirely up to manufacturer what interfaces are actually provided and even if interface is provided it does not mean BIOS allows it to be used for your purposes.
    If indeed OP's target is a 3668, it's probably a Kaby Lake, less likely a Skylake, and very unlikely to not support booting from NVME in in a motherboard M.2 socket.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 15.1, TW, 15.2 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2)&15.1 on i965P/Radeon
    Tertiary: TW,15.2,15.1,Fedora,Debian,more on Kaby Lake,iQ45,iQ43,iG41,iG3X,i965G,AMD,NVidia&&&

  6. #6
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    30,865
    Blog Entries
    15

    Default Re: Make new ssd the boot drive

    Hi
    @mrmazda, OP indicated they fitted the NVME device and it booted to windows, so system to me indicated NVME support?

    My system doesn't.... I have a PCIe card with NVME and SSD support (cable to SATA socket on M/B) that's why interested in lsblk...
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  7. #7
    Join Date
    Jun 2008
    Location
    USA
    Posts
    1,333

    Default Re: Make new ssd the boot drive

    I took pictures of the motherboard to show a tech and after reading these posts, looked at them to confirm. There is indeed a spot labeled M.2 but it is M.2_WIFI. I have seen posts that say the M.2 slots are sometimes hidden under other things like fans etc. Even if I didn't want to keep the wifi, or wanted to hunt under other things on the motherboard, there is no possible hiding place that isn't blocked by surrounding items that would keep the ssd from fitting. So, the PCIe adapter card is my best option.

    I ran the Tumbleweed Rescue from DVD, not usb. I ran the commands recommended by malcolmlewis. I had no way to do a screen copy, so I'll do my best to type what resulted. Remember, the ssd has a full, working, Windows system on it.
    Code:
    for lsblk:
    sda 917.1G
       sda1   500M
       sda2   128M
       sda3   917.1G
       sda4   860M
       sda5   11.9G
       sda6   1.1G
    nvme0n1   476.9G
        nvme0n1p1   260M
        nvme0n1p2   16M
        nvme0n1p3   475.7G
        nvme0n1p4   1000M
    I obviously made a copy error on sda vs. sda3, but I don't think it matters too much. For the other command:
    Code:
    efibootmgr
    BootCurrent: 0001
    Timeout: 0 seconds
    BootOrder: 0000,0001
    Boot0000* Windows boot mgr
    Boot0001* UEFI: PLDS DVD+/- RW DU -8A5LH
    I want to shrink sda3 to make room for some use by Tumbleweed. I don't know where this happens in the install process. I also don't know what file type to pick for either the new sda partition (FAT? etc) or the nvme (BTRFS? EXT3? EXT4?) Am I right that Tumbleweed can read NTFS? So, I could leave the sda alone and just put data on it? I don't like that idea.

    Anyway, what do I do next?
    Any sufficiently advanced technology is indistinguishable from magic. - Arthur C. Clarke

  8. #8
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    2,745
    Blog Entries
    1

    Default Re: Make new ssd the boot drive

    Quote Originally Posted by Prexy View Post
    I had no way to do a screen copy, so I'll do my best to type what resulted.
    Any time you are using a text only screen, you can capture the desired portion of screen output by running the command again and redirecting that command's output to a file. That file can be copied to a USB stick, floppy disk, or a filesystem on an external HDD or SSD, from which you can use another PC to copy and paste here, or upload to http://susepaste.org/ or other location. Redirection is a standard shell process, e.g.:
    Code:
    sudo parted -l > anyoldfilename.txt
    I'd rather see output from parted -l than lsblk in this case.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 15.1, TW, 15.2 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2)&15.1 on i965P/Radeon
    Tertiary: TW,15.2,15.1,Fedora,Debian,more on Kaby Lake,iQ45,iQ43,iG41,iG3X,i965G,AMD,NVidia&&&

  9. #9
    Join Date
    Jun 2008
    Location
    USA
    Posts
    1,333

    Default Re: Make new ssd the boot drive

    I took a shortcut and made a photo of the parted output. I see the mistake in the size of sda. It was 931.5G not 917.1G, which is the size of sda3. Pardon my ignorance, but can /dev/nvme0n1 ever be a boot device? I am familiar with only sda, sdb etc.

    Here is the picture of parted output:

    https://susepaste.org/13550031


    Any sufficiently advanced technology is indistinguishable from magic. - Arthur C. Clarke

  10. #10
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    30,865
    Blog Entries
    15

    Default Re: Make new ssd the boot drive

    Hi
    I suspect windows may have booted from sda, not the nvme device....

    What does the following show;

    Code:
    uuid
    efibootmgr -v
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

Page 1 of 13 12311 ... LastLast

Posting Permissions

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