new install will not boot but

SolydXK is too quiet for you? SolydXK Enthusiast Editions, based on Debian Testing is for you! Here you can find news about Debian Testing and Unstable too, and also tests on SolydXK programs.
The support for SolydXK EE is provided by the community.
User avatar
xendistar
Posts: 475
Joined: 08 Jun 2014 08:17
Location: Bournemouth, UK

new install will not boot but

Postby xendistar » 26 Dec 2018 15:27

I have done a fresh install on the new 201812 edition, but while I can get into the new install it does not boot into the new install.

Let me explain my setup, I have three disk

sda 500gb contain my old Home
sdb 500gb contains, backup partition, swap, var & tmp partitions
sdc 120gb ssd contains boot, root & home

SDA and SDB are connected to the sata2 on the motherboard, SDC boots from a sata3 pci-e card

SDC is see by setup and is selected as above and the sata3 card is seen by the bios at boot up although there is not option to choose sdc in the boot options.

When I boot up it goes through the bios screen and then ends up at the grub rescue screen, if I use Super Grub Rescue DVD and select the installed OS I can boot into my new Solydx install.

I have attached a copy of my fstab file, is this because I cant select sdc as a boot drive if so can I put the /boot/efi on to either sda or sdb?
fstab-screen-grab.jpg
I have no idea what the Ram Disk section of the fstab file means, I have never seen it before

Thanks in advance

User avatar
Arjen Balfoort
Site Admin
Posts: 8958
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: new install will not boot but

Postby Arjen Balfoort » 26 Dec 2018 16:31

What is the output of:

Code: Select all

sudo blkid
xendistar wrote:
26 Dec 2018 15:27
I have no idea what the Ram Disk section of the fstab file means, I have never seen it before
Those are settings to reduce writing to your SSD. You can either comment or remove those if you want.


SolydXK needs you!
Development | Testing | Translations

User avatar
xendistar
Posts: 475
Joined: 08 Jun 2014 08:17
Location: Bournemouth, UK

Re: new install will not boot but

Postby xendistar » 26 Dec 2018 19:06

Output as requested

Code: Select all

mit@andora:~$ sudo blkid
[sudo] password for mit: 
/dev/sda3: LABEL="Home" UUID="3e207549-90af-4da4-806f-3afef5d1bb62" TYPE="ext4" PARTUUID="bebddbe0-1eb3-4741-b944-5cb8e9dc1485"
/dev/sdb1: UUID="a122450b-1322-4dee-a3ce-db17a6207742" TYPE="swap" PARTUUID="635a79c3-01"
/dev/sdb2: LABEL="Backup2" UUID="0413948d-1006-4474-bb79-d276c383ae5c" TYPE="ext4" PARTUUID="635a79c3-02"
/dev/sdb3: UUID="13fc68e9-dfd0-4981-86e7-9e871a13069c" TYPE="ext4" PARTUUID="635a79c3-03"
/dev/sdb4: UUID="6a8fda51-e06e-47aa-9d7e-0525f099e327" TYPE="ext4" PARTUUID="635a79c3-04"
/dev/sdc1: LABEL="SolydX EE 10 64-" UUID="47917432-bfd7-4fa8-af60-c66e0a035f6d" TYPE="ext4" PARTUUID="bdd3de29-01"
/dev/sdc2: LABEL="HOME" UUID="f2170a4b-a62d-4206-9d26-a9f4beb714e9" TYPE="ext4" PARTUUID="bdd3de29-02"
/dev/sdc3: LABEL_FATBOOT="EFI" LABEL="EFI" UUID="F2F1-BF73" TYPE="vfat" PARTUUID="bdd3de29-03"
/dev/sr0: UUID="2017-05-06-18-08-06-00" LABEL="ISOIMAGE" TYPE="iso9660" PTTYPE="PMBR"
I will leave those setting alone for the time being

User avatar
Arjen Balfoort
Site Admin
Posts: 8958
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: new install will not boot but

Postby Arjen Balfoort » 27 Dec 2018 08:43

There's nothing wrong with the UUIDs.

Try to comment out the NAS mount and search for relevant errors with:

Code: Select all

sudo grep -i -E 'error|failed' /var/log/*


SolydXK needs you!
Development | Testing | Translations

User avatar
xendistar
Posts: 475
Joined: 08 Jun 2014 08:17
Location: Bournemouth, UK

Re: new install will not boot but

Postby xendistar » 27 Dec 2018 16:31

In regards to the NAS it has always shown up as failed but by the time I have logged into the desktop the NAS has mounted, it used to do that with the previous couple of install of EE.

I will have a search through /var/log shortly and report back

User avatar
xendistar
Posts: 475
Joined: 08 Jun 2014 08:17
Location: Bournemouth, UK

Re: new install will not boot but

Postby xendistar » 27 Dec 2018 19:09

OK so I rebooted the PC tonight and then ran the grep command and then thinned out all the results that were not dated the 27th, here is what was left (I have trimmed one entry as there was one line repeated over 30 consecutive lines, I left one line which is marked below):

Code: Select all

/var/log/syslD 27 00:00:06andra systemd[1]: logrotate.service: Failed with result 'exit-code'.                                                      
/var/log/syslD 27 00:00:06andra systemd[1]: Failed to start Rotate log files.                                                                       
/var/log/syslD 27 06:54:38andra colord[1028]: failed to get session [pid 955]: No data available                                                    
/var/log/syslD 27 07:39:33andra systemd[4437]: gpgconf: running /usr/bin/gpg-agent failed (exitcode=2): General error                               
/var/log/syslD 27 07:39:33andra systemd[4437]: gpgconf: fatal error (exit status 1)                                                                 
/var/log/syslD 27 07:39:34andra systemd[4453]: gpgconf: running /usr/bin/gpg-agent failed (exitcode=2): General error                               
/var/log/syslD 27 07:39:34andra systemd[4453]: gpgconf: fatal error (exit status 1)                                                                 
/var/log/syslD 27 07:39:34andra systemd[4453]: Failed to connect to API bus: Connection refused (THIS LINE WAS REPEATED 30 TIMES)                   
/var/log/syslD 27 18:18:25andra xfce4-notifyd[2067]: xfce4-notifyd: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.            
/var/log/syslD 27 18:18:25andra at-spi-bus-launcher[2000]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"              
/var/log/syslD 27 18:21:59andra systemd-udevd[356]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99.               
/var/log/syslD 27 18:21:59andra systemd-udevd[355]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99.               
/var/log/syslD 27 18:21:59andra kernel: [    1.931983] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20180
/var/log/syslD 27 18:21:59andra kernel: [    1.932064] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20180531/ps
/var/log/syslD 27 18:21:59andra kernel: [    1.932189] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20180
/var/log/syslD 27 18:21:59andra kernel: [    1.932257] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20180531/ps
/var/log/syslD 27 18:21:59andra kernel: [    1.932940] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20180
/var/log/syslD 27 18:21:59andra kernel: [    1.933045] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT4._GTF, AE_NOT_FOUND (20180531/ps
/var/log/syslD 27 18:21:59andra kernel: [    1.933206] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20180
/var/log/syslD 27 18:21:59andra kernel: [    1.933274] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20180531/ps
/var/log/syslD 27 18:21:59andra kernel: [    1.934303] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20180
/var/log/syslD 27 18:21:59andra kernel: [    1.934372] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20180531/ps
/var/log/syslD 27 18:21:59andra kernel: [    1.935548] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20180
/var/log/syslD 27 18:21:59andra kernel: [    1.935616] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT4._GTF, AE_NOT_FOUND (20180531/ps
/var/log/syslD 27 18:21:59andra kernel: [    4.966957] EXT4-fs (sdc1): re-mounted. Opts: errors=remount-ro                                          
/var/log/syslD 27 18:21:59andra kernel: [    5.640908] EXT4-fs (sdc2): mounted filesystem with ordered data mode. Opts: errors=remount-ro           
/var/log/syslD 27 18:21:59andra kernel: [    5.709611] EXT4-fs (sdb3): mounted filesystem with ordered data mode. Opts: errors=remount-ro           
/var/log/syslD 27 18:21:59andra kernel: [    5.787417] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: errors=remount-ro           
/var/log/syslD 27 18:21:59andra kernel: [    6.049258] EXT4-fs (sdb2): mounted filesystem with ordered data mode. Opts: errors=remount-ro           
/var/log/syslD 27 18:21:59andra kernel: [    6.066561] EXT4-fs (sdb4): mounted filesystem with ordered data mode. Opts: errors=remount-ro           
/var/log/syslD 27 18:21:59andra udisksd[766]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or direc
/var/log/syslD 27 18:21:59andra udisksd[766]: Failed to load the 'mdraid' libblockdev plugin                                                        
/var/log/syslD 27 18:22:00andra ntpd[816]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized                                                    
/var/log/syslD 27 18:22:00andra ntpd[816]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized                                                    
/var/log/syslD 27 18:22:00andra colord[808]: failed to get session [pid 747]: No data available                                                     
/var/log/syslD 27 18:22:01andra ntpd[816]: error resolving pool 0.debian.pool.ntp.org: Name or service not known (-2)                               
/var/log/syslD 27 18:22:01andra colord[808]: Unlinked OID in NET-SNMP-AGENT-MIB: nsErrorHistory ::= { netSnmpObjects 6 }                            
/var/log/syslD 27 18:22:01andra colord[808]: Cannot adopt OID in UCD-SNMP-MIB: logMatchErrorFlag ::= { logMatchEntry 100 }                          
/var/log/syslD 27 18:22:01andra colord[808]: Cannot adopt OID in UCD-SNMP-MIB: prErrorFlag ::= { prEntry 100 }                                      
/var/log/syslD 27 18:22:01andra colord[808]: Cannot adopt OID in UCD-SNMP-MIB: memSwapErrorMsg ::= { memory 101 }                                   
/var/log/syslD 27 18:22:01andra colord[808]: Cannot adopt OID in UCD-SNMP-MIB: memSwapError ::= { memory 100 }                                      
/var/log/syslD 27 18:22:01andra colord[808]: Cannot adopt OID in UCD-SNMP-MIB: memErrorName ::= { memory 2 }                                        
/var/log/syslD 27 18:22:01andra colord[808]: Cannot adopt OID in UCD-DLMOD-MIB: dlmodError ::= { dlmodEntry 4 }                                     
/var/log/syslD 27 18:22:01andra colord[808]: Cannot adopt OID in UCD-SNMP-MIB: fileErrorMsg ::= { fileEntry 101 }                                   
/var/log/syslD 27 18:22:01andra colord[808]: Cannot adopt OID in UCD-SNMP-MIB: fileErrorFlag ::= { fileEntry 100 }                                  
/var/log/syslD 27 18:22:01andra colord[808]: Cannot adopt OID in UCD-SNMP-MIB: ssErrorName ::= { systemStats 2 }                                    
/var/log/syslD 27 18:22:01andra colord[808]: Cannot adopt OID in NET-SNMP-AGENT-MIB: nsErrorHistory ::= { netSnmpObjects 6 }                        
/var/log/syslD 27 18:22:01andra colord[808]: Cannot adopt OID in UCD-SNMP-MIB: dskErrorMsg ::= { dskEntry 101 }                                     
/var/log/syslD 27 18:22:01andra colord[808]: Cannot adopt OID in UCD-SNMP-MIB: dskErrorFlag ::= { dskEntry 100 }                                    
/var/log/syslD 27 18:22:01andra colord[808]: Cannot adopt OID in UCD-SNMP-MIB: snmperrErrorFlag ::= { snmperrs 100 }                                
/var/log/syslD 27 18:22:01andra colord[808]: Cannot adopt OID in UCD-SNMP-MIB: laErrorFlag ::= { laEntry 100 }                                      
/var/log/syslD 27 18:22:02andra ntpd[816]: error resolving pool 1.debian.pool.ntp.org: Name or service not known (-2)                               
/var/log/syslD 27 18:22:03andra ntpd[816]: error resolving pool 2.debian.pool.ntp.org: Name or service not known (-2)                               
/var/log/syslD 27 18:22:04andra ntpd[816]: error resolving pool 3.debian.pool.ntp.org: Name or service not known (-2)                               
/var/log/syslD 27 18:22:05andra ntpd[816]: bind(23) AF_INET6 fe80::1994:7978:10a7:144%2#123 flags 0x11 failed: Cannot assign requested address      
/var/log/syslD 27 18:22:05andra ntpd[816]: failed to init interface for address fe80::1994:7978:10a7:144%2                                          
/var/log/syslD 27 18:22:05andra freshclam[1193]: ERROR: Problem with internal logger (UpdateLogFile = /var/log/clamav/freshclam.log).               
/var/log/syslD 27 18:22:05andra freshclam[1193]: ERROR: Can't open /var/log/clamav/freshclam.log in append mode (check permissions!).               
/var/log/syslD 27 18:22:05andra systemd[1]: clamav-freshclam.service: Failed with result 'exit-code'.                                               
/var/log/syslD 27 18:22:10andra colord[808]: failed to get session [pid 747]: No data available                                                     
/var/log/syslD 27 18:22:20andra backintime (mit/1): ERROR: Back In Time is not configured!                                                          
/var/log/syslD 27 18:22:21andra org.freedesktop.thumbnails.Thumbnailer1[2054]: ! SyncTeX Error : No file?                                           
grep: /var/lontended-upgraes:Is a directory                                                                                                         
/var/log/usergec 27 06:54:8 adora colord[1028]: failed to get session [pid 955]: No data available                                                  
/var/log/usergec 27 18:18:5 adora xfce4-notifyd[2067]: xfce4-notifyd: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.          
/var/log/usergec 27 18:21:9 adora udisksd[766]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or dir
/var/log/usergec 27 18:21:9 adora udisksd[766]: Failed to load the 'mdraid' libblockdev plugin                                                      
/var/log/usergec 27 18:22:0 adora colord[808]: failed to get session [pid 747]: No data available                                                   
/var/log/usergec 27 18:22:0 adora colord[808]: failed to get session [pid 747]: No data available                                                   
/var/log/usergec 27 18:22:0 adora backintime (mit/1): ERROR: Back In Time is not configured!                                                        
/var/log/usergec 27 18:22:1 adora org.freedesktop.thumbnails.Thumbnailer1[2054]: ! SyncTeX Error : No file?                                         
/var/log/Xorgl:	(WW) warnig, EE) error, (NI) not implemented, (??) unknown.                                                                         
/var/log/Xorgl:[    16.854 (E) Failed to load module "nv" (module does not exist, 0)                                                                
/var/log/Xorgl.old:	(WW) wrnig, (EE) error, (NI) not implemented, (??) unknown.                                                                     
/var/log/Xorgl.old:[     8613 (EE) Failed to load module "nv" (module does not exist, 0)   

User avatar
xendistar
Posts: 475
Joined: 08 Jun 2014 08:17
Location: Bournemouth, UK

Re: new install will not boot but

Postby xendistar » 27 Dec 2018 22:00

Been doing a bit of digging and I found a command and when I ran I got the following output that says grub is not installed:]

Code: Select all

mit@andora:~$ sudo apt policy grub-pc
[sudo] password for mit: 
grub-pc:
  Installed: (none)
  Candidate: 2.02+dfsg1-9
  Version table:
     2.02+dfsg1-9 500
        500 http://ftp.uk.debian.org/debian testing/main amd64 Packages
     2.02+dfsg1-8 -1
        100 /var/lib/dpkg/status
Well I can tell you that I have grub installed in someway or the other as I have the relevant grub.cfg in /boot/grub although the the /boot/efi folder is empty? Is this just a red herring?

When I boot the PC up and enter the boot menu (from Bios) and select the SSD drive to boot from it just comes up saying that this drive is not bootable and if I tap the space bar I end up at the Grub rescue prompt.

If it worth reinstalling and re configuring grub and if so what is the appropriate command?

User avatar
Arjen Balfoort
Site Admin
Posts: 8958
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: new install will not boot but

Postby Arjen Balfoort » 28 Dec 2018 12:14

Start a live SolydX session (boot the ISO) and open a terminal:

Code: Select all

live-chroot /dev/sdc1
mount /dev/sdc3 /boot/efi
mount /dev/sdb4 /var
mount /dev/sdb3 /tmp
mount /dev/sdc2 /home
grub-install --efi-directory=/boot/efi /dev/sdc
update-grub
umount /boot/efi /var /tmp /home
exit
This will install grub on /dev/sdc, point the efi files to /dev/sdc3 and generate a new grub.cfg file.


SolydXK needs you!
Development | Testing | Translations

User avatar
xendistar
Posts: 475
Joined: 08 Jun 2014 08:17
Location: Bournemouth, UK

Re: new install will not boot but

Postby xendistar » 29 Dec 2018 14:47

Thanks for the information, tried it twice and it did not work, here is the output I got from running each command

Code: Select all

solydxk@solydxk:~$ live-chroot /dev/sdc1
/etc/live-installer-3/live-installer-3.conf: line 8: --assume-yes: command not found
/etc/live-installer-3/live-installer-3.conf: line 9: --quiet: command not found
Use configured target: /target
Create directory /target
Mounting /dev/sdc1 on /target
Chrooting into /target
root@solydxk:/# mount /dev/sdc3 /boot/efi
root@solydxk:/# grub-install /dev/sda
Installing for x86_64-efi platform.
Installation finished. No error reported.
root@solydxk:/# update-grub
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-4.19.0-1-amd64
Found initrd image: /boot/initrd.img-4.19.0-1-amd64
Found linux image: /boot/vmlinuz-4.18.0-3-amd64
Found initrd image: /boot/initrd.img-4.18.0-3-amd64
mkdir: cannot create directory ‘/var/lib/os-prober/mount’: No such file or directory
mkdir: cannot create directory ‘/var/lib/os-prober/mount’: No such file or directory
mkdir: cannot create directory ‘/var/lib/os-prober/mount’: No such file or directory
mkdir: cannot create directory ‘/var/lib/os-prober/mount’: No such file or directory
mkdir: cannot create directory ‘/var/lib/os-prober/mount’: No such file or directory
mkdir: cannot create directory ‘/var/lib/os-prober/mount’: No such file or directory
mkdir: cannot create directory ‘/var/lib/os-prober/mount’: No such file or directory
done
root@solydxk:/# umount /boot/efi
root@solydxk:/# 
Are those errors an issue?

The /var/lib/os-prober/ directory is on /dev/sdc2 but is currently empty (no mount directory)

User avatar
Arjen Balfoort
Site Admin
Posts: 8958
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: new install will not boot but

Postby Arjen Balfoort » 29 Dec 2018 16:52

I forgot to let you mount /var e.o. as well.
I've updated my post: viewtopic.php?p=69420#p69420


SolydXK needs you!
Development | Testing | Translations

User avatar
xendistar
Posts: 475
Joined: 08 Jun 2014 08:17
Location: Bournemouth, UK

Re: new install will not boot but

Postby xendistar » 29 Dec 2018 19:26

OK that one did not work either, and there was a different error this time although I am not sure it means anything, it complained about not being able to find a grub drive on sdd1, well sdd1 is the usb memory stick I am installing SolydXK from.

After the boot failed again I selected the sda drive from the boot menu to boot from from but just comes back saying that this disk is not bootable

Code: Select all

solydxk@solydxk:~$ live-chroot /dev/sdc1
/etc/live-installer-3/live-installer-3.conf: line 8: --assume-yes: command not found
/etc/live-installer-3/live-installer-3.conf: line 9: --quiet: command not found
Use configured target: /target
Create directory /target
Mounting /dev/sdc1 on /target
Chrooting into /target
root@solydxk:/# mount /dev/sdc3 /boot/efi
root@solydxk:/# mont /dev/sdb4 /var
bash: mont: command not found
root@solydxk:/# mount /dev/sdb4 /var
root@solydxk:/# mount /dev/sdb3 /tmp
root@solydxk:/# mount /dev/sdc2 /home
root@solydxk:/# grub-install /dev/sda
Installing for x86_64-efi platform.
Installation finished. No error reported.
root@solydxk:/# update-grub
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-4.19.0-1-amd64
Found initrd image: /boot/initrd.img-4.19.0-1-amd64
Found linux image: /boot/vmlinuz-4.18.0-3-amd64
Found initrd image: /boot/initrd.img-4.18.0-3-amd64
grub-probe: error: cannot find a GRUB drive for /dev/sdd1.  Check your device.map.
done
root@solydxk:/# umount /boot/efi /var /tmp /home
root@solydxk:/#
Thanks for your Help Arjen

User avatar
Arjen Balfoort
Site Admin
Posts: 8958
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: new install will not boot but

Postby Arjen Balfoort » 29 Dec 2018 21:06

Let's try to force the location of the EFI files in the grub-install command.

Again, updated my post: viewtopic.php?p=69420#p69420


SolydXK needs you!
Development | Testing | Translations

User avatar
xendistar
Posts: 475
Joined: 08 Jun 2014 08:17
Location: Bournemouth, UK

Re: new install will not boot but

Postby xendistar » 29 Dec 2018 21:16

On /dev/sda do I need to setup any separate fat32 partition like I currently have on /dev/sdc3

Also since I last replied I wiped sda clean (It was holding an old copy of my Home directory) and reformatted it to ext4 as a single partition, it made no difference to the booting?

User avatar
Arjen Balfoort
Site Admin
Posts: 8958
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: new install will not boot but

Postby Arjen Balfoort » 29 Dec 2018 21:49

xendistar wrote:
29 Dec 2018 21:16
On /dev/sda do I need to setup any separate fat32 partition like I currently have on /dev/sdc3

Also since I last replied I wiped sda clean (It was holding an old copy of my Home directory) and reformatted it to ext4 as a single partition, it made no difference to the booting?
On second thought, it might be better to install Grub on /dev/sdc (see the updated post above). That's the drive where you created the root and efi partitions. The efi partition is the only partition that needs to be fat (a boot partition must be ext2/3/4 but you don't have a boot partition so you can skip that).


SolydXK needs you!
Development | Testing | Translations

User avatar
xendistar
Posts: 475
Joined: 08 Jun 2014 08:17
Location: Bournemouth, UK

Re: new install will not boot but

Postby xendistar » 29 Dec 2018 23:14

Unfortunately still not booting into SolydXK

I did have a little play at things but that did not work either but at least I can still get solydxk via the Super Grub Rescue DVD.

I am calling it a night, if I continue you playing with it I will break it.

Thanks for all the help so far

User avatar
xendistar
Posts: 475
Joined: 08 Jun 2014 08:17
Location: Bournemouth, UK

Re: new install will not boot but

Postby xendistar » 30 Dec 2018 16:24

After a good nights sleep I came back to this this afternoon with a bit of a clearer head and with some success I now have a booting PC. That is the good news, the bad news if there is any is that it is not booting from the SSD.

I have put the /boot/efi on a small partition on one of my two spinning harddisks with / & /home on the ssd (/var & /tmp are on another spinny disk).

I know this was something I tried with Arjen but I think drink and lateness clouded my actions. :facepalm: It was Arjens instructions that pointed me in the right direction this afternoon and got the job done, I just executed them correctly this time.

My thanks to Arjen for his help and patience's :clap:

User avatar
Arjen Balfoort
Site Admin
Posts: 8958
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: new install will not boot but

Postby Arjen Balfoort » 30 Dec 2018 21:13

Congratualations! Still, it's strange that you cannot boot from your SSD.


SolydXK needs you!
Development | Testing | Translations

User avatar
ilu
Posts: 2159
Joined: 09 Oct 2013 12:45

Re: new install will not boot but

Postby ilu » 30 Dec 2018 22:18

The problem is most probably the "sata3 pci-e card". Not all of them boot on all motherboards. It might work ... or not.

User avatar
xendistar
Posts: 475
Joined: 08 Jun 2014 08:17
Location: Bournemouth, UK

Re: new install will not boot but

Postby xendistar » 30 Dec 2018 22:23

As in my case not, but I don't boot the PC very often so at the end of the day make very little difference .

Still got a couple of jobs to do (processor swap to i7 and a dual monitor setup) which will hopefully add a few more years to the life of my PC


Return to “Testing Zone”

Who is online

Users browsing this forum: No registered users and 2 guests