no wagering :) On 5/8/15 1:17 PM, Clug wrote: > You wanna bet? (; my experience with this specific array is that it's > usually dead-on. I think it'll be a bit over 24 hours (which is where > it seems to settle). > > Honestly as long as it takes less than the 30 days I have to return > the bad drive for the RMA I'm fine (: > > On Fri, 8 May 2015, Linda Kateley wrote: > >> It looks like it does have some of the delay code in.. >> >> In freebsd the way it works is that it calculates the time, with the >> 5ms delay in-between each io. As time goes by and there is no other >> io activity, it recalculates. It will probably be apx 1/5 of the >> projected time.. or apx 6 hours. >> >> linda >> >> On 5/8/15 12:47 PM, Clug wrote: >>> On Fri, 8 May 2015, Linda Kateley wrote: >>> >>> >>>> Yea, it depends on how much data it needs to read to rebuild. If >>>> it's empty probably a couple seconds, if it is a 11+1 full 4TB >>>> drives maybe several days.. >>> >>> Uuugh. I just started it and it said it'll take 345 hours. >>> >>> But it just revised it's ETA to about 28 hours, but now it's back up >>> to 40. Either way I don't think it'll take half a month (: >>> >>> By the way, I was able to use the disk-by-id for both old and new >>> devices, so I basically went: >>> >>> # zpool offline media ata-WDC_WD30EFRX-68AX9N0_WD-WMC1T2656431 >>> # zpool replace media ata-WDC_WD30EFRX-68AX9N0_WD-WMC1T2656431 >>> ata-WDC_WD30EFRX-68EUZN0_WD-WMC4N3F9Y7P5 >>> >>> Then I fixed the partition table on the new drive and ran that again (; >>> >>> -- >>> _______________________________________________ >>> TCLUG Mailing List - Minneapolis/St. Paul, Minnesota >>> tclug-list at mn-linux.org >>> http://mailman.mn-linux.org/mailman/listinfo/tclug-list >> >> > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > tclug-list at mn-linux.org > http://mailman.mn-linux.org/mailman/listinfo/tclug-list -- Linda Kateley Kateley Company Skype ID-kateleyco http://kateleyco.com