SnapDrive 6 & Windows 2008 - can't see or connect disks in SD but can see them in Disk Management MMC - only mount read-only

[Raj Patel-2]

Hi,

Another question - I have a datawarehouse box - has 4 luns -> SD 6.1
and Server 2k8 both 64bit.

I can't seem to reconnect the LUN's using the SD wizard - however they
do end up appearing in the Server Disk Management MMC.

Catch is they will only mount read-only (but at least the data is fine).

In iSCSI session management it will see the connected LUN's related to
the igroup.

One of two things tends to happen - if I try to use SD I either get a
120 sec time out or I get an error about the lun already being mapped
(presumably by the built in iSCSI initiator).

As per a previous post - this box was fine until a controller/ontap upgrade.

I've tried zapping the igroup and mappings on the SAN and removing all
traces from SD and the MS iSCSI initiator but I can't seem to overcome
this problem.

Any ideas ? Worst case I can carve off a whole new set of LUN's and
move the data but I really don't want to have to do that if I don't
have to.

Thanks in advance,
Raj.

[Ledbetter, Charles]

Sounds to me like the NTFS volume inside the LUN is set to Hidden and/or
Readonly.  There's an old Veritas bug that would cause this.

Look for a utility called "vflag.exe" from Microsoft.  Mount the LUN
manually and run "vflag -display *" and look for one marked
hidden/readonly.

Use vflag to clear it.  You can also use Diskpart.exe to do the same
thing.

-Charles



-----Original Message-----
From: Raj Patel [mailto:phigmov@...]
Sent: Saturday, November 07, 2009 9:27 PM
To: toasters@...
Subject: SnapDrive 6 & Windows 2008 - can't see or connect disks in SD
but can see them in Disk Management MMC - only mount read-only


Hi,

Another question - I have a datawarehouse box - has 4 luns -> SD 6.1 and
Server 2k8 both 64bit.

I can't seem to reconnect the LUN's using the SD wizard - however they
do end up appearing in the Server Disk Management MMC.

Catch is they will only mount read-only (but at least the data is fine).

In iSCSI session management it will see the connected LUN's related to
the igroup.

One of two things tends to happen - if I try to use SD I either get a
120 sec time out or I get an error about the lun already being mapped
(presumably by the built in iSCSI initiator).

As per a previous post - this box was fine until a controller/ontap
upgrade.

I've tried zapping the igroup and mappings on the SAN and removing all
traces from SD and the MS iSCSI initiator but I can't seem to overcome
this problem.

Any ideas ? Worst case I can carve off a whole new set of LUN's and move
the data but I really don't want to have to do that if I don't have to.

Thanks in advance,
Raj.

[Raj Patel-2]

Thanks Charles,

Olaf from Netapp set me on the right track yesterday:

I used a combination of these articles to set me on the right track

http://communities.netapp.com/thread/3313

https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb41190

I still see four 'phantom' drives in Disk Management MMC (+ the real
four) but at least the four that I couldn't mount via SnapDrive or
would only mount read-only are now OK.

Thanks to everyone for their help.

Raj.

On 11/10/09, Ledbetter, Charles <Charles.Ledbetter@...> wrote:

> Sounds to me like the NTFS volume inside the LUN is set to Hidden and/or
> Readonly.  There's an old Veritas bug that would cause this.
>
> Look for a utility called "vflag.exe" from Microsoft.  Mount the LUN
> manually and run "vflag -display *" and look for one marked
> hidden/readonly.
>
> Use vflag to clear it.  You can also use Diskpart.exe to do the same
> thing.
>
> -Charles
>
>
>
> -----Original Message-----
> From: Raj Patel [mailto:phigmov@...]
> Sent: Saturday, November 07, 2009 9:27 PM
> To: toasters@...
> Subject: SnapDrive 6 & Windows 2008 - can't see or connect disks in SD
> but can see them in Disk Management MMC - only mount read-only
>
>
> Hi,
>
> Another question - I have a datawarehouse box - has 4 luns -> SD 6.1 and
> Server 2k8 both 64bit.
>
> I can't seem to reconnect the LUN's using the SD wizard - however they
> do end up appearing in the Server Disk Management MMC.
>
> Catch is they will only mount read-only (but at least the data is fine).
>
> In iSCSI session management it will see the connected LUN's related to
> the igroup.
>
> One of two things tends to happen - if I try to use SD I either get a
> 120 sec time out or I get an error about the lun already being mapped
> (presumably by the built in iSCSI initiator).
>
> As per a previous post - this box was fine until a controller/ontap
> upgrade.
>
> I've tried zapping the igroup and mappings on the SAN and removing all
> traces from SD and the MS iSCSI initiator but I can't seem to overcome
> this problem.
>
> Any ideas ? Worst case I can carve off a whole new set of LUN's and move
> the data but I really don't want to have to do that if I don't have to.
>
> Thanks in advance,
> Raj.
>