[This message has also been posted to linux.debian.user.]
In article <[EMAIL PROTECTED]>, Mikael Rudberg wrote:
>
> I forgot to add that i told grub to install into /deb/sda as well
>
> On 9/11/07, Mikael Rudberg <[EMAIL PROTECTED]> wrote:
>>
>> Hi
>>
>> Im clutching at straws here, i just purchased an Zonbu (mini pc running
>> Via C7/512 MB ram) and i'm trying to install Debian 4.0 on external USB
>> drive.
>> I've prepped an USB stick with the net install image. Boot's from it and
>> installs debian fine from what i can see
>> When i reboot i see that bios detects the USB-HD properlyi

Not really



>> but instead of
>> showing the kernel to boot it shows only the "Mininmal BASH like" version of
>> grub and no selection box.

That means GRUB doesn't see /boot/grub/menu.lst
BIOS launched GRUB, but GRUB is confused about what's where.


>> I tried to reinstall this time manually making the partitions on the
>> USB-HD
>>
>> sda1 /boot  (ext2) 100 MB bootable
>> sda2 /        (ext3) 20 GB
>> sda3 /swap
>>
>> Same issue again. tried it a couple of more times and once  i got "Error
>> 18" in GRUB

Chapter 14 of the GRUB manual describes the error codes.
"18 : Selected cylinder exceeds maximum supported by BIOS."

Are you sure your sda1 starts on cylinder 1?  It *is* possible
to install a partition on the wrong end of the drive.
But more likely it's looking for a drive that's not there
any more.

There seems to be some disagreement about which disk is which.
I would try some commands into that funny little GRUB shell.
Try this
   find /boot/grub/stage1
or
   find /usr/lib/grub/i386-pc/stage1
That's the example in the manual.  It looks on every partition
where it recognizes a file system.  Or type
   root ( <tab>
and it will list all partitions that might have boot files.
The tab is for name completion.  It's really handy when you are
trying to type the name of a Debian initrd file.

When it tells you where it
found it, you know what device name you'll need.
Perhaps your net install image was (hd0) when you installed,
and the target drive was (hd1), but now that the net install drive
is gone the target drive is (hd0).
This is a good reason to use file system labels in /etc/fstab
instead of device names.

Notice that all drives are "hd" to GRUB.  It doesn't distinguish
between SCSI (on USB or SATA) and "IDE" (on parallel ATA).
And CDs are beyond its comprehension, alas.

If your BIOS has one of the bugs mentioned in the Chapter 13
description of the "install" command, you'll have to install
with the 'd' option to override the wrong info from the BIOS.





>> I'm at a loss as what can be wrong. I tried to search the net but can't
>> find information that help me out here.

That happens all too often.  Folks are too busy to post the
answer when they figure stuff out.


Cameron


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to