LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Installing Slackware Live on an NVME drive. (https://www.linuxquestions.org/questions/slackware-14/installing-slackware-live-on-an-nvme-drive-4175667167/)

JamesGT 01-05-2020 10:39 PM

Installing Slackware Live on an NVME drive.
 
I am trying to install Slackware Live PLASMA 5 onto an older system that I've installed an NVME drive with a PCI-E adapter. The system is older, but it's still UEFI. The machine will not boot from the NVME drive, but I think I can boot from a recognized drive, then have it switch to booting from the NVME drive.

When I boot up my machine on Slackware Live, it can see and find the NVME drive, but when I run setup2hd, it doesn't find the NVME option as a drive. When I try to run Slackware 14.2 DVD installer, it does the same. Is there a way around this?

If I just dd'ed with iso2usb.sh would that work?

Alien Bob 01-06-2020 01:45 AM

Quote:

Originally Posted by JamesGT (Post 6075063)
When I boot up my machine on Slackware Live, it can see and find the NVME drive, but when I run setup2hd, it doesn't find the NVME option as a drive.

Did you partition your NVMe drive before you ran 'setup2hd'? Just like Slackware, the setup will only list partitions with a suitable Partition Type (i.e. 'linux') to choose from.

JamesGT 01-06-2020 09:53 AM

Quote:

Originally Posted by Alien Bob (Post 6075089)
Did you partition your NVMe drive before you ran 'setup2hd'? Just like Slackware, the setup will only list partitions with a suitable Partition Type (i.e. 'linux') to choose from.

Yes. I have about 4 or 5 drives in the machine, some have existing installs of Slackware, some do no not. It picks up all the SATA drives, not the NVME, but the NVME is on a PCI-E card. It's not an m.2 SATA, but an m.2 PCI-E. Does that matter? The bios doesn't pick it up either, but it picks up all the other drives that that setup2hd does.

I am pretty sure if I picked an m.2 SATA drive this wouldn't be an issue.

James

Lysander666 01-06-2020 10:12 AM

I am monitoring this thread with interest. I installed -current on a Gigabyte M.2 (2280) PCIe 3.0 (x2) NVMe 1.3 SSD with no issue. However, I was not using Slackware live, I was using the -current non-live .iso.

I am also very interested to see how you go with getting your system set up with persistent naming if you have four or five internal drives. I struggled and failed to get -current installed on a machine with four internal drives. I'll be interested to see how you go about it. Needless to say, getting the OS installed is only going to be the first hurdle. Good luck.

ReFracture 01-06-2020 02:40 PM

Quote:

Originally Posted by JamesGT (Post 6075198)
The bios doesn't pick it up either, but it picks up all the other drives that that setup2hd does.

What utility did you partition the drive with? I'm surprised anything is seeing the drive at all if your bios is not showing it.

JamesGT 01-06-2020 08:35 PM

Quote:

Originally Posted by Lysander666 (Post 6075206)
I am monitoring this thread with interest. I installed -current on a Gigabyte M.2 (2280) PCIe 3.0 (x2) NVMe 1.3 SSD with no issue. However, I was not using Slackware live, I was using the -current non-live .iso.

I am also very interested to see how you go with getting your system set up with persistent naming if you have four or five internal drives. I struggled and failed to get -current installed on a machine with four internal drives. I'll be interested to see how you go about it. Needless to say, getting the OS installed is only going to be the first hurdle. Good luck.

My system is an older AMD FM1 system, the Llano APUs. The motherboards can't see NVME on an PCI-E card. Newer systems shouldn't be a problem. This thing is almost 10 years old.

JamesGT 01-06-2020 08:37 PM

Quote:

Originally Posted by ReFracture (Post 6075315)
What utility did you partition the drive with? I'm surprised anything is seeing the drive at all if your bios is not showing it.

fdisk sees it, cfdisk sees it.

I can even access it and drop any files I want to on it like a regular drive when I've booted into any O/S. Only when I try to install an O/S on it, it can't find it.

James

bassmadrigal 01-07-2020 03:13 PM

Can you provide the output of

Code:

fdisk -l

ReFracture 01-07-2020 05:08 PM

Quote:

Originally Posted by JamesGT (Post 6075471)
fdisk sees it, cfdisk sees it.

I can even access it and drop any files I want to on it like a regular drive when I've booted into any O/S. Only when I try to install an O/S on it, it can't find it.

James

Quote:

Originally Posted by JamesGT (Post 6075469)
My system is an older AMD FM1 system, the Llano APUs. The motherboards can't see NVME on an PCI-E card. Newer systems shouldn't be a problem. This thing is almost 10 years old.

You might have found the root of the problem.

My Asus motherboard from 2012 can accept an NVME SSD through PCI-E, but similar to your case the bios won't see it and the board won't boot to it.
My motherboard (and actually the 09-2012 Mac Pros) could only be made to boot to NVME PCI-E adapted SSDs by way of a firmware hack.

You could try looking for a hacked bios for your motherboard but unless you have a very popular board I wouldn't expect (or even necessarily recommend) it. There's one for my Asus board but I chose not to go down that rabbit hole.

If you have a small SATA SSD or something lying around you could probably put the boot loader on that and have it just point to the NVME drive, but that might defeat the purpose. For what it's worth you aren't likely to see any significant gains in terms of OS responsiveness by switching to NVME from SATA, OS I/O is mostly tons of little reads scattered around and benefit greatly just from SSD's not having seek time like hard drives do.

JamesGT 01-07-2020 10:57 PM

Quote:

Originally Posted by ReFracture (Post 6075819)
If you have a small SATA SSD or something lying around you could probably put the boot loader on that and have it just point to the NVME drive, but that might defeat the purpose. For what it's worth you aren't likely to see any significant gains in terms of OS responsiveness by switching to NVME from SATA, OS I/O is mostly tons of little reads scattered around and benefit greatly just from SSD's not having seek time like hard drives do.

That's ok. That's what I am thinking I need to do with the boot loader. It doesn't even need to be an SSD, just a thumb drive recovery, enter the boot drive...off I go. I think that's ok for me for what I want to do.

Yes, going with an SSD is probably the right way to go with this system, and maybe I will...but I want to give this a go first. When it becomes a hassle, I'll just get the SSD.

James

JamesGT 01-07-2020 11:04 PM

Quote:

Originally Posted by bassmadrigal (Post 6075785)
Can you provide the output of

Code:

fdisk -l

Code:

Disk /dev/nvme0n1: 238.49 GiB, 256060514304 bytes, 500118192 sectors
Disk model: PCIe SSD                               
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: 0x2aad4b72

Device        Boot  Start      End  Sectors  Size Id Type
/dev/nvme0n1p1        2048    206847    204800  100M ef EFI (FAT-12/16/32)
/dev/nvme0n1p2 *    206848 500118191 499911344 238.4G 83 Linux




Disk /dev/sdc: 698.65 GiB, 750156374016 bytes, 1465149168 sectors
Disk model: SEAGATE ST375064
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: 0x3cc20338

Device    Boot Start        End    Sectors  Size Id Type
/dev/sdc1        2048 1465149167 1465147120 698.7G 83 Linux


Disk /dev/sda: 2.75 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: Hitachi HUS72403
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: B2B288A3-3BB1-4B56-A179-9DD14EBFB539

Device    Start        End    Sectors  Size Type
/dev/sda1  2048 5860533134 5860531087  2.7T Linux filesystem


Disk /dev/sdb: 465.78 GiB, 500107862016 bytes, 976773168 sectors
Disk model: ST500LX025-1U717
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x41ae8dcf

Device    Boot    Start      End  Sectors  Size Id Type
/dev/sdb1            2048 943720447 943718400  450G 83 Linux
/dev/sdb2      943720448 976773167  33052720 15.8G 82 Linux swap


Disk /dev/loop0: 16.12 MiB, 16896000 bytes, 33000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 304.85 MiB, 319635456 bytes, 624288 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 186.25 MiB, 195293184 bytes, 381432 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 522.88 MiB, 548261888 bytes, 1070824 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop4: 45.65 MiB, 47853568 bytes, 93464 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop5: 7.9 MiB, 8257536 bytes, 16128 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop6: 128.58 MiB, 134807552 bytes, 263296 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop7: 417.8 MiB, 437338112 bytes, 854176 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sdd: 59.77 GiB, 64160400896 bytes, 125313283 sectors
Disk model: Flash Drive FIT
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: gpt
Disk identifier: F87BF5C9-7D07-4CB1-9429-425745E22614

Device      Start      End  Sectors  Size Type
/dev/sdd1    2048      4095      2048    1M BIOS boot
/dev/sdd2    4096    208895    204800  100M EFI System
/dev/sdd3  208896 125313249 125104354 59.7G Linux filesystem


Disk /dev/loop8: 133.27 MiB, 139735040 bytes, 272920 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop9: 134.23 MiB, 140746752 bytes, 274896 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop10: 6.34 MiB, 6643712 bytes, 12976 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop11: 176.9 MiB, 185466880 bytes, 362240 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop12: 277.8 MiB, 291270656 bytes, 568888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop13: 15.48 MiB, 16224256 bytes, 31688 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop14: 2.29 MiB, 2396160 bytes, 4680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop15: 561 MiB, 588251136 bytes, 1148928 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop16: 116.58 MiB, 122232832 bytes, 238736 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop17: 1.31 GiB, 1400807424 bytes, 2735952 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop18: 5.62 MiB, 5873664 bytes, 11472 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop19: 60 KiB, 61440 bytes, 120 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop20: 9.71 MiB, 10162176 bytes, 19848 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


JamesGT 01-07-2020 11:07 PM

Hmmm...this time running setup2hd works. It sees the drive. I wonder if it has something to do with rebooting.

?

James

JamesGT 01-07-2020 11:10 PM

I am going to mark this solved...when I run into my next issue, I'll post about that. :)

JamesGT 01-11-2020 04:44 PM

I guess there is no additional issues. Installed Slackware Live Plasma 5 on my PCI-E carded NVME drive with setup2hd, created a USB boot stick and when it boots up it goes straight to the OS. Perfect!

I did install 14.2 as a test to make sure I could do it first and when I tested the drive for speed as I wanted to see what kind of speeds I would be getting. I was getting about 1.0Gb/s write, 1.2Gb/s read. With Slackware Live Plasma 5 it looks like about 700Mb/s read and write.


All times are GMT -5. The time now is 09:06 PM.