eagleknight

I keep getting a daily warning on a SSD I put in my system. I thought it was related some scheduled tasks on my Plex server at night because I run my VM's off this disk. Upon closer examination I receive the warning and within a minute I receive a second message saying it returned to normal. When I go in the console I never see it above 90F. Even when I did some initial copies of 100GB's or so I never seen the temp rise. Is this some weird issue with this drive or is it normal. Doesn't seem like it is really overheating. This drive doesn't give a graph in the SMART area of the temp over time either. SanDisk SDSSDXP240G - 280.4˚F (Maximum: 158˚F)

If I am running Scanner on my host to monitor and scan all disks on the system, will it function properly if I have a number of disks set to "offline" to pass to a VM that is running Drivepool? Are there any downsides?

Checking to make sure I understand this... Say I have 5 disk pooled as P: and have duplication turned on for this pool. Then I create a new pool from P:. Would this new pool also be protected with duplication?

Thanks, that points me in the right directions.

I might be switching to Backblaze for my backup. The personal version doesn't give options for folders because they want to keep it simplistic. I don't want my whole DrivePool to backup to the cloud because some stuff I don't need to. Backblaze personal only allows selections of drive letters. I have around a 10TB pool and would like to keep all my drives in a single pool. I tried doing a subpool, but you can't create 2 subpools under the top pool or am I doing something wrong? I did get the option to create another pool from the subpool, but that doesn't seem right. The other option I could have my DrivePool P: and use the SUBST command to map ex. X: and Y: drives to two folders at the top level.

Thanks, actually I bought one with a Marvel 88SE9215. No issues so far.

I need 4 additional SATA ports on my new Z170 board with SMART support. No RAID. Is the Marvel 88SE9230 chipset a safe bet?

I agree with nauip. Only have Crashplan backup what is on your logical Drivepool. Backing up each pooled drive would be a nightmare to piece together as you found out and you are creating extra overhead.

Thank you. That took care of the issue for both.

I upgraded from 8.1 to Windows 10 a few days ago. I removed the license and uninstalled both scanner and drivepool before the upgrade. I then installed the latest betas for both. .3103 for scanner. When it ran through and checked all my disks again it unable to read 177 sectors on my WD Passport 2TB drive and 1 sector on a Seagate GoFlex 2TB drive. I tried marking sectors to scan again, but they keep coming back as unreadable. I also tried running a checkdsk /r and running a 1 pass wipe on all unused data and rechecking. I am in process now of running a scan from the WD utilities on the WD drive. Both drives were Healthy before the upgrade. What should I do from here.

I hope this may help other's if you have a tricky sector that doesn't want to be fixed. I had a Samsung 2TB drive give a warning of 1 current pending sector count. I ignored the error because when it would be written again it should be reallocated and the number wasn't going up. When the file scan ran on the drive it identified one bad block. This kicked off drivepool to start moving files off the drive, which I like that feature. So I first tried doing the repair through scanner and this said it completed, but the bad block still remained. Since drivepool wanted to keep data off this drive until it showed healthy again I wanted to get that sector reallocated. I removed it from the drivepool at this point. After searching I found that running chkdsk should find the sector and fix it. The first time I ran chkdsk I only ran it with the /r parameter. Then found I should have probably included the /f as well. After running each time I marked all blocks as unchecked and kicked off another scan and the block still came back damaged. Long process considering it takes 6+ hours on each of these attempts. After this didn't work I tried Seatools, but it kept giving me the error when I ran the fixes from the program it couldn't read the serial. Final fix was I formatted the disk and I downloaded Eraser. I ran the psedorandom 1 pass across the disk to force a write to each sector and this finally cleared that pending sector. I then ran another stablebit scan and it seemed to return a false positive marking a bad block still. This time I marked the bad block as unchecked and ran the scan again and it came back as the drive healthy. As a safe measure I marked the whole drive unchecked once more and ran a scan and it returned as healthy. I then added it back to the drivepool.

Have you ran any memory checks? Could try running the Windows memory diagonostic tool.

What antivirus are others using with Drivepool? I recently ran into some issues with Avast marking parts of drivepool install as malicious. Any feedback on other Antivirus?

I had to reinstall Windows 8.1 and Drivepool is back up and running, but I don't seem to have permissions to the files. I tried using the reset utility, but it said the OS was not supported.

Yes, yes, and yes. I thought though if you kicked it off manually it would scan. If it doesn't that is Ok, I just wasn;t aware. It did finish scanning overnight.