Hi all ., i triying to mount static disk but i having this error when i run sudo mount -a , Ubantu OS
`mount: unknown filesystem type 'LVM2_member'`
here is my partition
root@s161300:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
|-sda1 8:1 0 1M 0 part
|-sda2 8:2 0 1K 0 part
|-sda5 8:5 0 976M 0 part /boot
`-sda6 8:6 0 464.8G 0 part
|-vg-root 252:0 0 448.6G 0 lvm /mnt/myfile
|-vg-swap 252:1 0 15.3G 0 lvm [SWAP]
`-vg-tmp 252:2 0 976M 0 lvm /tmp
mount -a attempts to mount all entries in /etc/fstab … so an output of cat /etc/fstab would be useful
i think i mount VG tag . and i enter docker start code . now i haveing below error
This is error now i getting
root@s161300:~# docker exec -it storagenode /app/dashboard.sh
Error response from daemon: Container fb3734330da46901518459539df532035adc2c7f243416fc77cb1ef69ababd0f is restarting, wait until the container is running
OK now i can see this error
Storage Node Dashboard ( Node Version: v1.1.1 )
======================
ID 1yjTP3xigEaymVWiLbUXBZr4vBjY1JC4ykpypHZzsQZLq2PRGC
Last Contact OFFLINE
Uptime 1s
Available Used Egress Ingress
Bandwidth N/A 0 B 0 B 0 B (since Apr 1)
Disk 400.0 GB 0 B
Internal 127.0.0.1:7778
External xxxxx:28967
and its keep end up with this error
root@s161300:~# docker exec -it storagenode /app/dashboard.sh
Error response from daemon: Container 3b1f47e2497f6479e95a428b7a277de74fe9cbe9bad7fa4dc4ad83d3fcc5bf37 is restarting, wait until the container is running
root@s161300:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/mapper/vg-root / ext4 errors=remount-ro 0 1
# /boot was on /dev/sda5 during installation
UUID=cc6dd5ce-5dbe-43aa-abbf-ca2c24657ebe /boot ext2 defaults 0 2
/dev/mapper/vg-tmp /tmp ext4 defaults 0 2
/dev/mapper/vg-swap none swap sw 0 0
root@s161300:~#
This is what u getting
> --name storagenode storjlabs/storagenode:beta
85ddbc75a5913d192ea91b810c8103a77929b799de51cd8c68692f08c466e83d
root@s161300:~# docker exec -it storagenode /app/dashboard.sh
2020-04-10T04:12:36.035Z INFO Configuration loaded from: /app/config/config.yaml
2020-04-10T04:12:36.146Z INFO Node ID: 1yjTP3xigEaymVWiLbUXBZr4vBjY1JC4ykpypHZzsQZLq2PRGC
Error: context canceled
I found the issue , its becoz of my DISK space not enough 
Running into the same problem, except I’m using 40TB so its not a space issue. Any ideas?
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 40T 0 disk
├─sda1 8:1 0 1M 0 part
├─sda2 8:2 0 1G 0 part /boot
└─sda3 8:3 0 40T 0 part
NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
sda3 LVM2_member Z9xRPN-Te6X-8aCk-AsPK-LGpB-B5Pd-DYIsOT
└─sda
admin@localhost:~$ sudo mount -a
mount: /mnt/storj-data: unknown filesystem type ‘LVM2_member’.
If the drive was used for something else, it was probably partitioned… 40 TB sounds a bit large for a single drive. Maybe you’re using some pre-allocated space on a drive array. Whatever…
Try this:
https://askubuntu.com/questions/766048/mount-unknown-filesystem-type-lvm2-member
Specifically:
vgchange -ay
That command should allow you to mount individual volumes within a volume group that was previously created and then attached to your filesystem.
1 Like