I deleted my /dev/null. How can I restore it?
Asked
Active
Viewed 4.4k times
72
-
6I once found that /dev/null was replaced with a normal file which only root could write to. I thought for a moment that I would have to reinstall everything but as mentioned below, the recovery is trival if you know the trick. – Stuart Woodward Dec 24 '11 at 12:15
-
1I managed to remove /dev/null by getting my pipe wrong flipping $ and & around when running an rm command in a script. Ouch! – flickerfly Oct 09 '15 at 22:28
-
@flickerfly You develop scripts as root? – Thorbjørn Ravn Andersen Jan 14 '20 at 14:02
-
3If the permissions are required, you have to test it eventually. Didn't say it was in production. – flickerfly Jan 14 '20 at 15:27
3 Answers
100
mknod /dev/null c 1 3
chmod 666 /dev/null
Use these command to create /dev/null or use null(4) manpage for further help.
steve
- 21,582
- 5
- 48
- 75
harish.venkat
- 7,313
- 2
- 25
- 30
-
5For completeness, I'd note that this applies to all linux-based systems; other systems may have different numbers. – Random832 Dec 21 '11 at 14:53
-
2Also this only sets up the device file itself, it will not restore its permissions. You'll have to `chmod go+w` it manually. – Attila O. Jul 03 '15 at 09:44
-
7
-
14
-
1`mknod -m 0666 /dev/null c 1 3` worked perfectly to restore /dev/null on CentOS 7, just to let other know. – Bozzy Jan 24 '19 at 10:13
-
I managed to totally bork my `/dev/null`, and these commands didn't help. A reboot reset everything for me. – Gamma032 Sep 14 '22 at 00:58
35
Under many traditional unices, you can recreate devices with their default permissions with the MAKEDEV script. This script is traditionally in /dev but is in /sbin on Ubuntu. Pass it an argument that indicates what devices you want to create; on Ubuntu that's std (you can write MAKEDEV null as well, that creates null as well as a number of other devices).
Under modern Linux systems running udev, you can tell udev to recreate all or some devices based on available drivers and connected hardware, through udevadm trigger:
udevadm trigger --sysname-match=null
Gilles 'SO- stop being evil'
- 807,993
- 194
- 1,674
- 2,175
-
Is this answer still current? I'm on CentOS 7 and I've just overwritten my /dev/null by mistake, the `udevadm trigger --sysname-match=null` trick didn't work for me, while `mknod -m 0666 /dev/null c 1 3` worked perfectly. – Bozzy Jan 24 '19 at 10:11
-
@Bozzy I know it worked with the pre-systemd udev. I haven't tried recently, but as far as I know this should still work. If you add `--verbose`, does it list `/sys/devices/virtual/mem/null `? – Gilles 'SO- stop being evil' Jan 24 '19 at 22:49
-
Yes, it lists that. I've tried to overwrite again /dev/null on my dev machine, but strangely enough I'm unable to do it here, so I can't do a more in-depth analysis now... – Bozzy Jan 25 '19 at 10:18
0
When I accidentally deleted /dev/null, a simple sudo rebootseemed to restore it.
It did cause my desktop icons to go crazy, but no damage seemed to be done
If that doesn't the other answers probably will be more help
