search

keybase / client

Keybase Go Library, Client, Service, OS X, iOS, Android, Electron
BSD 3-Clause "New" or "Revised" License
8.89k stars 1.23k forks source link

Mounted KBFS disappeared in Windows #2630

Open someonehere15 opened 8 years ago

someonehere15 commented 8 years ago

Keybase GUI Version: 1.0.15-20160413083549+d37acc1

I installed the GUI and the KBFS drive showed up in Explorer, and after a couple of minutes it disappeared. Restarted, Uninstalled, but still not showing up.

strib commented 8 years ago

Hi @someonehere15, would you be able to run keybase log send to share your logs with us, to help us debug? If so, please post the resulting log ID here after you run it.

someonehere15 commented 8 years ago

The log ID is b42e51dc205e72d191b1711c, but I also got these errors so I don't know if they got sent:

- WARNING error opening log "C:\\Users\\xxx\\AppData\\Roaming\\Keybase\\Keybase.app.log": open C:\Users\xxx\AppData\Roaming\Keybase\Keybase.app.log: The system cannot find the file specified.
- WARNING error opening log "C:\\Users\\xxx\\AppData\\Roaming\\Keybase\\keybase.start.log": open C:\Users\xxx\AppData\Roaming\Keybase\keybase.start.log: The system cannot find the file specified.
someonehere15 commented 8 years ago

Any way I can get the drive back somehow quickly?

someonehere15 commented 8 years ago

Any updates?

maxtaco commented 8 years ago

Hm, our records don't seem to indicate that you've purchased our VIP support contract!

someonehere15 commented 8 years ago

I'm not expecting the bug to be fixed so soon, I was just asking if there is any workaround for now, e.g. I can uninstall, delete some folder, and it clears up, because a simple reinstall didn't work.

maxtaco commented 8 years ago

Hopefully someone can take a look today. Most of us do take Sunday off!

zanderz commented 8 years ago

Try opening a Keybase CMD console and entering kbfsdokan -log-to-file -debug k:. That may bring back K: drive, but if it gives an error, I am afraid you will need to reboot. We are aware of some problems that can happen when writing out the encrypted blocks can't keep up with the local operation and are working on them. Thanks for your feedback on this preliminary experimental alpha, it is helpful and much appreciated. cc @taruti

someonehere15 commented 8 years ago

Still not working. I reinstalled again, but no. I get error (2) Dokan failed

cjb commented 8 years ago

Just to check: have you tried rebooting?

How about adding -debug after kbfsdokan?

zanderz commented 8 years ago

We are expecting that https://keybase.atlassian.net/browse/KBFS-978 will have an impact on issues of this type

someonehere15 commented 8 years ago

Yes, reboot, reinstall, dokan, everything, still not working

taruti commented 8 years ago

Is there a kbfsdokan process around? (Task Manager -> Processes). Can you do a keybase log send again?

someonehere15 commented 8 years ago

Hi, sorry for the delay, I couldn't earlier. The log id is 9e7762a1d8e1b3bab3487c1c. No matter what I do it still doesn't mount. Additionally, if I close the app, and the service, and open it again, without restarting, it is not logged in, and when I go to the ui login screen, enter a username, and it gets stuck with the loading circle.

zanderz commented 8 years ago

Do you mind trying this:

  1. make sure kbfsdokan is not running - kill it with task manager, if necessary
  2. issue keybase logout at the CLI
  3. issue keybase login at the CLI
  4. If the login window shows up, log in there and go to 5., below -but otherwise- 4a. if prompted to login at the CLI, cancel and do the following: 4b. quit out of the Keybase UI accessed via the tray icon 4c. make sure no Keybase.exe UI processes are running (use task manager) 4d. start %ProgramFiles(x86)%\Keybase\gui\Keybase.exe 4e. go back to step 3.
  5. Try mounting a different drive letter, as in "kbfsdokan -log-to-file -debug J:"

On Apr 21, 2016 7:45 AM, "someonehere15" notifications@github.com wrote:

Hi, sorry for the delay, I couldn't earlier. The log id is 9e7762a1d8e1b3bab3487c1c. No matter what I do it still doesn't mount. Additionally, if I close the app, and the service, and open it again, without restarting, it is not logged in, and when I go to the ui login screen, enter a username, and it gets stuck with the loading circle.

— You are receiving this because you commented. Reply to this email directly or view it on GitHub https://github.com/keybase/client/issues/2630#issuecomment-212878444

bojanrajkovic commented 8 years ago

I'm having the same issue--already tried pretty much all the steps. Here's the output from kbfsdokan -debug F::

2016-04-21T12:32:23.534511 - [INFO kbfs start.go:29] 001 KBFS version 1.0.2-20160413082914+483e6ce
2016-04-21T12:32:23.536995 - [DEBU kbfs connection.go:362] 002 (CONN MDServerRemote d1aa8ca3) Connection: getReconnectChan
2016-04-21T12:32:23.537494 - [DEBU kbfs connection.go:362] 003 (CONN KeybaseDaemonRPC ecbbb1b3) Connection: getReconnectChan
2016-04-21T12:32:23.537494 - [DEBU kbfs connection.go:362] 004 (CONN CryptoClient 5127083f) Connection: getReconnectChan
2016-04-21T12:32:23.537993 - [DEBU kbfs init.go:399] 007 Using remote bserver bserver.kbfs.keybase.io:443
2016-04-21T12:32:23.537993 - [DEBU kbfs(BSR) init.go:194] 008 new instance server addr bserver.kbfs.keybase.io:443
2016-04-21T12:32:23.538496 - [DEBU kbfs connection.go:243] 009 (CONN CryptoClient 5127083f) Connection: dialing transport
2016-04-21T12:32:23.538994 - [DEBU kbfs connection.go:271] 00a (CONN CryptoClient 5127083f) Connection: connected
2016-04-21T12:32:23.537993 - [DEBU kbfs connection.go:243] 006 (CONN KeybaseDaemonRPC ecbbb1b3) Connection: dialing transport
2016-04-21T12:32:23.537993 - [WARN kbfs connection.go:390] 005 MDServerRemote is disconnected: 1
2016-04-21T12:32:23.540995 - [DEBU kbfs connection.go:243] 00b (CONN MDServerRemote d1aa8ca3) Connection: dialing transport
2016-04-21T12:32:23.541495 - [DEBU kbfs connection.go:271] 00c (CONN KeybaseDaemonRPC ecbbb1b3) Connection: connected
2016-04-21T12:32:23.842614 - [DEBU kbfs connection.go:256] 00d MDServerRemote: OnConnect called with a new connection
2016-04-21T12:32:23.843460 - [DEBU kbfs mdserver_remote.go:110] 00e MDServerRemote: resetAuth called
2016-04-21T12:32:23.984961 - [DEBU kbfs keybase_daemon_rpc.go:561] 00f new session with username brajkovic, uid b41a139a9ef5b7140c6de418adb3bd19, crypt public key 0121e8467d2b5939fb1379dda77fe5a49b2509da9ffaac830197a3290dfb30df61070a, and verifying key 0120a634b70403615c28928c036d1ae8ad4f8b708a95355400866d7994b9844ff4280a
2016-04-21T12:32:24.011809 - [DEBU kbfs mdserver_remote.go:110] 010 MDServerRemote: received challenge
2016-04-21T12:32:24.013336 - [DEBU kbfs crypto_client.go:126] 011 Signed 446-byte message: err=<nil>
2016-04-21T12:32:24.014323 - [DEBU kbfs mdserver_remote.go:110] 012 MDServerRemote: authentication token signed
2016-04-21T12:32:24.043024 - [DEBU kbfs mdserver_remote.go:110] 013 MDServerRemote: authentication successful; ping interval: 30s
2016-04-21T12:32:24.071080 - [DEBU kbfs mdserver_remote.go:192] 014 MDServerRemote: requested list of folders for rekey
2016-04-21T12:32:24.073596 - [DEBU kbfs mdserver_remote.go:130] 015 MDServerRemote: starting new ping ticker with interval 30
2016-04-21T12:32:24.074597 - [DEBU kbfs connection.go:271] 016 (CONN MDServerRemote d1aa8ca3) Connection: connected
kbfsdokan error: (2) Dokan failed

I sent logs via keybase log send, the log ID is 582b4e4ba8c602b82d8bcf1c.

Edit: Possibly important information: the initial install of the beta seemed to cause a BSOD on my W10 machine.

someonehere15 commented 8 years ago

Nope, still nothing. I got asked for the password at the CLI, canceled, open gui, then tried to login again in CLI, again asking for password there. tried to mount again, still failed

zanderz commented 8 years ago

That doesn't sound quite like the sequence I intended; it is important to make sure all the UI processes have been stopped before restarting the GUI.

Would you care to join us in https://keybase-friends.slack.com/messages/kbfs/ sometime? It may be a bit faster.

zanderz commented 8 years ago

After further testing, we have been able to reproduce this state reliably and have been able to recover from it by removing the filesystem driver, removing Keybase from the boot startup sequence, rebooting, reinstalling the driver, and starting the keybase service and kbfs manually.

The steps are (use %ProgramFiles(x86)% as necessary):

  1. Delete %AppData%\Microsoft\Windows\Start Menu\Programs\Startup\Keybase.* (.lnk and .vbs)
  2. Open a console as administrator and issue %ProgramFiles%\Dokan\DokanLibrary\dokanctl.exe /r d
  3. Reboot
  4. Open a console as administrator and issue %ProgramFiles%\Dokan\DokanLibrary\dokanctl.exe /i d
  5. Open a Keybase CMD window (not as admin) and start the service by issuing keybase ctl start
  6. Make sure you are logged in to Keybase by issuing keybase login
  7. Make sure your keys are unlocked by issuing keybase unlock
  8. Issue kbfsdokan -debug k: and watch to see it stays running without saying "Dokan failed"

You should be able to reach K: if you have reliable network access. We have some work to do before we can say this problem is solved.

someonehere15 commented 8 years ago

just got the chance to try it and it worked! nice. thank you. It gets unmounted if I close CMD though. Can I get it to stay mounted now or was this just to test?

zanderz commented 8 years ago

That's great, thanks for letting us know. It will only work as long as kbfsdokan is running. Stay tuned, we are close to a new version which solves these issues.

zanderz commented 8 years ago

@someonehere15 A new version with many improvements was released today - please either download or issue the keybase update check command. Thanks!

arnonuem commented 7 years ago

worked for me too - thx @zanderz

arnonuem commented 7 years ago

@zanderz btw. why is the "unlock" command of keybase command line client not documented in keybase --help? OS: Win7 Ultimate

maxtaco commented 7 years ago

Replaced with keybase login

On Sat, Nov 5, 2016 at 9:15 AM, arnonuem notifications@github.com wrote:

Btw. why is the "unlock" command of keybase command line client not documented in keybase --help? OS: Win7 Ultimate

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/keybase/client/issues/2630#issuecomment-258610714, or mute the thread https://github.com/notifications/unsubscribe-auth/AA05_xIfCaByBzqU8J2KqX0BFN8I5r_2ks5q7IFWgaJpZM4IJLq- .

timmyRS commented 7 years ago

I have a somewhat different issue: K:\ is mounted and all files exist, but I can't access it using the normal windows explorer. The file dialog in Sublime Text is not able to access it, however the file dialog in notepad.exe can access all files and I can do all sorts of changes and they will also get saved to Keybase.

taruti commented 7 years ago

@timmyrs are you having issues only with Sublime Text or also with other applications?

timmyRS commented 7 years ago

@taruti It happens that I can only see the K:\ plate initially in some file dialogs of the system and then when I press for example "Open in Sublime Text" then the file dialog is also able to see it and I do never see the K:\ plate in my actual explorer. It is quite weird behaviour.