View source for Server Crash Recovery, Forensics, and Data Security Notes - Linux

 <nowiki>.Crash Recovery, Forensics, and Data Security Notes (Why my b0x3n crasged!?!?.</nowiki>
 <nowiki>.Helping you get UP and RUNNING safely and secure.............................</nowiki>
 <nowiki>.                                                                            .</nowiki>
 <nowiki>.  XXXXX   XXXXX     XXX     XXXXXX  X     X  XXXXXX  XXXXX                  .</nowiki>
 <nowiki>. X     X  X    X   X   X   X        X     X  X       X    X                 .</nowiki>
 <nowiki>. X        X    X  X     X   XXXXX   XXXXXXX  XXXX    X     X                .</nowiki>
 <nowiki>. X     X  XXXXX   XXXXXXX        X  X     X  X       X    X                 .</nowiki>
 <nowiki>.  XXXXX   X    X  X     X  XXXXXX   X     X  XXXXXX  XXXXX                  .</nowiki>
 <nowiki>.................................................Sat Aug  6 21:56:16 CDT 2005.</nowiki>
 <nowiki></nowiki>
 <nowiki>  1] Mounting proc filesystem fails on boot: dup2: Bad file descriptor</nowiki>
 <nowiki></nowiki>
 <nowiki>  While booting the system haults at the following message: "Mounting proc</nowiki>
 <nowiki>filesystem dup2: Bad file descriptor."  After running fsck everyting is clean</nowiki>
 <nowiki>and the system will still hault on the same error.</nowiki>
 <nowiki></nowiki><nowiki>  This error is actually happen because the /dev/null entry in the device</nowiki>
 <nowiki>inode permission is incorrect.  </nowiki>
 <nowiki></nowiki>
 <nowiki>  To get the system back up and running you must correct the problem with</nowiki>
 <nowiki>/dev/null.  Enter the root password at the service prompt and remount the root</nowiki>
 <nowiki>filesystem read/write, delete /dev/null and create a new one.</nowiki>
 <nowiki></nowiki>
 <nowiki>  mount -n -o remount,rw /dev/sdxX</nowiki>
 <nowiki></nowiki>
 <nowiki>  rm -rf /dev/null</nowiki>
 <nowiki></nowiki>
 <nowiki>  mknod -m 666 /dev/null c 1 3</nowiki>
 <nowiki></nowiki>
 <nowiki>  Change /dev/sdxX to the root partition.</nowiki>
 <nowiki></nowiki>
 <nowiki>  [cause analysis]: /dev/null was modified by (user, something installed, an</nowiki>
 <nowiki>intruder) giving it incorrect permissions or changing it to a regular file.</nowiki>
 <nowiki>This can also be caused if user does 'mv filename /dev/null' for example.  It</nowiki>
 <nowiki>is not likely that this condition was created by an intruder.  It is more</nowiki>
 <nowiki>likely the result of operator error.</nowiki>
 <nowiki></nowiki>

{{:Template:Archived Entry}} 

=== Recommended Newer Resources ===

{{:Ubuntu- check for bad sectors on system from GUI}}

* [[Linux Disk Utilities]]
* [[Drive Controller Types for the PC]]
* [[Disk Data Recovery]]
* [[Data Recovery From a Failing Hard Drive]]

[[Category:Computer_Technology]]
[[Category:Linux]]
[[Category:Security]]