Jump to content
Covecube Inc.

denywinarto

Members
  • Content Count

    77
  • Joined

  • Last visited

Posts posted by denywinarto


  1. 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 :(


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


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


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

     

     

     


  5. 3 hours ago, Christopher (Drashna) said:

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


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


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

     


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


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


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


  11. This afternoon i checked a particular disk and it says no smart error, however tonight it shows mechanical disk warning, but later about an hour its back to no error state, whats causing the inconsistency? The report is crucial for me because its a pxe server..

    Edit :

    And oddly i didnt get a single email notification about this, i already checked all options in notification tab, just tested the email notification and it works fine...


  12. Well thank goodness it finally works, 

    at first i did it without checking the 3 options, then it threw error that some files are being used,

    So i check the third option as recommended,thanks for the quick help chris 

     

    Bonus question if you dont mind chris, my new drive suddenly has a D letter, and removing the letter gives me

    "assigning or removing drive letters on the current boot or pagefile volume is not allowed" any idea?

     

    Hmm i tried removing the paging file size from that drive but i still cant remove it..

     

     


  13. 23 minutes ago, Christopher (Drashna) said:

    It may be worth getting a crash dump here.

    http://wiki.covecube.com/StableBit_DrivePool_System_Crashes

    Also, it may be worth upgrading to the latest beta, and see if that helps:
    http://dl.covecube.com/DrivePoolWindows/beta/download/StableBit.DrivePool_2.2.3.950_x64_BETA.exe

    Ok looks like my server is already setup that way,

    I've sent the dump log, Please have a look.

    I've installed the newest beta as well, let me try again now..


  14. Removing a pool apparently causes my server to reboots, thus i have to repeat the removal process..

    I'm positive cause it happens third time already,

    I have checked all 3 options on remove menu, but it still reboots my PC, so what should i do?

    I also tried searching and deleting files inside the pool but it wont help, the drive currently looks like this, this is after the reboot

    photo_2018-12-11_08-14-26.jpg

    I have also unmark the both options in drive usage limiter plugin after i post this but i havent tried removing again


  15. 2 hours ago, Christopher (Drashna) said:

    You want RAID0/10 then.  StableBit DrivePool isn't going to get you much better performance than the underlying drives. 

    As for PXE, using an SSD for this may be a good idea too.

     

    Also, if you're using Windows Server, you MUST check out Windows Deployment Services.  It's the built in PXE server for Windows, and is designed to install Windows over PXE.  But you can also load in any WinPE image (such as the client restore disk for Essentials), or any "tools" that use WinPE. 
    The advantage here is that WDS deduplicates the data, so you can fit a LOT of images into a relatively small amount of disk space.

    Additionally, there is/was WDSLinux that lets you boot a linux boot image over WDS (but only for BIOS, not UEFI, the last time I checked).

    Also... this is mostly me being a nerd and totally geeking out... but I used all of the above to actually boot windows from iSCSI over PXE.   It wasn't fast, but it worked! 

     

    Also, all that playing that I did is why I recommend a SSD for this. It may be simpler and work just as well, if not better than a RAID array. Especially, if it's an NVMe SSD.

     

    Thanks for the explanation chris,

    I'm already using ccboot for pxe booting.. 

    Too bad, i read somewhere smart parameters cant be read from stripped drives, is it true?

    As for ssd, i wanted to but well.. 12 tb of ssd would cost about four times of the 3 wd black that i told you :(

    Maybe next year when sdd prices go down i will replace them with ssd..


  16. I'm building a pxe server where IOPS and read performance is crucial, 

    and i was wondering, how is drivepool's performance options compared to raid 0?

    And which one gives the best result for read-intensive purpose?

     

    My plan is to raid 0  3x 4tb black WD,

    I'm also gonna synchronize them with my main server using syncovery for a periodical backup,

    and the files on this pxe server doesnt get updated very often..

    Thats why i choose raid 0.

     

    I'm leaning towards raid 0 for performance,

    but its non-expandability (have to backup and copy again) and DP scanners' ability interests me..t.


  17. On 7/15/2018 at 2:09 AM, Christopher (Drashna) said:

    Well, The file system repair can/will lock the volume until the repair is finished.  So that may be what you're seeing. 

    But more likely is that the errors on the disk are what is causing the issue here. 

    If you stop the StableBit Scanner service, that should be telling.  If the issue persists, then it's not StableBit Scanner.  But if it goes away, then let us know. 

    It's definitely the scanner cause the moment i uninstalled it the problem was gone.

    Is  there anyway to force file system repair during next boot? I don't see it on the options.

    I have to ignore this for now until the next reboot

     

×
×
  • Create New...