G
gtaus
I had a 2TB HDD fail in my Storage Pool of 24 drives (104TB). Although I had 20TB unused pool capacity, the one 2TB failed drive crashed my entire Storage Pool and all 5 of my VirtualDisks. I was expecting the failed 2TB HDD data to be reassigned to the other disks in the pool, but that did not happen. The failed 2TB HDD is marked at Retired. Using PowerShell, I was able to reconnect most of my VirtualDisks and remove the data to USB HDDs. SS would not let me remove the failed HDD and told me that I had to add more disks.
Today, I added a 4TB drive to replace the failed 2TB drive. Unfortunately, that did not solve my "add disks" problem. Worse yet, while adding the new 4TB drive, the Optimize Pool started. It got stuck at 1% and never progressed. So I clicked on the "Stop Optimization" command. For the past 8 hours, Get-StorageJob reports the "Rebalance" job is "Shutting Down" but has not moved from 0% complete and 0 BytesProcessed.
Additionally, I had a working VirtualDisk on the pool that went into "Repair" status at the same time and it too is stuck on "Running" but 0% complete and 0 BytesProcessed.
I have tried rebooting the computer a number of times, including adding the SS drives one at a time. In the past, I have used that method to break out of stuck jobs. For some reason, that method is not working for me this time and every reboot restarts the stuck jobs.
So, is it possible to force stop StorageJobs and if so, how do you go about stopping these stuck jobs? Thanks for any suggestions.
Continue reading...
Today, I added a 4TB drive to replace the failed 2TB drive. Unfortunately, that did not solve my "add disks" problem. Worse yet, while adding the new 4TB drive, the Optimize Pool started. It got stuck at 1% and never progressed. So I clicked on the "Stop Optimization" command. For the past 8 hours, Get-StorageJob reports the "Rebalance" job is "Shutting Down" but has not moved from 0% complete and 0 BytesProcessed.
Additionally, I had a working VirtualDisk on the pool that went into "Repair" status at the same time and it too is stuck on "Running" but 0% complete and 0 BytesProcessed.
I have tried rebooting the computer a number of times, including adding the SS drives one at a time. In the past, I have used that method to break out of stuck jobs. For some reason, that method is not working for me this time and every reboot restarts the stuck jobs.
So, is it possible to force stop StorageJobs and if so, how do you go about stopping these stuck jobs? Thanks for any suggestions.
Continue reading...