[dm-crypt] Are /dev objects required for clean shutdown?
arno at wagner.name
Tue Feb 6 17:15:12 CET 2018
from my experience copying Linux (Debian) installations,
you statically need /dev/console and /dev/null, everything
else will be created automatically. The static device files
will canish when the devfs is mounted on /dev/ and recreated
as well. But they seem to be needed before that happens
or booting hangs.
For Debian, these can be generated with (after umounting the
dev-fs or from a resuce system):
mknod -m 660 console c 5 1
mknod -m 660 null c 1 3
Incidentally, cryptsetup should not need a clean shutdown,
but the filesystem in there may like one. Although Linux
filesystems are generally very tolerant of surprising
shutdowns. Probably an effect of PC hardware historically
not being very reliable.
On Tue, Feb 06, 2018 at 16:48:06 CET, Pascal wrote:
> /dev on my CentOS 7 box took a 'rm -rf' yesterday, wiping out most of it.
> Easiest way to recover is to reboot (/dev is on a ramdrive and created from
> scratch during boot), but I'm worried about not getting a clean shutdown.
> Does cryptsetup need anything in /dev to shutdown cleanly? If so, how do I
> recreate the devices? The complete list of what is missing from /dev is
> huge, but the below all seem to be disk related and are all gone now:
> dm-crypt mailing list
> dm-crypt at saout.de
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno at wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
A good decision is based on knowledge and not on numbers. -- Plato
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
More information about the dm-crypt