Just try changing the hard disk mode in the bios from LBA to NORMAL or
LARGE just try them all

I had this problem here with a raid 1 system mirrored (I tested both disks
for bootability :-) and I had to set it to autodetect (of course) and set
one to be NORMAL or something like that

I don't know how dos will handle it though this was a 100% linux system so
I didn't care as long as it booted of either disk

the disk in question had like 15,000 clyinders or something like that

On Mon, 13 Mar 2000, Anthony Green wrote:

> Hey all .. 
> 
> Was wondering if any of you could help with the following lilo wierdness 
> 
> Just installed a new harddrive and new clean Debian install. Although
> configuring Lilo ... when my pc boots all I get is "LI" of the usual
> "LILO:" prompt and lilo just halts.
> 
> My /hda1 partition is DOS .. so I put in a DOS bootdisk ... fdisk /mbr
> to clean the mbr and then tried resetting up lilo again from linux (via
> bootdisk) and same thing happened.
> 
> My Linux / partition is on /dev/hdd1  .. and when using fdisk to view the
> partition table it gave me a warning re lilo may not work with it due to
> cylinders > 1024?  But my old hd had 4000+ cylinders and it worked fine ..
> .. lilo is installed on /dev/hda though so it shouldnt matter i thought.
> 
> Here follows some additional info .. stats and conf .. 
> 
> if anyone has any ideas I'd be greatful.
> 
> >cat lilo.conf
> # LILO configuration file
> # generated by 'liloconfig'
> #
> # Start LILO global section
> boot=/dev/hda
> compact
> install=/boot/boot.b
> map=/boot/map
> vga=normal
> delay=20
> # End LILO global section
> # Linux bootable partition config begins
> image=/vmlinuz
> root=/dev/hdd1
> label=Linux
> read-only# Non-UMSDOS filesystems should be mounted read-only for checking
> # Linux bootable partition config ends
> # DOS bootable partition config begins
> other=/dev/hda1
> label=Dos
> table=/dev/hda
> # DOS bootable partition config ends
> 
> >dmesg |grep -i hd 
> hda: Maxtor 7850 AR, 814MB w/64kB Cache, CHS=827/32/63
> hdb: WDC AC31600H, 1549MB w/128kB Cache, CHS=787/64/63, DMA
> hdc: QUANTUM SIROCCO2550A, 2445MB w/75kB Cache, CHS=4969/16/63, DMA
> hdd: FUJITSU MPE3136AT, 8063MB w/512kB Cache, CHS=16383/16/63, DMA
> 
> 
> >fdisk /dev/hda
> 
> Command (m for help): p
> 
> Disk /dev/hda: 32 heads, 63 sectors, 827 cylinders
> Units = cylinders of 2016 * 512 bytes
> 
>    Device Boot    Start       End    Blocks   Id  System
> /dev/hda1   *         1       488    491872+   6  FAT16
> /dev/hda2           489       519     31248   82  Linux swap
> 
> Command (m for help): q
> 
> >fdisk /dev/hdd
> 
> The number of cylinders for this disk is set to 16383.
> There is nothing wrong with that, but this is larger than 1024,
> and could in certain setups cause problems with:
> 1) software that runs at boot time (e.g., LILO)
> 2) booting and partitioning software from other OSs
>    (e.g., DOS FDISK, OS/2 FDISK)
> 
> Command (m for help): p
> 
> Disk /dev/hdd: 16 heads, 63 sectors, 16383 cylinders
> Units = cylinders of 1008 * 512 bytes
> 
>    Device Boot    Start       End    Blocks   Id  System
> /dev/hdd1             1      2032   1024096+  83  Linux
> /dev/hdd2          2033      3048    512064   83  Linux
> /dev/hdd3          3049      4064    512064   83  Linux
> /dev/hdd4          4065     16383   6208776    5  Extended
> /dev/hdd5          4065      5080    512032+  83  Linux
> 
> Command (m for help): q
> 
> 
> When I try and run "lilo" i get the following warning errors :
> 
> >lilo
> Warning: BIOS drive 0x83 may not be accessible
> Warning: BIOS drive 0x83 may not be accessible
> Warning: BIOS drive 0x83 may not be accessible
> Added Linux *
> Added Dos
> 
> 
> Thanks in advance .. 
> 
> -- 
> [EMAIL PROTECTED]
> Anthony Green
> --
> SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
> To unsubscribe send email to [EMAIL PROTECTED] with
> unsubscribe in the text
> 

--
SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
To unsubscribe send email to [EMAIL PROTECTED] with
unsubscribe in the text

Reply via email to