DragonFly BSD
DragonFly bugs List (threaded) for 2004-12
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: Re[2]: /boot/loader bug

From: Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>
Date: Mon, 20 Dec 2004 16:28:00 -0800 (PST)

:Hi Matt,
:MD>     Hmm.  We didn't change anything in that part of the loader.  It should
:MD>     have been able to still identify the disk.
:It does...maybe it's because of the biosdisk.c patch? The problem
:occured with todays cvsup (didn't do it yesterday). The releases
:before the patch was brought in worked fine for months.
:MD>     What does it say about your BIOS drives?
:It says
:BIOS drive C: is disk0
:BIOS drive D: is disk1
:which is perfectly correct. Anyway, when I press F1 to boot the
:default, it bombs out with the "Cannot work out..." message.

    Hmm.  I would have expected F1 to refer to the first disk and F2 to
    refer to the second one, though I'm not sure what happens if the first
    disk is not marked bootable. 

    Try recompiling your loader up with -DBOOT_BIOSDISK_DEBUG=Y and
    lets see if the extra information it spews out helps.  I don't see
    anything that could mis-identify the disk.

    Also disable the boot menu (in case the loader is still pushing into
    it), so you can see all the debug messages.  You can do that by 
    commenting out the beastie-start line at the end of /boot/loader.rc.

    Another thing that would be useful would be the fdisk output for both
    of your hard drives.  i.e. boot the CD and post the output of 'fdisk ad0'
    and 'fdisk ad4' (or whatever device ids the kernel assigns to those 
    two HDs).

					Matthew Dillon 

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