#27 clean unmount but require manually kill "imdisk devio for discutils library" to mount next.

[ccchan]

hi

yesterday or so, sometimes i've found that i need to kill the "task manager, users, ImDisk Devio for DiscUtils library"
to mount my splited .vmdks.

Today I cleanly unmounted the 1st VMDK,
it is a clean unmount.

but the 2nd VMDK, still need the above kill,
otherwise it will say the "some parameters wrong xxx" msg,

This is not a serial problem,
as i could still split data and upload to cloud.

So just file this ticket and let others know if newcomers cant mount the image.

thank you.

ps:
i mount using mountimage.exe,
and unmount using the virtual driver.

win10, 64b, 1809.

[ccchan]

title is cut:
clean unmount but require manually kill "imdisk devio for discutils library" to mount next.
thx

[v77]

You really should avoid to do that.
If DiscUtilsDevio is still running, this likely means that the dismount is not completed, and therefore you can lose data by killing this process.

In the "ImDisk Virtual Disk Driver" GUI, as long as the volume is in the list, this means that the volume is not dismounted.
If it is not present and DiscUtilsDevio still runs, then there is a bug. Even in this case, in an elevated command prompt, try to use these commands:
- get the list of imdisk volumes:
imdisk -l
- get informations about a volume:
imdisk -l -u unit
- force removal of a virtual disk:
imdisk -R -u unit
("unit" is the number you get with imdisk -l)

[ccchan]

hi

today after i used a vmdk (mount as RO, and then verify content /w another folder),
then unmount it.

at first it say some process hold the drive so cant unmount,
then i close all windows explorer,
then could unmount (cleanly) as show in screen-11's top.

--------after repeat this seems go away------screen-11's bottom
then i go to the 2nd vmdk,
rt click "mount as imdisk xxx",
and it doesn't show the size of the drive.
and failed to mount.
--------after repeat this seems go away------

then i click on the file selector instead,
choose the vmdk and it now show the size, see screen-12's middle,
but it still fails to mount! (screen-12's bottom)

screen-13 are the above commands you shown to me.

so, at the moment,
I am NOT ABLE to mount the 2nd VMDK.
1. Should I kill the ïmdisk devio for discutils library process
or 2. use the imdisk -R -u unit as you listed above? but as shown in
screen-13, device 0 and 1 has been removed.

i am free to help if any troubleshoot is needed.

at the moment i will kill that process otherwise
i cant mount any further vmdks.

thank you

[ccchan]

hi,
i tried to use "2", the commands you shown to remove 0 or 1,
as shown in screen-14.

but even after that.
the same error msg pops up.

so i think at the moment the only i can do is to kill that process...

thanks

[ccchan]

hey the problem in the title only happen with my m93p with the 1TB .vmdk,
win10pro, 64bit. 1809v

when I try with my t580, with a 250GB vmdk, it's fine!
win10home, 64bit. 1903v.

let me try later and tell you more!

sorry for that first.

(but my m93p still need to kill the process to go on).

[ccchan]

most update:
the m93p also functions ok now.

as i will use imdisk freq recently,
let me see see if that happens again.
thanks.

(the issue could be closed? any such function in
source forge as in github? thx)

[v77]

Ok thanks. I may have found something.
It's like DiscUtils takes too much time after it receives the dismount command. So for now, try to delay everything: wait a moment before starting the GUI, and wait before clicking OK.
I will add some checks for the next version.