Linux Lite Forums
Hardware - Support => Hard Drives and SSDs => Topic started by: Wirezfree on November 21, 2015, 02:36:09 PM
-
Hi,
I started new thread instead of using the other thread (https://www.linuxliteos.com/forums/installing-linux-lite/nothing-boots!!!/msg19012/#msg19012).
I think this is possibly disk related..??
I booted a live gparted, and prepared partitions in advance. (see below)
"IMPORTANT" the NUC contains a "Samsung nvme pcie ssd"
So gparted detected drive O.K, and allowed me to create partitions.
Linux kernel gives an odd, but normal: /dev/nvme0n1p1
I decide to install LL2.6 1st and make sure everything works.
I ran LL2.6 Live boot USB, installed it, and it all ran O.K, no errors.
On re-boot I get the "grub screen"
(http://i.imgur.com/J4ZR8pT.jpg)
I checked Win7 still booted O.K, and it booted fine.
Then I re-booted and selected "Linux Lite",
momentary disk access, then the following: (sorry only have camera phone)
(http://i.imgur.com/SqFUzpz.jpg)
More Info when I re-booted a LL Live USB:
it@it:~$ sudo os-prober
/dev/nvme0n1p1:Windows 7 (loader):Windows:chain
/dev/nvme0n1p3:Linux Lite 2.6 (14.04):Ubuntu:linux
it@it:~$ sudo parted -l
Model: Generic Flash Disk (scsi)
Disk /dev/sda: 8087MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 8087MB 8086MB primary fat32 boot
Model: ATA ST1000LM014-1EJ1 (scsi)
Disk /dev/sdb: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 53.7GB 53.7GB primary ntfs
2 53.7GB 75.2GB 21.5GB primary ext4
3 75.2GB 96.6GB 21.5GB primary ext4
4 96.6GB 999GB 902GB extended
5 96.6GB 977GB 880GB logical ntfs
Model: Unknown (unknown)
Disk /dev/nvme0n1: 128GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 53.7GB 53.7GB primary ntfs boot
2 53.7GB 75.2GB 21.5GB primary ext4
3 75.2GB 96.6GB 21.5GB primary ext4
4 96.6GB 127GB 30.1GB extended
5 96.6GB 115GB 18.3GB logical linux-swap(v1)
Couple of observations/notes:
1. The NUC Bios is set to Legacy & Safeboot "disabled", and the nvme pcie drive is recognised in BIOS
2. For the Win7 install I needed to install it initially to 2nd drive, add 2 NS hofixes, then "clone" to nvme drive.
This is because Win7 does not recognise nvme pcie drives.
3. I think the disk order is due to the nvme pcie card being plugged direct on Mobo, and 2nd disk is on SATA port
4. The nvme pcie disk "Model Unknown."..?? and it's sector size 512B/512B vs other disk is 512B/4096B ??
Googling shows nvme pcie drives appear to be problematic in terms of setting up for Linux Boot
I got confused, when discussions centred around UEFI & GPT started to be discussed, no mention of "Legacy scenario"..!!
So more research needed, but any comments welcome :)
-
where did you install grub to ?
have you tried installing grub to both of the disks and get the same result ?
-
Hi,
On the installer you only get to choose 1, I did it to /dev/nvme0n1
This I assumed worked, it gives me the grub screen to select from,
Given it wont boot, not sure how to install it also to /dev/nvme0n1p3 (this is the partition where LL is installed)
/dev/nvme0n1p1 is where Win7 is already installed.
/dev/nvme0n1p2 is where I planned Linux Mint to go.
-
Further update:
I noticed something just before the above error appears, it appears very quick, so I re-booted s few times..
It says: "error attempting to Read/Write outside of disk" "HD0"
Verified in BIOS that the nvme is showing:
(http://i.imgur.com/dWnmRu0.png)
-
I'm sure you've searched... but I came across a couple links...
http://askubuntu.com/questions/397485/what-to-do-when-i-get-an-attempt-to-read-or-write-outside-of-disk-hd0-error (http://askubuntu.com/questions/397485/what-to-do-when-i-get-an-attempt-to-read-or-write-outside-of-disk-hd0-error)
And
http://www.linuxquestions.org/questions/linux-laptop-and-netbook-25/boot-problem-after-installing-ubuntu-11-04-kernel-panic-not-syncing-vfs-919143/ (http://www.linuxquestions.org/questions/linux-laptop-and-netbook-25/boot-problem-after-installing-ubuntu-11-04-kernel-panic-not-syncing-vfs-919143/)
Maybe worth a look... Good Luck!!
-
@firenice03,
Thanks,
Yes I have those on a growing list with a few more, now this is where lack of knowledge shows.
All the things I have found, like 1 of those you linked to must be being done from a "Live Boot"
But how do I correctly mount and edit where these files reside..??
When I "Live Boot" I think all the various partitions show on the desktop,
Do I just double click, navigate to files and Edit, is it that simple.??
I think 1 you also listed, 1st Link,
Maybe be if you select the "Advanced > Recovery" option at boot... I will try that 1st
It's late, I'm tired, don't want make a mistake, will try later... after some shut-eye...
-
I am not familiar with your hardware, i wish i could help more.
I noticed you AHCI enabled, have you tried disabling it (IDE)then booting to LL or install LL in IDE mode ?
Just don't boot back into windows after. If you are successful booting to LL or installing, reboot then sudo update-grub. Lastly reboot again and change it back to AHCI and make sure you can boot to windows and LL.
Sorry thats all I can think of.
-
Not familiar with those types of drives so don't think I'll be much help here.
Try technomancer's suggestion of disabling AHCI to see if that solves issue.
Regarding how to edit files from a "live" LL disk, just mount the partition that you need to access files on to the "/mnt" directory. Then you can use file manager to browse the file system there and pick whatever file needs to be edited (probably as Root if it's a system file). Example:
Mount partition with this command:
sudo mount /dev/nvme0nlp3 /mnt
If you needed to edit the fstab file on that partition, (as a random example), command would be:
gksu leafpad /mnt/etc/fstab
Or you could just use gui file manager, right-click and open the /mnt/etc folder as root, right-click the fstab file and open with leafpad to edit it.
-
@firenice03
Thanks, The AHCI setting is only for the SATA port for a 2nd drive, it does not affect the mini pcie port where the mvne M2 disk plugs in.
@gold_finger
Many Thanks, I will note this, Now I need to figure out what, if anything needs editing to fix this..??, I'm just gathering some more info.
-
So, some more info, and some odd confusing results, sorry this is a bit long..
If I do an fdisk -l, the nvme does not show up..??
it@it:~$ sudo fdisk -l
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x77b04277
Device Boot Start End Blocks Id System
/dev/sda1 2048 104859647 52428800 7 HPFS/NTFS/exFAT
/dev/sda2 104859648 146802687 20971520 83 Linux
/dev/sda3 146802688 188745727 20971520 83 Linux
/dev/sda4 188745728 1951426559 881340416 5 Extended
/dev/sda5 188747776 1908412415 859832320 7 HPFS/NTFS/exFAT
Disk /dev/sdb: 8086 MB, 8086618112 bytes
37 heads, 13 sectors/track, 32836 cylinders, total 15794176 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 identifier: 0x000a0fdf
Device Boot Start End Blocks Id System
/dev/sdb1 * 2048 15794175 7896064 b W95 FAT32
But if I do a lsblk , it shows the exact structure inc the nvme drive that I did with "Live gparted" before install.
I assume the /media/it/ is because I'm doing this from a "Live Boot" , I have added some # notes on what is what
it@it:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 50G 0 part /media/it/Data # This is D:\ drive for Win7 , Data
├─sda2 8:2 0 20G 0 part # This was a place-holder for Mint /home
├─sda3 8:3 0 20G 0 part # This is LL /home
├─sda4 8:4 0 1K 0 part # extended
└─sda5 8:5 0 820G 0 part /media/it/1B3FF3B32DE36FDE # This is going to be a large shared ntfs partition
sdb 8:16 1 7.5G 0 disk
└─sdb1 8:17 1 7.5G 0 part /cdrom
loop0 7:0 0 747.6M 1 loop /rofs
nvme0n1 259:0 0 119.2G 0 disk
├─nvme0n1p1 259:1 0 50G 0 part /media/it/OpSys # This is Win7 C:\ OpSys
├─nvme0n1p2 259:2 0 20G 0 part /media/it/rootlm # This was a place-holder for Mint /
├─nvme0n1p3 259:3 0 20G 0 part /media/it/89ddbfbb-26a0-4476-ba01-736c7aee # This is where LL / is
├─nvme0n1p4 259:4 0 1K 0 part # extended
└─nvme0n1p5 259:5 0 17G 0 part # spare free space
Now if I check within a Live Boot, "Disks" shows the nvme drive, but in "other devices", not in Disk Drives.??
but with "gparted in the Live Boot" the nvme drive is "not" shown on the drop-down list of devices, it is shown in a "gparted live" , that's how I did the partitions..??
(http://i.imgur.com/Gh7KNWz.png)
Finally,
This is(I believe) the "grub.conf" referred to in other posts that that firenice03 and I found
Where the device was not correct in the "vmlinuz" line..?? , should this be referencing "/dev/nvme0n1"
There are 3 references to: UUID=89ddbfbb-26a0-4476-ba01-736c7aee234b
menuentry 'Description: Linux Lite 2.6 GNU/Linux' --class description_ --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-89ddbfbb-26a0-4476-ba01-736c7aee234b' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root 89ddbfbb-26a0-4476-ba01-736c7aee234b
else
search --no-floppy --fs-uuid --set=root 89ddbfbb-26a0-4476-ba01-736c7aee234b
fi
linux /boot/vmlinuz-3.13.0-62-generic root=UUID=89ddbfbb-26a0-4476-ba01-736c7aee234b ro quiet splash $vt_handoff
initrd /boot/initrd.img-3.13.0-62-generic
}
submenu 'Advanced options for Description: Linux Lite 2.6 GNU/Linux' $menuentry_id_option 'gnulinux-advanced-89ddbfbb-26a0-4476-ba01-736c7aee234b' {
menuentry 'Description: Linux Lite 2.6 GNU/Linux, with Linux 3.13.0-62-generic' --class description_ --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.13.0-62-generic-advanced-89ddbfbb-26a0-4476-ba01-736c7aee234b' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root 89ddbfbb-26a0-4476-ba01-736c7aee234b
else
search --no-floppy --fs-uuid --set=root 89ddbfbb-26a0-4476-ba01-736c7aee234b
fi
echo 'Loading Linux 3.13.0-62-generic ...'
linux /boot/vmlinuz-3.13.0-62-generic root=UUID=89ddbfbb-26a0-4476-ba01-736c7aee234b ro quiet splash $vt_handoff
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.13.0-62-generic
}
menuentry 'Description: Linux Lite 2.6 GNU/Linux, with Linux 3.13.0-62-generic (recovery mode)' --class description_ --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.13.0-62-generic-recovery-89ddbfbb-26a0-4476-ba01-736c7aee234b' {
recordfail
load_video
insmod gzio
insmod part_msdos
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root 89ddbfbb-26a0-4476-ba01-736c7aee234b
else
search --no-floppy --fs-uuid --set=root 89ddbfbb-26a0-4476-ba01-736c7aee234b
fi
echo 'Loading Linux 3.13.0-62-generic ...'
linux /boot/vmlinuz-3.13.0-62-generic root=UUID=89ddbfbb-26a0-4476-ba01-736c7aee234b ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.13.0-62-generic
Thanks to all for your help, much appreciated.. :)
-
Found this post (http://forums.linuxmint.com/viewtopic.php?f=46&t=204554&sid=c169b4c5829ddc59a2f021db5d2f167f#p1063395) saying problem likely caused by UEFI/(Bios) settings -- possibly solved by updating the firmware, if an update is available. Sounds like these types of systems are meant to boot in UEFI mode and the firmware is not set-up to properly handle Legacy/Bios mode booting. As you can read in rest of that thread, I had the OP run through various things to try getting it to work all to no avail.
Unfortunately, (assuming you don't find another solution), you may end up having to re-install everything (Windows and LL) in UEFI mode to get it working right.
P.s. Just for heck of it, run sudo blkid from terminal in live LL to see if UUID of LL on nvme disk matches that shown in your grub.conf output. If not, try editing it and see if that works. Other than that I'm afraid I have no idea how to get around the problem other than doing a UEFI-mode install.
-
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:
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 /dev/nvme0n1p3
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.
-
Just an update, still no luck with any of the suggestions.
I have just found this statement for the SM951:
The UEFI drivers for this M.2 PCIE SSD are built onto it and must be read/loaded into your UEFI BIOS first
I have a couple ideas, so one last try.
Then I think I will have to tell my friend to swap/rma the disk for a regular SATA drive in M.2 size/format.
-
@Jerry
Having exhausted all my options, a final google led me to this: NVM Express Disk Driver (http://manpages.ubuntu.com/manpages/trusty/en/man4/nvd.4freebsd.html)
It's in a Ubuntu 14.04 Man page, but seems to be linked to BSD.
Not sure if it's valid, or usable..??
I have absolutely no idea how to compile a kernel ???
But there is also a "load the driver as module at boot time",, however,
I don't seem to be able to find the loader.conf file , should I have one..??
or is there another way to do this with LL..??
any advice greatly received :)
-
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 doubt that will help. That's the MBR of the disk, so just like pointing to /dev/sda if it were regular disk. On boot-up (in Legacy mode on MBR disks), the MBR of drive only holds first stage boot loader which then points to rest of boot code on root partition (in this case) to finish booting process. The boot code on root partition is what needs to be specified in grub.conf.
Having exhausted all my options, a final google led me to this: NVM Express Disk Driver (http://manpages.ubuntu.com/manpages/trusty/en/man4/nvd.4freebsd.html)
It's in a Ubuntu 14.04 Man page, but seems to be linked to BSD.
Not sure if it's valid, or usable..??
I have absolutely no idea how to compile a kernel ???
But there is also a "load the driver as module at boot time",, however,
I don't seem to be able to find the loader.conf file , should I have one..??
or is there another way to do this with LL..??
any advice greatly received :)
I'm not sure if this will work, but might as well give it a try.
Boot with live LL dvd/usb and open a terminal.
Mount the root partition on installed disk to live environment
sudo mount /dev/nvme0n1p3 /mnt
for i in /dev /dev/pts /proc /sys; do sudo mount -B $i /mnt$i; done
Chroot into installed system
sudo chroot /mnt
Open grub file with nano. (When chrooted into system you're operating as root, so no need to precede commands with "sudo". Just enter commands as written below.)
nano /etc/default/grub
Use arrow keys to navigate to this line
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
Change it to read as
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_load=YES nvd_load=YES"
Hit Ctrl+O to "Write Out"/(Save changes); then Ctrl+X to exit nano and get back to terminal prompt.
Now update grub
update-grub
Exit out of chroot
exit
Unmount everything
for i in /sys /proc /dev/pts /dev; do sudo umount /mnt$i; done
sudo umount /mnt
Reboot (without live dvd/usb), cross your fingers and hopefully that worked.
-
@gold_finger
Thanks for all your help, unfortunately still the same issue. :(
I had found the following "Intel nvme page (https://communities.intel.com/community/itpeernetwork/blog/2014/10/10/finding-your-new-intel-ssd-for-pcie-think-nvme-not-scsi)" , and followed the check points, apart from point 4 , it all seemed to check out..??
I did this before your suggestions.
I think the clue maybe in the fact that whilst everything "appears" to checkout..??
If you look in "DISKS", the nvme drive is "not" in the disk section, it appears under "Other devices", see screenshot in an earlier post I dis.
Results from doing the checks on Intel Page:
1.)03:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd Device a802 (rev 01)
it@it:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 50G 0 part
├─sda2 8:2 0 20G 0 part
├─sda3 8:3 0 20G 0 part
├─sda4 8:4 0 1K 0 part
└─sda5 8:5 0 820G 0 part
sdb 8:16 1 7.5G 0 disk
└─sdb1 8:17 1 7.5G 0 part /cdrom
loop0 7:0 0 747.6M 1 loop /rofs
nvme0n1 259:0 0 119.2G 0 disk
├─nvme0n1p1 259:1 0 50G 0 part
├─nvme0n1p2 259:2 0 20G 0 part
├─nvme0n1p3 259:3 0 20G 0 part
├─nvme0n1p4 259:4 0 1K 0 part
└─nvme0n1p5 259:5 0 17G 0 part
it@it:~$
2.)it@it:~$ modinfo nvme
filename: /lib/modules/3.13.0-62-generic/kernel/drivers/block/nvme.ko
version: 0.8
license: GPL
author: Matthew Wilcox <[email protected]>
srcversion: 56D1A65BFAFAC90F460C031
alias: pci:v*d*sv*sd*bc01sc08i02*
depends:
intree: Y
vermagic: 3.13.0-62-generic SMP mod_unload modversions
signer: Magrathea: Glacier signing key
sig_key: E0:7C:FC:BE:E8:34:59:BA:45:54:3D:39:B2:C2:A5:78:75:74:50:01
sig_hashalgo: sha512
parm: shutdown_timeout:timeout in seconds for controller shutdown (byte)
parm: nvme_major:int
parm: use_threaded_interrupts:int
it@it:~$
3.)it@it:~$ lsmod | grep nvm
nvme 58970 0
it@it:~$
4.)$ ll /dev/nvme*n1
>> command not found
5.)it@it:~$ sudo hdparm -tT --direct /dev/nvme0n1
/dev/nvme0n1:
Timing O_DIRECT cached reads: 2118 MB in 2.00 seconds = 1058.31 MB/sec
Timing O_DIRECT disk reads: 3736 MB in 3.00 seconds = 1244.85 MB/sec
it@it:~$
-
It does appear that everything checks out and that there is a kernel driver for it built-in.
Re: #4, use command "ls -l" in place of "ll". Redhat Linux must have "ll" aliased to "ls -l" and Linux Lite doesn't.
I'm fresh out of ideas, but looks to me like drive should work. Best bet would be to post question on Ubuntu forums. Many more users on that forum and more likely that people there have tackled this problem before.
-
One final thought:
Can you set the boot priority to boot from the standard HDD first instead of the new drive? If so, maybe try installing grub to MBR on that drive and see if it makes any difference trying to boot from there.
Boot live LL dvd/usb and do following in a terminal:
sudo mount /dev/nvme0n1p3 /mnt
sudo grub-install boot-directory=/mnt/boot /dev/sda
sudo umount /mnt
Reboot without dvd/usb and with boot priority set to regular hard drive in first position.
If doesn't work, undo the edits to /etc/default/grub made according to my prior post, (run "update-grub" after re-edit, while in chroot); then try rebooting again.
If it works then at least you'll have a solution that makes computer usable. Can keep it like that until find solution to booting with grub on MBR of new drive. Only thing that's happening is the very initial grub boot stage is on MBR of standard drive and passes boot process on to root partition on new drive after that -- so I doubt whole boot process will be significantly different than if it started from MBR of new drive.
-
Hi,
Many Thanks.... Noted on trying Ubuntu Forum.
Here is the output for point 4 , I did 2 variants:
it@it:~$ ls -l /dev/nvme*n1
brw-rw---- 1 root disk 259, 0 Nov 24 06:47 /dev/nvme0n1
it@it:~$ ls -l /dev/nvme*
crw------- 1 root root 10, 57 Nov 24 06:47 /dev/nvme0
brw-rw---- 1 root disk 259, 0 Nov 24 06:47 /dev/nvme0n1
brw-rw---- 1 root disk 259, 1 Nov 24 06:47 /dev/nvme0n1p1
brw-rw---- 1 root disk 259, 2 Nov 24 06:47 /dev/nvme0n1p2
brw-rw---- 1 root disk 259, 3 Nov 24 06:47 /dev/nvme0n1p3
brw-rw---- 1 root disk 259, 4 Nov 24 06:47 /dev/nvme0n1p4
brw-rw---- 1 root disk 259, 5 Nov 24 06:47 /dev/nvme0n1p5
-
Hi,
Many thanks...
So to be clear, go into BIOS, move regular disk to top of list?
Then follow your commands you listed, there is no need to do
sudo update-grubat any point..??
It will still know where the Win7 install is..??
-
Yes -- change boot order of drive and run code shown to install to its MBR. Then reboot and see if grub can boot computer from there.
If we're lucky, LL will finally boot. If Windows doesn't show as a boot choice, then run "sudo update-grub" once booted into installed LL to add it to the menu. (Don't run update-grub along with other code in this case because that won't work.)
If computer still won't boot Linux, then change boot priority back to new drive so Windows works again (assuming it doesn't when booting from regular HDD).
-
Hi,
Something with commands..?
1st O.K, then 2nd errors.?
it@it:~$ sudo mount /dev/nvme0n1p3 /mnt
it@it:~$ sudo grub-install boot-directory=/mnt/boot /dev/sda
grub-install: error: More than one install device?.
it@it:~$
-
Unfortunately Wirezfree,
You're the second person who's system has me stumped today. I'm not sure why installing to /dev/sda didn't work and really have no idea where to go from here. Sorry.
-
Hi,
Many thanks for all your effort... very much appreciated...
I figured out the the why the command failed, when looking for the error I found there was a subtle difference in what you had:
sudo grub-install boot-directory=/mnt/boot /dev/sda
vs
sudo grub-install --boot-directory=/mnt/boot /dev/sda
withe extra -- in front of the boot , it then ran O.K, did the sudo umount /mnt and re-booted
Same error, but with a minor difference.
"error attempting to Read/Write outside of disk" "HD1"
the "hd changed to 1 from 0
"error attempting to Read/Write outside of disk" "HD0"
I'm going to have 1 last go at clearing all partition, and installing just LL
If this fails, I will get my friend to RMA/Swap the drive.
The question is then,
Go for the "AHCI" version of this drive, or just a standard M.2 SATA SSD
Thanks again
-
Good job finding the error. I was in a rush when I typed that out and somehow slipped my mind to put in the "--". Duh! (I've typed those instructions sooo many times for people I can't believe I left that off.) Sorry.
I'm going to have 1 last go at clearing all partition, and installing just LL
If this fails, I will get my friend to RMA/Swap the drive.
If the Win 7 version you have is a 64-bit retail copy (not an OEM version), I believe you can install that in UEFI mode. You may want to try installing both Windows and LL in UEFI mode instead. As I'm sure you're already aware of, you'll need to follow m654321's tutorial (https://www.linuxliteos.com/forums/tutorials/tutorial-how-to-set-up-a-winll-dual-boot-with-uefi-fully-enabled/) for the LL install. Use GParted from live LL to wipe out drive; then create new GPT partition table on it before trying to install anything. It must be using GPT partitions to install either OS in UEFI mode. Check Windows 7 forums for info on installing in that mode, but I think once it sees a GPT partition table it may automatically know to install that way. (That's just a guess, so please confirm on their forums.)
The question is then,
Go for the "AHCI" version of this drive, or just a standard M.2 SATA SSD
I'm pretty clueless when it comes to SSDs -- I don't have one myself and haven't spent any time learning about them.
-
So the story do far,
The "NVME" version of the drive was a "no go", friend returned it and got the "AHCI" version, and "Oh NO", this did not work.
At this stage I'm thinking could it possibly be a hardware issue with the M.2 slot on the motherboard..??
So there was one last option, use an M.2 version of a SATA SSD, so I got got one, on a return basis from a local supplier.
Guess what, It also would not work At this point, it really did look like it was a Hardware issue,
I had one last Google around, and found what was exactly the same issue on the Intel Site,
NUC5i7 trying to install in Legacy Mode, posted 21st Nov. (https://communities.intel.com/thread/93274#352615)
Quickly read down the thread, the poster tried an older BIOS, and it worked.
I quickly downloaded the older BIOS and flashed the NUC.........
I booted Win7 installer from USB stick, and guess what, I also could install Win7 :) :) :)
I then booted my LL USB installer, installed that, and guess what, It ran :) :) :)
So the NUC is now dual booting Win7 & LL2.6 on the M.2 SATA SSD.
Then on the above Intel Thread, an Intel person posted on the 24th Nov.
This issue has been reproduced and the engineering team is working on a fix. For now go back to the earlier BIOS. Thank you for all the information.
So what next..??,
Do I now take a chance on trying it again on the AHCI version,
I can see on the original posters screen shot the model number is the AHCI version, so it should work.?, I've posted the question on the thread.
Also, my friend wanted Linux Mint,
Not sure how to add that now, given I put LL on it first in my rush to see if it would work
So the moral of this story,
Don't give up, and don't assume the latest BIOS is always good ..!!!
.
-
Hi,
To finish this build of for my friend, I now want to clarify something... Before I break it
If I now try to install Linux Mint, with the "something else" option,
Select the relevant / and /home partitions, and then select /dev/sda for bootloader
Will this now also add Mint to Grub..?? or will I end up with just Mint..??
I'm sure I read that LL was different in that respect when you install it,
and it recognised other OS's, and it created/updated the Grub.
Thanks...
-
Well the NUC install complete.
- Triple Booting LL ~ Linux Mint ~ Win7
- Just need to wait for a BIOS update to solve Infra-red issue in Win7
Will hand it over to my friend, I think he owes me one...
I'm amazed at the boot up speed, I guess the M.2 AHCI disk is a significant part of that.
From the Grub selection to the LL Desktop is about @ 6secs.
Thanks to everybody who helped.