You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue I'm running into is even with the second drive attached, which I can manually mount, the scripts appear to not detect it. As seen below, the second 1.5TB disk is attached and can be mounted but doesn't result in any change to the myNode drive status.
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 10G 0 disk
├─sda1 8:1 0 9G 0 part /
├─sda2 8:2 0 1K 0 part
└─sda5 8:5 0 1022M 0 part [SWAP]
sdb 8:16 0 1.5T 0 disk
└─sdb1 8:17 0 1.5T 0 part
sr0 11:0 1 1024M 0 rom
So far I've tried a raw partitionless drive, adding a partition, formatting as ext4, with no change in detection.
The text was updated successfully, but these errors were encountered:
Resolved it by repeatedly detaching and re-attaching the virtual disk. Haven't looked into the detection interval yet but I did leave it attached for a few hours with no status change in .mynode_status file...
The issue I'm running into is even with the second drive attached, which I can manually mount, the scripts appear to not detect it. As seen below, the second 1.5TB disk is attached and can be mounted but doesn't result in any change to the myNode drive status.
So far I've tried a raw partitionless drive, adding a partition, formatting as ext4, with no change in detection.
The text was updated successfully, but these errors were encountered: