Solved

RH 7.3 reboot problem with /dev/null

Posted on 2004-04-21
5
241 Views
Last Modified: 2013-12-16
Hello,
I have a RedHat 7.3 kernel 2.4.20-13.7 system. everytime I reboot I end up in maintenace mode with /dev/null in read-only mode.

Here is how I fix it:
mount / -o remount,rw ; rm -fr /dev/null* ; cd /dev/ ; ./MAKEDEV null ; reboot
 but doing this everytime is impractical. Does anyone know of a workaround or kernel patch etc... that addresses this?

Thanks,
Q
0
Comment
Question by:qwyjibojones
  • 2
5 Comments
 
LVL 9

Accepted Solution

by:
Alf666 earned 125 total points
ID: 10878830
This will not be easy to find. There must be something (most probably a shell script) that has done something like :

rm /dev/null
whatever > /dev/null

or, much simpler :

cp whatever /dev/null

What you should do is check whether /dev/null is a file or is still a character device *before* rebooting.

If it's still a character device, then it's most probably f*** up by a boot script. Which will be easier to debug.

If it's already a file, then something during your using of your system is messing with it. It's going to be much harder to find.
But there's a slight chance that it's a shell script (or a proggie) you wrote yourself.

If it happens during boot, please tell me when (when does the message first appear).

Please, check this, and come back to me.
0
 

Author Comment

by:qwyjibojones
ID: 10899539
Hmmm...
Now that I need to re-create the problem, it seems to have stopped misbehaving.
I am using the system out of the box, and  haven't had a chance to do any scripting on it,( but it looks as though I am going to have to). I am guessing that some application is trying to use the bit bucket incorrectly, and is corrupting the file.

Are you saying that /dev/null starts out life as a character device and should get chaged once the system is up, to a file?

Do you think it wise to create a kill -or- start script that re-creates /dev/null?

Thanks,
Q


0
 
LVL 9

Expert Comment

by:Alf666
ID: 10901009
No. It should *always* be a character device.
But some script corrupts it. Most probably deletes it. Then, the next script that uses it creates the file.

Yes. It's wise. But it's a problem you'd better resolve. As a second thought, I'd say it's not wise. It's a patch. And if it bothers you, it will force you to fix it. That's wise ! :-)

0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Join & Write a Comment

Network Interface Card (NIC) bonding, also known as link aggregation, NIC teaming and trunking, is an important concept to understand and implement in any environment where high availability is of concern. Using this feature, a server administrator …
I. Introduction There's an interesting discussion going on now in an Experts Exchange Group — Attachments with no extension (http://www.experts-exchange.com/discussions/210281/Attachments-with-no-extension.html). This reminded me of questions tha…
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

706 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now