The service starting message on my machine lasts AGES. I'm working with support trying to get it resolved but I'm assuming it's a bug and I suppose it's possible that this is just how long it takes for drive pool to start.
I have 7 drives in the pool with 17TB of space. It takes around 40 minutes after a reboot before I can use the stablebit drive pool software or access any files.
Does anyone else experience this?
I'm using Server 2016 (I've just moved to a new host SSD drive), and i'm using the latest beta of drive pool.
ross.dargan got a reaction from vapedrib in How long is yours (Service Starting)