Jump to content
Covecube Inc.

Mick Mickle

Members
  • Posts

    83
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Mick Mickle

  1. Thanks, Christopher. It sounds like the problem is solved moving forward from 3090 and 3091. Still to come is data export/print capability for specific disk details, settings, and locations, some of which will be available in the future in Stablebit Cloud, I understand.
  2. At a minimum, update instructions should suggest a screen print before upgrade to document names and locations of disks. (Implementation of a print capability - Ticket 6750140 - would have gone a long way toward mitigating this upgrade problem.)
  3. I agree that "never scanned" resets aren't much of a problem, since Scanner will simply scan again. (It's weird that my server has just 1 of 11 disks that was still "Healthy" with all other correct settings after upgrade.) Of more concern to me are all the lost settings -- names, locations, whether to scan automatically (which would be duplicative for pass-through disks if Scanner is installed on both host & VM), etc. Those items have to be re-entered for customization to continue.
  4. Okay, went back to 3062, refreshed all disk settings with save, then upgraded to 3090 (forgot about 3091). Same problem. But I still have one disk that all details carry over on. If we can figure out the difference between that disk data and all the ones that have amnesia, maybe problem can be solved. What do you need?
  5. I did have previous versions working so I restored an earlier version of the \service\store folder, but no change in UI depiction. I then stopped the service again and copied my earlier backup of that folder over it -- big mistake. Now I'm in a trial license/license transfer loop. Hopefully, uninstalling, populating those folder with backup, and reinstalling previous version as planned will go smoother. If not, expect a ticket.
  6. A few years ago, I requested a basic feature to print the Scanner UI and disk details to use as a record of disk locations, details, and settings. (I don't think that feature was ever implemented.) Such a printout could be used to manually recreate disk settings after an update that loses that data, although it wouldn't help with specific disk surface scan results from the prior version. While writing this post, I reviewed the interface of 2.5.2.3190 and noticed that there is one disk, and only one, that retained its name, location, and health status. I think that I may have input that information more recently, while all the others haven't had disk details changed in a long time. So maybe Christopher's theory about corrupt data may be on track. Perhaps the data for that particular disk refreshed the relevant data file when saved, while the data files for the other disks remained corrupted or otherwise incompatible with the upgrade process. I'll be restoring 2.5.1.3062, then I'll refresh the disk settings for each disk by making a small change and saving the setting. Then, I'll upgrade to 2.5.2.3191 and see if that makes a difference.
  7. This is very similar to the issue I raised at the thread below. And once again, I updated my WS2012R2 Scanner 2.5.1.3062 with what I thought was the latest release version 2.5.2.3190 only to have the result be the loss of scanning history, individual disk scan information, and individual disk settings, including, unique names and bay locations. I see by your post that the release replacement 2.5.2.3191 doesn't fix that problem. I'm guessing those settings are in \ProgramData\StableBit Scanner\Service\Store, which now uses json extensions. Maybe there's a way to copy backup files from this folder back into it.
  8. For the benefit of other users, this is a known problem, per Christopher. I was able to get back to the release version 3062 with all disk configurations, custom names, and scan history by following these steps: Uninstall the beta, then delete the Scanner folders in Program Files (x86), ProgramData, and \User\AppData\Local & Roaming (just in case). I also stopped the Scanner Service before doing all this, just in case. Have the recovered folders from a recent backup (I use Acronis Backup 11.5) saved into a temporary folder already, then copy them to ProgramData and User\AppData. Install 3062 Release and you're back to where you were before the problem. ( I also copied the old Scanner.Service.exe.config into appropriate folder in Program Files (x86) because it had a recent date, although I don't think I've ever done anything with it except experiment.) I also gave the latest December 2017 beta 3130 a whirl, and it, too, loses all disk configuration settings and history of scans after ugrade from 3062 on WS2012R2. So I rinsed and repeated above steps. I rely too much on Scanner to keep track of the 12 HDDs in my server as to their bay location and whether they're in my VM DrivePool or not. (Upgrading to the beta Scanner in the VM WS2012R2E did not result in amnesia there.) P.S. I had no problems with Release 3062 in the several years I've been using it, BTW. I just thought the newer beta version might be better. And my long absence on this forum just reflects the problem-free experience I've been having. Kudos to CoveCube StableBit!
  9. I just upgraded from the Release version 2.5.1.3062 to Beta version 2.5.2.3103 on my WS 2012 R2 server. Now, my extensive custom names and locations as well as other settings under Disk Settings are gone. (Edit: Also, all disks, which had been scanned many times by the previous version, now show they have never been checked.) Is this a known issue? Any chance of finding a configuration file that may have been left behind by the earlier version or that I might have in a backup that I can restore in order to avoid examining all the bays and entering all the data again? Interestingly, I did the same upgrade using the wssx installation in WS 2012 R2 Essentials running in Hyper-V on the same server, and all the Disk Settings were preserved. What hurts most is that I was just fine with the release version, but 2.5.2.3103 has been out so long that I figured it was bullet proof, and I had previously upgraded some Windows 10 machines with it already.
  10. Old tread, but new question: For encrypting DrivePool drives, is Securstar's DriveCrypt Plus Pack supported? I would think so, but because of TrueCrypt not being supported, that throws other full-disk encryption solutions into question.
  11. Well, at first, I thought Beta 2.2.0.651 solved the MyMovies accessing and logging the DrivePool drive letter. It looked like only the UNC path was being referenced and logged by MyMovies. However, after I restarted the MyMovies General Service and the program began monitoring folders, their log did specify the DrivePool letter after all, replacing it with the UNC. So I guess it wasn't the "removable drive" aspect that you mentioned. However, my performance has dropped unacceptably: I'm watching TeraCopy transfer a 1.5GB file to the pool at about 500KBs right now. With the 561 release version, transfer speed was blazing enough that I didn't even look twice. Perhaps something else is in play here, but if rebooting my client computer doesn't help, I'll probably go back to the release version. Edit: Tried again later and got 30-35 MBps, so speed isn't the problem I thought it was.
  12. Christopher, thanks for your extensive reply. Maybe showing up as a removable drive is why My Movies logs continue to reference the DrivePool drive letter as well as the UNC. I'll update to the DrivePool beta you referenced and see if that changes things. My initial problem with My Movies General Service runaway memory stopped with a corrected erroneous path on one TV series title. That General Service continuing to parse the DrivePool letter rather than just the UNC path could be an efficiency/overhead (or other) issue, though. If the beta doesn't fix it, I'll upload a dump of the My Movies process. I must say, you guys would be going above and beyond to take a look at that. My hat's off to you for offering. I hope you're feeling better after your recent illness!
  13. Yeah, I was using My Movies back with WHS v1. I've also changed server names twice, which turned out to be a problem eventually getting all the path names for MM media files moved because TV shows only move all the episodes within a series, unlike movies which MM will offer to move all en masse. In fact, since Brian Binnerup said in my MM forum thread that version 5.22 Collection Management will filter by path, I just tested an old server name and found one hit for a TV episode with the wrong old path. I imagine that has been causing MM some issue. Other than the one old path name that I just corrected, all of my MM titles are using the right UNC \\servername\videos path. But the DrivePool drive X:\ still shows up in the MM log for some reason. Also, MM monitor settings are only using UNC, not the local server DrivePool letter. Just to be clear, MM has been working great, allowing WMC on the HTPC client to always play movies and TV shows. But the logs apparently show that the MM general service must be using a lot of overhead looking for files. My original MM support issue was that the general service is eating memory, and MM support thought that's probably caused by an error or corruption in the database. Now, they're thinking it might be because of DrivePool.
  14. Is the DrivePool pooled drive letter, in effect, a mapped network drive? The reason I ask is that I've been having trouble lately with My Movies, where drive X:\serverfolders\videos (X: being my pooled drive) shows up in My Movies logs rather than the UNC path of \\servername\videos. My Movies Support thinks that it might be because of the DrivePool setup http://www.mymovies.dk/forum.aspx?g=posts&m=204363#204363. Of course, I've been using DrivePool and My Movies for years; however, maybe some database glitch has brought a problem to the surface that involves this issue.
  15. Still got the problem. Possibly related to PerfectDisk 13?
  16. Thanks for the Ping info. I've used it before but already forgot if the column was functional in earlier versions. Downloaded and installed 3053 over the weekend and Ping is fixed. (Reminded me that Alex and I discussed possible use of a different color for Burst test some months ago, because it's easy to forget if you've left it running. Thought I'd nudge that idea a little bit.) Sorry so far off topic of this thread. About the Performance column. I'm still getting the issue with 3053 Beta. For example, the column will display only one drive's data in the column with others blank. Close UI and reopen, all fields in the column blank. Restart scanner service fixes temporarily: Start UI, all drives displayed in performance; close UI, and the whole column is blank. See contact update.
  17. Okay, I initiated a contact request 897285 and uploaded both the scanner.service.dmp and the errorreports.zip. But the scanner.ui.dmp was zero-size file. (The performance column has become blank again, but I haven't gotten around to messing with the performance counters you suggested earlier.)
  18. I noticed the blank Performance column also, but I forgot that there was a Q2150495 topic. The issue occurred when I upgraded 3048 Beta over 3041 Beta. Doing a repair to the installation didn't fix it, but uninstalling and reinstalling did. Second question though is that the Ping column is blank. When Ping is checked, resulting Performance is displayed in that column, but what's the Ping column for?
  19. I tested various connection settings for the MS Remote Desktop for Android using my phone, both with Wi-Fi enabled (on my LAN) and disabled (over the Internet on 4G). (My WS2012R2E server is setup for normal RWA with the router forwarding only ports 80 and 443. I'm pretty sure the connection results I found would be the same for WHS2011 as well. The server and all my client PCs have remote connections enabled (under Remote settings in System properties, and the Network Level Authorization restriction is unchecked just because I want the lowest common denominater for access from earlier OSs). This is what I found: 1. On the LAN with Wi-Fi, no Gateway is needed. Voila! Just using the Server’s or other PC’s computer name for the PC Name gets you there. (Using the RWA URL for the Server is a dead end, which I expected.) 2. On the Internet with 4G, without a Gateway, I can’t connect even to the Server using either the computer name or the RWA address (xxxx.homeserver.com or remotewebaccess.com) for the PC Name. But once you setup your Server as the Gateway with the RWA address for its PC Name, you can jump onto the Server or any other LAN PC using just the computer name in the PC Name for Remote Desktop connection (with that Gateway specified.) 3. Assuming that you leave the credentials fields blank when you set up the app connections, if you have the same credentials on your Server, which is the Gateway, and on your other PCs, then when you enter your credentials for target computer (Remote Desktop), that will be the only time you’re asked, because those same credentials will pass to the Gateway. This is the case, for example, if your target is your Server, which is one and the same as the Gateway. If the credential for your Server and target Remote Desktop are different, you’ll enter credentials for the Remote Desktop and then be asked again for the Gateway. So I set up two Remote Desktops for each computer I want to access, one for the Internet and one for the LAN, depending on whether I’m at home or not; e.g., Server and Server LAN, with Server LAN having “None” for the Gateway. It’s really that simple for me. I’ve done all the manual firewall and port settings in the past when I set up WS208R2 Hyper-V Server w/no GUI. But I prefer it to be easier when it can be.
  20. An afterthought: You do have "Allow remote connections to this computer" set on the server, right? Just wondering if that might be a hiccup.
  21. Actually, only ports 80 and 443, the standard RWA setup, need to be forwarded. Yeah, for traditional RDP - and for a specific computer without a gateway - 3389 should be forwarded as Doug said, but not necessary with WHS2011 or Essentials. If you can reach your server from the Internet with RWA, it should work as a Gateway and get you onto itself or another computer without 3389 (at least with this app on Android). And, think about it, when you RWA to your WHS or Essentials, you have the continuing option to RDP into any computers connected to the server, all without having 3389 forwarded. I've got to say, dbailey75, that I was surprised how easy it was to get connected with this Android app. It did totally bypass the RWA interface and the Dashboard. Really, the only connection specs I used were (1) DDNS address for the RWA to the server for the Gateway (___.remotewebaccess or homeserver.com) and (2) the computer name, "Server" or whatever, for the Remote Desktop. No IP addresses. (I just double-checked my settings.)
  22. I've just been using my username w/o any domain name prefix & it's been working fine for me. Or you can put in the server Name \ user name.
  23. On the RDP app, set up a "Gateway" and you can use it to access any PCs, including your server, that you've enabled remote access to on your LAN. Each of those PCs would be set up in the app as "Remote Desktops", and when you set them up, you need to specify the Gateway you set up earlier. So for me, I entered just the RWA (w/o the port, just as you'd connect if you were using RWA) address for my WS2012R2E as the Gateway. Name the Gateway with your server name. (I leave credentials blank and fill in when asked in case my phone ever gets compromised.) Under Remote Desktops, enter computer name for any LAN computer you've set up for Remote access. What you'll wind up with is a list of your computers, including your server if you want to RDP into it, and a list of gateways, but probably just one of those which is also your server. Then when you use the app, you select the computer (Remote Desktop) you want to control and the app will use your server to get there. Naturally, if you select your server, you'll connect through it, but stay on it. When you run the app, you are asked for username and password twice: once for the target computer and once for the gateway. If you enter all this credential info at the time you set up the gateway and RDs (or later), I reckon you bypass those prompts, but I prefer to maintain more security than that.
  24. Well, I see what you mean about every platform supporting RDP. I just discovered the free Microsoft Remote Desktop for Android in Google Play Store. It might replace TeamViewer as my favorite way to access my server and my other computers remotely from my phone and tablet. (It wasn't available when I got my Samsung Galaxy S3.) You can switch between mouse cursor and touch control of the remote desktop, so you can actually put the - ugh - Modern Start screen and apps in Win 8/2012 to practical use with an Android device.
  25. (Tried to post this as a support contact, but the contact web pages produce only an error right now.) With Scanner v 2.4.0.2929 in Essentials Experience VM of Windows Server 2012 R2 Essentials, Scanner completes a scan of a 2TB Seagate drive with no errors, including a file system check, then it starts scanning all over again, and the status still erroneously says that portions of this disk have never been checked for problems. The same outcome occurs when scanning with v 2.4.0.2928 on the host. Currently, that particular pass-through drive is working okay in DrivePool, and there are not SMART errors or warnings. Earlier, a couple of days ago, the VM started to boot slowly and everything became wonky until I set the DrivePool service to manual. With DrivePool service off, all seemed speedy and normal again. But I brought all the DrivePool drives online on the host and ran a chkdsk on each. On the particular drive in question, chkdsk /f couldn't complete and produced Windows event id 153 warnings. Also, SMART showed 2 Current Pending Sector Count and 2 Uncorrectable Sector Count. I then ran the Scanner scan on it in the host, and after completion, it said that the file system was damaged and needed to be repaired. Of course, Scanner then relies on chkdsk to do that (unfortunately, there's little feedback to chkdsk when you go through Scanner, whereas, you do get appropriate feedback when using the cmd line). (Whatever happened to the Scanner feature to salvage data from damaged sectors or to state that there's no data on the damaged sectors?) After hours of no feedback and the repair process still looking like it was underway, I stopped the process. Since then, no performance issues with that drive, no SMART warnings (SMART even shows 0 Reallocated Sectors Count), but Scanner continues to loop the scan as described above. I know the drive is "iffy", but why isn't Scanner working correctly on it? Could use a little improvement in the repair interface through Scanner, which currently leaves the user in the dark as to its progress. Edit: Since the Contact webpage is working today, I created a ticket on this.
×
×
  • Create New...