denywinarto

It says volume is busy, should i force repair? "Forcing a repair will forcefully close any file open on the volume being repaired"

Yeah, ok, i will try that once scanning is done. It found another issue though, file system damaged, should i ignore this or should i remove and chkdsk?

Thanks, seems to work, but i found a scanner bug i think,

One of my drives is showing smart warning, and i'm gonna RMA it and now i'm buying a new drive, just wanna make sure this is correct procedure, 1. Insert new drive to rack 2. Add new drive to pool 3. Remove bad drive pool from DP 4. Remove bad drive from rack Is that it? did i miss anything?

So you're saying you use S for drivepool then your drives are in NTFS folders? This is what i meant, then i guess the best way to do this is to have drivepool mapped to Z drive, then the rest of the drives mounted in NTFS folders inside C:\DrivePool\?

Hmm something strange just happened, my server reboots (not sure why i think Teamviewer crashed it), before reboot Drivepool was using N letter after reboot Drivepool changes it drive letter to O, and the new drive is suddenly mounted to N. My shares were gone, so i had to reorder the drive letters Kinda makes me wonder whats the best way to use NTFS mount points + drivepool and prevent something like this? Or maybe at least can i lock drivepool's drive letter somehow?

Sorry i meant this just wondering if its safe to move it to drivepool or back it up in case my C is screwed

So i mount my new hdd with mount points, and i put it on C which is reserved for OS.. few questions.. 1. Can i move the mount point file to drivepool partition? 2. what if my C got corrupted? can i restore the mount point somehow?

desktop.ini is indeed a virus, other AV is reporting the same.. Earlier this morning some of the folders changed its permission again.. and the shortcut virus is back.. e.g : correct permission should be : Everyone, admin and client the infected folders have extra permission from system, authenticated users , and users not sure if its cause i forgot to fix the permssion on those folders, or something else chenged them, but i'm pretty sure i made the parent folder inherited the correct permissions It's not as much folders as the last time though.. hopefully it's just me forgetting to change the permssion, will monitor again..

Now i know whats probably causing it. See like i said I'm sharing it with local diskless clients, and some of those clients have personal data that is saved even after reboot. Now this personal data is probably infected with virus. So i test one of the infected folders from client side. And surprisingly, the client can create a text document inside that folder! But deleting the text file requires admin account and was halted immediately, and strangely after a while text file is gone.. I double check the security and it's definitely shared with a standard account, and it doesnt have write permission. I tested the other folder that's not infected and it refuses to write anything prompting "destination folder access denied" So the writable folder is causing security hole... is this related with drivepool somehow? Edit, attached is the permission difference between writable folder (veep) and read only folder (vinyl) It seems like there's extra users for the writable folders.. I could probably remove those users, but problem is some new folders also have this writable behavior.. Edit : i changed the whole pool permission inheritance and seems like the shortcut virus arent back.. yet

Ok i just scanned my drives with nod32 and found 300 viruses. But the next day it found them again, through the poolpart instead the normal path to the drives.. So i was wondering, could one of drivepool features actually bring back the viruses? i'm using balancing feature btw

Asking this cause i was hit by a 2010 shortcut virus... My server is shared for public usage to a number of clients so the source might be from infected thumbdrives.. but i cant understand how can it affects read-only smb shares.. does drivepool alter smb share security or is this a known win server 2012 r2 security hole? Hopefully its the later, I have followed a guude to clean it. But its still kinda worries me if it happens again.. anyone know a fix or patch?

Yeah can confirm it's safe. And i Finally figured out the cause... my new drive has shorter length than the older ones.. no wonder it didn't detect it cause it's not even plugged in! never new they had different size though.. i moved the caddy screw higher and now it's working

"You shouldn't" meaning it's not safe? yeah tried almost everything, tested yesterday without drives plugged in, turns out there's no zoning Card is made in chinese so i'm refunding it and getting the US one (albeit twice more expensive) Wanted to debug it further but im held back by windows' tool limitation..

Hi, i need to access my jbod under linux to check zoning possibility.. cause strangely my hgst 4u60 is limiting the drives to 11. Ive tried lsi 9300 8e and dell sc8000 and both cant detect 12th drive, a 8tb red wd. But i can move around drives in my jbod as long as its under 11. Unfortunately i cant find any equivalent alternative for smp_utils under windows. So im gonna have to boot up ubuntu and access the jbod rack.. question is, is this safe for drivepool once i get back to windows? Cause if i recall i had permission issues when going back and forth with ubuntu and windows.. cant risk my data for this. Thanks