New server setup does not make hard drive bootable

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Craig,

I was able to confirm that the two machines in question which
exhibited the problem both run BIOS version 107.  However they were
not set to AHCI mode, but rather, Native IDE mode (and I did not try
re-running the provisioning on those).  Using Native IDE mode has
never caused us a problem with either performance or provisioning on
those machines in the past; we routinely load up Fedora and CentOS
without issue on those boxes.  Also note that on a similarly equipped
system which instead runs a DG965SSCK board, BIOS 1669 (not the
latest, but the only BIOS that correctly jives with 8GB of RAM in most
32 bit OSs without jumping through a bunch of hoops), and AHCI mode
manually set by me prior to provisioning, I can confirm that the same
problem exists with that box as well.  Hope that helps.

-Ray

p.s.  For some reason I did not receive a copy of either of the
replies to this thread to my gmail account.  Granted, I'm not
subscribed to gluster-users, but most listserves make everything Just
Work(tm) if the respondants do Reply All, by including the
respondant's email address as well as the listserv's address.  If you
did in fact hit Reply All, maybe something is buggered in the
gluster-users listserv?

>Ray -
>    Can you try something for us? Please make sure you are running BIOS version 107 - >http://downloadcenter.intel.com/Detail_Desc.aspx?ProductID=2929&DwnldID=16929&lang=eng and that your hard drive type is set >to SATA with AHCI. Then please try a reinstall.
>Thanks,
>Craig Carl
>Gluster Inc.
>Sent from a mobile device, please excuse my tpyos.
>On Aug 4, 2010, at 22:43, Ray Barnes <tical.net at gmail.com> wrote:
> Hi all.  The subject says it all.  After installing 3.0.4 in a new first
> server setup, the system does not boot from the hard drive because the
> "bootable" flag is not set in fdisk.  Hardware is an Intel DG35EC board with
> a Q6600 processor, 4GB of RAM and Seagate ST3500320AS drive (500gb).  I was
> able to get it to boot normally by simply enabling the boot flag in fdisk
> and nothing more, using a CentOS rescue CD.
>
> Is this a known issue?  Should I be filing a bug report?
>
> -Ray
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users


[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux