![]() ![]() To do this, we only need to know the physical name of our storage device. Once the hdparm tool is known, we can use the -r option with which we can check the status of this bit with a simple command. Remove and set the memory protection bit with hdparm: But I will tell you that among its options there are some quite interesting such as:Īlways remember to use the privileges, that is, run them as root user or putting sudo in front of them or they won't work. Remember that many USB storage media controllers, including card readers such as SD cards, also use this type of controller to operate, therefore it is also compatible with them.Īnd presents many options with which to work, although I do not recommend that you use them if you do not know what you do well, since being a low-level tool you could seriously damage your device, for example if we manipulate some critical options such as -B. The command hdparm is a low-level tool which acts as an interface between various Linux kernel drivers and SATA / PATA / SAS storage media using the libata library, as well as for old IDE media. In case this method doesn't work for you, then it will be because the bit we have talked about is acting, and that is why we will have to use the tool that we present below. In such a case we can only read the / dev / sda device in this case it has been mounted on the / mnt mount point. įor example, if in the / etc / fstab file the device is configured to mount automatically with the option ro (read only) or if we have mounted it with the command: But if one of these protected media has fallen into our hands and we do not know of the existence of this bit, we could waste hours thinking that our unit is damaged, or raising and lowering the tab that some pendrives or SD cards have to protect them without any result. It is certainly very practical when we store data that we do not want to be modified, preventing writing or deletion by mistake. While the controller of the storage medium USB or SD memory card, or whatever means, detect that this bit is active, the driver will prevent the kernel from ordering a write order and therefore it will only be able to read the content. In this case we are referring to a protection that is implemented in secondary storage media. Nor to the typical protection tab that we find in some SD cards or storage media. This bit should not be confused with the WP of the CPUs' flag registers, which prevent overwriting by creating a forking process on UNIX-like systems, thus protecting the main memory from data writing. And there is a bit of anti-writing protection that certain drivers allow, known as « write protection bit✽epending on whether it is active at 1 or 0, it will allow writing to the unit or not. If you have an SD memory card, pendrive or any USB storage disk you want write protect, in this article we tell you step by step and in an easy way how to do it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |