System fails to boot after fresh install on IDE NANDrive
 

Hi.

I'm having problems with my Debian install. The install is successful all the way trough, with the problem starting on reboot. Grub doesn't load, and I don't get any indication on the screen.

I've tried to install to the systems NANDrive HDD, as well as installing to a USB flashdrive. I've changed my installation medium to a different USB, etc.

What am I doing wrong?

My system is a enbedded system, with config:
Phoenix secureCore BIOS
IDE HDD - 2GB NANDrive
CPU: Atom Z510
RAM: 512MB

Pic of motherboard:
https://ibb.co/g9A4VS

** SOLUTION **
Problem was BIOS not recognising the GRUB boot loader in the MBR due to IDE NANDrive setup.
Solution involve creating a PuppyLinux flashdrive (with unetbootin). Next was running the GRUB4DOS tool found in the menu and replacing the MBR with GRUB4DOS bootloader. Everything worked fine after reboot.

Do you get any error messages?

You could try booting to the installation media and updating/reinstalling GRUB. https://www.brighthub.com/computing/...les/36648.aspx

Tried reinstalling GRUB, didn't work. Tried installing Ubuntu after that, same result. Did another GRUB reinstall and MBR fix with the boot-repair tool from the YannUbuntu PPA, which then suceeded in displaying a screen telling me that there is no OS. I've checked the NANDrive and USB flash for system files, and everything is there.

Maybe the board is corrupting everything somehow during install? Live Debian and Ubuntu runs fine thou.

Maybe missing files. Try again from 0

Linux Support

You may try reinstalling grub from Debian Recovery option(in Debian Installation DVD).

1. Boot into DVD
2. Select Graphical Rescue option
3. Go through devices and files loading and other configurations as you did at time of installation(everything is automatically done.
4. After all you will have 3 or 4 choices including
5. Select Reinstall GRUB Bootloader
6. Enter the device address, on which you installed like /dev/sda(be carefull, you've to only give path to device and not to partition as well as you should select right that one on which you installed.)
7. After Installation reboot
8. Try to boot into device(if device is not first to be booted).

Maybe the drive(s) you're installing to are 1. not in the boot sequence or 2. not bootable devices. For instance, SSD drives added to a PCI slot are not bootable unless the bios allows specifically is made for it.

I'll try it, thanks.
Did from zero multiple times, Changed install medium, and changed the computer from where i "burned" the USB flash. Tried with DD and with etcher. Same result.

The NanDrive is in the boot sequence, as well as the USB flashdrive. Tried installing to the flashdrive several times, which should work as it's possible to boot into live systems from flash drives. Leaves me banging my head to the wall...

to out of curiosity, I'd try this, after install or by whatever means available to me. I'd create a SuperGrub2 usb Stick, then after that I'd use that to boot from then have it search the HDD's to see if it finds a boot drive, then have it boot it to see if you can get in.

If anything it should give you a clue to what maybe going wrong if it does not find anything. If you get in then you're able to try and elevate the issue with your grub. and you'll know you have at least one means of getting in to your system until you do.

https://www.supergrubdisk.org/super-grub2-disk/

Tried it previously, but I'll try it again due to faulty USB Flash drive from before.
This shitty embedded system is seriously weird.

yes, it is that dummy hdd I bet emm and such as that ... someone with the know how really needs to get on the stick with that. Seeings how more and more Laptops and smaller systems are using that type of medium other than the conventional hdd, or sdd to install a Linux OS that needs grub. From what I've seen in here and people having issues with it. but that just my option.

I have not reviewed this in its entity. But I do know slackware has a bootable usb stick option after install. ;) it should still work. I've never had to give it a try.

I have not reviewed this in its entity. But I do know slackware has a bootable usb stick option after install. ;) it should still work. I've never had to give it a try.[/QUOTE]

Interesting, got to try that. I'll be doing a full review of all the options and try out the suggestions in the coming weekend. I'll get back to the thread with the results.

how is your drive partitioned? What is the ouput of fdsik -l?

Don't have any advanced setup for partitioning, just a swap and a root partition that's it. I did try with a separate boot partition, but that didn't have any effect. Tried ext2 and ext4 for root (don't really need any journalling).
I'll get back with output for fdsik -l in the weekend.

Had some extra time on my hands today and decided to give it a last go before trashing it directly out of the window.
Got thinking about possible issues as to why it refused to boot. I got a hint earlier with the experimentation that I did, when I reinstalled MBR, which at least gave me some indication that I could perhaps be related to the GRUB boot loader.

Lo and behold. Thought of puppy Linux and the bootloader that it was using GRUB4DOS and decided why not use that one, and see if the problem still persists?
Did a fresh install of Debian to the Nandrive, marked the root partition bootable. Booted up PuppyLinux and ran the GRUB4DOS program which overwrote MBR and installed GRUB4DOS. restarted the computer, and everything runs smoothly.

Would like to thank everyone for spending time trying to solve the problem with me.

PS: is there a way to change the title to "System fails to boot after error free install on NANDrive"
So people can find the solution more easily in the future?

go back to your original post then select edit, then advance then look for your heading slot to change it.

Glad you figured it out.