Jump to content
  • 0

Issues Removing Bad Disk


bzowk

Question

Hey Guys - 

Just wrote Support, but wanted to post here as well in case anyone had ideas and perhaps could reply sooner... 

I am a long time DrivePool user who currently has a 43.7tb pool comprised of 11 disks including an SSD used with the plugin.  To note, I do not use the duplication feature - just use it for additional space & consolidation.  I'm trying to remove a bad disk and am running into issues so wanted to write and see what my best bet would be to safely get as much data as possible from the bad one given what I'm running into.

This morning, Scanner notified me that one of the disks had a SMART error.  I looked and sure enough one of the 4tb disks had 8 uncorrectable sectors.  Fortunately, I had recently cleaned a lot of files; so had enough space to remove the disk while moving it's ~3tb of content to other disks in the pool.  I started this and it's where my issues began.  

Issue #1
After the disk started showing the status of "Removing", I lost keyboard & mouse.  Fortunately, I use Input Director with other PCs (network KVM) so was able to move the mouse over and stop the removal.  Once it stopped, keyboard & mouse returned.  I restarted the PC and started the removal again and got the same result.  I left it for about 15 minutes where I found I had intermittant keyboard & mouse control which improved over time.  

Issue #2
I let the above removal run for ~4 hours where it got to about 50%.  All of a sudden, a high, but constantly pitched beep came from my PC.  I powered it off and turned it back on and all came back seemingly ok.  When looking at the SMART for the bad disk, I noticed that it now had 72 uncorrectable sectors - more than the 8 this morning.  The pool was being measured, but started the removal again (selecting all 3 options) and again had the keyboard / mouse issue.  I stopped the removal via Input Director as I have to finish some work stuff first.

Issue #3
When starting or stopping the removal, it resets my pool to where it starts to re-measure it again.  Not only does this take a while, but I'm afraid it accessing the bad disk in such detail will cause more harm than good.  The 4+ hour removal was started at the beginning of a measure and the measure never finished / seemed to pause during the removal procedure.

Questions
1. Given the above, how do you suggest I proceed?
2. Is there a way to cancel the measurement of the pool temporarily or at least have it skip a disk?
3. Not sure why the 1st removal took 4+ hours.  Scanner showed it writing to other disks at 5MB/s - 50MB/s (more on slower side) but not sure why.  I'm thinking my best bet may be to remove the disk from the pool with data intact (if possible) then manually move/copy content I wish to retain from the bad disk back into the pool.  Is this possible or suggested?

Below is a snippet from the Service log (if it provides any info) which starts at the reboot after the beep, starting a disk removal, then cancelling it:

Quote

 0:00:51.8: Information: 0 : [Main] StableBit DrivePool 2.2.3.950
0:00:51.8: Information: 0 : [Main] Microsoft Windows NT 10.0.18362.0
0:00:51.8: Information: 0 : [Main] Loading settings...
0:00:51.8: Information: 0 : [Main] Checking StableBit CloudDrive start status...
0:00:52.6: Information: 0 : [Main] Not waiting for the StableBit CloudDrive system service. Service CloudDriveService was not found on computer '.'.
0:00:52.6: Information: 0 : [Main] Loading lifetime statistics...
0:00:52.6: Information: 0 : [Main] Starting remote control...
0:00:52.6: Information: 0 : Comm server started on: tcp://127.0.0.1:27525/Comm1
0:00:54.7: Information: 0 : [Main] Starting running file...
0:00:55.7: Information: 0 : [Main] Starting user feedback...
0:00:55.7: Information: 0 : [Main] Starting root tasks...
0:00:55.7: Information: 0 : [Main] Enumerating disks...
0:01:11.0: Information: 0 : [Disks] Updating disks / volumes...
0:01:11.8: Information: 0 : [Main] Starting disk metadata...
0:01:32.1: Information: 0 : [Main] Starting CoveFs...
0:01:32.2: Information: 0 : [CoveFs] Waiting for pools to mount...
0:01:32.2: Information: 0 : [CoveFs] All 1 pools mounted.
0:01:32.2: Information: 0 : [CoveFs] Waiting for pool parts to arrive...
0:01:32.2: Information: 0 : [CoveFs] All known pool parts have arrived. Continuing startup...
0:01:32.2: Information: 0 : [CoveFs] Pool found on: \\?\GLOBALROOT\Device\HarddiskVolume31 (pool ID=337fd488-b54e-4d1d-9d07-83d99b3efbe5)
0:01:32.3: Information: 0 : [Disks] Updating disks / volumes...
0:01:32.3: Information: 0 : [Rebalance] Loading balancers (LoadBuiltIn=True)...
0:01:32.9: Information: 0 : [FsControl] Set overall pool mode: PoolModeNoReportIncomplete (lastKey=FileDuplication, pool=337fd488-b54e-4d1d-9d07-83d99b3efbe5)
0:01:33.6: Warning: 0 : [PoolPartUpdates] Found missing pool part DECD5540-D658-42B1-BACD-14E378EDCC0E (isCloudDrive=False, isOtherPool=False)
0:01:33.9: Information: 0 : [Main] Updating free space...
0:01:34.3: Information: 0 : [Main] Starting notifications...
0:01:34.4: Information: 0 : [Main] Starting performance samplers...
0:01:34.4: Information: 0 : [Main] Starting notification tasks...
0:01:34.4: Information: 0 : [Main] Service started.
0:01:34.8: Information: 0 : [PoolPartUpdates] Remeasuring pool 337fd488-b54e-4d1d-9d07-83d99b3efbe5 (changes=MissingDiskIsBack)
0:07:20.0: Information: 0 : [FsControl] Set overall pool mode: PoolModeNoReportIncomplete, PoolModeOverrideAllowCreateDirectories (lastKey=DrivePoolService.Pool.Tasks.RemoveDriveFromPool, pool=337fd488-b54e-4d1d-9d07-83d99b3efbe5)
0:07:20.0: Information: 0 : [FsControl] Set overall pool mode: PoolModeNoReportIncomplete, PoolModeOverrideAllowCreateDirectories, PoolModeNoMeasure (lastKey=DrivePoolService.Pool.Tasks.RemoveDriveFromPool, pool=337fd488-b54e-4d1d-9d07-83d99b3efbe5)
0:07:20.0: Information: 0 : [FsControl] Set overall pool mode: PoolModeNoReportIncomplete, PoolModeOverrideAllowCreateDirectories, PoolModeNoMeasure, PoolModeNoReparse (lastKey=DrivePoolService.Pool.Tasks.RemoveDriveFromPool, pool=337fd488-b54e-4d1d-9d07-83d99b3efbe5)
0:15:21.5: Warning: 0 : [RemoveDriveFromPool] Error moving file from \\?\Volume{3189d0fd-c9f8-4beb-82a5-1704f20ee1d2}\PoolPart.decd5540-d658-42b1-bacd-14e378edcc0e\- Media -\TV Shows\Episode2.mkv to \\?\GLOBALROOT\Device\HarddiskVolume31\- Media -\TV Shows\Episode1.mkv. Continuing removal. (A device which does not exist was specified)
0:15:21.5: Warning: 0 : [RemoveDriveFromPool] Error removing \\?\Volume{3189d0fd-c9f8-4beb-82a5-1704f20ee1d2}\PoolPart.decd5540-d658-42b1-bacd-14e378edcc0e\ from the pool. Removal canceled
0:15:21.5: Information: 0 : [FsControl] Set overall pool mode: PoolModeNoReportIncomplete, PoolModeNoMeasure, PoolModeNoReparse (lastKey=DrivePoolService.Pool.Tasks.RemoveDriveFromPool, pool=337fd488-b54e-4d1d-9d07-83d99b3efbe5)
0:15:21.5: Information: 0 : [FsControl] Set overall pool mode: PoolModeNoReportIncomplete, PoolModeNoReparse (lastKey=DrivePoolService.Pool.Tasks.RemoveDriveFromPool, pool=337fd488-b54e-4d1d-9d07-83d99b3efbe5)
0:15:21.5: Information: 0 : [FsControl] Set overall pool mode: PoolModeNoReportIncomplete (lastKey=DrivePoolService.Pool.Tasks.RemoveDriveFromPool, pool=337fd488-b54e-4d1d-9d07-83d99b3efbe5)

Any suggestions would be appreciated - Thank You!

Link to comment
Share on other sites

2 answers to this question

Recommended Posts

  • 0

Tricky this. Are some of the HDDs connected through USB?

What you could do, if you have some spare machine somewhere:

1. Disconnect the faulty drive
2. Connect to another machine, see if you can copy data from it. If you can, then at least the data is safe.
3. If you could, then you could remove the drive that DP will say is missing. Then the Pool would be alright again but miss data.
4. Copy/move from (2) to the Pool

This is what I would do if I really though DP measuring and moving files might put to much stress on the HDD. Not sure if this is recommended by Stablebit though.

Link to comment
Share on other sites

  • 0

I think this was already resolved, but .... just in case:
 

dpcmd ignore-poolpart X: decd5540-d658-42b1-bacd-14e378edcc0e

Change "X:" to be the drive letter for your pool.  The "decd5540-d658-42b1-bacd-14e378edcc0e" is the part in the "PoolPart" folder's name.   This will immediately eject the drive from the pool, without removing it's content from the pooled drive. 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...