☁️
Zus Docs
  • About Züs
  • System
    • Providers and Services
      • Miner
      • Sharder
      • Blobber
      • Validator
      • Authorizer
      • Node Locator (0DNS)
    • Storage
      • Architecture and Data Management
      • Protocol
        • Allocations
        • Reference Objects
        • Challenges
        • Write Markers
          • Chain Hashing
          • Two Commit
        • Blobber Repair Protocol
      • ZS3 Server
        • Backup, Recovery and Replication
        • Encryption and Compression
        • S3FS Setup and Usage
        • Backup & Recovery with Restic on Blimp + ZS3 Server
        • Backup & Recovery with Veeam on Blimp + ZS3 Server
      • File Operations
        • Upload
        • Download
        • File Sharing
        • Partial Error Recovery
        • Streaming
        • Rent a Blobber
    • Smart Contracts
      • Storage S.C.
      • Miner S.C.
      • ZCN S.C.
      • ERC-20 S.C.s
      • Bridge Protocol
    • Blockchain & Consensus
      • Entities
    • User Authentication and Wallet Management System
      • OKTA Integration
      • Key Management System (KMS)
  • APIs
    • 0DNS API
    • JS API
    • Mobile API
  • CLIs
    • Storage CLI
      • Quickstart
      • Configuring the tool
    • Wallet CLI
      • Wallet Configuration
      • Quickstart
      • Configuring the tool
  • SDKs
    • Go SDK
      • GO SDK Microservices
    • JS SDK
  • Tokenomics
    • Staking
    • Reward & Penalty
  • ✨Züs Apps
    • 🗝️Vult
      • Getting Started
        • Web
        • Mobile
      • Vult AI
        • Batch Processing
        • Memory Retention
        • Technical Implementation
        • Architecture Overview
      • Login / Register
      • File Management Pages
      • File Sharing
      • Storage Management Dashboard
      • Storage Maintenance and Troubleshooting
      • Züs Subscription
      • Wallet Management
      • Refer a friend
      • Settings
    • 🏗️Blimp
      • Getting Started
      • Login / Register
      • Configure Storage
        • Create Standard Storage Allocation
        • Create Enterprise Allocation
        • Create S3 Server Allocation
        • Create Cloud Migration Allocation
        • Allocation Maintenance and Troubleshooting
      • File Management Pages
      • File Sharing
      • Manage Allocations
      • Upgrade Storage
      • Blimp Vault
      • Refer a friend
      • Settings
      • Launching ZS3 Server
      • Using CLI to backup files into Blimp + ZS3 Server
    • 🏠Chimney
      • Getting Started
      • Login / Register
      • Create New Deployment
      • Manage Your Deployments
      • Homepage
      • Staking Dashboard
      • Rank Dashboard
      • Monitor Dashboard
      • Stats Dashboard
      • Logs Dashboard
      • Wallet Dashboard
      • Operations on your Deployments
      • Restricted Blobbers
      • Settings
        • Manage Profile
        • Wallet Settings
        • Update Blobber Settings
        • Update Blobber Version
        • Refer a friend
        • Help
    • 🌐Atlus
      • Getting Started
      • Home page
      • Service Providers Page
      • Charts Page
        • Market Charts
        • Network Charts
        • Storage Charts
      • Blockchain Page
      • Server Map Page
      • Storage Explainer Page
      • Details Pages
        • Block Details Page
        • Transaction Details Page
        • Wallet Details Page
        • Miner Details Page
        • Sharder Details Page
        • Blobber Details Page
        • Validator Details Page
        • Authorizer Details Page
        • Allocation Details Page
      • Appendix: Common Components
    • ⚡Bolt
      • Getting Started
        • Web
        • Mobile
      • Login / Register
      • Sign In with external wallet
      • Staking Dashboard
      • Staking/Unstaking a provider
      • Claiming Rewards
      • Send/Receive ZCN tokens
      • Buy ZCN
      • Deposit/Withdraw ZCN tokens
      • Activity Dashboard
      • Refer a friend
      • Settings
  • Releases
    • Hardfork
Powered by GitBook
On this page
  • Mount HDD or SSD disks
  • Clean a stale or unsuccessful deployment
  • Get the blobber ID (outside chimney dashboard) or the Validator ID
  1. Züs Apps
  2. Chimney

Operations on your Deployments

Learn to troubleshoot and be flexible with your deployment, yourself.

PreviousWallet DashboardNextRestricted Blobbers

Last updated 1 year ago

After you successfully run the deployment script on your machine, you may need to know some operations that can come in handy chances are that you face any issues or need to move your deployment around.

Mount HDD or SSD disks

If you have external disks that you want to mount and use as storage space for your Chimney deployment, you can do this by mounting them to the blobber storage mountpoints:

  • HDD => /var/0chain/blobber/hdd

  • SSD => /var/0chain/blobber/ssd

Follow these steps to mount your disks:

Step1: Find your devices as volumes

Before you mount the disks, you need to find the device directory (or name) of them. Devices in the Linux OS are represented by virtual files in the /dev directory. To find the name of your disk devices, you can either run fdisk -l (for MBR partitioning) or gdisk -l (for GPT partitioning)

As you see in the output, you first get a list of all the devices then the partition table for each device. For the case in the image, there was a single device (/dev/sda) which was partitioned into 3 volumes (/dev/sda1, /dev/sda2 and /dev/sda3) with sda3 being the mai storage volume.

If you have multiple physical disks that you need to mount to your blobber, make sure they're represented by only one logical volume using LVM (Logical Volume Manager) or RAID, either hardware or software. To install/upgrade lvm run sudo apt-get install lvm2

Step2: Mount your volumes

Now that you have the file representing your storage volume, you need to mount that to the blobber's mount point. Run either of the following commands depending on your device type

# For HDD
mount /dev/sda3 /var/0chain/blobber/hdd
# For SSD
mount /dev/sda3 /var/0chain/blobber/ssd

Replace /dev/sda3 with your volume file you found from step 1.

Clean a stale or unsuccessful deployment

If your deployment was unsuccessful and you need to remove the old deployment before you run the new script. To do this, run the following command on your machine:

export PROJECT_ROOT=/var/0chain/blobber;
docker-compose -f ${PROJECT_ROOT}/docker-compose.yml down --volumes;
docker system prune --volumes --force;
rm -rf ${PROJECT_ROOT} || true;

If you've attached an hdd or ssd disk and have files, the mount points will not be removed. However, if you want to remove the mount points, unmount them first:

unmount /var/0chain/blobber/ssd and unmount /var/0chain/blobber/hdd

Get the blobber ID (outside chimney dashboard) or the Validator ID

docker-compose -f /var/0chain/blobber/docker-compose.yml logs blobber |\
     grep -A 4 "*== Blobber Wallet Info ==*" |\
     head -n4
docker-compose -f /var/0chain/blobber/docker-compose.yml logs validator |\
     grep -A 4 "*== Validator Wallet Info ==*" |\
     head -n4

Then, after you finish the cleanup, rebooot the device and remount them back if you'll rerun the script. Follow the instructions mentioned in the .

Normally, you can find your blobber ID in in Chimney. However, if for any reason you couldn't access it, you can get the ID of the blobber from your machine where the chimney deployment is running by running the following command:

For the validator, you can find its ID on Chimney if you inspected its funding transaction when you fund it from the , the validator id will be the "To" field of the transaction. However, if you couldn't access Chimney for any reason, you can find your id by running the following command on your machine:

✨
🏠
Mount section
Manage Blobbers Page
Wallet Page
Fig1: Example fdisk output