### BEGIN /etc/grub.d/40_custom #### This file provides an easy way to add custom menu entries. Simply type the# menu entries you want to add after this comment. Be careful not to change# the 'exec tail' line above.### END /etc/grub.d/40_custom ###

So have you managed to get into the BIOS by shutting down (not reboot) your PC .. then turning it ON, and as soon as you see the POST (Power On Self Test) screen or the manufacturer logo, hitting the "Del" key ?

Logged

WARNING: You are logged into reality as 'root'logging in as 'insane' is the only safe option.pcnetspec.co.uk

So have you managed to get into the BIOS by shutting down (not reboot) your PC .. then turning it ON, and as soon as you see the POST (Power On Self Test) screen or the manufacturer logo, hitting the "Del" key ?

Shutting down didn't work.I've tried [F8] Boot selection and tried all HD's but only SDC (500Gb) boots.I think the BIOS has crashed and I need to recover it but as I mentioned in my last post, I cant seem to download the installer!

What I think is happening is that the boot order changed (probably back to sda) but this isn't important if it's always going to be there .. we can tell GRUB to install to the sda MBR, but point to Kubuntu on sdc1.

The only way to be 100% sure is to access the BIOS .. and this would be easier .. but installing GRUB to the MBR of sda won't hurt anything (you'll still be able to boot how you are now), it just might not work.

You could try resetting the BIOS back to defaults with the jumper on the motherboard .. do you know how to do that ?(don't do it yet)

Have you tried a different keyboard ? .. preferably a PS/2 keyboard to access the BIOS ?

Logged

WARNING: You are logged into reality as 'root'logging in as 'insane' is the only safe option.pcnetspec.co.uk

Glad you got it working Out of interest, what's the default option in the GRUB menu now? I suspect you're using the GRUB that's on sda, unless you changed the boot order in the now-working BIOS? Anyway, many ways to skin this cat, glad it's working now.

Incidentally, it's worth playing with Manjaro in a VM (such a Virtualbox) before plumping for an installation on hardware. It's good practice, as it allows you to get familiar with an OS without risk of damaging everything. You can snapshot it so if the OS does break, you can roll back easily, plus you can keep a browser window open in the host OS while working in the terminal (outside of X) in the guest. VMs are awesome