Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
for soem reason when i set up my computer, i had my primary hard drive as my secondary slave... now i have a second hard drive, and i want my primary hard drive to be my secondary master and my secondary hard drive to be my secondary slave, however i am getting problems when trying to start up my computer, and i think i need to edit lilo.conf.... here is what my lilo.conf is right now
no, i didnt run /sbin/lilo, i just reset my computer... they arent the primary because.... i dont know, because i wasnt paying attention while putting my computer together... and when i run it, it will get into lilo, but when i try to run linux it will say error in hdd6, try passing init= to kernel... im runing mandrake 9.1... and is there any other files i need to edit?
ok, now im really screwed.... i tried changing the /etc/fstab and now when i try to boot up linux, it wont even work... i can get into a shell command as root, but it wont let me edit /etc/fstab even if i try to change the permission.... WHY IS THIS SO DIFFIUCLUT!!!
Okay - well, lilo.conf tells what should be written but you have to run lilo to actually write it. Just rebooting won't work. This is one thing a lot of people prefer about grub but it's absolutely no problem to do. If it's an issue, you can probably just make a 'configlilo' shell script like
- and, actually, I don't remember but Mandrake's probably got some nifty GUI for it.
Might be easier, at some point, to go ahead and hook 'em up as primary but you had it working before, so you can get it working again, either way.
I'm lost though - you got an error about 'hdd6' in one post. Is that still an issue? Now you can boot without errors and login as root but can't edit /etc/fstab?
Try 'root=/dev/hdc6 rw' or, after booting, 'mount -w -n -o remount /'. I'm guessing - guessing, now - that the reason you can't edit the file even as root is because /'s mounted read-only. But I'm not sure if I'm following everything. If you can get to a root prompt without boot errors, you should be most of the way there.
If this doesn't work, guru help is needed. I usually just wing it, myself.
here is what happened... i editied /etc/fstab and i had some boot problems... now when i try to boot i get into this "repair filesystem" place and i cant do anything.... now my /etc/fstab is blank, and i cant edit it at all... i have a /etc/fstab.OLD which is what i want, but i cant move it because it wont let me write to /etc/fstab... i tried the mount -w -n -o remount / and it had an error about /etc/fstab.... do you know where i can get a mandrake 9.1 bootdisk image... because my boot disk right now sucks, its some slackware one because i didnt make one when i installed mandrake... and you were rigth when you said that / is mounted as read only, but i cant remount it! jeez, sometimes linux really gets on my nerves
oh, and the problem that i had with running /sbin/lilo was that when i ran that my hd was connected as hdd and when i tried running that the lilo.conf was pointing to hdc, but there was no hdc attached, so after running that it gave an error saying that hdc did not exist...
Well, I'm learning all about how little I know about the filesystem and permissions today with a bunch of directories that won't go away.
Sounds like you might be needing to run fsck. Came across this bit of weirdness:
For compatibility with Mandrake distributions whose boot scripts depend upon an unau-
thorized UI change to the fsck program, if a filesystem type of loop is found in
fslist, it is treated as if opts=loop were specified as an argument to the -t option.
Anyway - like I say "Calling all gurus!"
But for future reference, make sure all your drives are all hooked up and everything's how you want it before rebooting. I can screw up all kinds of things and have additional terminals to go to to fix stuff but, once you reboot, what's done is done without a lot more effort.
Um, as far as the bootdisk, maybe see if Mandrake has some emergency disks on a mirror or something. You should be okay, though, as something like Tom's Root/Boot would be used for recovery and isn't a Mandrake disk. As long as the box comes up and the filesystem's accessible, I guess. Just need to figure out how to get to where you can edit the file again.