denywinarto

Sorry forgot to update, i managed to recover my data. and yes, drivepool had to be restarted. Painful (and expensive) lesson, but it taught me one thing, never ever create RDP shortcuts to your important servers

This morning my server was hacked and the hacker encrypt all of my drives with bitlocker. Now he gave me a password to unlock it and it was successful so i unlock all drives. But now on bottom right tray there's a multiple encrypting drive X... in progress.. There are over 180 TB of data. Now what i dont understand, drivepool still can't detect the drives. I am able to open the files on the unlocked drives though, do i have to wait until encryption process completed? what i dont understand is, isnt' it supposed to be decrypting instead of encrypting?

Thought i'd answer this here since my new server's been running stable for almost a month since the issue. The root of the issue was duplicated pool, as evidenced with whocrashed report showing drivepool's filesystem as one of the trigger. So the lesson is as i mentioned before, never try to create duplicated pool. I also learned that mounting hdd to folder is not really necessary if you use drivepool entirely, kinda makes new installation easier since we dont have to re-mount the drives

Specs : MSI Z390 Pro Intel i7 8700 32gb ram corsair HGST 4u60 LSI 9300 8i Intel i2Ti Last night there was a power surge, not sure what caused it, and it fried my nvme i think, it became undetected So i reinstalled a new nvme drive with server 2019. During installation it went just fine. But when i try to initialize drive, it freezes. And Got this BSOD screen saying Unexpected kernel mode trap What failed C1.dll The thing that bothers me is that it has been working fine for almost a year with server 2016. What i have tried 1. Full install all driver > resulting in spinning logo for 1 hour, so i just installed the audio and intel iris driver 2. Change the LSI 9300 8i, i happen to have a backup, but it's still the same thing, so its not sas card issue 3. Change the memory, 4. Remove the intel PCIE nic 5. Move the SAS card to another PCIE 6. Removing the cable plugged to the SAS card > this allows the windows to load correctly! But i cant access the jbod I was also wondering if corrupted drive or unfinished drivepool can cause this? Because on my very first attempt to reinstall, everything actually worked, but i installed an old drive with ntfs mounting in it. And drivepool created 2 pool, i was afraid it might mess my library, so i stopped DP service and i reinstall again, but now im stuck The only thing left is the motherboard and the rack... And i happen to not have any backup for them.. Been struggling for hours now, any idea? Edit : i swapped the mobo to lower end spec'ed and it seems to be stable now Now interestingly, at first i got 2 BSOD, during this time theres a duplicated pool that i mentioned earlier https://imgur.com/gallery/QPPOjcM But then after i turn off the drive from duplicated pool, delete poolpart, and it went back to 1 pool. It seems to be stable, no more crash until now, about 5 hours So its either the motherboard or incorrect drivepool pooling... Edit 2 : im gonna put this here, this is how i solved duplicated pool and how it was created : 1. Turn off the drive from the pool that i don't want 2. stop DP service 3. Turn on the drive from the pool that i don't want 4. delete poolpart.xxx from that drive 5. start DP service 6. Duplicated pool disappeared Also in my case, i had the old drive with previously NTFS mounted folders installed as secondary drive, cause i want to copy the old content (emby, radarr, sonarr, etc) while i want the drives to mount to the new NTFS mounted folders i created on the newly installed drive And this was a BAD idea, The initialized drive went straight mounted to the old drive, even after i delete the NTFS mounted folders to recycle bin. and this is how i got the pool initialization mixed up So lesson learned i guess, i will never use 2 drives if the older one has older NTFS mount folders

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

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..

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?

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.

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

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?

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?

Yeah i just figured it out myself, it didn't work even with registry imported, This might take some time if i fill up all 60 drives someday..

Can't seem to find any way to do this. My drives are mounted to 20ish ntfs mount folders, and now i want to migrate to another machine with better specs. The idea is just to swap the sas card and then i hope i dont have to remount the drives again because i want to minimize downtime. Is there anyway to copy these mount folders to the new machine? Or do i have to recreate and re-mount them again one by one? Cause when i tried to copy them, its actually copying the entire drive... Edit : Well i found out the registry location, HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\CPC\LOCALMOF\ So just export and import this key?

https://bitflock.com/2XXZBSTN Ah i thought bitflock was a part of scanner. The troubled drive was drive "K" Do you need the data for bad ssd as well?

Alright, fortunately i replaced it with exact same ssd.. will post it later.. Or.. do you need the bad ssd for this? If so then i might need to use the trial version.. Btw I currently have kingston and samsung (nvme & evo) ssd's on my servers, any if them still cant be read correctly by scanner? you want i could submit bitflock id for them..