TFerg53 Absent Member.
Absent Member.
888 views

I've had a rather peculiar problem develop about a month ago and,after working on it during that time and trying several things as suggestedby various TIDs and forums, am at kind of a loss on where to look and washoping someone here might be able to

I've had a rather peculiar problem develop about a month ago and, after working on it during that time and trying several things as suggested by various TIDs and forums, am at kind of a loss on where to look and was hoping someone here might be able to help? I have five VM servers set up and on-line. My three NW65SP8 servers with NSS volumes, the building server for my building, the proxy server for the Internet, and the web server all are losing their pools and volumes for some reason while the IPCOP server appears to be working fine as did two SUSE10/OES2 servers I had set up as test/potential migration servers, although I haven't thoroughly checked them.

The servers themselves remain up but I get a "Device "[V350-A2-D0:0] VMware Virtual Disk f/w:1.0" deactivated by driver due to device failure" error, and of course, "Error writing to the directory on <server>/VOL1 or SYS", etc." I can reset the servers and they come back up normally and stay that way until this happens again when they all deactivate their pools/volumes, something that has been happening about once or two a week.

Any ideas or where to look or what to use to fix this would sincerely be appreciated. One of the TIDs suggested using a newer version of SCSIHD to 3.03.10, but the problem continued after downloading and updating that file(s).

These are NW65SP8 on a VMware ESXi 4.1.0.

Thank you!

Tim
Labels (2)
0 Likes
7 Replies
TFerg53 Absent Member.
Absent Member.

Re: I've had a rather peculiar problem develop about a month agoand, after working on it during that time and trying several things assuggested by various TIDs and forums, am at kind of a loss on where to lookand was hoping someone here might be able

Sorry, guess I forgot the subject, I hate when this happens!

Tim


>>> Tim Ferguson<Tlf1@ccs135.com> 2/14/2011 2:16 PM >>>


I've had a rather peculiar problem develop about a month ago and, after working on it during that time and trying several things as suggested by various TIDs and forums, am at kind of a loss on where to look and was hoping someone here might be able to help? I have five VM servers set up and on-line. My three NW65SP8 servers with NSS volumes, the building server for my building, the proxy server for the Internet, and the web server all are losing their pools and volumes for some reason while the IPCOP server appears to be working fine as did two SUSE10/OES2 servers I had set up as test/potential migration servers, although I haven't thoroughly checked them.

The servers themselves remain up but I get a "Device "[V350-A2-D0:0] VMware Virtual Disk f/w:1.0" deactivated by driver due to device failure" error, and of course, "Error writing to the directory on <server>/VOL1 or SYS", etc." I can reset the servers and they come back up normally and stay that way until this happens again when they all deactivate their pools/volumes, something that has been happening about once or two a week.

Any ideas or where to look or what to use to fix this would sincerely be appreciated. One of the TIDs suggested using a newer version of SCSIHD to 3.03.10, but the problem continued after downloading and updating that file(s).

These are NW65SP8 on a VMware ESXi 4.1.0.

Thank you!

Tim
0 Likes
Knowledge Partner
Knowledge Partner

Re: I've had a rather peculiar problem develop about a month agoand, after working on it during that time and trying several things as suggestedby various TIDs and forums, am at kind of a loss on where to look and washoping someone here might be able

Hi.

On 14.02.2011 22:03, Tim Ferguson wrote:
> Sorry, guess I forgot the subject, I hate when this happens!
> Tim
>
> >>> Tim Ferguson<Tlf1@ccs135.com> 2/14/2011 2:16 PM>>>

> I've had a rather peculiar problem develop about a month ago and, after working
> on it during that time and trying several things as suggested by various TIDs
> and forums, am at kind of a loss on where to look and was hoping someone here
> might be able to help? I have five VM servers set up and on-line. My three
> NW65SP8 servers with NSS volumes, the building server for my building, the proxy
> server for the Internet, and the web server all are losing their pools and
> volumes for some reason while the IPCOP server appears to be working fine as did
> two SUSE10/OES2 servers I had set up as test/potential migration servers,
> although I haven't thoroughly checked them.
>
> The servers themselves remain up but I get a "Device "[V350-A2-D0:0] VMware
> Virtual Disk f/w:1.0" deactivated by driver due to device failure"


Netware/NSS is comparably sensitive to HD device timeouts and delays.
While e.g Windows allows 30 seconds of device inaccessibility before it
throws an error (or rather, more usual simply hangs up), Netware
deactivates a Hard Disk much earlier when it fails to respond to read or
write requests.

In other words, your storage in your VM Box is either flaky or
overloaded, and Netware is merely the first to notice it. You need to
check the VMWare and physical storage side. Start with the stats for the
storage latency in VMWare.

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
TFerg53 Absent Member.
Absent Member.

Re: I've had a rather peculiar problem develop about a monthagoand, after working on it during that time and trying several things assuggestedby various TIDs and forums, am at kind of a loss on where to lookand washoping someone here might be able to

Ok, thanks, Massimo, I sincerely appreciate the information.

Tim


>>> Massimo Rosen<mrosenNO@SPAMcfc-it.de> 2/14/2011 5:29 PM >>>

Hi.

On 14.02.2011 22:03, Tim Ferguson wrote:

> Sorry, guess I forgot the subject, I hate when this happens!
> Tim
>

> >>> Tim Ferguson<Tlf1@ccs135.com> 2/14/2011 2:16 PM>>>

> I've had a rather peculiar problem develop about a month ago and, after working
> on it during that time and trying several things as suggested by various TIDs
> and forums, am at kind of a loss on where to look and was hoping someone here
> might be able to help? I have five VM servers set up and on-line. My three
> NW65SP8 servers with NSS volumes, the building server for my building, the proxy
> server for the Internet, and the web server all are losing their pools and
> volumes for some reason while the IPCOP server appears to be working fine as did
> two SUSE10/OES2 servers I had set up as test/potential migration servers,
> although I haven't thoroughly checked them.
>
> The servers themselves remain up but I get a "Device "[V350-A2-D0:0] VMware
> Virtual Disk f/w:1.0" deactivated by driver due to device failure"


Netware/NSS is comparably sensitive to HD device timeouts and delays.
While e.g Windows allows 30 seconds of device inaccessibility before it
throws an error (or rather, more usual simply hangs up), Netware
deactivates a Hard Disk much earlier when it fails to respond to read or
write requests.

In other words, your storage in your VM Box is either flaky or
overloaded, and Netware is merely the first to notice it. You need to
check the VMWare and physical storage side. Start with the stats for the
storage latency in VMWare.

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de
0 Likes
TFerg53 Absent Member.
Absent Member.

Re: I've had a rather peculiar problem develop about a monthagoand,after working on it during that time and trying several thingsassuggestedby various TIDs and forums, am at kind of a loss on where tolookand washoping someone here might be able to he

I would assume this is not an overload because of the times it has been happening, normally during off-peak or low-peak hours. Also, would this also be a problem with SLES10/OES2 then as I was preparing to create SLES10/OES2 VM's to start migrating our current servers to.

Thank you!

Tim


>>> Tim Ferguson<Tlf1@ccs135.com> 2/15/2011 3:58 PM >>>


Ok, thanks, Massimo, I sincerely appreciate the information.

Tim


>>> Massimo Rosen<mrosenNO@SPAMcfc-it.de> 2/14/2011 5:29 PM >>>

Hi.

On 14.02.2011 22:03, Tim Ferguson wrote:

> Sorry, guess I forgot the subject, I hate when this happens!
> Tim
>

> >>> Tim Ferguson<Tlf1@ccs135.com> 2/14/2011 2:16 PM>>>

> I've had a rather peculiar problem develop about a month ago and, after working
> on it during that time and trying several things as suggested by various TIDs
> and forums, am at kind of a loss on where to look and was hoping someone here
> might be able to help? I have five VM servers set up and on-line. My three
> NW65SP8 servers with NSS volumes, the building server for my building, the proxy
> server for the Internet, and the web server all are losing their pools and
> volumes for some reason while the IPCOP server appears to be working fine as did
> two SUSE10/OES2 servers I had set up as test/potential migration servers,
> although I haven't thoroughly checked them.
>
> The servers themselves remain up but I get a "Device "[V350-A2-D0:0] VMware
> Virtual Disk f/w:1.0" deactivated by driver due to device failure"


Netware/NSS is comparably sensitive to HD device timeouts and delays.
While e.g Windows allows 30 seconds of device inaccessibility before it
throws an error (or rather, more usual simply hangs up), Netware
deactivates a Hard Disk much earlier when it fails to respond to read or
write requests.

In other words, your storage in your VM Box is either flaky or
overloaded, and Netware is merely the first to notice it. You need to
check the VMWare and physical storage side. Start with the stats for the
storage latency in VMWare.

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de
0 Likes
hspeirs Absent Member.
Absent Member.

Re: I've had a rather peculiar problem develop about a monthagoand,after working on it during that time and trying several things assuggestedbyvarious TIDs and forums, am at kind of a loss on where to lookand washopingsomeone here might be able to he

Tim,

> I would assume this is not an overload because of the times it has been
> happening, normally during off-peak or low-peak hours. Also, would this
> also be a problem with SLES10/OES2 then as I was preparing to create
> SLES10/OES2 VM's to start migrating our current servers to.


The is a retries= switch you can add to the scsihd.cdm command line, try
increasing it.

One thing I have found is that NetWare in VM is VERY sensitive to memory
- in the VM Settings, set a memory reservation equal to the amount of
memory allocated to the VM.

H.
0 Likes
TFerg53 Absent Member.
Absent Member.

Re: A rather peculiar problem...(cont.)

Thank you, Hamish, I sincerely appreciate it and will apply it.

Tim


>>> Hamish<hamish@haitch.net> 2/15/2011 5:28 PM >>>

Tim,


> I would assume this is not an overload because of the times it has been
> happening, normally during off-peak or low-peak hours. Also, would this
> also be a problem with SLES10/OES2 then as I was preparing to create
> SLES10/OES2 VM's to start migrating our current servers to.


The is a retries= switch you can add to the scsihd.cdm command line, try
increasing it.

One thing I have found is that NetWare in VM is VERY sensitive to memory
- in the VM Settings, set a memory reservation equal to the amount of
memory allocated to the VM.

H.
0 Likes
TFerg53 Absent Member.
Absent Member.

Re: I've had a rather peculiar problem develop about a monthagoand,after working on it during that time and trying several thingsassuggestedbyvarious TIDs and forums, am at kind of a loss on where tolookand washopingsomeone here might be able to help

Thank you, Hamish, I've been out for a few days and just had a chance to check postings, but I have added the retries= switch to the scsihd.cdm command line and see how it goes.

Thanks again,
Tim


>>> Hamish<hamish@haitch.net> 2/15/2011 5:28 PM >>>

Tim,


> I would assume this is not an overload because of the times it has been
> happening, normally during off-peak or low-peak hours. Also, would this
> also be a problem with SLES10/OES2 then as I was preparing to create
> SLES10/OES2 VM's to start migrating our current servers to.


The is a retries= switch you can add to the scsihd.cdm command line, try
increasing it.

One thing I have found is that NetWare in VM is VERY sensitive to memory
- in the VM Settings, set a memory reservation equal to the amount of
memory allocated to the VM.

H.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.