Unable to create filesystem "getting error mkfs.ext3: inode_size (128) * inodes_count (0) too big for "

By -
mkfs.ext3: inode_size (128) * inodes_count (0) too big for

After you ran sudo fdisk /dev/sdb1 , and deleted the existing partitions by hitting the d key and creating a new one by hitting n, did you choose 'p' (primary) or 'e' (extended).

If you chose 'e', re-run the command and choose 'p' instead. That should solve your problem.

Comments

Post a Comment

Popular posts from this blog

How to delete SEA in VIOS

By -
Remove the network en0 #ifconfig en0 down #ifconfig en0 detach Delete SEA $ lsdev -type sea name             status      description ent27            Defined     Shared Ethernet Adapter $ chdev -dev en26 -attr state=detach en27 changed $ rmdev -dev ent26;rmdev -dev en26;rmdev -dev et26 ent27 deleted $ rmdev -dev en26 en27 deleted $ rmdev -dev et26 et27 deleted system information #prtconf|more rmdev -dev ent3;rmdev -dev en3;rmdev -dev et3
Read more

CPU speed webpage "http://www.spec.org/cpu2006/results/cint2006.html"

By -
1. Cpu speed is the speed from SpecInt for the cpu model and MHz being considered.  It can be obtained from the SpecInt WebSite at http://www.spec.org/cpu2006/results/cint2006.html 2. Cpu throughput is the throughput from SpecInt for the cpu model and MHz being considered.  It can be obtained from the SpecInt web site at http://www.spec.org/cpu2006/results/rint2006.html 3. For Linux the cpu model can be obtained via "cat /proc/cpuinfo".  For Windows, depending on the version, it can usually be obtained from Computer or 'My Computer' properties.  Right click on Computer or 'My Computer' to get to properties.  e.g. "Intel(R) Xeon(R) CPU X5680 @ 3.33GHz (2 processors)"
Read more

Webmin configuration for LDAP

By -
We cannot add or delete users by default so we have to do below changes in LDAP module in GUI mode only. Configuring the module The most complex part of using this module is configuring it to talk to your LDAP server. By default, it will attempt to auto-detect the settings by looking at the LDAP client settings on your system, documented on the LDAPClient page. However, if this fails (perhaps because the LDAP server is not one of its own clients), you will need to configure the module manually as follows : On the module's main page, click on the Module Config link. In the LDAP server host field, enter the hostname of your LDAP server. If it is running on the same machine, enter localhost. If the LDAP server is using encryption, change the LDAP server uses TLS? option to Yes. In the Bind to LDAP server as field, enter the full DN of the administrative user for your LDAP server. This might be something like cn=Manager,dc=my-domain,dc=com. In the Credentials for bind name above field,...
Read more