Linux Lite Forums

Pages: 1 2 3

[size=1em]Hi,[/size]

[size=1em]I started new thread instead of using the other thread.[/size]
[size=1em]I think this is possibly disk related..??[/size]
[size=1em]I booted a live gparted, and prepared partitions in advance. (see below)[/size]

[size=1em]"IMPORTANT" the NUC contains a "Samsung nvme pcie ssd"[/size]
[size=1em]So gparted detected drive O.K, and allowed me to create partitions.[/size]
[size=1em]Linux kernel gives an odd, but normal: /dev/nvme0n1p1[/size]
[size=1em]I decide to install LL2.6 1st and make sure everything works.[/size]
[size=1em]I ran LL2.6 Live boot USB, installed it, and it all ran O.K, no errors.[/size]
[size=1em]On re-boot I get the "grub screen"[/size]

[size=1em][img height=600 width=800]http://i.imgur.com/J4ZR8pT.jpg[/img][/size]

[size=1em]I checked Win7 still booted O.K, and it booted fine.[/size]
[size=1em]Then I re-booted and selected "Linux Lite",[/size]
[size=1em]momentary disk access, then the following: (sorry only have camera phone)[/size]

[size=1em][img height=600 width=800]http://i.imgur.com/SqFUzpz.jpg[/img][/size]

[size=1em]More Info when I re-booted a LL Live USB:[/size]

Code:
it@it:~$ sudo os-prober

/dev/nvme0n1p1:Windows 7 (loader):Windows:chain

/dev/nvme0n1p3:Linux Lite 2.6 (14.04):Ubuntu:linux

Code:
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)

[size=1em]Couple of observations/notes:[/size]
[size=1em]1. The NUC Bios is set to Legacy & Safeboot "disabled", and the nvme pcie drive is recognised in BIOS[/size]
[size=1em]2. For the Win7 install I needed to install it initially to 2nd drive, add 2 NS hofixes, then "clone" to nvme drive.[/size]
[size=1em] This is because Win7 does not recognise nvme pcie drives.[/size]
[size=1em]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[/size]
[size=1em]4. The nvme pcie disk "Model Unknown."..?? and it's sector size 512B/512B vs other disk is 512B/4096B ??[/size]

[size=1em]Googling shows nvme pcie drives appear to be problematic in terms of setting up for Linux Boot[/size]
[size=1em]I got confused, when discussions centred around UEFI & GPT started to be discussed, no mention of "Legacy scenario"..!![/size]
[size=1em]So more research needed, but any comments welcome Smile

[/size]

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:

[Image: dWnmRu0.png]

I'm sure you've searched... but I came across a couple links...
http://askubuntu.com/questions/397485/wh...-hd0-error
And
http://www.linuxquestions.org/questions/...fs-919143/

Maybe worth a look... Good Luck!!

,

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:

Code:
sudo mount /dev/nvme0nlp3 /mnt

If you needed to edit the fstab file on that partition, (as a random example), command would be:

Code:
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.

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.

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..??

Code:
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

Code:
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..??
[Image: 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: [color=rgb(255, 0, 0)]UUID=89ddbfbb-26a0-4476-ba01-736c7aee234b[/color]

Code:
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.. Smile

Pages: 1 2 3

Wirezfree

technomancer

Wirezfree

Wirezfree

firenice03

Wirezfree

technomancer

gold_finger

Wirezfree

Wirezfree