Chip

That probably wouldn't help. I'm often not physically at the server when I do a reboot, and it could be anywhere from 5 minutes to a couple hours before I get around to checking the pool and reseating the drive if necessary. But just for reference, I rebooted the server 4.5hrs ago for a windows security update, and it's only at 73% on the check process. It's quite time consuming when you have a large collection of disks, and performance suffers significantly until it's complete.

Is there any way to disable this measuring process, or at least make it optional? I have one drive that is a bit slow on the uptake, and half the time it's "missing" after a reboot. Simply pulling the tray and re-inserting it fixes the issue 100% of the time - I don't know if it's the drive, the tray, or the backplane. Scanner shows no issues with the drive, and I'm happy to simply pull and reinsert the tray once or twice a month when it happens. What I'm less content with is the 4+ hours worth of measuring and checking that drivepool goes through every time this happens. I have 34 disks adding up to over 140TB in one big pool, and remeasuring all of that every other reboot just plain isn't necessary. It's one thing if the server crashed or restarted for unknown reasons, but if the reboot was just for regularly scheduled updates, then the measuring process is just unnecessarily slowing things down substantially for hours on end - not to mention putting unnecessary wear on every drive in the system. Could you add an option to disable automatic remeasuring, or at least throw a dialog window when a missing disk comes back online to ask whether a remeasure should be performed?

I realize this is an older thread, but its age is part of the reason I'm posting. I'm considering a move from unraid to drivepool + snapraid, and I'm cruious if anybody has suffered a drive failure and how the recovery procedure went. In theory, drivepool shouldn't care that it's a physically different drive as long as the contents are identical, but I'm curious if it works that well in practice. Are there any special steps needed, or do you fire up the pool after the rebuild and it "just works"? How long does the rebuild process take? I'm also curious how flexraid handles disk writes during it's snapshot process, but that's probably more of a question for the snapraid people.