I have a Seagate Barracuda that I'd like to use as the only drive in box
I have. I was able to go through the install but have noticed that 
DiskDruid seems to make one primary partition, and put the rest on
extended partitions (not what I want). So I used fdisk. Anyhow all that
worked and the system came up after the install finished. So I spent 
some time configuring devices and had everything working. Then I decided
to put kernel 2.2.2 on it. I compiled the source and changed the links 
in /boot and made a new initrd and edited /etc/lilo.conf and ran lilo
and upgraded all the necessary RPMs. Anyhow I should have written down
the message that lilo gave me, but it said the same thing five times, 
twice before saying it added the first entry, and three times after. The
message had something to do with "may have trouble accessing drive 
<hex #>." Anyhow I thought it was in reference to the cylinders thing so
I ignored it. Now when I try to boot off that drive, it gets as far as
"LI" and just beeps (a bunch of short ones, not one long one). So here's
the info from fdisk:

[root@sark /root]# fdisk /dev/sda
The number of cylinders for this disk is set to 2006.
This is larger than 1024, and may 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/sda: 64 heads, 32 sectors, 2006 cylinders
Units = cylinders of 2048 * 512 bytes

   Device Boot    Start      End   Blocks   Id  System
/dev/sda1   *         1      701   717808   83  Linux native
/dev/sda2           702      902   205824   83  Linux native
/dev/sda3           903      967    66560   82  Linux swap
/dev/sda4           968     2006  1063936   83  Linux native

Command (m for help): q


I though that since the root partition (sda1) was under 1024 cylinders
that I wouldn't have a problem. I tried to use a rescue disk but it
gave me an IO error after the prompt for the ramdisk. I tried Tom's root
boot but that asked for a ramdisk (though tomsrb didn't need one) so I
hit enter and it gave me a kernel panic. I'm running off an IDe drive 
but would like to have the SCSI one work so I can put the IDE in another
box.


-- 
__________________________________________________
 Justin Georgeson                    
 Institute for Advanced Technology -- System Administrator 
 University of Texas at Austin -- Dept. of Computer Science 
 http://www.cs.utexas.edu/users/pyros
 [EMAIL PROTECTED]
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]

Reply via email to