Closed cyborgshead closed 6 years ago
@hleb-albau as-is now
NAME FSTYPE SIZE MOUNTPOINT LABEL
sda 3.7T
sdb 3.7T
sdc 3.7T
sdd 3.7T
└─sdd1 ext4 3.7T /cyberdata cyberdata
nvme0n1 465.8G
└─nvme0n1p1 ext4 465.8G /cyberdata/staging/elassandra SSD2
nvme2n1 931.5G
└─nvme2n1p1 ext4 931.5G /cyberdata/eth SSD3
nvme1n1 465.8G
└─nvme1n1p1 ext4 465.8G /
made partitioning and add labels, mountpoints for previously non-used disks
sda
└─sda1 ext4 HDD1 976a3ef1-2804-49a0-a5eb-86f3787553de /backupsData
sdb
└─sdb1 ext4 HDD2 82e340d9-6c3f-488f-91e7-bb5bf013b854 /generalData1
sdc
└─sdc1 ext4 HDD3 3be01179-27ce-4ec9-8640-fb2f0dd06be3 /generalData2
sdd
└─sdd1 ext4 cyberdata f9698264-4655-4998-a045-fb2392f0976c /cyberdata
nvme0n1
└─nvme0n1p1 ext4 SSD2 d43942e1-e079-466e-bb0e-6c3399bb9c4b /cyberdata/staging/elassandra
nvme2n1
└─nvme2n1p1 ext4 SSD3 0a7c1427-5b49-4a76-b347-a3efb7b9f3a4 /cyberdata/eth
nvme1n1
└─nvme1n1p1 ext4 a7ff1a71-4abd-4d10-9f79-49799511909a /
@hleb-albau @YodaMike described how it should be not at all, kind of
ssd512-1 /
ssd512-2 /ssd512
ssd1024-1 /ssd1024
hdd4-1 /cyberdata
hdd4-2 /backups
hdd4-3 /generalStorage1
hdd4-4 /generalStorage2
ln /var/lib/docker -> /cyberdata/docker
ln /cyberdata/parity -> /ssd512/chains/parity
ln /cyberdata/bitcoind -> /ssd512/chains/bitcoind
ln /cyberdata/staging/elassandra -> /ssd1024/elassandra
Previous issue https://github.com/cyberFund/cybernode-archive/issues/120#issuecomment-360815506
We also need to move system disk from m2
mounted disk to standard, because mars
experiencing problems with boot.
downgraded mars from ubuntu 17.10 to 16.04 installed netdata installed docker installed portainer
/dev/sda1
failed to mount with errors JBD2: Invalid checksum recovering block 5 in log
etc. Attempt to fix that with fsck /dev/sda1
fails with error.
fsck from util-linux 2.27.1
e2fsck 1.42.13 (17-May-2015)
/dev/sda1 has unsupported feature(s): metadata_csum
e2fsck: Get a newer version of e2fsck!
Solution is to boot from network and check filesystem. I uploaded pixiecore
PXE boot server on earth@earth.
sudo pixiecore quick xyz --dhcp-no-bind
Runs PXE server with netboot.xyz image and without own DHCP server.
Booted into live Grbl image, run fsck, fixed filesystem, rebooted.
Current mappings:
$ lsblk -o NAME,SIZE,LABEL,MOUNTPOINT
NAME SIZE LABEL MOUNTPOINT
sdd 3,7T
└─sdd1 3,7T cyberdata /cyberdata
sdb 3,7T
└─sdb1 3,7T HDD2 /cyberdata/elassandra-search
nvme2n1 931,5G
└─nvme2n1p1 931,5G SSD2 /cyberdata/ssd05tb
nvme1n1 465,8G
├─nvme1n1p3 64G [SWAP]
├─nvme1n1p1 512M /boot/efi
└─nvme1n1p2 401,3G /
loop0 81,3M /snap/core/3887
sdc 3,7T
└─sdc1 3,7T HDD3 /cyberdata/elassandra-markets
sda 3,7T
└─sda1 3,7T HDD1 /backupsData
nvme0n1 465,8G
└─nvme0n1p1 465,8G SSD1 /cyberdata/ssd1tb
Done, info here https://cyberfund.github.io/knowledge/staging/setup/
@YodaMike please describe @abitrolly current set of mappings of disks (and what the problems with current mappings) and right way which they should be mapped.