Hi,
Thanks for all the help,
Yes I had seen that thread(mmm... I recognise that username
) 1 of hundreds of posts I have now looked at.
- The BIOS was the first thing I updated, even before installing any OS's, I read that there was a few issues with older versions of BIOS not recognising the nvme pcie disk.
- TTBOMK I have everything set for "Legacy", and per the BIOS picture the nvme pcie disk shows, and it boots Windows O.K
Here is the sudo blkid:
So if I understand correctly the grub.conf is pointing by UUID to the partition /dev/nvme0n1p3
The thread firenice03 and myself found seem to imply that pointing directly to the root boot device,
where the grub is /dev/nvme0n1 instead of the UUID for the LL partition is, may solve it..??
I guess given it's not working, do I have much to loose.?? ~ "NOT sure"
Change the root=UUID=89ddbfbb-26a0-4476-ba01-736c7aee234b to: root=/dev/nvme0n1 or should it be [color=rgb(255, 0, 0)]/dev/nvme0n1p3[/color]
From your previous post, I would open the grub.conf as root, edit the file.
Additionally I found there are 2 variants of this M2 ssd,This one, a pcie and also a plain ahci, but with reduced performance.(maybe for legacy scenarios.?)Maybe my friends is going to have to do return/rma and get a ahci version.??Not sure if he was aware of this,or even understood the difference, and also if it would make a difference.
??Thanks again.. much appreciated.
Thanks for all the help,
Yes I had seen that thread(mmm... I recognise that username
) 1 of hundreds of posts I have now looked at.- The BIOS was the first thing I updated, even before installing any OS's, I read that there was a few issues with older versions of BIOS not recognising the nvme pcie disk.
- TTBOMK I have everything set for "Legacy", and per the BIOS picture the nvme pcie disk shows, and it boots Windows O.K
Here is the sudo blkid:
Code:
it@it:~$ sudo blkid
/dev/loop0: TYPE="squashfs"
/dev/nvme0n1p1: LABEL="OpSys" UUID="8050EF0F50EF0B2C" TYPE="ntfs"
/dev/nvme0n1p2: LABEL="rootlm" UUID="5459ab50-69f9-4ecb-88ba-3bf56fe65a55" TYPE="ext4"
/dev/nvme0n1p3: UUID="89ddbfbb-26a0-4476-ba01-736c7aee234b" TYPE="ext4" # The LL install partition
/dev/nvme0n1p5: UUID="c9ee7c1a-581a-4103-9ba4-2984c9051cc1" TYPE="swap"
/dev/sda1: LABEL="Data" UUID="545937484610D8B1" TYPE="ntfs"
/dev/sda2: LABEL="homelm" UUID="a5a28014-affb-44db-93b1-293b34481633" TYPE="ext4"
/dev/sda3: LABEL="homell" UUID="9188d164-5929-4ae0-8413-d39e7de47e1f" TYPE="ext4"
/dev/sda5: UUID="1B3FF3B32DE36FDE" TYPE="ntfs"
/dev/sdb1: LABEL="MULTIBOOT" UUID="1293-FD4C" TYPE="vfat"
it@it:~$So if I understand correctly the grub.conf is pointing by UUID to the partition /dev/nvme0n1p3
The thread firenice03 and myself found seem to imply that pointing directly to the root boot device,
where the grub is /dev/nvme0n1 instead of the UUID for the LL partition is, may solve it..??
I guess given it's not working, do I have much to loose.?? ~ "NOT sure"
Change the root=UUID=89ddbfbb-26a0-4476-ba01-736c7aee234b to: root=/dev/nvme0n1 or should it be [color=rgb(255, 0, 0)]/dev/nvme0n1p3[/color]
From your previous post, I would open the grub.conf as root, edit the file.
Additionally I found there are 2 variants of this M2 ssd,This one, a pcie and also a plain ahci, but with reduced performance.(maybe for legacy scenarios.?)Maybe my friends is going to have to do return/rma and get a ahci version.??Not sure if he was aware of this,or even understood the difference, and also if it would make a difference.
??Thanks again.. much appreciated.
Upgrades WIP 2.6 to 2.8 - (6 X 2.6 to 2.8 completed on: 20/02/16 All O.K )
Linux Lite 3.0 Humming on a ASRock N3070 Mobo ~ btrfs RAID 10 Install on 4 Disks
Computers Early days:
ZX Spectrum(1982) , HP-150 MS-DOS(1983) , Amstrad CPC464(1984) , BBC Micro B+64(1985) , My First PC HP-Vectra(1987)
Linux Lite 3.0 Humming on a ASRock N3070 Mobo ~ btrfs RAID 10 Install on 4 Disks
Computers Early days:
ZX Spectrum(1982) , HP-150 MS-DOS(1983) , Amstrad CPC464(1984) , BBC Micro B+64(1985) , My First PC HP-Vectra(1987)