[SOLVED] Cleaning up device drivers after USB memory stick
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I need to clean up system device drivers in a proper manner. Some USB-stick has been physically removed several times leaving orphaned device drivers. (As you will guess. System is currently running Linux Mint 11 Katya (/etc/issue) LiveCD).
In below listing, only /dev/sdf1 is active USB-stick. /dev/sdd1 and /dev/sde1 are orphans.
Any suggestions to how I can properly remove the noneused device drivers properly?
They are not drivers, they are either character files or links created by udevd for the purpose of marshaling hot plugged devices. Don't worry if they exist, they don't do any harm to the system nor do they consume an amount of processor load. If you will delete them as root udev will still create them for you when the need comes to use one.
As to the device records you called 'orphans' you may clean the udev data base if you want:
~# udevadm info --cleanup-db
Likewise they are not harmful and they are not eating up the processor. I often experience similar pseudo-nuisance when device is remove before the system is ready.
There are also times when the file system journal commits something that no longer exists (specially under ext4) so the solution is simply to run 'fsck' and the bad record will go. Usually 'orphaned' records disappear at next boot up.
Hope that helps.
Last edited by malekmustaq; 12-09-2012 at 11:07 AM.