A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Windows 10 » Windows 10 Help Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

"Get Volume Name for Volume Mount Point"



 
 
Thread Tools Rate Thread Display Modes
  #1  
Old December 12th 16, 10:54 PM posted to alt.comp.os.windows-10
No_Name
external usenet poster
 
Posts: 7
Default "Get Volume Name for Volume Mount Point"

My backup software (DiskImage by LSoft) runs a backup fine, but tells me at
the end that there is "one problem", and it is always the same problem,
thus:

GetVolumeNameForVolumeMountPoint(1) for "\\?\GLOBALROOT\Device
\HarddiskVolume1\" failed. Error = 1 (Unknown error code).


Basically, I'm asking if there is a way I can create a volume name? I've
not had to do a restore yet, so I don't know if it would prevent a full
restore or not. Thanks for any help.

Tony
Ads
  #2  
Old December 13th 16, 01:29 AM posted to alt.comp.os.windows-10
T
external usenet poster
 
Posts: 4,600
Default "Get Volume Name for Volume Mount Point"

On 12/12/2016 01:54 PM, wrote:
My backup software (DiskImage by LSoft) runs a backup fine, but tells me at
the end that there is "one problem", and it is always the same problem,
thus:

GetVolumeNameForVolumeMountPoint(1) for "\\?\GLOBALROOT\Device
\HarddiskVolume1\" failed. Error = 1 (Unknown error code).


Basically, I'm asking if there is a way I can create a volume name? I've
not had to do a restore yet, so I don't know if it would prevent a full
restore or not. Thanks for any help.

Tony


Hi Tony,

Your backup drive may be bad. Check it by seeing if you
can browser around it with Windows Explorer and if
you cam create files and delete them.

Defraggler also has a quick and dirty SMART test of your
hard drive (Drive Health). Do not use on an SSD or
flash drive:
http://www.piriform.com/defraggler/download

USB Backup drives go bad a lot (they are usually so cheap,
it is amazing they work at all). These guys make good drives,
but I have seen them go bad too. Their tech support is
EXTRAORDINARY (disclaimer, I sell them almost exclusively):
http://www.g-technology.com/products

If your drive is good, it is time to contact LSoft. There
may be a bug in their software.

And ALWAYS, ALWAYS test your backups to make sure they are good.
I can not tell you how many times folks have relied on backups
that were not actually there. They had never though to verify
their backups (or couldn't be bothered).

-T
  #3  
Old December 13th 16, 01:34 AM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default "Get Volume Name for Volume Mount Point"

wrote:
My backup software (DiskImage by LSoft) runs a backup fine, but tells me at
the end that there is "one problem", and it is always the same problem,
thus:

GetVolumeNameForVolumeMountPoint(1) for "\\?\GLOBALROOT\Device
\HarddiskVolume1\" failed. Error = 1 (Unknown error code).


Basically, I'm asking if there is a way I can create a volume name? I've
not had to do a restore yet, so I don't know if it would prevent a full
restore or not. Thanks for any help.

Tony


Are you in the "top row - middle item" window when it happens ?

http://lsoft.net/diskimage_screen.aspx#!prettyPhoto

A utility that uses a "similar" identifier, is dd.exe.

dd --list

And that will list all the partitions, and give some
details. You might be able to figure out which partition
it is complaining about, and then take action based
on what you learn.

http://www.chrysocome.net/dd

http://www.chrysocome.net/downloads/dd-0.6beta3.zip

To use that, you want to start an Administrator Command Prompt
window, as access to disks at the physical level requires
administrator.

Windows also has a built-in command "mountvol", but that
doesn't give enough info in this case. The third-party
"dd" port is more likely to hint at which one is the
trouble-maker.

Paul
  #4  
Old December 13th 16, 02:58 AM posted to alt.comp.os.windows-10
Jason
external usenet poster
 
Posts: 878
Default "Get Volume Name for Volume Mount Point"

On Mon, 12 Dec 2016 16:29:08 -0800 "T" wrote in
article
And ALWAYS, ALWAYS test your backups to make sure they are good.

+1!

Years and years ago I learned the lesson about testing. Most backup
software has a validation function that reads the backup to see if it's
damaged. That's a halfway measure. It doesn't beat taking a deep breath
and restoring a full backup as a test, however.
  #5  
Old December 13th 16, 03:13 AM posted to alt.comp.os.windows-10
pjp[_10_]
external usenet poster
 
Posts: 1,183
Default "Get Volume Name for Volume Mount Point"

In article , lid says...

On 12/12/2016 01:54 PM,
wrote:
My backup software (DiskImage by LSoft) runs a backup fine, but tells me at
the end that there is "one problem", and it is always the same problem,
thus:

GetVolumeNameForVolumeMountPoint(1) for "\\?\GLOBALROOT\Device
\HarddiskVolume1\" failed. Error = 1 (Unknown error code).


Basically, I'm asking if there is a way I can create a volume name? I've
not had to do a restore yet, so I don't know if it would prevent a full
restore or not. Thanks for any help.

Tony


Hi Tony,

Your backup drive may be bad. Check it by seeing if you
can browser around it with Windows Explorer and if
you cam create files and delete them.

Defraggler also has a quick and dirty SMART test of your
hard drive (Drive Health). Do not use on an SSD or
flash drive:
http://www.piriform.com/defraggler/download

USB Backup drives go bad a lot (they are usually so cheap,
it is amazing they work at all). These guys make good drives,
but I have seen them go bad too. Their tech support is
EXTRAORDINARY (disclaimer, I sell them almost exclusively):
http://www.g-technology.com/products

If your drive is good, it is time to contact LSoft. There
may be a bug in their software.

And ALWAYS, ALWAYS test your backups to make sure they are good.
I can not tell you how many times folks have relied on backups
that were not actually there. They had never though to verify
their backups (or couldn't be bothered).

-T


The biggest problem with having a backup is insuring it's actually
usable. For most the only way of determining this is to actually try and
restore the backup. This means on original pc the original system gets
overwritten. That's not viable as it puts that system at risk so the
best they can hope for is some verify feature when creating the backup
and hope it's all never needed or works if it is.
  #6  
Old December 13th 16, 03:16 AM posted to alt.comp.os.windows-10
T
external usenet poster
 
Posts: 4,600
Default "Get Volume Name for Volume Mount Point"

On 12/12/2016 06:13 PM, pjp wrote:
In article , lid says...

On 12/12/2016 01:54 PM,
wrote:
My backup software (DiskImage by LSoft) runs a backup fine, but tells me at
the end that there is "one problem", and it is always the same problem,
thus:

GetVolumeNameForVolumeMountPoint(1) for "\\?\GLOBALROOT\Device
\HarddiskVolume1\" failed. Error = 1 (Unknown error code).


Basically, I'm asking if there is a way I can create a volume name? I've
not had to do a restore yet, so I don't know if it would prevent a full
restore or not. Thanks for any help.

Tony


Hi Tony,

Your backup drive may be bad. Check it by seeing if you
can browser around it with Windows Explorer and if
you cam create files and delete them.

Defraggler also has a quick and dirty SMART test of your
hard drive (Drive Health). Do not use on an SSD or
flash drive:
http://www.piriform.com/defraggler/download

USB Backup drives go bad a lot (they are usually so cheap,
it is amazing they work at all). These guys make good drives,
but I have seen them go bad too. Their tech support is
EXTRAORDINARY (disclaimer, I sell them almost exclusively):
http://www.g-technology.com/products

If your drive is good, it is time to contact LSoft. There
may be a bug in their software.

And ALWAYS, ALWAYS test your backups to make sure they are good.
I can not tell you how many times folks have relied on backups
that were not actually there. They had never though to verify
their backups (or couldn't be bothered).

-T


The biggest problem with having a backup is insuring it's actually
usable. For most the only way of determining this is to actually try and
restore the backup. This means on original pc the original system gets
overwritten. That's not viable as it puts that system at risk so the
best they can hope for is some verify feature when creating the backup
and hope it's all never needed or works if it is.



I love open source for this reason.

Absolute requirement: I must be able to manipulate the backup
with a file browser. ABSOLUTELY NO PROPRIETARY ****E!



  #7  
Old December 13th 16, 03:17 AM posted to alt.comp.os.windows-10
T
external usenet poster
 
Posts: 4,600
Default "Get Volume Name for Volume Mount Point"

On 12/12/2016 05:58 PM, Jason wrote:
On Mon, 12 Dec 2016 16:29:08 -0800 "T" wrote in
article
And ALWAYS, ALWAYS test your backups to make sure they are good.

+1!

Years and years ago I learned the lesson about testing. Most backup
software has a validation function that reads the backup to see if it's
damaged. That's a halfway measure. It doesn't beat taking a deep breath
and restoring a full backup as a test, however.


I have seen a lot of tears over the years over not verifying
your backups.
  #8  
Old December 13th 16, 03:56 AM posted to alt.comp.os.windows-10
Jason
external usenet poster
 
Posts: 878
Default "Get Volume Name for Volume Mount Point"

On Mon, 12 Dec 2016 22:13:37 -0400 "pjp"
wrote in article

For most the only way of determining this is to actually try and
restore the backup. This means on original pc the original system gets
overwritten. That's not viable as it puts that system at risk


The system is already "at risk" if that doesn't work, so what's to be
lost?
  #9  
Old December 13th 16, 03:57 AM posted to alt.comp.os.windows-10
Jason
external usenet poster
 
Posts: 878
Default "Get Volume Name for Volume Mount Point"

On Mon, 12 Dec 2016 18:16:09 -0800 "T" wrote in
article
Absolute requirement: I must be able to manipulate the backup
with a file browser.


Acronis lets you do this. It's a simple way to recover a file or two if
necessary. I used it a week ago for just that purpose - stoopid me had
deleted a couple of files I thought were saved elsewhere. (They weren't!)
  #10  
Old December 13th 16, 04:54 AM posted to alt.comp.os.windows-10
Char Jackson
external usenet poster
 
Posts: 10,449
Default "Get Volume Name for Volume Mount Point"

On Mon, 12 Dec 2016 21:56:35 -0500, Jason wrote:

On Mon, 12 Dec 2016 22:13:37 -0400 "pjp"
wrote in article

For most the only way of determining this is to actually try and
restore the backup. This means on original pc the original system gets
overwritten. That's not viable as it puts that system at risk


The system is already "at risk" if that doesn't work, so what's to be
lost?


Surely you see the difference between a currently working system that
may or may not have a viable backup and a system that's been completely
trashed by trying to restore a mangled backup?

I'm with pjp on the scenario that he described. A better way, but not so
practical for a whole lot of people, is to temporarily install a spare
drive and restore to that. Most people are not going to go there, so
using the backup program to 'verify' each backup is about as good as
it's going to get, unfortunately.

  #11  
Old December 13th 16, 04:57 AM posted to alt.comp.os.windows-10
Char Jackson
external usenet poster
 
Posts: 10,449
Default "Get Volume Name for Volume Mount Point"

On Mon, 12 Dec 2016 21:57:46 -0500, Jason wrote:

On Mon, 12 Dec 2016 18:16:09 -0800 "T" wrote in
article
Absolute requirement: I must be able to manipulate the backup
with a file browser.


Acronis lets you do this.


I think all of the major backup/archive/imaging packages offer the same,
but you typically have to mount the archive first. That's the step that
T is objecting to, I believe.

  #12  
Old December 13th 16, 05:09 AM posted to alt.comp.os.windows-10
Jason
external usenet poster
 
Posts: 878
Default "Get Volume Name for Volume Mount Point"

On Mon, 12 Dec 2016 18:17:07 -0800 "T" wrote in
article
I have seen a lot of tears over the years over not verifying
your backups.


I've shed a few... I do a full backup and then half a dozen incrementals
until the next full one. After each, I copy the backup to an external
drive and then run verification on the copy.
  #13  
Old December 13th 16, 06:02 AM posted to alt.comp.os.windows-10
T
external usenet poster
 
Posts: 4,600
Default "Get Volume Name for Volume Mount Point"

On 12/12/2016 08:09 PM, Jason wrote:
On Mon, 12 Dec 2016 18:17:07 -0800 "T" wrote in
article
I have seen a lot of tears over the years over not verifying
your backups.


I've shed a few... I do a full backup and then half a dozen incrementals
until the next full one. After each, I copy the backup to an external
drive and then run verification on the copy.


I am a backup whore
  #14  
Old December 13th 16, 06:30 AM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default "Get Volume Name for Volume Mount Point"

pjp wrote:
In article , lid says...
On 12/12/2016 01:54 PM,
wrote:
My backup software (DiskImage by LSoft) runs a backup fine, but tells me at
the end that there is "one problem", and it is always the same problem,
thus:

GetVolumeNameForVolumeMountPoint(1) for "\\?\GLOBALROOT\Device
\HarddiskVolume1\" failed. Error = 1 (Unknown error code).


Basically, I'm asking if there is a way I can create a volume name? I've
not had to do a restore yet, so I don't know if it would prevent a full
restore or not. Thanks for any help.

Tony

Hi Tony,

Your backup drive may be bad. Check it by seeing if you
can browser around it with Windows Explorer and if
you cam create files and delete them.

Defraggler also has a quick and dirty SMART test of your
hard drive (Drive Health). Do not use on an SSD or
flash drive:
http://www.piriform.com/defraggler/download

USB Backup drives go bad a lot (they are usually so cheap,
it is amazing they work at all). These guys make good drives,
but I have seen them go bad too. Their tech support is
EXTRAORDINARY (disclaimer, I sell them almost exclusively):
http://www.g-technology.com/products

If your drive is good, it is time to contact LSoft. There
may be a bug in their software.

And ALWAYS, ALWAYS test your backups to make sure they are good.
I can not tell you how many times folks have relied on backups
that were not actually there. They had never though to verify
their backups (or couldn't be bothered).

-T


The biggest problem with having a backup is insuring it's actually
usable. For most the only way of determining this is to actually try and
restore the backup. This means on original pc the original system gets
overwritten. That's not viable as it puts that system at risk so the
best they can hope for is some verify feature when creating the backup
and hope it's all never needed or works if it is.


You restore to an empty drive.

You know, that drive you keep for emergencies.

You have to own empty drives, if you expect to
"dial in" backup/restore software. I recommend a
minimum of two spare drives.

And yes, this does encourage the collection of
vast numbers of hard drives. (Once you start buying
spare hard drives, you... just... can't... stop.) So this
is good business for Seagate and WDC. They love
backup people :-)

Paul
  #15  
Old December 14th 16, 06:28 PM posted to alt.comp.os.windows-10
No_Name
external usenet poster
 
Posts: 7
Default "Get Volume Name for Volume Mount Point"


My thanks to all who replied!

I was (finally) able to get through to LSoft tech support,and the tech told
me that the message is basically an unknown glitch to them, but development
is searching for a workaround. But he also said: "If you can verify the
backup" (I did) "and if you can explore the backup and extract files from
it" (I can), "then it should restore with no problem".

Tony


 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 12:01 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.