Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Status stuck at "Looking for Drive" with drive attached #48

Closed
psalocin opened this issue Nov 11, 2019 · 1 comment
Closed

Status stuck at "Looking for Drive" with drive attached #48

psalocin opened this issue Nov 11, 2019 · 1 comment

Comments

@psalocin
Copy link

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.

@psalocin
Copy link
Author

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...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant