[ale] Can no longer boot one of my drives - SOLVED

[James P. Kinney III]

You said it better. I was mixing my boot parts. Correct - BIOS has
renumbered things and grub sees the BIOS setup and now chokes. The
kernel is _NOT_ involved yet. 

This should only happen with a BIOS new enough to support booting from a
usb port device.

On Thu, 2007-12-20 at 20:59 -0500, Daniel Kahn Gillmor wrote:
> On Thu 2007-12-20 18:02:22 -0500, James P. Kinney III wrote:
> 
> > The USB device will be seen by the bios as a SCSI drive. The new
> > kernels treat ALL drives as scsi devices. So now the scsi chain is
> > renumbered and the grub device numbering doesn't work since what was
> > drive 0 is now drive 1 'cause the USB drive is now drive 0.
> 
> This doesn't quite make sense to me.  If it's a bootloader problem,
> the kernel isn't even loaded at this stage: It might be loading kernel
> 2.2 for all it knows, right?  So how would the kernel's interpretation
> of the disk ordering affect grub?
> 
> It seems more likely that the BIOS was presenting the USB block device
> as "disk 0" instead of the builtin disk, and grub was just choking on
> that, expecting disk 0 to point to the other device.
> 
> Regards,
> 
>       --dkg
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale
-- 
James P. Kinney III          
CEO & Director of Engineering 
Local Net Solutions,LLC        
770-493-8244                    
http://www.localnetsolutions.com

GPG ID: 829C6CA7 James P. Kinney III (M.S. Physics)
<jkinney at localnetsolutions.com>
Fingerprint = 3C9E 6366 54FC A3FE BA4D 0659 6190 ADC3 829C 6CA7
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part