×


Search For:


NTFS partition failed to mount

This article will guide you on methods to resolve NTFS partition failed to mount error. 

Causes of NTFS partition failed to mount error:

1. File system errors

After using #NTFS drive in #Windows you have detached it without removing it safely. Therefore NTFS journal has not been emptied from temporary streams.

To fix the problem:

i. Open Disk Utility under #Mac OS X. 

ii. You will find it in Applications – Utilities.

iii. Choose NTFS partition on the left and find First Aid tab on the right. 

iv. Under this tab you will find Verify Disk option. 

v. Run Verify and then Repair.


MySQL error 1819 HY000

This article will guide you on how to resolve MySQL error 1819 (HY000) which happens when creating a MySQL user with a relatively weak password.  

Because of validate_password_policy we applied on database, we are not able to change and assign simple or weak passwords it don't allow to to change password and came up with error.

To resolve this error, We can check validate_password_policy applied on machine. Also you can change your password under Low policy.


Solution to MySQL Error Your Password does not satisfy the Current Policy Requirements:

1. Set the Password_policy value to low, next is setting the same Password_Policy value in my.cnf file and the last is uninstalling the plugin that is used for validating password.

2. Set the Password_Policy to low:

Default Password level of plugin can be changed at runtime or using config file. 

To do this, default authentication plugin has to be checked:

SHOW VARIABLES LIKE 'default authentication plugin';

3. For checking the current variables for validating the password you should run the following command:

SHOW VARIABLES LIKE 'validate_password%';

4. Validate_password is a variable that is used to inform the server about the validate_password plugin. 

This plugin tests the passwords and improve security. 

Following output will be displayed, if you run the above command:

mysql> SHOW VARIABLES LIKE 'validate_password%';


GlusterFS vs Ceph performance

This article will guide you on the differences between GlusterFS vs Ceph Performance. The decision on transfer sizes could itself account for Ceph running faster or slower than Gluster. 

Deciding whether to use Ceph vs. Gluster depends on numerous factors, but either can provide extendable and stable storage of your data.

Ceph and Gluster are both systems used for managing distributed storage. The goal is high performance, massive storage, and compatibility.

Ceph provides a POSIX-compliant network file system (#CephFS) that aims for high performance, large data storage, and maximum compatibility. 

GlusterFS and Ceph are two distributed persistent storage systems. #GlusterFS is at its core a network filesystem. 

Ceph is at the core an object store.


Email address rejected by server error in iPhone

This article will guide you on methods to resolve "Email address rejected by server" error which happens in iPhone devices mainly due to wrong mail settings. 

The recipient was rejected by the server because it does not allow relaying. Chances are you need to check your outgoing mail server settings. Go to Settings - Mail, Contacts, Calendar and tap on your email account. Tap on "Account, then go down to the "Outgoing Mail Server" section and tap on "SMTP."

If you can't send email try the following: On your iPhone or iPod Touch screen tap Settings and then Mail, Contacts, Calendars. 

Select your email account from the list, and then select it again on the next screen. 

Scroll down to the bottom and tap on the SMTP field under Outgoing Mail Server.


To fix email rejected by server:

1. Go to Settings > Mail > Accounts and select the account you are having difficulty with.

2. Click on your email address at the top of the screen.

3. Go down to the bottom of the screen where it says SMTP and click on it.

4. Select the Primary Server at the top of the screen.


OnApp Cloud

This article will guide you on OnApp cloud. You will also learn about its dashboard and features. 

OnApp Enterprise is a complete on-premises cloud solution for SMBs and enterprises. 

It makes private and hybrid cloud easier to manage and easier to scale. 

OnApp clouds can be created on almost any commodity x64 infrastructure, and across heterogeneous compute and storage hardware.


The features of OnApp cloud comprise of:

1. Public, private & hybrid cloud, plus VPS

2. Xen, KVM & VMware, plus Amazon EC2

3. Storage, backup and disaster recovery

4. Smart servers & bare metal servers

5. Global cloud & CDN through OnApp federation

6. CPU, disk, IOPS,RAM, servers, networks & more


OnApp is used:

i. By Telcos, MSPs and other service providers to create, manage and sell their own IaaS cloud products - either using their own datacenter infrastructure, third party infrastructure or hyperscale infrastructure.

ii. OnApp is used by hosts, telcos, MSPs, CDN vendors and other service providers to sell public/private/hybrid cloud services; and by enterprises for on-premise private & hybrid public/private cloud.


Kernel-memory-leaking Intel processor design

This article will guide you on how to fix Kernel-memory-leaking. Kernel-memory-leaking Intel processor design occurs due to a flaw in the Intel x86-64 hardware. 

The simplest way to detect a memory leak is also the way you're most likely to find one: running out of memory. 

That's also the worst way to discover a leak! Before you run out of memory and crash your application, you're likely to notice your system slowing down.

A memory leak can diminish the performance of the computer by reducing the amount of available memory.

Most memory leaks result in general software reliability problems, but if an attacker can intentionally trigger a memory leak, the attacker might be able to launch a denial of service attack (by crashing the program) or take advantage of other unexpected program behavior resulting from a low memory condition.


Memory leaks have two common and sometimes overlapping causes:

1. Error conditions and other exceptional circumstances.

2. Confusion over which part of the program is responsible for freeing the memory.