Jump to content
XPEnology Community

gnoboot - stuck in POST HDD Detection after install


neolabs

Recommended Posts

Hi there, first post, but i'm following this amazing project since almost 2 years, so many changes ...

 

I've just tryed the gnoboot work and i have an ununderstanding issue with 2 differents motherboard : Asus P5QL and Asus P5Q

 

1 i boot on the usb stick with the gnoboot img, choosing the gnoboot.me boot, running Synology assistant to upload the original .pat file = working great

 

the "Nas" need to restart, and then, when still in the POST, the motherboard scanning the HDD drives, and get stuck when detecting the only one I put in.

 

I've tryied with 3 differents hard drive, many different size.

 

To make it work, i have to unplug the HDD when booting up the computer, and then, just before running the automatic boot from gnoboot, i have to replug the drive.

 

- - -

Latest bios installed on the 2 mobos, SATA drives in AHCI.

 

If i want to make the computer boot again with a normal HDD detection in the POST, i have to delete all the partitions ...

Link to comment
Share on other sites

How about using a Linux livecd with your disks connected, does it work?

 

I think this more of a hardware problem or something. It doesn't even load the GRUB and kernel. You can also try changing from AHCI to IDE mode, check if that works.

Link to comment
Share on other sites

if i delete the partition on the hard drive, the computer didn't get stuck.

 

It appends on the first reboot, after uploading the .pat file.

 

If i don't unplugged the drive before the motherboard check the Hard drive.

 

If the sata mode is in IDE mode, the computer start normally ... the problem seems to be with the AHCI mode ...

Link to comment
Share on other sites

if i delete the partition on the hard drive, the computer didn't get stuck.

 

It appends on the first reboot, after uploading the .pat file.

 

If i don't unplugged the drive before the motherboard check the Hard drive.

 

If the sata mode is in IDE mode, the computer start normally ... the problem seems to be with the AHCI mode ...

 

A quick google resulted to this. So i think this more of hardware bug/limitation.

Link to comment
Share on other sites

×
×
  • Create New...