Windows 2000 Extended partition problem

Hi all,
I am facing a strange problem with my SCSI miniport SATA RAID driver under windows 2000.

1> I have 160 GB Maxtor (SATA) drives.

2> I create a extended partition on a basic disk and then create logical drives on extended partition.

3>After creating two logical drives i get a system settings change message box:
“Windows has finished installing new devices. … Please reboot …”.

4> This happens irrespective of the RAID-level.

This is a message that windows displayes when it detects/installs the new devices.
This only happens for the Maxtor 160 GB drives.I tried with seagates but was not able to see the problem.

Another point i should mention is that by design we export a dummy device which is a null device.For this we have a seperate .inf file and is installed when our driver is installed.

I have no clue why this system setting change message box is displayed.
I would really appriciate any pointers on this.

Thanks,
Ajitabh

---------------------------------
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway - Enter today

If you put the drive in and leave it for a while without creating the
partitions i presume you don’t get the message?

The OS knows how to configure a few critical types of device - those
that would let you login so PNP can install other devices. Disks are
one, and often get installed twice - once through the critical device
system and then again when an INF match is found. If the device can’t
be removed during the second install you’ll get the benign reboot popup.

Is it possible your driver isn’t properly letting the disk device get
removed and reinstalled once it’s been used?

-p


From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Driver Coder
Sent: Thursday, April 01, 2004 8:58 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Windows 2000 Extended partition problem

Hi all,
I am facing a strange problem with my SCSI miniport SATA RAID driver
under windows 2000.

1> I have 160 GB Maxtor (SATA) drives.

2> I create a extended partition on a basic disk and then create logical
drives on extended partition.

3>After creating two logical drives i get a system settings change
message box:
“Windows has finished installing new devices. … Please reboot
…”.

4> This happens irrespective of the RAID-level.

This is a message that windows displayes when it detects/installs the
new devices.
This only happens for the Maxtor 160 GB drives.I tried with seagates but
was not able to see the problem.

Another point i should mention is that by design we export a dummy
device which is a null device.For this we have a seperate .inf file and
is installed when our driver is installed.

I have no clue why this system setting change message box is displayed.
I would really appriciate any pointers on this.

Thanks,
Ajitabh

________________________________

Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway
http:veaway/static/index2.html> - Enter today — Questions? First check the
Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256 You are
currently subscribed to ntdev as: xxxxx@windows.microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com</http:>

Hi Peter,

You are correct if i do not create the partitions i do not see the reboot message.
AFAIK Scsi miniport driver does not have to do anything with drive removal. All it gets is a enquiry and we respond to it. Moreover i do not export actual MAXTOR disk to the operating system. We COOK UP the enquiry data and give it to the above layer and this is done since we are the RAID driver.

One thing i am not sure of is why would it only happen for MAXTOR 160 GB SATA drives and not with 160GB Seagates. If there would have been a problem from the driver side it would have occured on both the drives. Isn’t it??

Any pointers are appriciated.
Thanks for the reponse,
Ajitabh

Peter Wieland wrote:
If you put the drive in and leave it for a while without creating the
partitions i presume you don’t get the message?

The OS knows how to configure a few critical types of device - those
that would let you login so PNP can install other devices. Disks are
one, and often get installed twice - once through the critical device
system and then again when an INF match is found. If the device can’t
be removed during the second install you’ll get the benign reboot popup.

Is it possible your driver isn’t properly letting the disk device get
removed and reinstalled once it’s been used?

-p



From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Driver Coder
Sent: Thursday, April 01, 2004 8:58 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Windows 2000 Extended partition problem

Hi all,
I am facing a strange problem with my SCSI miniport SATA RAID driver
under windows 2000.

1> I have 160 GB Maxtor (SATA) drives.

2> I create a extended partition on a basic disk and then create logical
drives on extended partition.

3>After creating two logical drives i get a system settings change
message box:
“Windows has finished installing new devices. … Please reboot
…”.

4> This happens irrespective of the RAID-level.

This is a message that windows displayes when it detects/installs the
new devices.
This only happens for the Maxtor 160 GB drives.I tried with seagates but
was not able to see the problem.

Another point i should mention is that by design we export a dummy
device which is a null device.For this we have a seperate .inf file and
is installed when our driver is installed.

I have no clue why this system setting change message box is displayed.
I would really appriciate any pointers on this.

Thanks,
Ajitabh



Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway
veaway/static/index2.html> - Enter today — Questions? First check the
Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256 You are
currently subscribed to ntdev as: xxxxx@windows.microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com


Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@yahoo.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

---------------------------------
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway - Enter today

i missed the word “miniport” in your original post - you’re right that
the miniport shouldn’t have much affect on the system. I’m a little
suspicious about the extra device you’re exposing - if it’s possible you
might turn that off and see if it’s affecting the situation in any way.

it is strange that it happens with the maxtor and not with the seagate
drive. I presume you expose the same information for both disks
(inquiry data, geometry, disk size, etc…)?

you might take a look at this KB article
(http://support.microsoft.com/default.aspx?scid=kb;en-us;303128) about
debuging query remove vetos. It should tell you who vetos the remove -
if it’s the file system then something is keeping an open handle to the
maxtor drive but not to the seagate drive. If it’s the disk driver then
you should be able to look at the disk code in the DDK to see why it’s
vetoing the remove.

besides that i’m out of ideas. hopefully this will get you unwedged.

-p


From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Driver Coder
Sent: Friday, April 02, 2004 6:29 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Windows 2000 Extended partition problem

Hi Peter,

You are correct if i do not create the partitions i do not see the
reboot message.
AFAIK Scsi miniport driver does not have to do anything with drive
removal. All it gets is a enquiry and we respond to it. Moreover i do
not export actual MAXTOR disk to the operating system. We COOK UP the
enquiry data and give it to the above layer and this is done since we
are the RAID driver.

One thing i am not sure of is why would it only happen for MAXTOR 160 GB
SATA drives and not with 160GB Seagates. If there would have been a
problem from the driver side it would have occured on both the drives.
Isn’t it??

Any pointers are appriciated.
Thanks for the reponse,
Ajitabh

Peter Wieland wrote:

If you put the drive in and leave it for a while without
creating the
partitions i presume you don’t get the message?

The OS knows how to configure a few critical types of device -
those
that would let you login so PNP can install other devices. Disks
are
one, and often get installed twice - once through the critical
device
system and then again when an INF match is found. If the device
can’t
be removed during the second install you’ll get the benign
reboot popup.

Is it possible your driver isn’t properly letting the disk
device get
removed and reinstalled once it’s been used?

-p



From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Driver
Coder
Sent: Thursday, April 01, 2004 8:58 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Windows 2000 Extended partition problem

Hi all,
I am facing a strange problem with my SCSI miniport SATA RAID
driver
under windows 2000.

1> I have 160 GB Maxtor (SATA) drives.

2> I create a extended partition on a basic disk and then create
logical
drives on extended partition.

3>After creating two logical drives i get a system settings
change
message box:
“Windows has finished installing new devices. … Please reboot
…”.

4> This happens irrespective of the RAID-level.

This is a message that windows displayes when it
detects/installs the
new devices.
This only happens for the Maxtor 160 GB drives.I tried with
seagates but
was not able to see the problem.

Another point i should mention is that by design we export a
dummy
device which is a null device.For this we have a seperate .inf
file and
is installed when our driver is installed.

I have no clue why this system setting change message box is
displayed.
I would really appriciate any pointers on this.

Thanks,
Ajitabh



Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway
veaway/static/index2.html> - Enter today — Questions? First
check the
Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
You are
currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To
unsubscribe send a blank email to
xxxxx@lists.osr.com


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@yahoo.com
To unsubscribe send a blank email to
xxxxx@lists.osr.com

________________________________

Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway
http:veaway/static/index2.html> - Enter today — Questions? First check the
Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256 You are
currently subscribed to ntdev as: xxxxx@windows.microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com</http:>

Thanks again,
Yes i am exporting the same data for both disks.
I am going to try the debugging pointed by you. I hope i am able to get a resolution to this problem quickly.

Thanks,
Ajitabh

wrote:
i missed the word “miniport” in your original post - you’re right that
the miniport shouldn’t have much affect on the system. I’m a little
suspicious about the extra device you’re exposing - if it’s possible you
might turn that off and see if it’s affecting the situation in any way.

it is strange that it happens with the maxtor and not with the seagate
drive. I presume you expose the same information for both disks
(inquiry data, geometry, disk size, etc…)?

you might take a look at this KB article
(http://support.microsoft.com/default.aspx?scid=kb;en-us;303128) about
debuging query remove vetos. It should tell you who vetos the remove -
if it’s the file system then something is keeping an open handle to the
maxtor drive but not to the seagate drive. If it’s the disk driver then
you should be able to look at the disk code in the DDK to see why it’s
vetoing the remove.

besides that i’m out of ideas. hopefully this will get you unwedged.

-p



From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Driver Coder
Sent: Friday, April 02, 2004 6:29 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Windows 2000 Extended partition problem

Hi Peter,

You are correct if i do not create the partitions i do not see the
reboot message.
AFAIK Scsi miniport driver does not have to do anything with drive
removal. All it gets is a enquiry and we respond to it. Moreover i do
not export actual MAXTOR disk to the operating system. We COOK UP the
enquiry data and give it to the above layer and this is done since we
are the RAID driver.

One thing i am not sure of is why would it only happen for MAXTOR 160 GB
SATA drives and not with 160GB Seagates. If there would have been a
problem from the driver side it would have occured on both the drives.
Isn’t it??

Any pointers are appriciated.
Thanks for the reponse,
Ajitabh

Peter Wieland
wrote:

If you put the drive in and leave it for a while without
creating the
partitions i presume you don’t get the message?

The OS knows how to configure a few critical types of device -
those
that would let you login so PNP can install other devices. Disks
are
one, and often get installed twice - once through the critical
device
system and then again when an INF match is found. If the device
can’t
be removed during the second install you’ll get the benign
reboot popup.

Is it possible your driver isn’t properly letting the disk
device get
removed and reinstalled once it’s been used?

-p



From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Driver
Coder
Sent: Thursday, April 01, 2004 8:58 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Windows 2000 Extended partition problem

Hi all,
I am facing a strange problem with my SCSI miniport SATA RAID
driver
under windows 2000.

1> I have 160 GB Maxtor (SATA) drives.

2> I create a extended partition on a basic disk and then create
logical
drives on extended partition.

3>After creating two logical drives i get a system settings
change
message box:
“Windows has finished installing new devices. … Please reboot
…”.

4> This happens irrespective of the RAID-level.

This is a message that windows displayes when it
detects/installs the
new devices.
This only happens for the Maxtor 160 GB drives.I tried with
seagates but
was not able to see the problem.

Another point i should mention is that by design we export a
dummy
device which is a null device.For this we have a seperate .inf
file and
is installed when our driver is installed.

I have no clue why this system setting change message box is
displayed.
I would really appriciate any pointers on this.

Thanks,
Ajitabh



Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway
veaway/static/index2.html> - Enter today — Questions? First
check the
Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
You are
currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To
unsubscribe send a blank email to
xxxxx@lists.osr.com


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@yahoo.com
To unsubscribe send a blank email to
xxxxx@lists.osr.com



Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway
veaway/static/index2.html> - Enter today — Questions? First check the
Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256 You are
currently subscribed to ntdev as: xxxxx@windows.microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com


Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@yahoo.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

---------------------------------
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway - Enter today