iSCSI page failure

Have you tried OS reinstall?I guess something messed up your apache config file,or you may need contact support center to find help.

What version of RAIDiator are you running?

Have you tried clearing your web browser cache?

What web browser are you using? Does using a different web browser make a difference?

You may wish to download your config backup (System > Config Backup), extract the zip contents and look at /etc/ietd.conf. Are the deleted LUNS still mentioned there?

If you look in the hidden ".iscsi" folder on your C volume (must be logged into CIFS i.e. \\ip.address.of.nas as "admin") do you see the deleted LUNS still there?


Btw iSCSI on the ReadyNAS is not yet compatible with ESXi 5, though NetGear is working on a 4.2.20 release to address this. This shouldn't affect use of Frontview though.

Hi

Thanks for the replies..

@MDM
RAIDiator version is 4.2.17, which I believe is up to date.
Ok, I have used Chrome, IE9 and Firefox and all do the same, web browser cache has been cleared.
Only the 3 current LUNS are listed and no evidence of previous, deleted, LUNS exists.

How do I access the hidden .iscsi folder c volume over CIFS as admin?, if i use a browser with \\readynas4200 the all i will get are the default shares listed.

I had read, after I posted, that there were compatibility issues with ESXi 5 so I now understand why this does not work. But I upgraded after ESXi 4.1 was failing to connect to any LUNS so there might be a wider issue here

@de niro
I haven't tried the OS reinstall as I do not want to lose the current iSCSI datastores if I can help it. Whilst this is a test system, it will be going live soon enough and I need to be able to fix these types of issues on a live system without drastic measures. If the apache config file was messed up wouldn't I lose access to most if not all the web interface? (not that up on apache configs so not 100% sure if this is the case). You're right I think a call to support might be in order :)

Regards
Drac

dean wheatley wrote:
\\readynas4200 the all i will get are the default shares listed.

You can use the command line of your PC. e.g. in XP/2003, go to Start > Run, type cmd and press enter.

dean wheatley wrote:
@de niro I haven't tried the OS reinstall as I do not want to lose the current iSCSI datastores if I can help it. Whilst this is a test system, it will be going live soon enough and I need to be able to fix these types of issues on a live system without drastic measures.

An OS Re-install wouldn't touch your iSCSI data stores.

dean wheatley wrote:
If the apache config file was messed up wouldn't I lose access to most if not all the web interface? (not that up on apache configs so not 100% sure if this is the case). You're right I think a call to support might be in order :)

The /etc/ietd.conf (included in the System > Config Backup) file is used for iSCSI. If there is a problem with this only the iSCSI section would be affected.

There is a newer firmware RAIDiator 4.2.19 available now (4.2.20 is expected to hopefully support iSCSI with ESXI 5), but I would work with support before updating the firmware.

If only the current LUNs are listed, deleting the files in /c/.iscsi for the deleted LUNs should be enough to rectify the problem. After doing that updating the firmware would be recommended as 4.2.19 addresses a problem for iSCSI: http://www.readynas.com/RAIDiator_x86_4_2_19_Notes

I managed to get this sorted, with the help of Netgear support. I updated the firmware first (which had no effect) then ran the OS reinstall which seemed to fix the issue. Based on what you have said I'm guessing that somehow the /etc/ietd.conf had become corrupted as it was only the iSCSI section of the web interface that was effected. Once that was done I was able to reconnect all my iSCSI stores and start all the VM's back up no problem. I have also been getting some odd errors stating "Snapshot on volume C was invalidated and has been removed due to reserve space being completely used" Not sure if this has any bearing in the situation?

I still can't access the .iscsi hidden folder. I tried your method through the CMD prompt but maybe my syntax is wrong. I used \\readynas\c\.iscsi, \\readynas\c, //readynas/c/.icsi and //readynas/c?

I get it now, read a few more forum questions on this. The computer I was using to try and connect to the c drive was using a windows domain account, when I tried to get to the root share from a non domain computer the c drive was listed along with admin drive and a couple of others. When tried to drill down into the folder I was prompted for a username and password, once I had logged in I had access to the system drives. There was nothing in them to speak of but at least I was able to access it.

Cheers for the advice...it's good to know someone out there can offer help :)

Oops I forgot to mention to use the "net use" command on the Windows command line to delete connections to NAS and make new one

If the data is still there it should be in the hidden .iscsi folder

No probs, I got it sorted in the end. My VM data was still there and I was able to reconnect Hyper -v to the datastore and start all my VM's back up. Now I have a whole different issue :) But i'll post that in a new thread..

Thanks for all your help!