denywinarto Posted February 14, 2019 Posted February 14, 2019 I swapped to new machine and OS yesterday morning, from Windows 2012 r2 to 2016 New CPU, boards, Installed OS from scratch and I also changed the SAS card to faster one, And i just reactivated scanner today, But now it's saying all drives have system damaged issue. Windows also warning me multiple times, throwing "restart to repair drive error" I didnt turn off the JBOD when swapping machine though, But drivepool seems to be fine, when i try to repair one of the drives with scanner, it says" task failed, shutting down" or something like that What should i do then? Quote
0 denywinarto Posted February 16, 2019 Author Posted February 16, 2019 Well i scanned 6 of my drives, 2 worked, it seems to chkdsk during startup, but the others just wont work, throwing "task failed, shutting down" (I'm doing this partially everyday cause i want to minimize downtime) those 2 drives seems to be normal again on scanner. but what about the other drives? Quote
0 Christopher (Drashna) Posted February 18, 2019 Posted February 18, 2019 What controller card are you using now? Also, is this for the surface scan? If so, try running the burst test on the drives in question. If that comes back with errors, there are communication issues with the drive, and not actually damaged sectors (but it ends up with the same result). And do these errors happen when manually running CHKDSK? Quote
0 denywinarto Posted February 18, 2019 Author Posted February 18, 2019 2 hours ago, Christopher (Drashna) said: What controller card are you using now? Also, is this for the surface scan? If so, try running the burst test on the drives in question. If that comes back with errors, there are communication issues with the drive, and not actually damaged sectors (but it ends up with the same result). And do these errors happen when manually running CHKDSK? LSI SAS 9300 8e I havent even started any scans, it just popped up after starting the scanner. Havent had another chance to run chkdsk again, but last time there were 2 drives that also reports the same error using CHKDSK, and they were fixed already. But the rest of the drives is giving " task failed, shutting down" when i try to fix them using scanner Edit : Hmm a minute, i'm running the drive repair one by one to the damaged drives again.and this is what i got : So out of 14 damaged drives, 1 showing will be repaired on next shutdown 6 failed to repair, throwing task failed, shutting down 6 can be repaired successfully 1 showing : the volume cannot be repaired, there was no additional information provided as to why, you may run chkdsk from the command line to try to repair this volume Another thing i noticed chris, the poolpart on each drives is no longer on hidden state, IIRC werent they supposed to be hidden? i will try running chkdsk tomorrow morning Quote
0 Christopher (Drashna) Posted February 20, 2019 Posted February 20, 2019 They should be hidden, yes. but that's not mandatory. We do that to protect users ... well, from themselves. If you removed the disk from the pool, they won't be hidden, either. Though, if there is an issue with the file system, then it could cause this. Quote
0 denywinarto Posted February 20, 2019 Author Posted February 20, 2019 Ok, some good news, i just tried again, out of remaining 7 damaged drives, 1 can be repaired, 2 can be repaired after reboot, but 4 are still giving task failed shutting down error. i have submitted the service.zip on dropbox chris, please have a look. Quote
0 Christopher (Drashna) Posted February 27, 2019 Posted February 27, 2019 Okay, flagged for Alex: https://stablebit.com/Admin/IssueAnalysis/28064 Quote
0 denywinarto Posted March 3, 2019 Author Posted March 3, 2019 Thanks chris, I now have 2 drives left that ive been trying to fix for the past few days. But they both always throw "task failed, shutting down" no matter what i do... Any idea how to fix this? Quote
0 Christopher (Drashna) Posted March 10, 2019 Posted March 10, 2019 Just to make sure, are you on the latest beta? http://dl.covecube.com/ScannerWindows/beta/download/StableBit.Scanner_2.5.4.3220_BETA.exe Quote
0 denywinarto Posted March 10, 2019 Author Posted March 10, 2019 3 hours ago, Christopher (Drashna) said: Just to make sure, are you on the latest beta? http://dl.covecube.com/ScannerWindows/beta/download/StableBit.Scanner_2.5.4.3220_BETA.exe Ok it was not up to date yet, I installed that version and ran the scan on damaged drive again, but its still throwing rhe same error, "task failed, shutting down" Already sent the service.zip again for this version chris, please check it.. Quote
0 denywinarto Posted March 22, 2019 Author Posted March 22, 2019 Good news chris, apparently after completing full scan on the troubled drive, the damaged status is gone, so it's probably some kind of bug or something when switching OS.. or sas card Quote
Question
denywinarto
I swapped to new machine and OS yesterday morning,
from Windows 2012 r2 to 2016
New CPU, boards, Installed OS from scratch
and I also changed the SAS card to faster one,
And i just reactivated scanner today,
But now it's saying all drives have system damaged issue.
Windows also warning me multiple times, throwing "restart to repair drive error"
I didnt turn off the JBOD when swapping machine though,
But drivepool seems to be fine, when i try to repair one of the drives with scanner,
it says" task failed, shutting down" or something like that
What should i do then?
11 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.