Cannot open the disk 'D:\Program Files\Sage\sage-vmware-4.1\disk.vmdk'

53 views
Skip to first unread message

Rolandb

unread,
Nov 30, 2009, 10:57:36 PM11/30/09
to sage-support
Hi,

How serious is the following message?

Cannot open the disk 'D:\Program Files\Sage\sage-vmware-4.1\disk.vmdk'
or one of the snapshot disks it depends on.
Reason: Failed to lock the file.

Roland

Rolandb

unread,
Dec 1, 2009, 2:00:52 PM12/1/09
to sage-support
Hi,

Sage fails to start. Does this mean that I lost all my notebook files?

That would be very sad...........

Thanks in advance of a solution which save my files!!

Roland

Robert Bradshaw

unread,
Dec 1, 2009, 3:57:27 PM12/1/09
to sage-s...@googlegroups.com
I don't know much about Windows, but did you try restarting? That
might release any stale file locks. (Don't worry, your data should
still be there.)
> --
> To post to this group, send email to sage-s...@googlegroups.com
> To unsubscribe from this group, send email to sage-support...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/sage-support
> URL: http://www.sagemath.org

Rolandb

unread,
Dec 1, 2009, 11:58:47 PM12/1/09
to sage-support
I tried everything I could imagine: restarting VMWARE, inspection of
the individual vdmk files, restarting the computer, ...

It seems that I have to re-install Sage (for Windows).
The problem is that by re-installing, I will loose all my notebook
files.
So, I want to save those files first! BUT HOW?

Roland

William Stein

unread,
Dec 2, 2009, 12:10:25 AM12/2/09
to sage-support
Do you have enough disk space?

Do you have permissions? Can you run as an admin?

How big are all the files in sage-vmware-4.1? Could you consider
using 7zip to zip (or whatever) to zip up the whole directory and
somehow make it available online, so somebody else can try to mount
your disks and get your files?

William

dimpase

unread,
Dec 2, 2009, 12:24:55 AM12/2/09
to sage-support
well, you probably just need to remove some stale locks.
That is, somewhere on the VM, there is a place where files indicating
"busy" status
of a particular volume, so-called locks, are stored. On Windows hosts,
they have .lck extensions.
So you need to remove the one that is
causing you the trouble. However, a VM reboot should have taken care
of it.
(YMMV: It has been ages since I worked with VMware, so I might sound
vague on this)

Rolandb

unread,
Dec 2, 2009, 1:27:47 AM12/2/09
to sage-support
Hi William,

The 7zip file is 0.98 Gb, but I don't have a online place to download
it to.

Is there an other solution?

Roland

On 2 dec, 06:10, William Stein <wst...@gmail.com> wrote:

Rolandb

unread,
Dec 2, 2009, 10:45:38 PM12/2/09
to sage-support
Dear William,

The Sage files can be downloaded via http://rapidshare.com/files/315349439/sage-vmware-4.1.7z

Maybe I should add that my problem arose due to fact that due to the
SIGSEGV ERROR I had to restart my computer.

Thanks in advance for considering my problem!

Roland

On 2 dec, 06:10, William Stein <wst...@gmail.com> wrote:

Robert Bradshaw

unread,
Dec 2, 2009, 11:45:37 PM12/2/09
to sage-s...@googlegroups.com
On Dec 1, 2009, at 9:24 PM, dimpase wrote:

> well, you probably just need to remove some stale locks.
> That is, somewhere on the VM, there is a place where files indicating
> "busy" status
> of a particular volume, so-called locks, are stored. On Windows hosts,
> they have .lck extensions.
> So you need to remove the one that is
> causing you the trouble. However, a VM reboot should have taken care
> of it.
> (YMMV: It has been ages since I worked with VMware, so I might sound
> vague on this)
>

In other words, are there any .lck files sitting around your virtual
disks that you should delete, like a D:\Program Files\Sage\sage-
vmware-4.1\disk.vmdk.lck? . That alone might solve the problem.

- Robert


Rolandb

unread,
Dec 3, 2009, 2:35:02 PM12/3/09
to sage-support
Dear Robert,

I removed the maps *.lcd: no solution.
I cleaned my registry: no solution
I restarted my computer: no solution
.....
I became angry and I saved all disk*.* files, I installed Sage for
Windows again and replaced the new disk*.* files with the old files

Guess what: problem solved!

Maybe something for FAQ if people experience a SIGSEGV ERROR.

Thanks for all your support.

Roland

Robert Bradshaw

unread,
Dec 3, 2009, 3:11:53 PM12/3/09
to sage-s...@googlegroups.com
Glad you finally got this working. You should report this upstream to
vmware as well, as it sounds like a bug in their emulator.

- Robert

P.S. Just in case, there is a "download all" option on the notebook
that you might want to use :).
> --
> To post to this group, send email to sage-s...@googlegroups.com
> To unsubscribe from this group, send email to sage-support...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages