LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 02-21-2003, 02:53 AM   #1
Boom
Member
 
Registered: Jan 2003
Distribution: Deadhat 8.0
Posts: 42

Rep: Reputation: 15
Cant boot. My boot.local is misconfigured


Im running Suse 8.1. I realized that hdparm settings arent stored after a reboot so I rooted around and found out I needed to edit my /etc/init.d/boot/local file. I added a line something like this

hdparm -X69 -c3 -k1 /dev/hde

I didnt really understand what the "keepsettings" or k did exactly but I didnt want the setting to change so I put it in there. Upon rebooting it gets to the -k command and I get an IO error and the drive freezes bad. So bad that the drive isnt recognizable by BIOS unless I physically tap on it, I assume the arm gets stuck.

I can boot from CD and get into a recovery prompt where I can navigate around but I dont know how to edit the boot.local file with commands. I type "startx" but i get some error that it doesnt exist. How can I fix this?
 
Old 02-21-2003, 03:09 AM   #2
Texicle
Member
 
Registered: Oct 2002
Location: Northern Ontario, Canada
Distribution: Slackware 10.0
Posts: 789

Rep: Reputation: 30
How did you originally edit the file? If you can boot into a command line, then I'd open the file with your favorite text editor and get rid of that line. However, if the drive works after you tap on it physically, I'd say you've got a hardware problem to work with too. The only editor I've worked with is vi so I'd do this as root in command line:

vi /etc/init.d/boot/local

I would then use my arrow keys to get to the beginning of the line you added and type:

dd

This will delete that whole line. Afterwards, I'd type:

:wq

To write and quit the file. Notice that there is a colon ( : ) in front of wq? That's important. This should at least get you back to a working state. After you're back to normal and you still want whatever you were trying to do to work, come back for help and hopefully someone here will be able to advise you better than I can. Hope this works.
 
Old 02-21-2003, 03:19 AM   #3
Boom
Member
 
Registered: Jan 2003
Distribution: Deadhat 8.0
Posts: 42

Original Poster
Rep: Reputation: 15
I originally edited the file with kwrite. Its weird. The drive only has the problem after I try to do a normal boot into Suse and get the IO error. I can do the recovery boot and its fine, boot into my Windows partiton and its fine, but if I try to boot into Suse normally and get to the point where its processing the boot.local file I get the error and the drive activity light just goes out and its frozen until I beat on the drive. Anyway I'll try the advice you gave me and hopefully I can get it working again. Thanks!

Boom
 
Old 02-21-2003, 11:03 PM   #4
Boom
Member
 
Registered: Jan 2003
Distribution: Deadhat 8.0
Posts: 42

Original Poster
Rep: Reputation: 15
I accessed the boot.local file with vi. Its odd because the file looks totally different from the one I modified to begin with. The one I modified didnt have any code in it it was basically:

###use this file to configure options after booting###

or something similar

I saved the file to my desktop before I alterted it as a backup but I cannot access the desktop from the recovery command prompt. I navigate to my /user and /root dirs and dont see anything.

I even moved the boot.local and hdparm files out of their original directories hoping that would disable them, but I still get the same error, something like

processing /etc/init.d/boot.local

I/O 32-bit
-X69 DMA
-K (keepsettings) command I/O error

The HD light just stays on and everything is frozen.
 
Old 02-23-2003, 05:23 AM   #5
Boom
Member
 
Registered: Jan 2003
Distribution: Deadhat 8.0
Posts: 42

Original Poster
Rep: Reputation: 15
Question

Why is it when I go into a rescue boot none of my changes are saved across a reboot? When I move files or edit files they are unchanged after I reboot. Do I have to save them somehow?
 
Old 03-06-2003, 09:26 PM   #6
Texicle
Member
 
Registered: Oct 2002
Location: Northern Ontario, Canada
Distribution: Slackware 10.0
Posts: 789

Rep: Reputation: 30
Sorry it's been so long, I lost your post. Hopefully your problem is solved by now, but if not, maybe the following will help:

Quote:
Originally posted by Boom
I accessed the boot.local file with vi. Its odd because the file looks totally different from the one I modified to begin with. The one I modified didnt have any code in it it was basically:

###use this file to configure options after booting###

or something similar
Yeah I've heard about editors viewing files differently. It's weird.

Quote:
I saved the file to my desktop before I alterted it as a backup but I cannot access the desktop from the recovery command prompt. I navigate to my /user and /root dirs and dont see anything.
Okay, you should navigate to /home/Boom/Desktop instead (or whatever your user name is if not Boom).

Quote:
I even moved the boot.local and hdparm files out of their original directories hoping that would disable them, but I still get the same error, something like

processing /etc/init.d/boot.local

I/O 32-bit
-X69 DMA
-K (keepsettings) command I/O error
Move them back to where they should be. And then use your vi to edit /etc/init.d/boot.local:

vi /etc/init.d/boot.local

You should be able to edit your file and remove the keepsettings (-K) portion of it by commenting it out with a # at the beginning of the line.

Quote:
The HD light just stays on and everything is frozen.
Hopefully this solves that problem.
 
Old 03-06-2003, 09:30 PM   #7
Texicle
Member
 
Registered: Oct 2002
Location: Northern Ontario, Canada
Distribution: Slackware 10.0
Posts: 789

Rep: Reputation: 30
Quote:
Originally posted by Boom
Why is it when I go into a rescue boot none of my changes are saved across a reboot? When I move files or edit files they are unchanged after I reboot. Do I have to save them somehow?
When you normaly boot, do you boot from floppy or CD-ROM or just off the hard drive? If you're using a boot floppy or bootable CD to do a rescue boot, it is most likely using the startup files from the disk instead of what was saved on your system. Try not booting from a rescue disk and see how it goes. If you need to boot from a rescue disk, type:

root=/dev/hda1

or whatever your root partition is on and you should be able to get to command line and make changes there. Once changes are made and saved you should be able to reboot with the new changes. Hope this helps.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
boot problems...rc.local uh-oh! ryan62580 Mandriva 5 03-11-2005 09:04 AM
boot hangs after running /etc/init.d/boot.local eddieb Linux - Newbie 2 07-18-2004 07:57 AM
rc.local - does not load during boot Beuzekom Linux - Newbie 13 04-28-2004 12:25 PM
rc.local won't run at boot on 9.1 aus9 Slackware 24 04-22-2004 05:35 AM
rc.local not running on boot??? Evilone Linux - Software 1 09-08-2003 02:01 PM


All times are GMT -5. The time now is 06:26 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration