no linux after reboot

[Grant Allan]

> On Sat, Dec 10, 2005 at 04:41:59AM +1300, Grant Allan wrote:
>> >> On Sat, Dec 10, 2005 at 03:18:32AM +1300, Grant Allan wrote:
>> >>> >> hi,
>> >>> >>
>> >>> >> i have some more news: grub.conf looks OK to me.
>> >>> >> but grub-install generates an error as follows:
>> >>> >>    /dev/hdd1 does not have any corresponding BIOS drive
>> >>> >>
>> >>> >> does that maybe mean that i should jump into BIOS and get it to
>> >>> >> autodetect
>> >>> >> my hard drives?  i forgot to do that yesterday.
>> >>> >
>> >>> > It's probably already doing that.  It's unrelated.
>> >>> >
>> >>> >> cheers,
>> >>> >> grant
>> >>> >
>> >>> > Just another detail to take care of what the installer missed.
>> After
>> >>> > you have chrooted to /mnt/sysimage, edit /boot/grub/device.map to
>> add
>> >>> > the line
>> >>> >
>> >>> > (hd3)     /dev/hdd
>> >>> >
>> >>> > assuming "hd3" is not mapped to some other device.  Note that in
>> >>> > grub.conf, numbering starts at 0, not 1.  Then do the grub-install
>> >>> > thing.  If that doesn't work, you may need to tell us more about
>> the
>> >>> > drive and partitioning arrangement, and post grub.conf, if you
>> can.
>> >>> >
>> >>> > Cheers,
>> >>> > --
>> >>> > Bob McClure, Jr.
>> >>>
>> >>> Hi,
>> >>>
>> >>> Yay, I'm no longer getting windows!  Furthermore, I have learned
>> today
>> >>> about bottom posting.
>> >>
>> >> Hurray!  And don't be afraid to trim unrelated or unnecessary cruft
>> >> like mailing list footer and excess lines in the sigs.
>> >>
>> >>> However, I now have the following on rebooting my machine:
>> >>>
>> >>> GRUB Loading stage1.5
>> >>> GRUB loading, please wait...
>> >>> Error 21
>> >>>
>> >>> To make sure I tell you the right stuff regarding partitions &
>> disks,
>> >>> please can you tell me if there is a way to query for this info
>> (e.g.
>> >>> using linux rescue)?
>> >>
>> >> Hmm.  I dunno.  If you have another machine on your local net, maybe
>> >> you could start up networking during the rescue startup, then chroot
>> >> to /mnt/sysimage, and then you could scp (secure cp using SSH) the
>> >> info to another machine.
>> >>
>> >>> I have both put old and new hard drives on the one ribbon, but by my
>> >>> understanding that doesn't add up with the name /hdd, so I'd like to
>> >>> find
>> >>> out for sure.
>> >>
>> >> That's correct.  Here's how the labeling goes:
>> >>
>> >> Controller  Drive   Device   Grub map
>> >> ---------   -----   ------   --------
>> >> Primary     Master  /dev/hda (hd0)
>> >> Primary     Slave   /dev/hdb (hd1)
>> >> Secondary   Master  /dev/hdc (hd2)
>> >> Secondary   Slave   /dev/hdd (hd3)
>> >>
>> >> I might also mention that, in general, jumpering drives as Cable
>> >> Select (CS) is evil.  Just jumper the drives as master and slave as
>> >> appropriate.  That _always_ works.
>> >>
>> >>> Thanks again,
>> >>> Grant
>> >>
>> >> Cheers,
>> >> --
>> >> Bob McClure, Jr.             Bobcat Open Systems, Inc.
>> >
>> > ok,
>> >
>> > so since my second hard-drive is on the same ribbon as /dev/hda, i
>> expect
>> > it to be hdb, not hdd.
>> >
>> > this makes it odd that calling grub-install generated an error that
>> > "/dev/hdd1 does not have any corresponding BIOS drive"
>> >
>> > is it possible to fire up that druid thingy from the rescue cd to see
>> if
>> > the names are mixed up?
>> >
>> > cheers,
>> > grant
>>
>>
>> hi,
>>
>> my new drive is jumpered to be slave.  (but i didn't check whether the
>> existing disk was master, just assumed it would be.)
>>
>> i have run up qtparted on a "system recovery CD" that i have.  it
>> confirms
>> that my disks are /dev/hda and /dev/hdd.  partition details:
>>
>>  /dev/hda1  80G    ntfs     Active
>>  /dev/hda-1  8M    free
>>
>>  /dev/hdd1  100M   ext3     Active   /boot
>>  /dev/hdd2  2G     fat32
>>  /dev/hdd3  10G    ext3              /home
>>  /dev/hdd4  25G    extended
>>   +-- /dev/hdd5    unknow
>
> Hmm.  That's odd if you're certain that the new drive is on the cable
> to the primary controller.  I'd be interested in how the BIOS reports
> the drives during POST (power-on self test, i.e. boot).
>
> I also wonder why it lists /dev/hdd5 as unknown.  What is your root
> partition?
>
> But if "linux rescue" mounts it without carps, I'd run "mount" or "df"
> before doing the chroot, to see what is where.
>
>> cheers,
>> grant
>
> Cheers,
> --
> Bob McClure, Jr.             Bobcat Open Systems, Inc.

"mount" says:
/dev/VolGroup00/LogVol00 on / type ext3 (rw, defaults)
/dev/hdd1 on /boot type ext3 (rw, defaults)
/dev/hdd3 on /home type exts (rw, defaults)
/dev/hdd2 on /mnt/fat32 type vfat (rw, defaults)
/dev/proc on /proc type proc (rw, defaults)
/dev/sys on /sys type sysfs (rw, defaults)

i don't see any POST, the error is pretty much instant.  but i've just
gone to BIOS and seen that Primary Drive 1 is set to "OFF".  hmmm... might
tweak that and see what happens.

cheers,
grant