I had the same problem on mi computer when i installed ANY 64bit OS

In my case it was: when you boot from a CD (any bootable 64bitOS), the bios
maps the hard drives in diferent order when you boot from your hd.

When i boot from CD mi SATA for the grub is hd1 (hd1,0) for kernet partition
BUT when i boot from the hd the SATA is (hd0,0). Don't ask me why, but it
happened to my on win64 & gentooamd64 but not on win32, so copy your boot
configuration in grub.conf and make 3 boot options one with hd0, hd1, hd2...

I World bet one of those will start

I have an MSI, with Nforce3 Ultra chipset, Bios 1.c or something like that.

Hope helpful, write back if you need help.






-----Mensaje original-----
De: Boyd Stephen Smith Jr. [mailto:[EMAIL PROTECTED] 
Enviado el: sábado, 11 de marzo de 2006 2:58
Para: gentoo-amd64@lists.gentoo.org
Asunto: Re: [gentoo-amd64] /dev/hda1 won't mount from grub

On Friday 10 March 2006 07:13, "Gavin" <[EMAIL PROTECTED]> 
wrote about 'Re: [gentoo-amd64] /dev/hda1 won't mount from grub':
> Do you mean to 'touch' everything in /boot?  Yes I added 'notail' to the
> fstab entry.  Should I make /boot ext2?

Yes, something along the lines of:
find /boot -type f -print0 | xargs -0 --no-run-if-empty touch

If you like reiser'd boot, the notail thing is a minor issue.  In fact, 
adding notail can make reiser faster as the expense of storage space (but 
you'd loose that storage space to any other filesystem anyway...)

*I* run ext2/3 on boot because when I installed I didn't know 2 things (1) 
notail makes grub work or (2) you can tell reiser to use less than 33M for 
journal.  Also, it can make some system recovery easier -- since ext2/3 is 
the most widely built-in filesystem, among linux kernels.

-- 
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh
-- 
gentoo-amd64@gentoo.org mailing list


-- 
gentoo-amd64@gentoo.org mailing list

Reply via email to