我已经在谷歌云上运行了一个ES节点。我尝试在同一个区域中再部署一个节点。但是得到以下错误：
deploymentCoordinator: DEPLOYED
elasticsearchNode: DEPLOYMENT_FAILED
Replica elasticsearch2-elasticsearch-aidd failed with status PERMANENTLY_FAILING: Replica State changed to PERMANENTLY_FAILING. Replica was unhealthy 2 consecutive times.
根据troubleshooting guide，这不是配额问题。虽然只是为了确保我检查了完整的配额页面。我无处可达。
/gagent/metaOutput日志的输出是：
cat /gagent/metaOutput/stderr.4.txt
+++ cmdfunc48ec81cdc3035833d37ee18a066dd74543212f52
+++ cat
+++ /bin/bash elasticsearch_setup.sh
safe_format_and_mount: Running: fsck.ext4 -a /dev/disk/by-id/google-elasticsearch2-elasticsearch-aidd-data
safe_format_and_mount: fsck.ext4: Bad magic number in super-block while trying to open /dev/disk/by-id/google-elasticsearch2-elasticsearch-aidd-data
safe_format_and_mount: /dev/disk/by-id/google-elasticsearch2-elasticsearch-aidd-data:
safe_format_and_mount: The superblock could not be read or does not describe a correct ext2
safe_format_and_mount: filesystem. If the device is valid and it really contains an ext2
safe_format_and_mount: filesystem (and not swap or ufs or something else), then the superblock
safe_format_and_mount: is corrupt, and you might try running e2fsck with an alternate superblock:
safe_format_and_mount: e2fsck -b 8193 <device>
safe_format_and_mount:
safe_format_and_mount: Fsck could not correct errors on /dev/disk/by-id/google-elasticsearch2-elasticsearch-aidd-data
safe_format_and_mount: Running: mount -o discard,defaults /dev/disk/by-id/google-elasticsearch2-elasticsearch-aidd-data /elasticsearch
safe_format_and_mount: mount: you must specify the filesystem type
safe_format_and_mount: Running: mkfs.ext4 -F /dev/disk/by-id/google-elasticsearch2-elasticsearch-aidd-data
safe_format_and_mount: mke2fs 1.42.5 (29-Jul-2012)
safe_format_and_mount: Discarding device blocks: done
safe_format_and_mount: Filesystem label=
safe_format_and_mount: OS type: Linux
safe_format_and_mount: Block size=4096 (log=2)
safe_format_and_mount: Fragment size=4096 (log=2)
safe_format_and_mount: Stride=0 blocks, Stripe width=0 blocks
safe_format_and_mount: 1310720 inodes, 5242880 blocks
safe_format_and_mount: 262144 blocks (5.00%) reserved for the super user
safe_format_and_mount: First data block=0
safe_format_and_mount: Maximum filesystem blocks=4294967296
safe_format_and_mount: 160 block groups
safe_format_and_mount: 32768 blocks per group, 32768 fragments per group
safe_format_and_mount: 8192 inodes per group
safe_format_and_mount: Superblock backups stored on blocks:
safe_format_and_mount: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
safe_format_and_mount: 4096000
safe_format_and_mount:
safe_format_and_mount: Allocating group tables: 71/160
safe_format_and_mou144/160
safe_format_and_modone
safe_format_and_mount: Writing inode tables: 71/160
safe_format_and_144/160
safe_format_and_mdone
safe_format_and_mount: Creating journal (32768 blocks): done
safe_format_and_mount: Writing superblocks and filesystem accounting information: 68/160
safe_format_and_mount141/160
safe_format_and_mount:done
safe_format_and_mount:
safe_format_and_mount: Running: mount -o discard,defaults /dev/disk/by-id/google-elasticsearch2-elasticsearch-aidd-data /elasticsearch
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
safe_format_and_mount: Fsck could not correct errors on /dev/disk/by-id/google-elasticsearch2-elasticsearch-aidd-da
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
Still waiting for resourceview elasticsearchnode-f18a8 to have 1 members ...
有one relates SO question，但唯一未被接受的答案表明它是配额问题。至少对我来说并非如此。
有什么想法吗？我应该如何解决这个问题？