Shucked External - Parameter is incorrect

F

FenFox

Limp Gawd
Joined
Dec 20, 2016
Messages
296
-Just shucked an older Western Digital My Book 5 TB external HDD.

-Connected it to my desktop PC and when I double click the drive letter I just see: "H:\ is not accessible - The parameter is incorrect."

-I don't need anything on the HDD - will doing a quick format fix this or should I go about addressing this issue another way?

It is a bit bizarre that this happened because I was pretty damn careful/cautious when shucking and installing the drive so I have no idea why this error even occurred. Does this message indicate corruption?
 
Is it using some encryption hardware that is still inside the external enclosure?
 
DrLobotomy said:
Is it using some encryption hardware that is still inside the external enclosure?
Click to expand...

Uh, I don't know? This is literally all there was inside:
biqHhCr.jpg

It looks the exact same as all the EasyStore Externals everyone shucks.
 
Last edited:
Would running chkdsk /F /R /X <drive letter>
solve this issue? One person said if you do that it should fix the drive but the drive will be slower / won't last long after.
 
Delete the volume in disk management. then create a new volume, format, and good to go.
 
rive22 said:
Delete the volume in disk management. then create a new volume, format, and good to go.
Click to expand...

Kinda weird how the Healthy Primary Partition is only 582 GB RAW and there are 2 parts Unallocated?
Will Deleting the volume really fix that?

KbiEYMM.png



I can't delete the unallocated volumes. I can only create "New Simple Volume" on one of them.
If I delete the H: Volume will it also delete the unallocated volumes?
 
Last edited:
open a cmd as admin and run these commands

diskpart
list disk
select disk "number" without quotes
clean
convert gpt
create partition primary
select partition 1
format FS=NTFS quick
assign letter=whatever you want
exit
 
Last edited:
rive22 said:
open a cmd as admin and run these commands

diskpart
list disk
select disk (whatever the number)
clean
convert gpt
create partition primary
select partition 1
active
format FS=NTFS quick
assign letter=(whatever you want)
exit
Click to expand...

So that will create a single volume? Will it work from an external enclosure connected via USB? I would rather not do this in my desktop as I have a lot of other drives connected and I don't wanna make an 'opposie'
 
I had that same issue with a 2TB MyBook recently. I plugged the USB card back to the drive and it read fine, use it as a sata drive and I got the parameter issue.
I just can't remember if I just put the drive back in the enclosure or what.
 
rive22 said:
open a cmd as admin and run these commands

diskpart
list disk
select disk "whatever the number" without quotes
clean
convert gpt
create partition primary
select partition 1
active
format FS=NTFS quick
assign letter=whatever you want
exit
Click to expand...

"active" wouldn't actually do anything, I just got:

"The selected disk is not a fixed MBR disk. The ACTIVE command can only be used on fixed MBR disks."
So I typed exit and did a NTFS quick format in Windows Disk Management. Now it shows up as:
DReJy2u.png

But it doesn't show up under "This PC" as a drive. Do I need to assign it a letter first? Right click on New Volume --> Change drive letters and path --> add --> Select a drive letter?
 
Yep, it's working now. Thanks a lot guys. :) I guess it was encryption on that WD controller. I dunno.
 
rive22 said:
open a cmd as admin and run these commands

diskpart
list disk
select disk "number" without quotes
clean
convert gpt
create partition primary
select partition 1
format FS=NTFS quick format FS=refs quick
assign letter=whatever you want
exit
Click to expand...

Fixed that for you
No one should be making something ntfs anymore.
 
Brian_B said:
Can you do ReFS on Win10 Home/Pro? I thought they removed it?

https://mcpmag.com/articles/2017/08/23/refs-creation-support-ending.aspx
Click to expand...

News to me. I played around with ReFS drives on an array in Win 8.1 and Win10 just not very long ago (the win10 one I did was just two weeks ago in v1903 on win10 pro). And I just copied a couple terrabytes this last weekend from my old NTFS formatted SSD on my gaming PC onto my server with some ReFS arrays. So not sure what the article is talking about.
As far as I know you always had to and still do have to apply a RegEdit tweak to enable ReFS, so maybe the article is talking about MS removing it that way? Or maybe MS removed it then added it back in 1903?
 
Old externals used 4K sectors and MBR partition table (not GPT) for WinXP compatibility.
 
EniGmA1987 said:
News to me. I played around with ReFS drives on an array in Win 8.1 and Win10 just not very long ago (the win10 one I did was just two weeks ago in v1903 on win10 pro). And I just copied a couple terrabytes this last weekend from my old NTFS formatted SSD on my gaming PC onto my server with some ReFS arrays. So not sure what the article is talking about.
As far as I know you always had to and still do have to apply a RegEdit tweak to enable ReFS, so maybe the article is talking about MS removing it that way? Or maybe MS removed it then added it back in 1903?
Click to expand...

The ability to create new ReFS volumes was removed from 10 home/pro quite some time ago. Existing volumes can still be accessed.

Microsoft has given up on making ReFS a general successor to NTFS. ReFS is slow and there are no recovery tools availible. There's really no reason to be messing with it in a situation like this. If you want data scrubbing on your home server ZFS is the mature solution.
 
rive22 said:
open a cmd as admin and run these commands

diskpart
list disk
select disk "number" without quotes
clean
Click to expand...

Clean is really one of the most useful things to know about storage. It can fix just about anything. Even a drive that was messed up on Linux or MacOS can be fixed back to new using diskpart "clean" command. The only thing I have had hit or miss success with is removing a drive from Windows Storage Space improperly. Something is left on the drive that even clean can't always get rid of. But Storage Space will usually see it, and you can remove the pool status in there.

I have saved several USB flash drives with clean that got hosed during image flashing or formatting.
 
You must log in or register to reply here.
Back
Top