Registered: Nov 2003
Location: Eagle, Idaho
Distribution: Fedora Core 1, SuSE Server 9.0
Posts: 23
HCL Entries: 0
Reviews: 0

I am having problems getting my server to boot up because as soon as I start to mount filesystems, it says that it is having problems because it can't write to /dev/null. I'm not sure why exactly this would be necessary, but oh well. It doesn't work. i can't even get my system to get to a workable point. It freezes in boot when it fails to mount all of the filesystems and then puts me into shell so that I can fix the problem. The thing that mystifies me is that it is still able to read the filesystem because I can see everything on the hard drive when i get into shell. Any suggestions on how to fix this? I'm completely stumped. This is the first time that I have ever had anything like this happen to me. Thanks for any help that anyone can provide.

I'm running Fedora Core 1 with a few updates
Athlon 1.4GHz
512 MB Ram
40 GB hard drive (100 mb /boot, 1 gb swap, the rest for /)
60 gb hard drive (/home)
dual NICs
ATI graphics card (although I feel that this information might be irrelevant)

Thanks

-Jalsk

Report this post to a moderator | IP: Logged

Registered: Feb 2003
Location: Atlanta, GA
Distribution: RH 7.2/7.3/9, RHAS 2.1, RHEL3
Posts: 320
HCL Entries: 0
Reviews: 0

Try this from your shell:

code:

mknod -m 666 /dev/null c 1 3 
chown root.mem /dev/null

__________________
Registered User #319990
If I helped you, please rate my post by clicking here

Report this post to a moderator | IP: Logged

Registered: Mar 2004
Location:
Distribution:
Posts: 61
HCL Entries: 0
Reviews: 0

as root exec 'chmod 666 /dev/null' and try again

Report this post to a moderator | IP: Logged

Registered: Nov 2003
Location: Eagle, Idaho
Distribution: Fedora Core 1, SuSE Server 9.0
Posts: 23
HCL Entries: 0
Reviews: 0

That didn't work. Here is exactly what I'm getting:

/etc/rc.d/rc.sysinit: line 88: /dev/null: Read-only file system
/etc/rc.d/rc.sysinit: line 91: /dev/null: Read-only file system
Configuring Kernel Parameters: Dup2: Bad File Descriptor
[ FAILED ]
Setting clock (localtime): Mon May 10 07:33:20 MDT 2004 dup2 bad file descriptor
[ FAILED ]
Loading Default keymap (us): /etc/rc.d/rc.sysinit: line 159: /dev/null: Read-only file system
[ FAILED ]
Setting hostname mercury: dup2: Bad file descriptor
[ FAILED ]
/etc/rc.d/rc.sysinit: line 183: /dev/null: Read-only file system
Initializing USB controller (usb-uhci): dup2: Bad file descriptor
[ FAILED ]
/etc/rc.d/rc.sysinit: line 194: /dev/null: Read-only file system
Checking root file-system
dup2: Bad file descriptor
[ FAILED ]

*** An error occured during the file system check.
*** Dropping you to a shell: the system will reboot
*** when you leave the shell.
Give root password for maintenance
(or type Control-D to continue):

Report this post to a moderator | IP: Logged

Registered: Mar 2004
Location:
Distribution:
Posts: 61
HCL Entries: 0
Reviews: 0

please post output of:

ls -la /dev/null

Report this post to a moderator | IP: Logged

Registered: Nov 2003
Location: Wellington, New Zealand
Distribution: RH9 Kernel 2.4
Posts: 4
HCL Entries: 0
Reviews: 0

try the following:

mount -o remount, rw /
rm /dev/null
mknod -m 666 /dev/null c 1 3

Report this post to a moderator | IP: Logged

Registered: May 2004
Location: Uruguay
Distribution: Linux Red Hat 9.0
Posts: 5
HCL Entries: 0
Reviews: 0

I fixed that same problem in RH9

( post #7)

Last note help me to fix this problem. I don't know how It happend, but I was "playing" with users accounts in /etc/passwd and changed UID.

Thanks for help me

Report this post to a moderator | IP: Logged

Registered: Feb 2003
Location: Detroit, MI USA
Distribution: RedHat 8.0
Posts: 14
HCL Entries: 0
Reviews: 0

That last reply fixed the same problem for me.

My boss was ready to toss me AND the Linux server out.

__________________
jnr

Report this post to a moderator | IP: Logged

Registered: Jul 2004
Location:
Distribution:
Posts: 2
HCL Entries: 0
Reviews: 0

quote:

---

try the following:

mount -o remount, rw /
rm /dev/null
mknod -m 666 /dev/null c 1 3

---

Report this post to a moderator | IP: Logged

Registered: May 2004
Location:
Distribution: Slackware 9.1, Red Hat 9, NetBSD
Posts: 369
HCL Entries: 0
Reviews: 0

No user should have /dev/null as a home directory because /dev/null is never a directory, it is a device file. When you made the account, you probably removed /dev/null and recreated it as a directory. You need to rmdir /dev/null and recreate it using the directions given upthread. Any directions telling you to make a user with a home directory of /dev/null are flawed. Use /fake or some other nonexistent directory for a user that is not allowed to log in and will own no files.

Report this post to a moderator | IP: Logged

Registered: Jul 2004
Location:
Distribution:
Posts: 2
HCL Entries: 0
Reviews: 0

cannot delete directory as it says it is not empty.

try ls /dev/null and it returns nothing (indicating that there is no contents in the directory)

How do I deal with these conflicting reports?

Report this post to a moderator | IP: Logged

Registered: Jan 2004
Location: Roughly 29.467 / -81.206
Distribution: FreeBSD, NetBSD (the ones I do work on)
Posts: 305
HCL Entries: 1
Reviews: 3

cd /dev
rm -rvf null/

And for god's sakes... be careful with that command. More sysadmins have killed their systems with than than {cr,h}ackers ever will.


The reason it says the directory isn't empty is because it probably has some hidden files.


Now... follow the mknod and chmod commands listed above... then reboot.

EDIT: While it is not wise to have a usr directory of /dev/null it can be done. As long as that directory stays as a device. Any files saved will be thrown away and any attempts to read files will find none. But it is wiser to create a folder like, /tmp/emptydir and make that the home directory.

Last edited by frob23 on 07-17-2004 at 11:11 AM

Report this post to a moderator | IP: Logged