Storage Miner
Last updated
Last updated
Section Brief:
The OS requirement of the Storage server is as following:
Recommended OS and Version
Linux 64-bit Intel/AMD
CPU Core
≥ 4
Memory
≥ 8 GB
Bandwidth
≥ 5 M
Public network IP
required
Linux Kernel Version
5.11 or higher
The following commands are executed with root privileges, if the prompt
Permission deniedappears, you need to switch to root privileges, or addsudoat the top of these commands.
By default, cess-bucket uses port 4001 to listen for incoming connections, if your platform blocks the port by default, you may need to enable the access to the port.
Check the hard disk status using the df -h command:
The disk is not mounted If the hard drive for storage mining cannot be found. Use the command below to view unmounted hard disks:
The unmounted disk is /dev/vdb in the demonstration above. We will be using /dev/vdb to demonstrate the mounting operation.
Allocate the /dev/vdb disk：
Format the newly divided disk into ext4 format：
Enter "y" to continue if the system asks to proceed:
Create /cess directory to mount the disk. Using/cess as an example:
replace
/dev/vdbwith your own disk name./cesshas to remain the same as created in the previous step. If you are not under root privileges, try :
echo "/dev/vdb /cess ext4 defaults 0 0" | sudo tee -a /etc/fstab
Mount /cess :
Check the disk mounting status:
If the "/cess" appers, the disk has been successfully mounted.
Miners need to create two wallet accounts.
Please refer to the CESS Account section above for creating a CESS account. Please go to the CESS faucet to get TCESS. Join CESS telegram to get our assistance.
If Install cess nodeadm success shows up, the installation is successful .
Set up bucket configuration
Start bucket
The following should be seen:
View chain node log
As shown in the figure below, if we see that the height of the block corresponding to "best" is about the latest height in CESS Explorer, it means the local chain node synchronization is completed.
View storage node log
As shown in the figure below, it is the log information when the storage node starts normally. It shows: the rpc address used by the storage node and the address of the boot node, the connection to the boot node, its own peer id, the chain network and the p2p network, the synchronization information of the currently used chain node, and the workspace.
View bucket status
An example of the returned results is shown below：
see specific explanation of the names above in Appendix
Stop and remove all service
Remove all program data
Update the cess-nodeadm
Pull images
peer id
The id for peer communication.
state
Positive: Working fine
Frozen: Out of staking
Exit: Quiting the network as a storage miners
Offline: Being kicked out of the network
staking amount
The amount of TCESS being staked.
validated space
The sapce validated to store user's data.
used space
The space used by storage users.
locked space
The space locked when waiting for users' data being uploaded.
staking account
The account to stake TCESS(>4000).
earnings account
The account to earn space reward.
earning account: used for receiving rewards from mining.
staking account: used for staking and signing blockchain transactions.
Please make sure you have sufficient TCESS before you claim bucket space: Staking amount needed: 4000TCESS/ 1000 GB
If you have previously deployed nodeadm on your machine, please jump to this and then go to the next section. If you are new, just ignore it.
Please make sure the cess-nodeadm version v0.4.4 is correct, check the most updated version.
If the installation fails, please refer to
If the Config process fails, please refer to
Only when the chain synchronization is completed, you can operate other functions such as increase the staking, view the status of the node, etc.
The chain network must be consistent with the p2p network.
Do not delete or change files in the workspace.
You need to exit first.
Please use this command carefully, once you exit, you cannot resume.
Do not perform this operation unless the CESS network has been redeployed and it is confirmed that the data can be cleared.
Please make sure the cess-nodeadm version v0.4.4 is correct, check the most updated version.
