Open chiair opened 3 years ago
Same issue, My striped drives refuse to show.
@briggsyuk Are your striped drives made using "Dynamic Disk"? @chiair what type of drives are they? Network, dynamic, RAID, or simple volume?
@briggsyuk Are your striped drives made using "Dynamic Disk"? @chiair what type of drives are they? Network, dynamic, RAID, or simple volume?
I have network drive and simple volume and ssd but None will show
Does your C drive at least show up? Are any of these dynamic disk? Are you running the GUI in an admin powershell window or non-admin window. Check out this past thread for possible solutions - https://github.com/MrPig91/PSChiaPlotter/issues/63
Does your C drive at least show up? Are any of these dynamic disk? Are you running the GUI in an admin powershell window or non-admin window. Check out this past thread for possible solutions - #63
No, Even the c drive won't show up No, my disk is basic and not dynamic I use administrator power shell, when i use non-admin show me error And it doesn't open at all. I tested this but nothing showed up
Get-CimInstance -Class Win32_LogicalDisk -Filter "DriveType=4"
my drive type = "3"
when use non-admin user show me this error @MrPig91
d drives made using "Dynamic Disk"?
They where made using windows disk management so if this means dynamic disk then yes.
d drives made using "Dynamic Disk"?
They where made using windows disk management so if this means dynamic disk then yes.
Yes @MrPig91
@chiair are you running Windows 8 or 8.1 by any chance? Because Windows PowerShell adheres to Windows security constraints, a user of Windows PowerShell cannot do anything that the user account does not have permission to do. @briggsyuk Dynamic Disks have been depreciated my Microsoft for many many years and the new solution is to use Storage Spaces. Since you have one drive that is large enough (J) you can redo that in Storage Spaces and then copy all the data from H to the newly configured J then setup H & P (if P is a single disk just convert it to Basic in Device Manager) the same way. There are workarounds to getting dynamic disks to work but they are sketchy and since not fully supported would be a risk IMHO.
@chiair are you running Windows 8 or 8.1 by any chance? Because Windows PowerShell adheres to Windows security constraints, a user of Windows PowerShell cannot do anything that the user account does not have permission to do. @briggsyuk Dynamic Disks have been depreciated my Microsoft for many many years and the new solution is to use Storage Spaces. Since you have one drive that is large enough (J) you can redo that in Storage Spaces and then copy all the data from H to the newly configured J then setup H & P (if P is a single disk just convert it to Basic in Device Manager) the same way. There are workarounds to getting dynamic disks to work but they are sketchy and since not fully supported would be a risk IMHO.
Yes, i use win 8.1,Do you think I'll change it to Windows 10?
@chiair THB I hated 8 and 8.1 (probably more than deserved), and I would personally upgrade to Windows 10 (you can still do it for free).
Can you open PowerShell as admin and post the results of each of the following commands?
Get-Volume Get-Partition | Where {$_.AccessPaths.Count -gt 1} Get-Disk Get-PhysicalDisk
Even if you are an administrator on the local Windows 8 (or Windows 7) desktop machine and you do not launch Windows PowerShell with admin rights, you will get errors when attempting to do things like see the configuration of your disk drives. This command and associated error appears here.
PS C:\> get-disk
get-disk : Access to a CIM resource was not available to the client.
At line:1 char:1
+ get-disk
+ ~~~~~~~~
+ CategoryInfo : PermissionDenied: (MSFT\_Disk:ROOT/Microsoft/Windows/S
torage/MSFT\_Disk) [Get-Disk], CimException
+ FullyQualifiedErrorId : MI RESULT 2,Get-Disk
There is an inconsistency with errors arising when attempting to run cmdlets that require elevated rights. For example, when inside a non-elevated Windows PowerShell console, the error from Get-Disk is _Access to a CIM resource was not available to the client. _The error from Stop-Service is _Cannot open xxx service on computer. _While the Get-VM cmdlets simply returns no information (an no error). Therefore, as a first step in troubleshooting, check for console rights.
@chiair THB I hated 8 and 8.1 (probably more than deserved), and I would personally upgrade to Windows 10 (you can still do it for free).
Can you open PowerShell as admin and post the results of each of the following commands?
Get-Volume Get-Partition | Where {$_.AccessPaths.Count -gt 1} Get-Disk Get-PhysicalDisk
Even if you are an administrator on the local Windows 8 (or Windows 7) desktop machine and you do not launch Windows PowerShell with admin rights, you will get errors when attempting to do things like see the configuration of your disk drives. This command and associated error appears here.
PS C:\> get-disk get-disk : Access to a CIM resource was not available to the client. At line:1 char:1 + get-disk + ~~~~~~~~ + CategoryInfo : PermissionDenied: (MSFT\_Disk:ROOT/Microsoft/Windows/S torage/MSFT\_Disk) [Get-Disk], CimException + FullyQualifiedErrorId : MI RESULT 2,Get-Disk
There is an inconsistency with errors arising when attempting to run cmdlets that require elevated rights. For example, when inside a non-elevated Windows PowerShell console, the error from Get-Disk is _Access to a CIM resource was not available to the client. _The error from Stop-Service is _Cannot open xxx service on computer. _While the Get-VM cmdlets simply returns no information (an no error). Therefore, as a first step in troubleshooting, check for console rights.
Hi, all of Commands work and show system drives with empty volume and drive name
Can you screen grab all the results? Sorry I'm a visual person. Thank you.
Hi, why aren't computer drives shown in plotting and farming drive section?