Skip to main content

How to Restore the Original Storage Capacity of Pen Drive

                     In the following post we will see how to restore the actual storage capacity of your pen drive. Sometimes it happens that your pen drive show smaller storage capacity than original storage capacity. For example If you have a 8 GB pen drive which has original storage capacity of 7.18 GB but now it is showing total space 4.32 GB. Usually it happens when you make your pen drive bootable for linux or other Operating Systems or your pen drive got older.


To get back your pen drive with original storage capacity you need to do following things:

1) Mount your pen drive into windows operating system

2) Open cmd as administrator

3) Execute following command in the cmd

 C:\\Windows\System32>diskpart
 
 your cmd will change C:\\Windows\System32> to DISKPART>
        Now type the below command:
 
 DISKPART>list disk


 
 It gives the list of all disk partition and available devices along with
        index(start with 0) like
 
 Disk 0 Online 298 GB 0 B
 Disk 1 Online 4530 MB 235 B
 
 
 
 
 You need to select the pen drive by index, 
        which you can decide based on memory showing in same line.
        Execute command:
 
 DISKPART>select disk 1   [In your case index may differ than 1]
 
 
 
 
 
 Now you have to clean the disk and crate partition.
        To do this use following commands:
 
 DISKPART>clean
 DISKPART>create partition primary
 DISKPART>exit
 
 
 

Note :- Play with memory management is very critical process. Do the process carefully nevertheless If any unfortunate things occur, Only you will be responsible for that.


Comments

Popular posts from this blog

How to Create a Namespace in Aerospike Database

                      T his post is about creating a namespace in Aerospike. I could not find any concrete method to create a namespace like create database in MySQL and MongoDB. So I am suggesting a way to create a namespace in Aerospike Database. Step-1: Locate config file aerospike.conf and open it in your favorite editor and make sure you have permission to modify the file. In my system the path of file /etc/aerospike/aerospike.conf (Default in Ubuntu). Here the content of the file. # Aerospike database configuration file. service { user root group root paxos-single-replica-limit 1 # Number of nodes where the replica pidfile /var/run/aerospike/asd.pid service-threads 4 transaction-queues 4 transaction-threads-per-queue 4 proto-fd-max 15000 } logging { # Log file must be an absolute path. file /var/log/aerospike/aerospike.log { context any info } } network { service { address any port 3000 } heartbeat { mode multicast address 239.1.99.222 p

java.lang.IllegalArgumentException: Could not instantiate implementation: org.janusgraph.diskstorage.cassandra.thrift.CassandraThriftStoreManager

If you are trying to get started with Janus Graph with Apache Cassandra. You may get the following error. Caused by: org.janusgraph.diskstorage.TemporaryBackendException: Temporary failure in storage backend at org.janusgraph.diskstorage.cassandra.thrift.CassandraThriftStoreManager.getCassandraPartitioner(CassandraThriftStoreManager.java:219) ~[janusgraph-cassandra-0.2.0.jar:na] at org.janusgraph.diskstorage.cassandra.thrift.CassandraThriftStoreManager.<init>(CassandraThriftStoreManager.java:198) ~[janusgraph-cassandra-0.2.0.jar:na] ... 48 common frames omitted Caused by: org.apache.thrift.transport.TTransportException: java.net.ConnectException: Connection refused (Connection refused) at org.apache.thrift.transport.TSocket.open(TSocket.java:187) ~[libthrift-0.9.2.jar:0.9.2] at org.apache.thrift.transport.TFramedTransport.open(TFramedTransport.java:81) ~[libthrift-0.9.2.jar:0.9.2] at org.janusgraph.diskstorage.cassandra.thrift.thriftpool.CTConnectionFactory.makeR

com.mongodb.MongoCommandException: Command failed with error 18: 'Authentication failed.' on server

If you are trying to connect Mongo DB Server and it insanely throwing following error. com.mongodb.MongoTimeoutException : Timed out after 1000 ms while waiting for a server that matches ReadPreferenceServerSelector{readPreference=primary}. Client view of cluster state is {type=UNKNOWN, servers=[{address=192.168.1.10:27010, type=UNKNOWN, state=CONNECTING, exception={ com.mongodb.MongoSecurityException: Exception authenticating MongoCredential {mechanism=null, userName='user123', source='admin', password=<hidden>, mechanismProperties={}}}, caused by {com.mongodb.MongoCommandException: Command failed with error 18 : 'Authentication failed.' on server 192.168.1.10:27010 . The full response is { "ok" : 0.0, "code" : 18, "errmsg" : "Authentication failed." }}}] If you start looking the error content First you encounter with Timeout Exception which may mislead you. It is basically an authentication error. I