pjakesson Posted October 2, 2014 Share Posted October 2, 2014 Hello, I cloned my system disk to a new install, and most things went well. Except, after reboot there are no shares (all on pool) exported Then I run the WSS Troubleshooter and the share are exported correctly to my clients, though the Dashboard says the shares are still missing and gives a critical error. And it seems the shares stick until next reboot. thanks in advance Per Quote Link to comment Share on other sites More sharing options...
0 Christopher (Drashna) Posted October 3, 2014 Share Posted October 3, 2014 What do you mean by "stick"? On the server, can you see the X:\ServerFolders\sharename folders on the pool? If so, run "compmgmt.msc" on the server. Find the "Shared Folder" section, and check the "Shares" option. You should see a number of shares. The important ones are the ones that should be showing up in the dashboard. If these are there, then go to the "Services" section, and make sure all of the "Windows Home Server" or "Windows Server Solutions" services are started (except for the "initialization" service). Quote Link to comment Share on other sites More sharing options...
0 pjakesson Posted October 3, 2014 Author Share Posted October 3, 2014 Well they "stick" until next reboot, then I have to run WSS troubleshooter again in order to see the shares from my client machines. I will try your steps this afternoon after work, ~16.00 CET Per Quote Link to comment Share on other sites More sharing options...
0 Christopher (Drashna) Posted October 3, 2014 Share Posted October 3, 2014 Thank you for uploading the log files. However, could you do a complete uninstall of both products, and install the latest version? http://wiki.covecube.com/StableBit_DrivePool_Q8964978 http://wiki.covecube.com/StableBit_Scanner_Q8964978 https://stablebit.com/DrivePool/Download https://stablebit.com/Scanner/Download If the problem persists after that, then could you enable tracing, and duplicate the issue? http://wiki.covecube.com/StableBit_DrivePool_Log_Collection Quote Link to comment Share on other sites More sharing options...
0 pjakesson Posted October 3, 2014 Author Share Posted October 3, 2014 I could try the new versions, but I'd like to troubleshoot my current system first a bit. I think I have removed ServerFolders directory on D: and thus no "original" empty shares (Music, Videos....). Perhaps that is fooling WSS troubleshooter? Per Quote Link to comment Share on other sites More sharing options...
0 pjakesson Posted October 3, 2014 Author Share Posted October 3, 2014 I found a forum thread about my problem: http://forum.covecube.com/discussion/349/m4-lossing-shares-on-whs-2011-restart/p1 Is my version of DrivePool, version 1.3.1.7541, older than build 5536 mentioned to fix this problem? Per Quote Link to comment Share on other sites More sharing options...
0 pjakesson Posted October 4, 2014 Author Share Posted October 4, 2014 Hello again, somehow mysteriously it fix itself, the shares show up in Dashboard and are accessible from clients. I cannot say I did anything obvious to fix it. Strange, consider it case closed. Thanks anyway. Per Quote Link to comment Share on other sites More sharing options...
0 Christopher (Drashna) Posted October 4, 2014 Share Posted October 4, 2014 Well, I'm glad to hear that at least. As for the issue, there are a few things that could have caused this issue though. When it was "not working", was it just displaying that in the dashboard? Or where the shares completely inaccessible from another system? If it was just the dashboard, then the issue is with the "Windows Home Server Storage Manager" service, and not DrivePool or the Shared folders specifically. In fact, if you could grab, zip up and send me the entire "C:\ProgramData\Microsoft\Windows Server\Logs" folder, I will take a look a them to see what is going on. Email them to me at "christopher@covecube.com". That, or the issue *may* have been one of the ones fixed in version "1.3.3.7563" [D] Changed how pools are enumerated at boot time to get rid of the 1 second delay between when the virtual disk driver is loaded and when it spawns its disks.) As this may be enough to cause the discrepancy, especially on a quick booting system. Regards Quote Link to comment Share on other sites More sharing options...
0 pjakesson Posted October 6, 2014 Author Share Posted October 6, 2014 Well, I'm glad to hear that at least. As for the issue, there are a few things that could have caused this issue though. When it was "not working", was it just displaying that in the dashboard? Or where the shares completely inaccessible from another system? If it was just the dashboard, then the issue is with the "Windows Home Server Storage Manager" service, and not DrivePool or the Shared folders specifically. In fact, if you could grab, zip up and send me the entire "C:\ProgramData\Microsoft\Windows Server\Logs" folder, I will take a look a them to see what is going on. Email them to me at "christopher@covecube.com". Thanks for looking into this. Yes in fact it was just showing "missing" in the Dashboard but all clients could access the shares. But as I said suddenly the showed up in the Dashboard and all pointing to my Drivepool, so it "fixed" itself. . But... I still have a Dashboard warning "One or more pre-defined server folders are missing" but it doesn't says which one. I email you the logs when I get back from work. Thanks in advance. Per Quote Link to comment Share on other sites More sharing options...
0 pjakesson Posted October 6, 2014 Author Share Posted October 6, 2014 Thanks for your offer to help me Christopher, but since all shares seemed to work but still an annoying warning was left, I rebooted the server, and voila, the warning is gone. regards Per Quote Link to comment Share on other sites More sharing options...
0 Christopher (Drashna) Posted October 8, 2014 Share Posted October 8, 2014 Ah, yeah. For the most part.... warnings/errors like that usually get fixed by rebooting. However, sometimes, they get "stuck" and don't disappear normally. Worst case, delete the error, and it should "go away". Also, I would recommend not sharing the "D:\" drive at all. Unless you have a very good reason. And that is because, by default, Windows creates an "administrative" share for each of the drives, which you can find by using "\\SERVERNAME\d$\" Quote Link to comment Share on other sites More sharing options...
0 pjakesson Posted October 9, 2014 Author Share Posted October 9, 2014 Also, I would recommend not sharing the "D:\" drive at all. Unless you have a very good reason. And that is because, by default, Windows creates an "administrative" share for each of the drives, which you can find by using "\\SERVERNAME\d$\" Ah, I didn't know that, then I'll try to use \\SERVER\D$\ instead. Per Quote Link to comment Share on other sites More sharing options...
0 Christopher (Drashna) Posted October 10, 2014 Share Posted October 10, 2014 That, and the "$" symbol has the added advantage of hiding the share for normal view on the network. Quote Link to comment Share on other sites More sharing options...
Question
pjakesson
Hello,
I cloned my system disk to a new install, and most things went well.
Except, after reboot there are no shares (all on pool) exported
Then I run the WSS Troubleshooter and the share are exported correctly to my clients,
though the Dashboard says the shares are still missing and gives a critical error.
And it seems the shares stick until next reboot.
thanks in advance
Per
Link to comment
Share on other sites
12 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.