Knightsman
asked on
Cant get seagate 4TB Drive to initialize "incorrect function" error
I have tried Diskpart, tried Partition manager, partition magic. I have 2 4TB Drives.
They show up under disk management as "notinitialized" However if I right click on Disk 1, the option to "initialize" is greyed out. I do get a request anytime I open disk managment to initialize the disks, adn I choose GPT (both give this error though). Once I click ok, I get Title: "Virtual Disk Manager" Text: "Incorrect function"
This is on a Lenovo thinkstation D20
Not sure what else to do.
They show up under disk management as "notinitialized" However if I right click on Disk 1, the option to "initialize" is greyed out. I do get a request anytime I open disk managment to initialize the disks, adn I choose GPT (both give this error though). Once I click ok, I get Title: "Virtual Disk Manager" Text: "Incorrect function"
This is on a Lenovo thinkstation D20
Not sure what else to do.
arnold
Which os is in use?
put the disk in a caddy and try to format from there
Can tou try to stop and start virtual disk service from services.msc? You might get an Incorrect function error too. Look the task manager's process tab and try to kill virtual disk service from there then it would show stopped then you need to start the service from services.msc
open disk manager right click on the disk and bring it offline. Then again bring online then try to initiakized.
open disk manager right click on the disk and bring it offline. Then again bring online then try to initiakized.
ASKER
Windows 7 Pro.
I thought about a caddy, but its at a remote site. was installed but not finalized onsite. Cant get out there until tomorrow, but even then im still concerned its not going to work properly.
I thought about a caddy, but its at a remote site. was installed but not finalized onsite. Cant get out there until tomorrow, but even then im still concerned its not going to work properly.
ASKER
When stopping it, I get "windows could not stop the virtual disk services on local computer.
I get an Error 1067: the process terminated unexpectedly
I get an Error 1067: the process terminated unexpectedly
ASKER
it did stop the services, and I restarted the services as you instructed, same results.
Which windows 7 32 or 64? Updates? Sp?
Diskpar
Are the drives combined/striped using MB SATA rAId?
Diskpar
Are the drives combined/striped using MB SATA rAId?
Try using the seagate disk tools to initialize the drive.
Delete any partitions on it, convert to GPT and try to initialize it.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I would first try these drives on other machine and if they work there then you have a problem with this specific computer only. Either drives of such size are not supported or the motherboards BIOS should be updated.
ASKER
Win 7 Pro 64 Thinkstation D20
I've verified it will not work with GPT partitions, but It will work with splitting them into two, which is fine.
Cant delete partitions, none have been created.
When I try to initialize with MBR, it still gives me the incorrect function error.
I would update the bios, but the only update to it, is for the CPU. Not worth the chance of failure if the update isnt related.
I've checked drivers, all are updated.
I've verified it will not work with GPT partitions, but It will work with splitting them into two, which is fine.
Cant delete partitions, none have been created.
When I try to initialize with MBR, it still gives me the incorrect function error.
I would update the bios, but the only update to it, is for the CPU. Not worth the chance of failure if the update isnt related.
I've checked drivers, all are updated.
Do the drives fail on one machine only? Or is the problem for other machines as well?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Its been a while, but wanted to update. The Raid controller doesnt support anything over 2TB. Moved the drives to sata ports on the MB, and worked fine.