Siduction Forum

I have an Acer Veriton M6620G. I am trying to install Latest Siduction on an SSD Samsung 840 EVO.
I have changed CMOS settings from (factory default) RAID to AHCI. CMOS does detect SSD. LIVE USB Siduction found it. Followed installation program it said successful installation. Rebooted. CMOS does not find SSD boot drive in HD boot selection. Booting in old ata HD that has linux on it. Grub finds it but I can not boot into it.
This sounds somewhat like my problem http://askubuntu.com/questions/448962/bios-not-detecting-boot-files-for-14-04lts-singel-os-installation (http://askubuntu.com/questions/448962/bios-not-detecting-boot-files-for-14-04lts-singel-os-installation). The issue I have is the solution which is ubuntu and they do go their own way at times. Is there something I can try that Siduction would see as best way to solve it?

I see in the ubuntu post that they're mentioning EFI.  Does your laptop have UEFI firmware instead of a Legacy BIOS?

If it does, I wrote a howto for installing in UEFI mode here:
http://forum.siduction.org/index.php?topic=4254.0

If it is running in UEFI mode, it should still see the SSD.  Maybe you could tell us more about your hardware.  Is the SSD your only HD?  How about running "fdisk -l" when using the live usb and pasting the info here.  Or, as root, run "parted", then type "print all" at the prompt and paste that info.

I'm only guessing here, since I see that your machine came with Windows 7, and, many Windows 7 machines don't have UEFI firmware.  So, please give us more specific info, and we'll try to narrow it down a little more.

There are few motherboards that need the "boot" flag set on the partition where /boot lives, even with grub installed to the MBR.  It doesn't hurt to set it and leave it, whether the motherboard needs it or not.

I tried again.
efibootmgr -v
Timeout: 1 seconds
BootOrder: 000C,0002,000E,000F,0010,000D,0005,000B
Boot0002* HL-DT-ST DVDRAM GHA2N BIOS(3,0,00)AMBO
Boot0005  ST32000542AS  BIOS(2,0,00)AMBO
Boot000B  ST31000528AS  BIOS(2,0,00)AMBO
Boot000C* Maxtor 6Y160P0        BIOS(2,0,00)AMBO
Boot000D  Samsung SSD 840 EVO 250GB     BIOS(2,0,00)AMBO
Boot000E  WDC WD5000AAKX-22ERMA0        BIOS(2,0,00)AMBO
Boot000F  SanDisk Cruzer Blade 1.26     BIOS(2,0,00)AMBO
Boot0010  UEFI: SanDisk Cruzer Blade 1.26       ACPI(a0341d0,0)PCI(1a,0)USB(1,0)USB(5,0)HD(1,800,ee8400,0011dae3)AMBO
fdisk
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


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 / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1  1953525167   976762583+  ee  GPT

WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdc: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 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: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1   488397167   244198583+  ee  GPT

Disk /dev/sdb: 163.9 GB, 163928604672 bytes
255 heads, 63 sectors/track, 19929 cylinders, total 320173056 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: 0x7e6f0411

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1              63   319131224   159565581   83  Linux
/dev/sdb2       319131225   320159384      514080   82  Linux swap / Solaris

Disk /dev/sdd: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 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: 0x7fe4b93d

   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1            2048    62916607    31457280   27  Hidden NTFS WinRE
/dev/sdd2   *    62916608    63121407      102400    7  HPFS/NTFS/exFAT
/dev/sdd3        63121408   976771119   456824856    7  HPFS/NTFS/exFAT

WARNING: GPT (GUID Partition Table) detected on '/dev/sde'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sde: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 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: 0xefdd142b

   Device Boot      Start         End      Blocks   Id  System
/dev/sde1               1  3907029167  1953514583+  ee  GPT

Disk /dev/sdf: 8004 MB, 8004304896 bytes
255 heads, 63 sectors/track, 973 cylinders, total 15633408 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: 0x0011dae3

   Device Boot      Start         End      Blocks   Id  System
/dev/sdf1   *        2048    15633407     7815680    c  W95 FAT32 (LBA)

Disk /dev/sdg: 15.6 GB, 15610576896 bytes
119 heads, 55 sectors/track, 4658 cylinders, total 30489408 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: 0xc3072e18

   Device Boot      Start         End      Blocks   Id  System
/dev/sdg1   *        8064    30489407    15240672    c  W95 FAT32 (LBA)

Selected UEFI: SanDisk (thanks for info about CMOS selection F12 in my case)
SSD was sdc1 and added /boot/efi there installed siduction there.
Rebooted and F12 still does not bring up SSD as a choice.
HW info if this helps:
Not sure what Boot Mode: Legacy BIOS in UEFI means or how to change it if that is what is causing the trouble.
Think I may try out boot-repair on sdc1 see if that works. Worst that can happen is that it still doesn't work.
Adding Installation Report.

Maybe a little progress. I do have an old HD with Linux on it. In it's grub shows up sdc1 (my SSD). It shows 2 options. 1) sdc1 bootloader when I chose that up comes an error
No such device: 774f73e4-8ee2-400f-8dfc-895c5d15c6d0
Hit any key to continue
Option 2) sdc1 bootloader advanced.
Picking that one and I get ... GRUB!!! with 2 kernels.
In both cases picking either one with no extra commands gets you the same error message.
My hope is that someone knows what commands I can try and find out how to fix things.
Strange thing is UUID is right so it appears something is not working right. Also, /boot/efi is empty, although in /boot/ I do see efi files.

Just a thought. Should I start a new topic in installation or keep it here as it could still be a hardware problem?

You're OK to stay here -- we can always move the entire thread if needed.  I would study that UEFI system and see if you can learn how to set it to "legacy" mode, if it has that mode.  I have so far managed to escape the necessity to work with UEFI, although it's getting closer to the time to do that.