lilo issue after adding hard drive
I added a sata drive in the past week and had problems getting/seeing the drive. Well yesterday I finally got it so I could mount it automatically from boot and access the drive. Here's my post with the info about adding the sata drive.
I went to adjust lilo.conf so that me new image would be the default. Code:
cat /etc/lilo.conf Quote:
My main concern is can I reboot with this lilo issue?? Thanks for any and all help.!! |
A little confusing here since SATA drives normally show up as /dev/sda like the messages said. Not sure if you really want to point to your IDE drive like in your config or if you meant to change this.
lilo -v isn't a good way to install lilo. If you want to install lilo in the MBR, take the boot= line out of your lilo.conf and specify a drive on the command line: lilo -v -b /dev/hda # for your ide drive mbr lilo -v -b /dev/sda # for your sata drive mbr BTW you will boot alot faster if you use compact in your lilo.conf. Just add it on a line after lba32. |
On my machine an ide drive is hda, a sata drive would be sda
Quote:
|
I believe there is a misunderstanding of my lilo.conf file. The part you see as "image = bzImage-S" and "label = Slack_sata" is just were I recompiled my kernel so my sata controller was built into the kernel. Not to boot up from the sata drive. I just wanted to get the sata partition sda4 to auto mount at boot up while I finish building Slack 12 on the sata drive.
to Randux .. I was under the impression that lilo -v was the way to update my lilo.conf after making changes to it in 10.2, but I will give your command a try to see if that is my problem. I will also change lilo so compact is in the line below lba32. I only tried to change the "default" line in lilo.conf so the Slack_sata would be the default and not Slack_10.2.6.2 but didn't work so I changed it back and still have the error I posted above. I just didn't understand why lilo wouldn't update when the only thing that changed was my fstab. Hope this clears things up a bit. Thanks for the help and info. |
Quote:
Quote:
You could also mount it cli with the command mount. Trying it that way should give you some error messages which might help if there is a problem. For example: Quote:
|
Quote:
I don't know what's causing the lilo error.?? Or if I can just reboot without any problems?? Thanks for your help Justwantin.. |
Sometimes I just back up and start from scratch ..... again. Then methodically work through the whole thing again one step at a time until it breaks or continues working correctly
If I were you I'd run liloconfig and let slack make me a new simple lilo and install it to MBR and see if it all works with the default kernel. Then edit and add stanza and for another kernel and see if that works. Also I am wondering if there is something out of ordinary with your sata drive or maybe the kernel you compiled. Sorry I can't be of more help but happy to help a tarheel anyday. |
Quote:
Also is there a way to update fstab?? Quote:
Thanks, |
One thing I do notice about /dev directory. There isn't a device name sda or sda1 but there is a hda and hda1. There is sda2 -sda15. I also commented out the /dev/sda3 from fstab. I'm still unsure about rebooting. I'll try running liloconfig later on today.
|
Don't specify a default in lilo. Maybe you have the syntax wrong. Let it give you a menu, and you choose which one to boot. Maybe this will boot the right kernel.
I don't know why you don't have an sda unless you messed up your partitioning. What do you get from fdisk -l? (that's a little L, not a number 1) |
Code:
# fdisk -l Code:
# cat /proc/partitions Thanks Randux, |
For comparison this is what I get when I run fdisk -l. Note that there are there are details of both hda and sda partition schemes as well as drive details. Have you left out partr of your fdisk -l output or is that all you get when you run the command?
Quote:
Do not be worried about re-booting. If lilo doesn't work you can use your install disk to boot your machine if it doesn't. |
Hi,
Quote:
Quote:
Quote:
I like to use; Code:
~#lilo -v -t -b /dev/hda #test the lilo.conf for hda |
Does anybody know why his sata drive doesn't show up in fdisk -l? That's not good.
|
Gary, what I meant by that when I said lilo -v isn't a good way to install lilo, is because I have seen it get messed up when there's more than one drive. Therefore I make a point never to specify a boot= parm in the conf, I specify -b on the command line (which I think you were the one who told me!). Also, I often run big multiboots and I write lilo to all the MBRs so I can still get to any system if one drive dies.
|
All times are GMT -5. The time now is 03:03 PM. |