Files aren't being saved

[myrdraal0]

I installed iSCSI cake this morning and was initially very pleased
with how everything was working; but, unfortunately, I later
discovered that whenever I reboot either the target or the initiator,
all my previously saved files are gone. Basically I end up with an
empty volume after every reboot.

Here is my system config:
Target:
Windows Server 2008 x64 (running under Hyper-V)
1.5GB RAM allocated to VM
126GB boot drive (running in .vhd file)
4.5TB RAID volume is directly mapped into this VM
500GB partition from RAID volume is being shared as iSCSI target
Local cache was disabled in iSCSI Cake after discovering this issue
(just in case), but it makes no difference

Initiator:
Windows Vista IA32 (physical system)
2GB RAM
Attaching to 500GB target

Any help with this would be appreciated, this is obviously a serious
problem that I'd like to get resolved.

Thanks!

[Jin]

The default mode will discard initiator's data after disconnect. You
can right click the disk to stop it and double click it to change its
property. Check the Enable super client and Disable CHAP option. Then
you will be able to save data to target.

[myrdraal0]

Thanks for the respose Jin! I obviously didn't understand te meaning
of the super client.

Unfortunately, when I enable that mode, I can no longer start the
disk. I get an error message that says "Disk start failed".
Hopefully you have another easy workaround for this:).

Thanks!

> > Thanks!- Hide quoted text -
>
> - Show quoted text -

[Jin]

Super client mode needs to open the source disk exclusively. Normally,
this error is due to some applications are using the source disk. You
can OpenedFilesView to find out what files are opened. Is file mode
disk an option for you? That could make things easier.

> > - Show quoted text -- Hide quoted text -

[myrdraal0]

I did verify that the disk is not being used by anything, but that
didn't fix the issue. After reading through some other posts I'm
thinking this may have to do with the fact that I'm using GPT
partitions - would that cause this problem?

Anyway, I'm creating a 500GB vmdk file right now that will hopefully
get this all working. My question on vmdk files is: Will my
performance suffer significantly over using the partition directly? I
am setting it up to pre-allocate the entire vmdk file so it probably
won't be done until tonight.

[Jin]

iSCSI Cake does not support GPT means a client can not see the
partition as what shows on server if the partition is formatted and
assigned a drive letter. If the GPT volume is not formated on server,
the client has no problem to use it as a physical disk to do
partitioning and formating. I think it was something else that had
prevented your disk from starting. You can send the iSCSICakeLog.txt
to sup...@iscsicake.com for further diagnosing.

[myrdraal0]

OK, I looked at that log and it looks like you are probably right -
but I still can't see any program that is using the partition.

Here's what I've done:
1) Ran Process Explorer and searched for any open handles on that
volume
2) Opened Disk Manager and verified that I can remove the drive letter
without any problems (typically if the drive is in use Windows will
give a message about removing the drive letter on the next boot)
3) Completely stopped McAffe just in case that is causing the issue.
4) Stopped the explorer process and created the new volume - then
immediately tried to start it in iSCSI Cake - but it still gives the
same error

Can you think of any other way to be sure I have exclusive access to
the partition?

BTW: this seems to be working well with the vmdk file, so I'm happy
with the product regardless - but I would still like to get it working
directly with its own partition if possible.

On Mar 30, 10:00 am, Jin <j...@iscsicake.com> wrote:
> iSCSI Cake does not support GPT means a client can not see the
> partition as what shows on server if the partition is formatted and
> assigned a drive letter. If the GPT volume is not formated on server,
> the client has no problem to use it as a physical disk to do
> partitioning and formating. I think it was something else that had
> prevented your disk from starting. You can send the iSCSICakeLog.txt

> to supp...@iscsicake.com for further diagnosing.

[Jin]

I think have fixed this small bug. iSCSI Cake is supposed to be able
to lock a volume. Can you try this one? http://www.iscsicake.com/iscsi/ccdisksetup1.8.0330.exe
One thing I need to mention is that the partition is not accessible on
the server unless you stop the iSCSI disk.

[myrdraal0]

I did install that version, but it didn't make any difference.

Fortunately, I re-read your previous message and was able to get this
working. The problem was that I had formatted the partition before
setting it up as a target disk. If I leave the partition unfomatted,
then it starts fine under Cake and I can just format it from the
initiator. This process does appear to leave the data completely
unreadable on the server - but that is an OK traid-off and I assume it
will start working once you get GPT support added (although it looks
like that isn't a priority for you guys).

Thanks for your help on this Jin!

On Mar 30, 10:53 am, Jin <j...@iscsicake.com> wrote:
> I think have fixed this small bug. iSCSI Cake is supposed to be able

> to lock a volume. Can you try this one?http://www.iscsicake.com/iscsi/ccdisksetup1.8.0330.exe