Can I add an ssd and boot from it?? <SOLVED> [Solved]

[GlockdocVegas]

I have enough knowledge to get me in trouble!!

I have a smaller than I would like hard drive and would like to add a 2nd drive ( Samsung 870 EVO SSD ) to my machine then set that drive up as my boot drive. Before I order the drive I thought I would ask. I have dug around and it seems I can add a 2nd drive to my laptop and and 2.5" sata 3 ssd will work. The directions to install seem pretty straight forward.

Are there any issues I should expect with MX?

Thanks in advance!

Code: Select all

System:    Host: <filter> Kernel: 4.19.0-13-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-13-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: KDE Plasma 5.14.5 tk: Qt 5.11.3 wm: kwin_x11 dm: LightDM 1.26.0 
           Distro: MX-19.4_x64 patito feo October 21  2019 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: Hewlett-Packard product: HP ProBook 6550b v: N/A 
           serial: <filter> Chassis: type: 10 serial: <filter> 
           Mobo: Hewlett-Packard model: 146D v: KBC Version 73.11 serial: <filter> 
           BIOS: Hewlett-Packard v: 68CDE Ver. F.01 date: 06/25/2010 
Battery:   ID-1: BAT0 charge: 41.9 Wh condition: 44.4/56.6 Wh (78%) volts: 12.3/11.1 
           model: Hewlett-Packard Primary type: Li-ion serial: <filter> status: Unknown 
           Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M325 serial: <filter> 
           charge: 55% (should be ignored) rechargeable: yes status: Discharging 
CPU:       Topology: Dual Core model: Intel Core i7 M 620 bits: 64 type: MT MCP arch: Nehalem 
           family: 6 model-id: 25 (37) stepping: 5 microcode: 7 L2 cache: 4096 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21277 
           Speed: 1352 MHz min/max: 1199/2667 MHz boost: enabled Core speeds (MHz): 1: 1407 
           2: 1398 3: 1334 4: 1452 
           Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable 
           Type: l1tf mitigation: PTE Inversion 
           Type: mds 
           status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Core Processor Integrated Graphics vendor: Hewlett-Packard 
           driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0046 
           Display: x11 server: X.Org 1.20.4 driver: intel compositor: kwin_x11 
           resolution: 1024x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel Ironlake Mobile v: 2.1 Mesa 18.3.6 
           direct render: Yes 
Audio:     Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Hewlett-Packard 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:3b56 
           Sound Server: ALSA v: k4.19.0-13-amd64 
Network:   Device-1: Intel 82577LC Gigabit Network vendor: Hewlett-Packard driver: e1000e 
           v: 3.2.6-k port: 4020 bus ID: 00:19.0 chip ID: 8086:10eb 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel Centrino Advanced-N 6200 driver: iwlwifi v: kernel port: 4000 
           bus ID: 44:00.0 chip ID: 8086:4239 
           IF: wlan0 state: up mac: <filter> 
           IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A 
Drives:    Local Storage: total: 149.05 GiB used: 94.40 GiB (63.3%) 
           ID-1: /dev/sda vendor: Western Digital model: WD1600BEKT-60V5T1 size: 149.05 GiB 
           block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm 
           serial: <filter> rev: 1A12 scheme: MBR 
Partition: ID-1: / raw size: 117.69 GiB size: 114.84 GiB (97.58%) used: 94.35 GiB (82.2%) 
           fs: ext4 dev: /dev/sda1 
           ID-2: swap-1 size: 2.00 GiB used: 56.0 MiB (2.7%) fs: swap 
           swappiness: 15 (default 60) cache pressure: 100 (default) dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 56.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://mirror.kku.ac.th/mx-packages/mx/repo/ buster main non-free
           Active apt repos in: /etc/apt/sources.list.d/opera-stable.list 
           1: deb https://deb.opera.com/opera-stable/ stable non-free
           Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 
           1: deb [arch=amd64] https://repo.skype.com/deb stable main
           Active apt repos in: /etc/apt/sources.list.d/teams.list 
           1: deb [arch=amd64] https://packages.microsoft.com/repos/ms-teams stable main
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 251 Uptime: 6d 2h 54m Memory: 7.59 GiB used: 4.33 GiB (57.1%) 
           Init: SysVinit v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 
           Shell: quick-system-in running in: quick-system-in inxi: 3.0.36 

[radonrose]

IMHO, the worst thing that can happen is having to add your SSD where your HDD is now, and the HDD in the now empty slot.

If the storage allows it, you can clone the root and home partitions as they are. If not, you can always use the MX Live USB Maker.

[agnivo007]

Well, I bought the same sammy 870 evo and using it. You seem to have extra hdd bay which should suffice the upgrade.

You have a BIOS update: Release date:Nov 30, 2015 File name:sp73917.exe
https://support.hp.com/us-en/drivers/se ... pc/4173845

[GlockdocVegas]

@agnivo007 by chance do you have a link for linux instructions? Just a quick search it seems I have to boot up into windoes, make a live usb, then boot into bios. Thanks!

@radonrose I thought that might be the way to go. Make a live usb, flash the os to the new ssd and set it to boot 1st. Might be a simpler way, but my pay grade might not be high enough! LOL

[rob.chaffe]

https://clonezilla.org/

Rob

[Huckleberry Finn]

You can copy all partitions one by one on live session without extra things. (And finally install grub on the new drive using "MX Boot Repair" on live-session.)

• On live-session GParted: (Just like copying a directory from here to there) : Right-click on partition: "copy" , then change device from upper-right, right-click on "unallocated space": "paste". That's it. (even the uuids will stay the same)

• Or, again on live session just use the terminal: gzip .. then (whenever you like) gunzip:
  
  viewtopic.php?p=524785#p524785
  
  viewtopic.php?p=526112#p526112

• Not to mention "dd".

• And as you already mentioned: "MX Snapshot". Maybe the simplest of all. Nothing to know special, just install it as you install the official MX.
  
  Just, in case you can't see an icon to Install - that happens mostly on personal snapshots - : open a terminal:

  Code: Select all

  mx-pkexec minstall

[agnivo007]

I'm on phone now, will check and try to post alternative bios flashing instructions later.

[agnivo007]

@GlockdocVegas Officially, the HP exe supports STANDALONE UPDATING and also making a bootable USB bios updater drive which requires Windows to function. What I understand is that you do not have installed/access to a windows machine or VM. Am I right?

So, if you have windows installed on the same machine just run the HP exe file and choose update bios. If not, from a different windows machine, get a usb key made by the exe and boot with it on this system.

If you don't have access to windows:
Can you please confirm if your BIOS setup menu (F10) has any options to update firmware from file/usb key? I ask because a lot of old HP BIOSs may not have this feature (yours is from 2010) while modern ones can just auto-update over a LAN port! Just go into every menu and check for "firmware update" , "flash system rom" and post results.

[GlockdocVegas]

So yes, I can add the ssd and, once I fix the next issue, should be able to boot just fine.

After adding the drive I got the option at to boot from either drive from BIOS. MX, however, did not see the drive. Played around with it and realized I needed to format it. Used USB format, show all drives, and now mx sees it. Not sure that was my best option, but it was the one I could find. Not sure if MX thinks it is a usb or if that even matters. Would hate to kill the ssd speed advantage because I formatted it wrong.

Next problem is mxlive usb maker does not give me ANY way to pull my iso file off the 2nd drive. It's 60g which is more space than I have on my main drive. The only 60g usb I have handy is the one I am going to use for the live usb.....but then this is a different topic and I will make a different post.

Thank you to all of your that helped out.

***UPDATE****** Switched from KDE desktopto XFCE desktop and was able to pull my iso off the 2nd drive. Solved that issue before I could post to help.

[agnivo007]

You need to partition the new disk properly, not just a USB format you did (forcing the utility on a hdd). Better follow the partition copy paste method as given in the earlier post. I'm sorry to say, you kindly messed up the thing without asking anyone. Creating a fresh partition table and asking for steps would have helped, not rushing into it. I wonder if you have successfully moved the install...

I didn't hear from you regarding BIOS, guess you don't want to do it right now?